[Touch-packages] [Bug 1814072] Re: software-properties-gtk does not recognize https mirrors under Ubuntu Software

2019-02-01 Thread Bryan Quigley
it also does not recognize lines like this:
deb mirror+https://bryanquigley.com/mirrors.txt disco main restricted universe 
multiverse

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

Title:
  software-properties-gtk does not recognize https mirrors under Ubuntu
  Software

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  1. Change main Ubuntu mirrors to https in /etc/apt/sources.list and do "apt 
update"
  2. Run software-properties-gtk
  3. Go to "Ubuntu Software" tab

  What happens:

  The tab "Ubuntu Software" does not list https mirrors. The
  corresponding boxes are not checked, the correct "Download from" entry
  is not selected and falls back to "Main server". The correct sources
  are just listed under "Other Software".

  What should happen:

  The tab "Ubuntu Software" should recognize the https mirrors from apt
  and tick the corresponding boxes and select the correct server in the
  "Download from" list.

  Ubuntu 18.04
  software-properties-gtk 0.96.24.32.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1814072/+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 1814072] Re: software-properties-gtk does not recognize https mirrors under Ubuntu Software

2019-02-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  software-properties-gtk does not recognize https mirrors under Ubuntu
  Software

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  1. Change main Ubuntu mirrors to https in /etc/apt/sources.list and do "apt 
update"
  2. Run software-properties-gtk
  3. Go to "Ubuntu Software" tab

  What happens:

  The tab "Ubuntu Software" does not list https mirrors. The
  corresponding boxes are not checked, the correct "Download from" entry
  is not selected and falls back to "Main server". The correct sources
  are just listed under "Other Software".

  What should happen:

  The tab "Ubuntu Software" should recognize the https mirrors from apt
  and tick the corresponding boxes and select the correct server in the
  "Download from" list.

  Ubuntu 18.04
  software-properties-gtk 0.96.24.32.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1814072/+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 1010722] Re: /usr/bin/canberra-gtk-play --id="desktop-login" --description="GNOME Login" Failed to play sound: File or data not found

2019-02-01 Thread Launchpad Bug Tracker
[Expired for libcanberra (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  /usr/bin/canberra-gtk-play --id="desktop-login" --description="GNOME
  Login" Failed to play sound: File or data not found

Status in libcanberra package in Ubuntu:
  Expired

Bug description:
  No StartUp Sound.
  Command -  /usr/bin/canberra-gtk-play --id="desktop-login" 
--description="GNOME Login" 
  Gives error - Failed to play sound: File or data not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1010722/+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 1794476] Re: curl-config uses krb5-config, but libcurl4-openssl-dev only Suggests libkrb5-dev

2019-02-01 Thread Launchpad Bug Tracker
[Expired for curl (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  curl-config uses krb5-config, but libcurl4-openssl-dev only Suggests
  libkrb5-dev

Status in curl package in Ubuntu:
  Expired

Bug description:
  Attempt to run curl-config on the system, on which libkrb5-dev is not
  installed, results in error

 /usr/bin/curl-config: krb5-config: not found

  At the same time, libcurl4-openssl-dev only Suggests libkrb5-dev.

  Either curl-config should gracefully handle lack of krb5-config, or
  the dependency should be stronger.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcurl4-openssl-dev 7.58.0-2ubuntu3.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18
  Uname: Linux 4.15.0-33-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Sep 26 11:25:10 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-18 (2046 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  SourcePackage: curl
  UpgradeStatus: Upgraded to bionic on 2018-04-11 (168 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1794476/+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 1783157] Re: package ntp 1:4.2.8p10+dfsg-5ubuntu7.1 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1

2019-02-01 Thread Launchpad Bug Tracker
[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package ntp 1:4.2.8p10+dfsg-5ubuntu7.1 failed to install/upgrade:
  installed ntp package post-installation script subprocess returned
  error exit status 1

Status in ntp package in Ubuntu:
  Expired

Bug description:
  I also had the bug on grub-efi-amd64-signed
   https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518

  Perhaps there is a link between both.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Jul 23 17:43:41 2018
  DpkgTerminalLog:
   Paramétrage de ntp (1:4.2.8p10+dfsg-5ubuntu7.1) ...
   Le groupe « ntp » existe déjà, sans être un groupe système. Fin de la 
procédure.
   dpkg: erreur de traitement du paquet ntp (--configure) :
installed ntp package post-installation script subprocess returned error 
exit status 1
  ErrorMessage: installed ntp package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-05-28 (56 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=dd8086cc-9a2b-4430-b205-55feaeb96308 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  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.3
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p10+dfsg-5ubuntu7.1 failed to install/upgrade: 
installed ntp package post-installation script subprocess 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/ntp/+bug/1783157/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]

2019-02-01 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  No sound card detected by PulseAudio and ALSA, but is visible in lspci
  [Dell XPS 13 9360]

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
  the troubleshooting steps here:

  https://help.ubuntu.com/community/SoundTroubleshooting

  and have included some output of those diagnostic steps below:

  
  $ sudo aplay -l
  aplay: device_list:270: no soundcards found...

  $ find /lib/modules/`uname -r` | grep snd
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
  ...and lots more

  $ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 131
Memory at dc228000 (64-bit, non-prefetchable) [size=16K]
Memory at dc20 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  Sound settings still only list dummy output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 18:44:06 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 01KT0M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1003076] Re: Apport "Other Problem" option needs expanded functionality

2019-02-01 Thread Logan Rosen
*** This bug is a duplicate of bug 585454 ***
https://bugs.launchpad.net/bugs/585454

** This bug has been marked a duplicate of bug 585454
   Bad behavior when no PID/program is specified.

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

Title:
  Apport "Other Problem" option needs expanded functionality

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When you slecet the "Other Problem"  from the kind of problem you want
  to report list you recieve a dialog that says

   "You need to specify a package or a PID. See --help for more
  information"

  Here's the problem: 
  1) "ubuntubug -- help" doesn't explain how to get the process ID (PID)
  2)  It makes you think there should be a 'Help' button on the 'No Package 
Selected' dialog
  3)  

  
  Some solutions:
  1)  The main Apport window should implement the --WIndow option which would 
allow the user to click on click on any open window to report a bug on that 
application
  2)   The main Apport window could display the same list of Processes and IDs 
that the System Monitor window displays - thereby allowing the user to select 
the appropriate process from the simply by clicking on the Process Name in the 
window. (see attached image)
  3)   It would be totally awesome if when you could right click on the Process 
Name in the System Monitor window and get a pop-up menu detailing the proces' 
properties - that there could be a menu option there called "Report A Bug" that 
launched apport

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: apport-gtk 2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.4.0-3.7-generic 3.4.0
  Uname: Linux 3.4.0-3-generic x86_64
  ApportVersion: 2.1-0ubuntu1
  Architecture: amd64
  Date: Tue May 22 11:46:36 2012
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120522)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1003076/+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 1392034] Re: The "Other problem" radio item is completely useless

2019-02-01 Thread Logan Rosen
*** This bug is a duplicate of bug 585454 ***
https://bugs.launchpad.net/bugs/585454

** Package changed: reportbug (Ubuntu) => apport (Ubuntu)

** This bug has been marked a duplicate of bug 585454
   Bad behavior when no PID/program is specified.

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

Title:
  The "Other problem" radio item is completely useless

Status in apport package in Ubuntu:
  New

Bug description:
  After selecting the "other problem" radio button, one gets a message
  like this

  "You need to specify a package or a PID. See --help for more
  information."

  No point in having the radio button if that's all it's going to say!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: reportbug (not installed)
  Uname: Linux 3.17.0-ur44 x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 12 11:46:49 2014
  SourcePackage: reportbug
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1392034/+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 1392034] [NEW] The "Other problem" radio item is completely useless

2019-02-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After selecting the "other problem" radio button, one gets a message
like this

"You need to specify a package or a PID. See --help for more
information."

No point in having the radio button if that's all it's going to say!

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: reportbug (not installed)
Uname: Linux 3.17.0-ur44 x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Nov 12 11:46:49 2014
SourcePackage: reportbug
UpgradeStatus: Upgraded to utopic on 2014-10-25 (18 days ago)

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


** Tags: amd64 apport-bug utopic
-- 
The "Other problem" radio item is completely useless
https://bugs.launchpad.net/bugs/1392034
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apport 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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

2019-02-01 Thread zwigno
I also see the IPv6 requests when a USB device is plugged in.  In this
case it is a Z-Wave device.  I don't have any cannon stuff.  I'm running
18.04.1 LTS.

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1770706] Re: openvswitch with ifupdown after reboot

2019-02-01 Thread Marcos Felipe Schwarz
** Package changed: systemd (Ubuntu) => openvswitch (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/1770706

Title:
  openvswitch with ifupdown after reboot

Status in openvswitch package in Ubuntu:
  Confirmed

Bug description:
  Recently I needed to install OVS on fresh ubuntu 18.04.

  1). # lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2). # apt-cache policy openvswitch-switch
  openvswitch-switch:
Installed: 2.9.0-0ubuntu1
Candidate: 2.9.0-0ubuntu1
Version table:
   *** 2.9.0-0ubuntu1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3). OVS configured after reboot.

  4). OVS was not configured after reboot.

  
  After this actions:

  - remove netplan.io
  - install ifupdown
  - install openvswitch-switch
  - add verified ovs related statements to /etc/network/interfaces
  - reboot

  
  I got this in journal:

  мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1328]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
  мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1368]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
  мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1392]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
  мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1424]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
  мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: networking.service: Failed 
with result 'exit-code'.
  мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: Failed to start Raise 
network interfaces.
  мая 11 16:28:42 host2.lab.atlantis.ru ovs-vsctl[2041]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
  мая 11 16:28:43 host2.lab.atlantis.ru ovs-vsctl[2091]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
  мая 11 16:28:43 host2.lab.atlantis.ru ovs-vsctl[2137]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
  мая 11 16:28:43 host2.lab.atlantis.ru systemd[1]: networking.service: Failed 
with result 'exit-code'.
  мая 11 16:28:43 host2.lab.atlantis.ru systemd[1]: Failed to start Raise 
network interfaces.
  мая 11 16:30:05 host2.lab.atlantis.ru ovs-vsctl[2243]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
  мая 11 16:30:06 host2.lab.atlantis.ru ovs-vsctl[2293]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
  мая 11 16:30:07 host2.lab.atlantis.ru ovs-vsctl[2339]: 
ovs|2|db_ctl_base|ERR|no bridge named br0
  мая 11 16:30:07 host2.lab.atlantis.ru systemd[1]: networking.service: Failed 
with result 'exit-code'.
  мая 11 16:30:07 host2.lab.atlantis.ru systemd[1]: Failed to start Raise 
network interfaces.


  Problem was fixed after the following changes to unit files:

  # diff /lib/systemd/system/ovsdb-server.service 
/etc/systemd/system/ovsdb-server.service 
  4c4
  < Before=network.target network.service
  ---
  > Before=network.target networking.service

  
  # diff /lib/systemd/system/ovs-vswitchd.service 
/etc/systemd/system/ovs-vswitchd.service 
  4c4
  < Before=network.target network.service
  ---
  > Before=network.target networking.service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1770706/+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 1813390] Re: package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 I cannot upgrade my 14.04

2019-02-01 Thread Steve Beattie
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1 I cannot upgrade my 14.04 version to 16.04

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Cannot upgrade 14.04 version to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.103ubuntu4.11
  ProcVersionSignature: Ubuntu 3.13.0-151.201-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-151-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Sat Jan 26 12:32:59 2019
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2016-03-28 (1033 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.19
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: Upgraded to xenial on 2019-01-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1813390/+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 311029] Re: curl and pycurl is not compiled with sftp support

2019-02-01 Thread Launchpad Bug Tracker
This bug was fixed in the package curl - 7.63.0-1ubuntu1

---
curl (7.63.0-1ubuntu1) disco; urgency=medium

  * debian/control, debian/rules:
- build with libssh instead of libssh2, that's a better maintained
  library and it's in Ubuntu main (lp: #311029)

 -- Sebastien Bacher   Thu, 31 Jan 2019 15:29:39
+0100

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

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

Title:
  curl and pycurl is not compiled with sftp support

Status in curl package in Ubuntu:
  Fix Released
Status in curl package in Debian:
  Fix Released

Bug description:
  Binary package hint: curl

  Running curl --version, I see:
  Protocols: tftp ftp telnet dict ldap ldaps http file https ftps
  SFTP is obviously missing, although it is supported by curl upstream
  The SFTP is also missing from python-pycurl, probably because libcurl doesn't 
have it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/311029/+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 550332] Re: [AV200 - Xonar DX] Playback problem - Volume control is very laggy

2019-02-01 Thread Flávio Martins
I no longer have this sound card to evaluate.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [AV200 - Xonar DX] Playback problem - Volume control is very laggy

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  When i change volume the audio stops and takes 5+ seconds to come back.
  Indicator-sound crashes because of it.

  I get a message about "waiting for sound system" but sometimes
  eventually the volume changes.

  It feels as if there is no DMA with the sound card. Hope you
  understand what i mean.

  Tryed the snapshots on the audio ppa: didn't fix

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-17-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfe9fc000 irq 17'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'DX'/'Asus Virtuoso 100 (rev 2) at 0xe800, irq 16'
 Mixer name : 'AV200'
 Components : 'CS4398 CS4362A CS5361 AV200'
 Controls  : 16
 Simple ctrls  : 9
  Card2.Amixer.info:
   Card hw:2 'CinemaTM'/'Microsoft Microsoft® LifeCam Cinema(TM) at 
usb-:00:1d.7-4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB045e:075d'
 Controls  : 2
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 56
 Mono: Capture 0 [0%] [0.00dB] [on]
  Date: Sun Mar 28 16:58:19 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 1 DX AV200 - Xonar DX
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [AV200 - Xonar DX] Playback problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/550332/+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 1798597] Re: Backport packages for 18.04.2 HWE stack

2019-02-01 Thread Timo Aaltonen
kisak: yes, see bug 1811225

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-7 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in wayland source package in Bionic:
  Fix Released
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Released
Status in xorg-hwe-18.04 source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new major release, but since it's renamed there's no real
  chance of regression when it hits the archive

  xorg drivers: same as xserver

  
  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1798597] Re: Backport packages for 18.04.2 HWE stack

2019-02-01 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-intel-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel-
hwe-18.04/2:2.99.917+git20171229-1ubuntu1~18.04.1 in a few hours, and
then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-7 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in wayland source package in Bionic:
  Fix Released
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Released
Status in xorg-hwe-18.04 source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  

[Touch-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack

2019-02-01 Thread kisak
Good day, just wondering if mesa 18.2.8 was still in the plan?

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in xf86-input-wacom-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-7 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in wayland source package in Bionic:
  Fix Released
Status in xf86-input-wacom-hwe-18.04 source package in Bionic:
  Fix Released
Status in xorg-hwe-18.04 source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.2 images.

  
  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  
  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-7: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  18.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new major release, but since it's renamed there's no real
  chance of regression when it hits the archive

  xorg drivers: same as xserver

  
  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty

2019-02-01 Thread Richard Eames
I filmed my computer boot up to better show what happens. The right
monitor is on the integrated video card (the R7), and doesn't show
anything initially. The center and left monitor turn on and mirror each
other during boot, and show grub and most of the kernel and systemd
messages, then at some point all output is sent to the right monitor. I
believe the systemd log says something along the lines of "detecting all
video cards" at that point.

** Attachment added: "Computerbootup.webm"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235238/+files/Computerbootup.webm

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

Title:
  Monitors on second GPU not working after upgrade to zesty

Status in Light Display Manager:
  New
Status in xserver-xorg-driver-radeonhd:
  Invalid
Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm not 100% sure this is the right package to file the bug against,
  but since upgrading to zesty the two monitors on my second GPU are no
  longer detected once I reach the greeter screen at login time.
  However, both of them display information during boot.

  Let me know how I can narrow down the bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 22 01:42:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-29 (388 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .

2019-02-01 Thread Chris Rainey
[SOLVED]

Just needed to:

$ sudo apt install gstreamer1.0-plugins-bad


I'm not sure why this isn't included in the restricted-extras or libdvd-pkg 
depends?

** Summary changed:

- DVD playback error:  unable to play . . . DVD source is required . . .
+ [SOLVED]  DVD playback error:  unable to play . . . DVD source is required . 
. .

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Invalid

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

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

Title:
  [SOLVED]  DVD playback error:  unable to play . . . DVD source is
  required . . .

Status in gstreamer1.0 package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  Successful installation of libdvd-pkg and dpkg-reconfigure,
  afterwards, to complete compilation.

  Inserted known-good DVD and clicked on "Open in Videos" which launched
  the Totem player.

  Error msg:  "Unable to play the file, DVD source is required, but is
  not installed."

  DVD will play normally in VLC player after installation on same
  machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.4-1
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 15:21:45 2018
  InstallationDate: Installed on 2018-11-13 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+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 1814342] [NEW] fc-match does not return the correct font

2019-02-01 Thread Ron Koerner
Public bug reported:

On Ubuntu 18.10 the command `fc-match monospace:bold` returns

DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"

instead of

DejaVuSansMono-Bold.ttf: "DejaVu Sans Mono" "Bold"

This works correctly on Ubuntu 18.04.1 which is using fontconfig 2.12.6, 
whereas 18.10 uses 2.13.0.
I compiled 2.13.1 from source and just installed libfontconfig.so.1.12.0.

This solves the problem.

While it does not sound much, this bug also causes Java 8 AWT/Swing font
rendering to be uglier than it has to be. Instead of "DejaVu Sans Mono
Bold" and emboldened version of "DejaVu Sans Mono" is used which has a
different size, which goes counter to the notion of a "monospace" font.

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

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

Title:
  fc-match does not return the correct font

Status in fontconfig package in Ubuntu:
  New

Bug description:
  On Ubuntu 18.10 the command `fc-match monospace:bold` returns

  DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"

  instead of

  DejaVuSansMono-Bold.ttf: "DejaVu Sans Mono" "Bold"

  This works correctly on Ubuntu 18.04.1 which is using fontconfig 2.12.6, 
whereas 18.10 uses 2.13.0.
  I compiled 2.13.1 from source and just installed libfontconfig.so.1.12.0.

  This solves the problem.

  While it does not sound much, this bug also causes Java 8 AWT/Swing
  font rendering to be uglier than it has to be. Instead of "DejaVu Sans
  Mono Bold" and emboldened version of "DejaVu Sans Mono" is used which
  has a different size, which goes counter to the notion of a
  "monospace" font.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1814342/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty

2019-02-01 Thread Richard Eames
** Attachment added: "dmesg log"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235234/+files/dmesg.log

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

Title:
  Monitors on second GPU not working after upgrade to zesty

Status in Light Display Manager:
  New
Status in xserver-xorg-driver-radeonhd:
  Invalid
Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm not 100% sure this is the right package to file the bug against,
  but since upgrading to zesty the two monitors on my second GPU are no
  longer detected once I reach the greeter screen at login time.
  However, both of them display information during boot.

  Let me know how I can narrow down the bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 22 01:42:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-29 (388 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1811248] Re: systemd--networkd mounts denied for lxc guest

2019-02-01 Thread km
*** This bug is a duplicate of bug 1813622 ***
https://bugs.launchpad.net/bugs/1813622

** This bug has been marked a duplicate of bug 1813622
   systemd-resolved, systemd-networkd and others fail to start in lxc container 
with v240 systemd

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

Title:
  systemd--networkd mounts denied for lxc guest

Status in apparmor package in Ubuntu:
  New

Bug description:
  Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7
  Guest Arch Linux | systemd 240.0

  After having upgraded in the guest systemd from 239.370 to 240.0 the
  host's AA is exhibiting

  > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED"
  operation="mount" info="failed flags match" error=-13 profile="lxc-
  container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw,
  rslave"

  and the guest

  > systemd-networkd.service: Failed to set up mount namespacing: Permission 
denied
  > systemd-networkd.service: Failed at step NAMESPACE spawning 
/usr/lib/systemd/systemd-networkd: Permission denied

  According to lxc bug tracker https://github.com/lxc/lxc/issues/2778

  > While we'd like to allow such mounts we cannot do so until the
  apparmor_parser is fixed to handle them correctly.

  other cross references

  https://github.com/systemd/systemd/issues/11371
  https://bugs.archlinux.org/task/61313

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty

2019-02-01 Thread Richard Eames
I've come across this again after upgrading to 18.10

$ xrandr --listproviders  
Providers: number : 1
Provider 0: id: 0x56 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3 
associated providers: 0 name:KAVERI @ pci::00:01.0

$ sudo lspci -nn | grep -E 'VGA|Display'
[sudo] password for richard: 
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:1313]
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] RV770 [Radeon HD 4850] [1002:9442]

Only the built-in Radeon R7 is being used

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

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

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

Title:
  Monitors on second GPU not working after upgrade to zesty

Status in Light Display Manager:
  New
Status in xserver-xorg-driver-radeonhd:
  Invalid
Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm not 100% sure this is the right package to file the bug against,
  but since upgrading to zesty the two monitors on my second GPU are no
  longer detected once I reach the greeter screen at login time.
  However, both of them display information during boot.

  Let me know how I can narrow down the bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 22 01:42:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-29 (388 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-02-01 Thread Jon Wedaman
Just noticed what might be a regression from this fix.
`/usr/local/sbin:/usr/local/bin` are now missing from unit on newest
ubuntu bionic ami (us-east-1: ami-012fd5eb46f56731f)

ubuntu@ubuntu:~$ dpkg-query -W systemd
systemd 237-3ubuntu10.11
ubuntu@ubuntu:~$ sudo systemd-run /usr/bin/env
Running as unit: run-r6c6668bf9774455dbb628d2d79de5949.service
ubuntu@ubuntu:~$ journalctl -e | grep PATH=
Feb 01 20:46:24 ubuntu env[6051]: PATH=/sbin:/usr/sbin:/bin:/usr/bin:/snap/bin

The prior ami (us-east-1: ami-0b86cfbff176b7d3a) doesn't have this
issue. So I checked for differences. I noticed that if I remove
`/usr/lib/systemd/system-environment-generators/snapd-env-generator` and
reboot then I get better output:

ubuntu@ubuntu:~$ sudo systemd-run /usr/bin/env
Running as unit: run-r6c6668bf9774455dbb628d2d79de5949.service
ubuntu@ubuntu:~$ journalctl -e | grep PATH=
Feb 01 20:51:44 ubuntu env[3337]: 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed
Status in snapd source package in Cosmic:
  Confirmed
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

   * When a generator started to be provided by systemd, it was
  recognized that $PATH is not correctly set, nonetheless, due to an
  environment bug that systemd generators run in.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

  Output should contain a complete and a valid PATH, i.e.
  PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" 
or similar.

  [Regression Potential]

   * snapd generator was already fixed separately to cause no harm, when
  running under a broken systemd. With the corrected environment,
  generators will now run with a correct PATH out of the box. A slight
  change of PATH will be observed by all generators, when running in
  containers/initramfs-less boots. However most generators will not be
  affected as they typically do not execute external binaries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1811471] Re: local resolver stub fails to handle multiple TCP dns queries

2019-02-01 Thread Dan Streetman
hddemux failure should be ignored; its autopkgtests are fixed in
-proposed with bug 1814062

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

Title:
  local resolver stub fails to handle multiple TCP dns queries

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  The systemd local 'stub' resolver handles all local DNS queries (by
  default configuration used in Ubuntu), and essentially proxies all
  requests to its configured upstream DNS resolvers.

  Most local DNS resolution by applications uses glibc's getaddrinfo()
  function.  This function is configured in various ways by the
  /etc/resolv.conf file, which tells glibc what nameserver/resolver to
  contact as well as how to talk to the name server.

  By default, glibc performs UDP DNS queries, with a single DNS query
  per UDP packet.  The UDP packet size is limited per DNS spec to 512
  bytes.  For some DNS lookups, a 512 byte UDP packet is not large
  enough to contain the entire response - for example, an A record
  lookup with a large number (e.g. 30) of A record addresses.  This
  number of A record entries is possible in some cases of load
  balancing.  When the DNS UDP response size is larger than 512 bytes,
  the server puts as much response as it can into the DNS UDP response,
  and marks the "trunacted" flag.  This lets glibc know that the DNS UDP
  packet did not contain the entire response for all the A records.

  When glibc sees a UDP response that is "trunacted", by default it
  ignores the contents of that response and issues a new DNS query,
  using TCP instead of UDP.  The TCP packet size has a higher size limit
  (though see bug 1804487 which is a bug in systemd's max-sizing of TCP
  DNS packets), and so *should* allow glibc to receive the entire DNS
  response.

  However, glibc issues DNS queries for both A and  records.  When
  it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet
  with a single A query, and one UDP DNS packet with a single 
  query).  When glibc uses TCP, it puts both DNS queries into a single
  TCP DNS packet - the RFC refers to this as "pipelining"
  (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that
  clients SHOULD do this, and that servers MUST expect to receive
  pipelined queries and SHOULD respond to all of them.  (Technically
  pipelining can be separate DNS queries, one per TCP packet, but both
  using the same TCP connection - but the clear intention of pipelining
  is to improve TCP performance, and putting both DNS queries into a
  single TCP packet is clearly more performant than using separate TCP
  packets).

  Unfortunately, systemd's local stub resolver has only very basic
  support for TCP DNS, and it handles TCP DNS queries almost identically
  to UDP DNS queries - it reads the DNS query 2-byte header (containing
  the length of the query data), reads in the single DNS query data,
  performs lookup and sends a response to that DNS query, and closes the
  TCP connection.  It does not check for "pipelined" queries in the TCP
  connection.

  That would be bad enough, as glibc is (rightly) expecting a response
  to both its A and  queries; however what glibc gets is a TCP
  connection-reset error.  That is because the local systemd stub
  resolver has closed its TCP socket while input data was still pending
  (i.e. it never even read the second pipelined DNS query).  When the
  kernel sees unread input bytes in a TCP connection that is closed, it
  sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the
  RST, it dumps all data in its socket buffer and passes the ECONNRESET
  error up to the application.  So glibc gets nothing besides a
  connection reset error.

  Note also that even if the systemd local stub resolver's socket
  flushes its input buffer before closing the TCP connection (which will
  avoid the TCP RST), glibc still expects responses to both its A and
   queries before systemd closes the TCP connection, and so a simple
  change to systemd to flush the input buffer is not enough to fix the
  bug (and would also not actually fix the bug since glibc would never
  get the  response).

  [Test Case]

  This can be reproduced on any system using a local systemd stub
  resolver, when using an application that uses getaddrinfo() - such as
  ssh, telnet, ping, etc - or with a simple C program that uses
  getaddrinfo().  The dns name looked up must have enough A records to
  overflow the 512 byte maximum for a UDP DNS packet; e.g.:

  $ ping 

[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"

2019-02-01 Thread Bryan Seitz
I have the image, how can I get it to you privately to test? (Or
alternatively, I can test it with the new version if you have a link?)

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

Title:
  cpio in Busybox 1.27 ingnores "unsafe links"

Status in busybox package in Ubuntu:
  Fix Released
Status in debirf package in Ubuntu:
  Confirmed
Status in busybox source package in Bionic:
  In Progress
Status in debirf source package in Bionic:
  Confirmed
Status in busybox source package in Cosmic:
  Fix Released
Status in debirf source package in Cosmic:
  Confirmed

Bug description:
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3

  3) Expected my CPIO archive to be fully extracted with proper symlinks
  Command: unxz < /rootfs.cxz | cpio -i

  4) 'Unsafe' symlinks were ignored such as:

  sbin/init -> /lib/systemd/systemd

  With the broken 1.27 sbin/init does not get created at all and my
  debirf initrd fails to load/boot properly.

  1.22 from Xenial works.
  GNU Cpio also works.

  It looks like 1.28 adds an env var to override this behavior:

  libarchive: do not extract unsafe symlinks unless
  $EXTRACT_UNSAFE_SYMLINKS=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+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 1814317] [NEW] Errors were encountered while processing: /var/cache/apt/archives/mysql-server-5.7_5.7.25-0ubuntu0.18.04.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error

2019-02-01 Thread mashum eesha
Public bug reported:

this is it

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

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

Title:
  Errors were encountered while processing:  /var/cache/apt/archives
  /mysql-server-5.7_5.7.25-0ubuntu0.18.04.2_amd64.deb E: Sub-process
  /usr/bin/dpkg returned an error code (1)

Status in debconf package in Ubuntu:
  New

Bug description:
  this is it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1814317/+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 1814302] Re: Quasselcore apparmor profile issue in lxd container.

2019-02-01 Thread Yancy Burns
** Also affects: apparmor
   Importance: Undecided
   Status: New

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

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

Title:
  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in quassel package in Ubuntu:
  New

Bug description:
  Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04
  container. Everything up todate via apt.

  Install quassel-core. Service will not start.

  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

  I then added "/usr/bin/quasselcore rm," to
  "/etc/apparmor.d/usr.bin.quasselcore".

  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

  Quasselcore service now starts and I can connect to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1814302/+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 1814302] [NEW] Quasselcore apparmor profile issue in lxd container.

2019-02-01 Thread Yancy Burns
Public bug reported:

Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04
container. Everything up todate via apt.

Install quassel-core. Service will not start.

Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

I then added "/usr/bin/quasselcore rm," to
"/etc/apparmor.d/usr.bin.quasselcore".

Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

Quasselcore service now starts and I can connect to it.

** Affects: apparmor
 Importance: Undecided
 Status: New

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

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

Title:
  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04
  container. Everything up todate via apt.

  Install quassel-core. Service will not start.

  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

  I then added "/usr/bin/quasselcore rm," to
  "/etc/apparmor.d/usr.bin.quasselcore".

  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

  Quasselcore service now starts and I can connect to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1814302/+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 1814299] [NEW] package libelf1:amd64 0.170-0.5.0ubuntu1 failed to install/upgrade: triggers ci file contains unknown directive '

2019-02-01 Thread Fila Kolodny
Public bug reported:

Install failed

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: libelf1:amd64 0.170-0.5.0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Tue Jan 29 13:33:50 2019
ErrorMessage: triggers ci file contains unknown directive 'https://bugs.launchpad.net/bugs/1814299

Title:
  package libelf1:amd64 0.170-0.5.0ubuntu1 failed to install/upgrade:
  triggers ci file contains unknown directive 'https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1814299/+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 1811592] Re: systemd-tmpfiles-setup.service fails after update

2019-02-01 Thread Brian Murray
*** This bug is a duplicate of bug 1811580 ***
https://bugs.launchpad.net/bugs/1811580

** This bug has been marked a duplicate of bug 1811580
   systemd fails to start sshd at reboot

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

Title:
  systemd-tmpfiles-setup.service fails after update

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  1. Description:   Ubuntu 16.04.5 LTS
  Release:  16.04

  2. apt-cache policy systemd 
  systemd:
Installed: 229-4ubuntu21.15
Candidate: 229-4ubuntu21.15
Version table:
   *** 229-4ubuntu21.15 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3. After VPS was rebooted I can't to connect via SSH

  4. SSH Service fail because systemd-tmpfiles service fail to start after 
update
  I can connect to VPS (openVZ) only via emergency console

  journalctl -b 0 -u systemd-tmpfiles-setup.service
  -- Logs begin at Sun 2019-01-13 18:34:20 EET, end at Sun 2019-01-13 18:50:00 
EET. --
  Jan 13 18:34:20 wok.f.time4vps.cloud systemd[1]: Starting Create Volatile 
Files and Directories...
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate 
path /var/run/screen: Too many levels of symbolic links
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate 
path /var/run/sshd: Too many levels of symbolic links
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate 
path /var/run/sudo: Too many levels of symbolic links
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate 
path /var/run/sudo/ts: Too many levels of symbolic links
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of 
/run/utmp failed: Invalid argument
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: 
systemd-tmpfiles-setup.service: Main process exited, code=exited, 
status=1/FAILURE
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: Failed to start Create 
Volatile Files and Directories.
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: 
systemd-tmpfiles-setup.service: Unit entered failed state.
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: 
systemd-tmpfiles-setup.service: Failed with result 'exit-code'.

  
  workaround to start SSH is mkdir /run/sshd

  The situation like this
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811592/+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 1164016] Re: restore type-ahead find

2019-02-01 Thread Chris Billington
I don't know how long it will take, but in the meantime Ubuntu could
ship the patch maintained by the Arch community:

https://aur.archlinux.org/cgit/aur.git/tree/nautilus-restore-
typeahead.patch?h=nautilus-typeahead

It looks like this patch is kept up to date pretty well. There is a
similar patch for gtk3 to make the file chooser dialog have type-ahead.

It's the best of both worlds, since you can still tap ctrl-f to search.

Whilst it would be nice for the Nautilus devs to upstream the patch or
for there to be a dialog about what kind of patch they might accept (if
any), in the meantime distros can include the patch, there is little
downside since the patch is maintained and not bit rotting. Canonical
would not be committing themselves to maintaining it by including it.

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1811471] Re: local resolver stub fails to handle multiple TCP dns queries

2019-02-01 Thread Dan Streetman
bionic regressions:

systemd on all archs have failed for months.  tests should be ignored.

snapd on all archs have failed intermittently for very long time.  tests
are flaky and should be ignored.

remaining tests being retried:

linux-gcp-edge (system problem - oom while testing)

linux (flaky tests - intermittently fails for a long time)

linux-oracle (system problem - out of disk space while testing)


cosmic regressions:

hddemux on all archs started failing recently; the version in -proposed
appears to be fixed, so the failure of this pkg can be ignored as it's
not caused by this sru.

remaining tests being retried:

apt (flaky test - fails intermittently in the same way for a while)

linux (flaky tests - intermittently fails for a long time)

snapd/amd64 (flaky test, test watchdog has 1 second timeout, and timed
out)

systemd (test output hard to read - seems to be timeout, likely
overloaded test system)

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

Title:
  local resolver stub fails to handle multiple TCP dns queries

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  The systemd local 'stub' resolver handles all local DNS queries (by
  default configuration used in Ubuntu), and essentially proxies all
  requests to its configured upstream DNS resolvers.

  Most local DNS resolution by applications uses glibc's getaddrinfo()
  function.  This function is configured in various ways by the
  /etc/resolv.conf file, which tells glibc what nameserver/resolver to
  contact as well as how to talk to the name server.

  By default, glibc performs UDP DNS queries, with a single DNS query
  per UDP packet.  The UDP packet size is limited per DNS spec to 512
  bytes.  For some DNS lookups, a 512 byte UDP packet is not large
  enough to contain the entire response - for example, an A record
  lookup with a large number (e.g. 30) of A record addresses.  This
  number of A record entries is possible in some cases of load
  balancing.  When the DNS UDP response size is larger than 512 bytes,
  the server puts as much response as it can into the DNS UDP response,
  and marks the "trunacted" flag.  This lets glibc know that the DNS UDP
  packet did not contain the entire response for all the A records.

  When glibc sees a UDP response that is "trunacted", by default it
  ignores the contents of that response and issues a new DNS query,
  using TCP instead of UDP.  The TCP packet size has a higher size limit
  (though see bug 1804487 which is a bug in systemd's max-sizing of TCP
  DNS packets), and so *should* allow glibc to receive the entire DNS
  response.

  However, glibc issues DNS queries for both A and  records.  When
  it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet
  with a single A query, and one UDP DNS packet with a single 
  query).  When glibc uses TCP, it puts both DNS queries into a single
  TCP DNS packet - the RFC refers to this as "pipelining"
  (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that
  clients SHOULD do this, and that servers MUST expect to receive
  pipelined queries and SHOULD respond to all of them.  (Technically
  pipelining can be separate DNS queries, one per TCP packet, but both
  using the same TCP connection - but the clear intention of pipelining
  is to improve TCP performance, and putting both DNS queries into a
  single TCP packet is clearly more performant than using separate TCP
  packets).

  Unfortunately, systemd's local stub resolver has only very basic
  support for TCP DNS, and it handles TCP DNS queries almost identically
  to UDP DNS queries - it reads the DNS query 2-byte header (containing
  the length of the query data), reads in the single DNS query data,
  performs lookup and sends a response to that DNS query, and closes the
  TCP connection.  It does not check for "pipelined" queries in the TCP
  connection.

  That would be bad enough, as glibc is (rightly) expecting a response
  to both its A and  queries; however what glibc gets is a TCP
  connection-reset error.  That is because the local systemd stub
  resolver has closed its TCP socket while input data was still pending
  (i.e. it never even read the second pipelined DNS query).  When the
  kernel sees unread input bytes in a TCP connection that is closed, it
  sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the
  RST, it dumps all data in its socket buffer and passes the ECONNRESET
  error up to the application.  So glibc gets nothing besides a
  

[Touch-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

2019-02-01 Thread Earle Lyons
Just removed the hold on kmod (24-1ubuntu3) and updated to kmod
(24-1ubuntu3.2). The touchpad is still working. Thanks for everyone's
effort on this issue. Greatly appreciate it.

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+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 1164016] Re: restore type-ahead find

2019-02-01 Thread teo1978
> In reality,
> recursive search is useful, and I want to use it, but it's different to
> typeahead

Exactly, they are two completely different, unrelated things, and if the
Nautilus devs can't understand something as elementary as that, Ubuntu
shouldn't be using software developed by those people as the default
file explorer.

This issue is just one example; nautilus developers have taken quite a
few "design decisions" that are - ahem - let's say contrary to common
sense, degrading usability rather than improve things.

Keeping Nautilus as the file explorer means Ubuntu will have to keep
struggling with this sort of things and maintaining patches like this
one. Of course, if there's no better alternative out there (I find it
hard to believe that such a shitty file manager is the best available,
but I don't know, it might be), then it'll have to be this.

> I do think things will eventually go back this way
> (...) I do think Nautilus can satisfy everyone's preferences here

How long do we have to wait for them to recapacitate and revert breaking
stuff that had been designed correctly in the first place ages ago?

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1164016] Re: restore type-ahead find

2019-02-01 Thread Mihir Gadgil
Is there any timeline as to when this stupidity is going to be fixed?
This is a very very very basic functionality for any file explorer;
something any new application should add. Taking it out of a software
that has already had it for years and annoying people who rely on it is
simply illogical.

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1814290] [NEW] package perl-base 5.26.2-7ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

2019-02-01 Thread Petar Ivanovski
Public bug reported:

i cant open ubuntu software it is just says that is being loaded and its
stuck like that

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: perl-base 5.26.2-7ubuntu0.1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
AptOrdering:
 perl-base:amd64: Configure
 perl-modules-5.26:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Feb  1 17:33:52 2019
DpkgTerminalLog:
 dpkg: error processing package perl-base (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2019-01-20 (11 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: perl
Title: package perl-base 5.26.2-7ubuntu0.1 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)

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


** Tags: amd64 apport-package cosmic

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

Title:
  package perl-base 5.26.2-7ubuntu0.1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in perl package in Ubuntu:
  New

Bug description:
  i cant open ubuntu software it is just says that is being loaded and
  its stuck like that

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: perl-base 5.26.2-7ubuntu0.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  AptOrdering:
   perl-base:amd64: Configure
   perl-modules-5.26:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Feb  1 17:33:52 2019
  DpkgTerminalLog:
   dpkg: error processing package perl-base (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2019-01-20 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: perl
  Title: package perl-base 5.26.2-7ubuntu0.1 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/perl/+bug/1814290/+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 1164016] Re: restore type-ahead find

2019-02-01 Thread Chris Billington
I don't think it's true that an option is always good. I think software
should endeavour to have decent default options, and if multiple use
cases can be accommodated without an option, then that is preferable.

But you're right, a recursive search with ctrl-f vs typeahaed with
simple typing would accomplish what everyone wants without an option.

I'm using the 'search in current folder only' setting in order to make
the search more like typeahead, but this has the downside that I have to
go into the settings to do an actual recursive search. In reality,
recursive search is useful, and I want to use it, but it's different to
typeahead and it's a shame I have to pick one or the other.

Ideally for me would be typing is just going to select things similarly
to the old typeahead behaviour, and ctrl-f would do a search, either in
the current folder or recursively depending on a checkbox that would
ideally be in the main interface next to the search box rather than in
the settings menu - since one often wants one or the other, it's not
really an all-time preference.

I do think things will eventually go back this way. There is currently
wasted effort trying to make search meet the requirements of type-ahead,
whereas this would be unnecessary if typeahead existed too. Search is
becoming a bit of a frankenstein trying to be both, with returning items
from the current folder first, and having the search-in-current-folder-
only setting being global. It should just be search - features should do
one thing each instead of trying to please everyone.

I understand that search has been improved a lot in response to
complaints about type-ahead being removed, and this shows that the devs
are trying to meet people's use cases. But ultimately I think it is
misguided and making the search implementation more complex than it
otherwise would need to be. They are really are different features. So I
know there has been a lot of vitriol over this issue, but I would
encourage the nautilus devs to consider that they should become
different features once again. Ctrl-f to search will not confuse
anybody, type-ahead will not confuse anybody, whereas the current search
is trying to be both and so can behave unexpectedly in terms of the
order of search results and whether the search is recursive. Presumably
this means code complexity too.

I also understand that the old type-ahead code was holding back the
codebase and so it was desirable to excise it. I imagine new typeahead
functionality, working as much as possible within the current codebase
and its future directions, would be more amenable to nautilus dev
approval than just restoring the old code. For example, we probably
don't need the popup box in the bottom right as you type. It should just
be type a few characters and have a few-second timeout before forgetting
them, just like it is on other platforms such as windows and macos (I
think). It seems similar to me to the case or removing nautilus handling
the desktop. The code was holding back the codebase, but now we see that
a desktop extension for gnome-shell is in development by the main
nautilus dev.

I do think Nautilus can satisfy everyone's preferences here, and I do
think typeahead will eventually be re implemented once tensions die
down, especially if the nautilus devs can do it on their terms instead
of rejecting a patch that just re-adds code that they don't want to
maintain. A good typeahead implementation would even allow Nautilus to
remove code that customises how the search works to make it more useful
as typeahead - there would no longer be a need for that if typeahead
were present in its own right.

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1812014] Re: keyboard not responding after suspend after some time

2019-02-01 Thread Krzysztof
journalctl -b-1 > prevlog.txt

** Attachment added: "prevlog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+attachment/5235109/+files/prevlog.txt

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

Title:
  keyboard not responding after suspend after some time

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-08-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1814284] [NEW] зависает всё

2019-02-01 Thread Качурин Максим Лаврентьевич
Public bug reported:

компьютер зависает на долго или прихода пере запускатькомпютер

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Feb  1 21:48:54 2019
DistUpgraded: 2019-01-28 16:16:38,613 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Palit Microsystems Inc. GF108 [GeForce GT 630] [1569:0f00]
InstallationDate: Installed on 2019-01-03 (29 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-01-28 (4 days ago)
dmi.bios.date: 07/11/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.90
dmi.board.name: H61M-VG3
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.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-VG3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.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.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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
xserver.bootTime: Fri Feb  1 21:29:29 2019
xserver.configfile: default
xserver.errors:
 [drm] Failed to open DRM device for pci::01:00.0: -19
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  зависает всё

Status in xorg package in Ubuntu:
  New

Bug description:
  компьютер зависает на долго или прихода пере запускатькомпютер

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb  1 21:48:54 2019
  DistUpgraded: 2019-01-28 16:16:38,613 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Palit Microsystems Inc. GF108 [GeForce GT 630] [1569:0f00]
  InstallationDate: Installed on 2019-01-03 (29 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-01-28 (4 days ago)
  dmi.bios.date: 07/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.90
  dmi.board.name: H61M-VG3
  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: 

[Touch-packages] [Bug 1814109] Re: Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu

2019-02-01 Thread Brian Murray
** Tags added: rls-dd-incoming

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

Title:
  Nautilus corrupts 7z archive files when extracting via 'Extract here'
  context menu

Status in libarchive package in Ubuntu:
  Triaged

Bug description:
  Nautilus corrupts 7z archive files when extracting via 'Extract here' context 
menu.
  Extractions completes without errors, but the files are corrupted (mangled 
bytes, wrong size).
  This does happen only when extracting with 'Extract here' context menu action.
  Using 7z or p7zip via command line or opening the archive via file-roller and 
then drag
  single files or directory to a folder works well.
  This only happens with this particular archive, others 7z archives are 
extracted correctly.

  Original 7z archive:
  https://drive.google.com/open?id=1eZJm1ST3P-52tFSvHXbUn9-WSe_B3Ag9

  Re-zipped corrupted archive here:
  https://drive.google.com/open?id=1N--99RuWdmg6oUGrAz7pLoRpuJOIBEE5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 15:03:45 2019
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'222'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1133x703+51+273'"
   b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'false'
  InstallationDate: Installed on 2018-05-31 (245 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (103 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1814109/+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 1813432] Re: Specific PDF file fails to print to HP m551dn printer

2019-02-01 Thread Jonathan Kamens
I tried `lp -d duplex -o fit-to-page -o pdftops-renderer=XXX` with
hybrid, gs, pdftops, pdftocairo, and mupdf as the renderers (for the
last I had to install both mupdf and mupdf-tools).

The only one that made it through to the printer was gs.

All claimed to print, but gs was the only one that actually did.

Please note my comments at the end of
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/428817. I using a
PPD for my printer downloaded directly from HP because for some
inexplicable reason it is not installed with Ubuntu (or, at least, it
was not installed with Ubuntu 18.10, when I configured the printer).
This may be relevant.

For me, the sticking point remains, why does this one PDF file cause
problems when no others (that I've seen) do?

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

Title:
  Specific PDF file fails to print to HP m551dn printer

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  One particular PDF file is failing to print. I have no idea why. When
  I say failing to print I mean that my computer thinks the file printed
  but the printer shows no sign of ever having received it. The display
  of the printer never changes to show that it is receiving or printing
  a file, and the job log of the printer doesn't show that it was
  received either. I also checked the printer event log and it doesn't
  show any events at the time I attempted to print the file.

  Unfortunately I can't attach the PDF file itself because it contains
  private information, and I can't find another PDF that exhibits this
  problem. I even tried generating a new PDF exactly the same way the
  old one was generated -- with the scan to email PDF function on my
  scanner -- and the new PDF prints just fine.

  I tried uploading the PDF directly to the printer with FTP and it
  prints just fine that way.

  I enabled CUPS debug mode before attempting to print the file.
  Attached is the resulting contents of /var/log/cups/error_log.

  I wish I knew what was going on here but honestly I have no idea.
  Perhaps you can learn something from the error_log. I hope so.

  Other files, including other PDFs, do print.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-3
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 17:47:49 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA_: 
ipps://m551dn.local:443/ipp/print
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd', 
'/etc/cups/ppd/duplex.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1813432/+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 1164016] Re: restore type-ahead find

2019-02-01 Thread teo1978
There's no need for an option.

You can already do a recursive search with Ctrl+F.
I "can't believe" one would want to enable type-ahead-recursive-search instead 
of type-ahead-select-in-current-folder by default just to spare themselves the 
trouble of hitting Ctrl+F.

However, an option, even if for enabling the weirdest preference or for
accomodating the rarest use case, is always a good thing. What is
absolutely unacceptable is a wrong default behavior that, even worse,
cannot even be changed to the more sensible one. That is, the current
situation.

I am stuck with 16.04 because upgrading to 18.04 would mean having to
live with this crap, which is like living without a file explorer at all
(that's doable for somebody accustomed to doing everyday tasks from a
terminal, but that's not me, nor the average user).

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is

2019-02-01 Thread Frederick Gibson
I've reverted back to before installing the Nvidia driver.  Nvidia now
has new drivers which I think will solve this problem, so this bug can
be closed.

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

Title:
  package libwayland-server0 1.16.0-1ubuntu1.1 failed to
  install/upgrade: trying to overwrite shared '/usr/share/doc
  /libwayland-server0/changelog.Debian.gz', which is different from
  other instances of package libwayland-server0:i386

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  Trying to install nvidia-driver-390 on Dell XPS 15 6570

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libwayland-server0 1.16.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jan 31 18:32:20 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-14-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed
  DuplicateSignature:
   package:libwayland-server0:1.16.0-1ubuntu1.1
   Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', 
which is different from other instances of package libelf1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2019-01-31 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: wayland
  Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0HWTMH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+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 1811592] Re: systemd-tmpfiles-setup.service fails after update

2019-02-01 Thread Brian Murray
** Tags added: regression-update

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

Title:
  systemd-tmpfiles-setup.service fails after update

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  1. Description:   Ubuntu 16.04.5 LTS
  Release:  16.04

  2. apt-cache policy systemd 
  systemd:
Installed: 229-4ubuntu21.15
Candidate: 229-4ubuntu21.15
Version table:
   *** 229-4ubuntu21.15 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3. After VPS was rebooted I can't to connect via SSH

  4. SSH Service fail because systemd-tmpfiles service fail to start after 
update
  I can connect to VPS (openVZ) only via emergency console

  journalctl -b 0 -u systemd-tmpfiles-setup.service
  -- Logs begin at Sun 2019-01-13 18:34:20 EET, end at Sun 2019-01-13 18:50:00 
EET. --
  Jan 13 18:34:20 wok.f.time4vps.cloud systemd[1]: Starting Create Volatile 
Files and Directories...
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate 
path /var/run/screen: Too many levels of symbolic links
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate 
path /var/run/sshd: Too many levels of symbolic links
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate 
path /var/run/sudo: Too many levels of symbolic links
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate 
path /var/run/sudo/ts: Too many levels of symbolic links
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of 
/run/utmp failed: Invalid argument
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: 
systemd-tmpfiles-setup.service: Main process exited, code=exited, 
status=1/FAILURE
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: Failed to start Create 
Volatile Files and Directories.
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: 
systemd-tmpfiles-setup.service: Unit entered failed state.
  Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: 
systemd-tmpfiles-setup.service: Failed with result 'exit-code'.

  
  workaround to start SSH is mkdir /run/sshd

  The situation like this
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811592/+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 1409872] Re: avahi-0.6.31 doesn't pass Apple conformance test

2019-02-01 Thread Stephen H. Gerstacker
I posted this on the Avahi Github issue, but I felt it was appropriate
here as well:

---

I've been researching this issue for my company. We specifically need to
pass the mDNS portion of the BCT, so our scope is limited, but I do have
some insights.

There is a definitely an issue if you are broadcasting a service with
the "%h" wildcard as the service name. During the service collision
portion, this falls down, but, if you are broadcasting under any other
static name, you can get much further.

Newer versions of the test seem to require that specific services need
to be broadcasted. This is not mentioned in the documentation anywhere,
but, if I simple broadcast the _smb._tcp. service with any static name
(e.g. "Living Room" or "SMB"), then the mDNS test does pass for BCT
1.5.0.

Technically we have to pass the mDNS portion of the test on BCT 1.3.1.
With the set up above, we fail one test, and that's because one reply
comes back from Avahi too quickly. Interestingly enough, BCT 1.3.3 seems
to have addressed the timing issue, allowing slightly better tolerances.
I believe the response in question needs to come in between the 250ms
and 750ms window, and Avahi appears to come in slightly before that
window. In the newer versions of BCT, this isn't an issue. I imagine
either BCT 1.3.1 has too tight of tolerances, or isn't sampling
improperly.

There are actually very strict instructions on setting up the test
environment, and I even found that with the strict network set up, it
could still potentially fail. You need an AirPort Extreme set up to act
as an access point and that is it. No DHCP, no network connection, and
crucially, no SMB broadcast if you're using a Time Capsule (this can
break the test). The test machine was a MacBook Air running macOS 10.12
and connected via ethernet. The Avahi machine was an Asus laptop running
Ubuntu 18.10 (Avahi 0.7) connected via wifi. Everything is link local.
This all comes from the "Bonjour Conformance Test for Wi-Fi Alliance
Version 0.1" document.

We're exploring whether we can actually use the 1.5.0 test, as this
would make Avahi simply work in the mDNS portion of the test.

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

Title:
  avahi-0.6.31 doesn't pass Apple conformance test

Status in Avahi:
  Unknown
Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  We are working on to support Apple bonjour conformance test-1.3.0 and
  test fails with avahi version 0.6.31 for test case - SRV
  PROBING/ANNOUNCEMENTS. This test fails both on IPV4 and IPV6. And the
  configured network package - dhcpcd-6.6.4.

  After parsing all logs(wireshark, apple PC and linux PC syslogs), and
  looks like avahi does not support a particular scenario in which Apple
  bonjour conformance test looks for. And also confirmed Apple test is
  inline with the RFC 6762 document for a special use-case(resolving SRV
  names on power up).

  Below is the bug description,

  setup:
  Apple MAC with Bonjour conformance test - 1.3.0 (latest OS x)
  Apple airport  (latest version)
  Linux device(PC) (ubuntu 14.04)

  Configure all above devices to communicate on link local mode.

  1) Start avahi bonjour conformance test on APPLE PC and Power ON linux
  device with avahi-0.6.31 and with _ssh._tcp.local service file

  2) First Linux device sends SRV initial probe message on link and followed by 
apple test sends same SRV (Linux device) question on link,
 example:(commands on wire shark)
  Linux Device sends ->  Who has "SSH" SRV QM question?
  Apple Bonjour Conformance Test -> Who has "SSH" SRV QM question?

  3) Then after this there is no message from Linux device on network and Apple 
test expecting new SRV probe message from device.
And so conformance test failed, since device couldn't able to send new 
SRV probe message with new name for service "SSH"

  4) After parsing log files found that,
 avahi-daemon logged service with new name ("SSH #2") in log file and could 
not publish/probe SRV message on network.

Linux device syslog messages,
Loading service file /etc/avahi/services/ssh.service
Service name conflict for "SSH" (/etc/avahi/services/ssh.service), 
retrying with "SSH #2).

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

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


Re: [Touch-packages] [Bug 1814262] Re: Wired interface gets impossibly high metric 20100

2019-02-01 Thread Rachel Greenham
Noted. I see there's no report of anything similar already, and if it 
was the sort of problem it looked like to me, people would be screaming 
blue murder about it, so I think I'll wait and see if it recurs or 
becomes an ongoing problem, rather than a one-off. Maybe my LAN was 
having a bad hair day...

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

Title:
  Wired interface gets impossibly high metric 20100

Status in network-manager package in Ubuntu:
  New

Bug description:
  Actually this might be a heisenbug. I've had an issue with this all
  morning since network-manager got an update this morning, but just now
  *while this bug was being submitted* it decided to correct itself.

  What I was getting was, on a machine (Dell XPS 13 9370) with WiFi and
  a (Caldigit) Thunderbolt 3 dock with an ethernet port: After the
  network-manager update I noticed everything was slower than I was used
  to, and in gnome-shell the network icon showing was the WiFi one, not
  the wired one.

  Looking at the output of route, or route -n for simplicity, I would
  see this:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG60000 wlp2s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20100  00 
enp63s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So the metric on the default route on enp63s0 had 20,000 mysteriously
  added to it, which would obviously make it extremely low-priority. The
  system was choosing the wifi connection instead, which isn't that
  great in my office, hence observable slowness.

  Now, this morning, this seemed to be the sticky situation. It didn't
  show any sign of changing, whatever I did, after restarts of network-
  manager, undock/redock, reboots, etc. I could change it manually with
  ifmetric (and it would work), but that was about it.

  I would have reported the bug then, but I had to go out. When I got
  back I plugged in and initially saw the same thing again (that's where
  the above snippet was pasted from). But *while* the ubuntu-bug
  network-manager command was running, I noticed the gnome-shell network
  icon switch to wired, checked again, and saw:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG10000 
enp63s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20600  00 wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So now the wifi connection has 20,000 added to it, which may still be
  wrong? But I wouldn't otherwise have noticed it because the system is
  again *behaving* as expected.

  This all seemed to happen after the network-manager upgrade (from
  1.12.6-0ubuntu4 to 1.15.2-0ubuntu1) this morning. I can't say if these
  metric+20,000 values were present before then, because I didn't have
  any cause to go looking at it, it always just worked. Could it be some
  issue with how the newer network-manager, or one of its associated
  packages, is figuring out the metrics on new connections? Like it's
  running some new heuristic to determine which one should really be the
  preferred? If it's like it was just now, when it fixed itself after a
  minute or so, that's not really a problem, but if it's like it was
  this morning when it just seemed to be stuck with the ethernet
  connection at 20100, it is.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.15.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  1 13:15:06 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-11 (142 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  IpRoute:
   default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 
   default via 192.168.1.254 dev enp63s0 proto dhcp metric 20100 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 
100 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 

[Touch-packages] [Bug 1814262] Re: Wired interface gets impossibly high metric 20100

2019-02-01 Thread Sebastien Bacher
Thank you for your bug report. Is there any chance that you could also
report the issue upstream on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager? We do keep
up with updates for that component but don't know the code as well that
they do and there might have a better idea of what's wrong there

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

Title:
  Wired interface gets impossibly high metric 20100

Status in network-manager package in Ubuntu:
  New

Bug description:
  Actually this might be a heisenbug. I've had an issue with this all
  morning since network-manager got an update this morning, but just now
  *while this bug was being submitted* it decided to correct itself.

  What I was getting was, on a machine (Dell XPS 13 9370) with WiFi and
  a (Caldigit) Thunderbolt 3 dock with an ethernet port: After the
  network-manager update I noticed everything was slower than I was used
  to, and in gnome-shell the network icon showing was the WiFi one, not
  the wired one.

  Looking at the output of route, or route -n for simplicity, I would
  see this:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG60000 wlp2s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20100  00 
enp63s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So the metric on the default route on enp63s0 had 20,000 mysteriously
  added to it, which would obviously make it extremely low-priority. The
  system was choosing the wifi connection instead, which isn't that
  great in my office, hence observable slowness.

  Now, this morning, this seemed to be the sticky situation. It didn't
  show any sign of changing, whatever I did, after restarts of network-
  manager, undock/redock, reboots, etc. I could change it manually with
  ifmetric (and it would work), but that was about it.

  I would have reported the bug then, but I had to go out. When I got
  back I plugged in and initially saw the same thing again (that's where
  the above snippet was pasted from). But *while* the ubuntu-bug
  network-manager command was running, I noticed the gnome-shell network
  icon switch to wired, checked again, and saw:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG10000 
enp63s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20600  00 wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So now the wifi connection has 20,000 added to it, which may still be
  wrong? But I wouldn't otherwise have noticed it because the system is
  again *behaving* as expected.

  This all seemed to happen after the network-manager upgrade (from
  1.12.6-0ubuntu4 to 1.15.2-0ubuntu1) this morning. I can't say if these
  metric+20,000 values were present before then, because I didn't have
  any cause to go looking at it, it always just worked. Could it be some
  issue with how the newer network-manager, or one of its associated
  packages, is figuring out the metrics on new connections? Like it's
  running some new heuristic to determine which one should really be the
  preferred? If it's like it was just now, when it fixed itself after a
  minute or so, that's not really a problem, but if it's like it was
  this morning when it just seemed to be stuck with the ethernet
  connection at 20100, it is.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.15.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  1 13:15:06 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-11 (142 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  IpRoute:
   default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 
   default via 192.168.1.254 dev enp63s0 proto dhcp metric 20100 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 
100 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 

[Touch-packages] [Bug 1814262] [NEW] Wired interface gets impossibly high metric 20100

2019-02-01 Thread Rachel Greenham
Public bug reported:

Actually this might be a heisenbug. I've had an issue with this all
morning since network-manager got an update this morning, but just now
*while this bug was being submitted* it decided to correct itself.

What I was getting was, on a machine (Dell XPS 13 9370) with WiFi and a
(Caldigit) Thunderbolt 3 dock with an ethernet port: After the network-
manager update I noticed everything was slower than I was used to, and
in gnome-shell the network icon showing was the WiFi one, not the wired
one.

Looking at the output of route, or route -n for simplicity, I would see
this:

rachel@rainbow:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.1.254   0.0.0.0 UG60000 wlp2s0
0.0.0.0 192.168.1.254   0.0.0.0 UG20100  00 enp63s0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
192.168.1.0 0.0.0.0 255.255.255.0   U 10000 enp63s0
192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

So the metric on the default route on enp63s0 had 20,000 mysteriously
added to it, which would obviously make it extremely low-priority. The
system was choosing the wifi connection instead, which isn't that great
in my office, hence observable slowness.

Now, this morning, this seemed to be the sticky situation. It didn't
show any sign of changing, whatever I did, after restarts of network-
manager, undock/redock, reboots, etc. I could change it manually with
ifmetric (and it would work), but that was about it.

I would have reported the bug then, but I had to go out. When I got back
I plugged in and initially saw the same thing again (that's where the
above snippet was pasted from). But *while* the ubuntu-bug network-
manager command was running, I noticed the gnome-shell network icon
switch to wired, checked again, and saw:

rachel@rainbow:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.1.254   0.0.0.0 UG10000 enp63s0
0.0.0.0 192.168.1.254   0.0.0.0 UG20600  00 wlp2s0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
192.168.1.0 0.0.0.0 255.255.255.0   U 10000 enp63s0
192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

So now the wifi connection has 20,000 added to it, which may still be
wrong? But I wouldn't otherwise have noticed it because the system is
again *behaving* as expected.

This all seemed to happen after the network-manager upgrade (from
1.12.6-0ubuntu4 to 1.15.2-0ubuntu1) this morning. I can't say if these
metric+20,000 values were present before then, because I didn't have any
cause to go looking at it, it always just worked. Could it be some issue
with how the newer network-manager, or one of its associated packages,
is figuring out the metrics on new connections? Like it's running some
new heuristic to determine which one should really be the preferred? If
it's like it was just now, when it fixed itself after a minute or so,
that's not really a problem, but if it's like it was this morning when
it just seemed to be stuck with the ethernet connection at 20100, it is.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: network-manager 1.15.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb  1 13:15:06 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-09-11 (142 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
IpRoute:
 default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 
 default via 192.168.1.254 dev enp63s0 proto dhcp metric 20100 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 
100 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to disco on 2019-01-13 (18 days ago)
nmcli-dev:
 DEVICE   TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH
  CONNECTION  CON-UUID  
CON-PATH   
 wlp2s0   wifi  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Strange Noises  
ae54-3c3d-4714-8bf5-7e56bb7249c6  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 enp63s0  ethernet  

[Touch-packages] [Bug 1814261] [NEW] gpm prevents loging to the console: spurious “Enter” events seems inserted

2019-02-01 Thread EOLE team
Public bug reported:

Hello,

When our servers boot, We can't login because of spurious “enter”.

We have this problem on virtual and physical machines since:

* kernel linux-image-4.15.0-44-generic on bionic
* kernel linux-image-4.4.0-142-generic on xenial

To reproduce:

1. start an ubuntu server with the specific kernel
2. install GPM
3. on a console
   1. type the user name “root”
   2. hit “enter”
   3. wait few seconds => spurious “Enter” are send to the console
4. Stop gpm.service
5. retry to login on a console => no problem


lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

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


** Tags: bionic xenial

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

Title:
  gpm prevents loging to the console: spurious “Enter” events seems
  inserted

Status in gpm package in Ubuntu:
  New

Bug description:
  Hello,

  When our servers boot, We can't login because of spurious “enter”.

  We have this problem on virtual and physical machines since:

  * kernel linux-image-4.15.0-44-generic on bionic
  * kernel linux-image-4.4.0-142-generic on xenial

  To reproduce:

  1. start an ubuntu server with the specific kernel
  2. install GPM
  3. on a console
 1. type the user name “root”
 2. hit “enter”
 3. wait few seconds => spurious “Enter” are send to the console
  4. Stop gpm.service
  5. retry to login on a console => no problem

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1814261/+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 1772222] Re: dangling symlink in /etc/rsyslog.d breaks rsyslogd

2019-02-01 Thread Francis Ginther
** Tags added: id-5c53201e63be5660c62cfdcf

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

Title:
  dangling symlink in /etc/rsyslog.d breaks rsyslogd

Status in rsyslog package in Ubuntu:
  New
Status in rsyslog source package in Bionic:
  New

Bug description:
  Since upgrading from artful to bionic, I noticed that
  /var/log/kern.log, etc., were not being updated on my machine.

  In comparing to another machine running a fresh install of bionic, I
  discovered that this seems to be the culprit:

  [agnew(etc)] ls -l /etc/rsyslog.d/99-conjure-up.conf 
  lrwxrwxrwx 1 root root 45 Jun 14  2017 /etc/rsyslog.d/99-conjure-up.conf -> 
/usr/share/conjure-up/conjure-up-rsyslog.conf
  [agnew(etc)] ls -l /usr/share/conjure-up/conjure-up-rsyslog.conf
  ls: cannot access '/usr/share/conjure-up/conjure-up-rsyslog.conf': No such 
file or directory
  [agnew(etc)] _

  Before deletion:

  [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log
  lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
  [agnew(etc)] _

  After deletion:

  [agnew(etc)] sudo rm /etc/rsyslog.d/99-conjure-up.conf 
  [agnew(etc)] sudo service rsyslog restart

  [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log
  lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
  rsyslogd 30686 syslog8w   REG  253,122782   15213384 
/var/log/syslog
  rsyslogd 30686 syslog9w   REG  253,1 2065   15219687 
/var/log/auth.log
  [agnew(etc)] _

  It didn't occur to me to check the service status until writing this
  bug report, but in fact it does report the problem on startup:

  May 20 14:39:27 agnew rsyslogd[31786]: error during parsing file 
/etc/rsyslog.d/postfix.conf, on or before line 1: error accessing config file 
or directory '/etc/rsyslog.d/99-conjure
  May 20 14:39:27 agnew rsyslogd[31786]: CONFIG ERROR: there are no active 
actions configured. Inputs will run, but no output whatsoever is created. 
[v8.32.0 try http://www.rsyslog.com

  However, it's unlikely this warning will be discovered until it's too
  late, if ever -- consider a remote syslogging setup on a machine that
  has since been decommissioned or reinstalled -- and so it would
  probably better for rsyslogd to cope with dangling symlinks.  Indeed,
  given the age of the symlink, this is a regression from artful or
  earlier.

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

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


Re: [Touch-packages] [Bug 1814243] Re: apt update decides to abort on its own

2019-02-01 Thread Christian Ehrhardt 
> Did you switch terminals in between or reset it?

No it was all in the same terminal - not even a re-login via ssh

> Those should not be related, it sounds more like a terminal screwup.
> Like, sometimes, at  least in gnome-terminal, it reaches a point where
> readline and friends fail for some reason.

I found nothing in /var/crash (the system was set up to collect them).

So for now it seems we have no good lead.

Please let me know what you would need in case I can trigger it again.
Then until I find something mark it incomplete.

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

Title:
  apt update decides to abort on its own

Status in apt package in Ubuntu:
  New

Bug description:
  Hi,
  I saw this by accident and I'm not sure if it is a bug or if it just was a 
bad config.
  But I wanted to report to be sure this isn't missed.

  I happened to do an apt upgrade like this:

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
irqbalance libcaca-dev libcaca0 libmysqlclient20 libvirt-clients 
libvirt-daemon libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvirt0 
psmisc qemu qemu-block-extra qemu-kvm qemu-system qemu-system-arm 
qemu-system-common qemu-system-data qemu-system-gui
qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-s390x 
qemu-system-sparc qemu-system-x86 qemu-user-static qemu-utils snapd 
ubuntu-core-launcher ubuntu-snappy ubuntu-snappy-cli
  30 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 82,8 MB of archives.
  After this operation, 6.298 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Abort.

  
  The "bug" now is that thie "Abort" at the end was not my decision.
  It directly went to that.
  dist-upgrade did the same.

  I was puzzled at first, did an `apt update` to be sure but the problem
  continued to trigger.

  One thing that I found was that on update I saw a message like this:
  E: The repository 'http://ppa.launchpad.net/ci-train-ppa-service/3520/ubuntu 
cosmic Release' no longer has a Release file.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  That is correct this PPA was deleted a while ago, but that should not kill 
the upgrade right?
  I removed the files, updated and now things are working fine:
$ sudo rm 
/etc/apt/sources.list.d/ci-train-ppa-service-ubuntu-3520-cosmic.list*
$ sudo apt update
 [...]
$ sudo apt upgrade (now working)

  This might be an intentional protection against "lost repos" but then
  there should be a better message?

  I'll file it as low prio, let me know what you think.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814243/+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 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is

2019-02-01 Thread Frederick Gibson
frederick@graphMetrix-1:~$ sudo apt --fix-broken install
[sudo] password for frederick: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libsdl-ttf2.0-0 linux-headers-4.18.0-10 linux-headers-4.18.0-10-generic
  linux-image-4.18.0-10-generic linux-modules-4.18.0-10-generic
  linux-modules-extra-4.18.0-10-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libelf1:i386 libwayland-client0:i386 libwayland-server0:i386
The following NEW packages will be installed:
  libelf1:i386 libwayland-client0:i386 libwayland-server0:i386
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
7 not fully installed or removed.
Need to get 0 B/104 kB of archives.
After this operation, 367 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 276791 files and directories currently installed.)
Preparing to unpack .../libelf1_0.170-0.5.0ubuntu1_i386.deb ...
Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack):
 trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which 
is different from other instances of package libelf1:i386
Preparing to unpack .../libwayland-client0_1.16.0-1ubuntu1.1_i386.deb ...
Unpacking libwayland-client0:i386 (1.16.0-1ubuntu1.1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libwayland-client0_1.16.0-1ubuntu1.1_i386.deb 
(--unpack):
 trying to overwrite shared 
'/usr/share/doc/libwayland-client0/changelog.Debian.gz', which is different 
from other instances of package libwayland-client0:i386
Preparing to unpack .../libwayland-server0_1.16.0-1ubuntu1.1_i386.deb ...
Unpacking libwayland-server0:i386 (1.16.0-1ubuntu1.1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libwayland-server0_1.16.0-1ubuntu1.1_i386.deb 
(--unpack):
 trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
Errors were encountered while processing:
 /var/cache/apt/archives/libelf1_0.170-0.5.0ubuntu1_i386.deb
 /var/cache/apt/archives/libwayland-client0_1.16.0-1ubuntu1.1_i386.deb
 /var/cache/apt/archives/libwayland-server0_1.16.0-1ubuntu1.1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package libwayland-server0 1.16.0-1ubuntu1.1 failed to
  install/upgrade: trying to overwrite shared '/usr/share/doc
  /libwayland-server0/changelog.Debian.gz', which is different from
  other instances of package libwayland-server0:i386

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  Trying to install nvidia-driver-390 on Dell XPS 15 6570

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libwayland-server0 1.16.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jan 31 18:32:20 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-14-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed
  DuplicateSignature:
   package:libwayland-server0:1.16.0-1ubuntu1.1
   Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', 
which is different from other instances of package libelf1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2019-01-31 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 

[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2019-02-01 Thread Treviño
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Triaged
Status in upower source package in Cosmic:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is

2019-02-01 Thread Frederick Gibson
frederick@graphMetrix-1:~$ sudo dpkg -P libnvidia-gl-390:i386 
libgl1-mesa-dri:i386
[sudo] password for frederick: 
dpkg: dependency problems prevent removal of libnvidia-gl-390:i386:
 libnvidia-ifr1-390:i386 depends on libnvidia-gl-390.

dpkg: error processing package libnvidia-gl-390:i386 (--purge):
 dependency problems - not removing
dpkg: dependency problems prevent removal of libgl1-mesa-dri:i386:
 libglx-mesa0:i386 depends on libgl1-mesa-dri.

dpkg: error processing package libgl1-mesa-dri:i386 (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libnvidia-gl-390:i386
 libgl1-mesa-dri:i386

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

Title:
  package libwayland-server0 1.16.0-1ubuntu1.1 failed to
  install/upgrade: trying to overwrite shared '/usr/share/doc
  /libwayland-server0/changelog.Debian.gz', which is different from
  other instances of package libwayland-server0:i386

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  Trying to install nvidia-driver-390 on Dell XPS 15 6570

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libwayland-server0 1.16.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jan 31 18:32:20 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-14-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed
  DuplicateSignature:
   package:libwayland-server0:1.16.0-1ubuntu1.1
   Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', 
which is different from other instances of package libelf1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2019-01-31 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: wayland
  Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0HWTMH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:

[Touch-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is

2019-02-01 Thread Frederick Gibson
I'm also getting a Segmentation Fault with Gimp:

```
GNU Image Manipulation Program version 2.10.6
git-describe: GIMP_2_10_4-278-g0a8173ffde
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
8.2.0-4ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-8 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto 
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-4ubuntu1) 

using GEGL version 0.4.8 (compiled against version 0.4.8)
using GLib version 2.58.1 (compiled against version 2.57.2)
using GdkPixbuf version 2.38.0 (compiled against version 2.36.12)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.0 (compiled against version 2.13.0)
using Cairo version 1.15.12 (compiled against version 1.15.12)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 9501 - Thread 9501 #

[New LWP 9502]
[New LWP 9503]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (fd=12, buf=0x7ffd389644d0, nbytes=256) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target IdFrame 
* 1Thread 0x7fc9dee16e00 (LWP 9501) "gimp-2.10" __libc_read (fd=12, 
buf=0x7ffd389644d0, nbytes=256) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7fc9dcf25700 (LWP 9502) "gmain" 0x7fc9e1c9c6d9 in 
__GI___poll (fds=0x558c28f8feb0, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  3Thread 0x7fc9dc724700 (LWP 9503) "gdbus" 0x7fc9e1c9c6d9 in 
__GI___poll (fds=0x558c28fa9890, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29

Thread 3 (Thread 0x7fc9dc724700 (LWP 9503)):
#0  0x7fc9e1c9c6d9 in __GI___poll (fds=0x558c28fa9890, nfds=2, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
sc_ret = 
#1  0x7fc9e1f73e46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7fc9e1f741d2 in g_main_loop_run () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3  0x7fc9e28ef7b6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
No symbol table info available.
#4  0x7fc9e1f9c135 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5  0x7fc9e1d80164 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140504963630848, 
8221769982414159155, 140725552829518, 140725552829519, 140725552829648, 
140504963627264, -8247743653170905805, -8247679106546401997}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 
#6  0x7fc9e1ca8def in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.

Thread 2 (Thread 0x7fc9dcf25700 (LWP 9502)):
#0  0x7fc9e1c9c6d9 in __GI___poll (fds=0x558c28f8feb0, nfds=1, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
sc_ret = 
#1  0x7fc9e1f73e46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7fc9e1f73f6c in g_main_context_iteration () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3  0x7fc9e1f73fb1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7fc9e1f9c135 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5  0x7fc9e1d80164 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = 

[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2019-02-01 Thread Agustin Barto
$ apt-cache policy linux-image-generic upower gnome-control-center gnome-shell
linux-image-generic:
  Installed: 4.18.0.14.15
  Candidate: 4.18.0.14.15
  Version table:
 *** 4.18.0.14.15 500
500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 4.18.0.13.14 500
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu cosmic-security/main amd64 Packages
 4.18.0.10.11 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
upower:
  Installed: 0.99.8-2ubuntu0.2
  Candidate: 0.99.8-2ubuntu0.2
  Version table:
 *** 0.99.8-2ubuntu0.2 500
500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 0.99.8-2ubuntu0.1 500
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
 0.99.8-2 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
gnome-control-center:
  Installed: 1:3.30.2-1ubuntu0.18.10.2
  Candidate: 1:3.30.2-1ubuntu0.18.10.2
  Version table:
 *** 1:3.30.2-1ubuntu0.18.10.2 500
500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:3.30.2-1ubuntu0.18.10.1 500
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
 1:3.30.1-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
gnome-shell:
  Installed: 3.30.2-0ubuntu1.18.10.1
  Candidate: 3.30.2-0ubuntu1.18.10.1
  Version table:
 *** 3.30.2-0ubuntu1.18.10.1 500
500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 3.30.1-2ubuntu1.18.10.2 500
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
 3.30.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Triaged
Status in upower source package in Cosmic:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log 

[Touch-packages] [Bug 1814243] Re: apt update decides to abort on its own

2019-02-01 Thread Julian Andres Klode
Did you switch terminals in between or reset it?

Those should not be related, it sounds more like a terminal screwup.
Like, sometimes, at  least in gnome-terminal, it reaches a point where
readline and friends fail for some reason.

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

Title:
  apt update decides to abort on its own

Status in apt package in Ubuntu:
  New

Bug description:
  Hi,
  I saw this by accident and I'm not sure if it is a bug or if it just was a 
bad config.
  But I wanted to report to be sure this isn't missed.

  I happened to do an apt upgrade like this:

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
irqbalance libcaca-dev libcaca0 libmysqlclient20 libvirt-clients 
libvirt-daemon libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvirt0 
psmisc qemu qemu-block-extra qemu-kvm qemu-system qemu-system-arm 
qemu-system-common qemu-system-data qemu-system-gui
qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-s390x 
qemu-system-sparc qemu-system-x86 qemu-user-static qemu-utils snapd 
ubuntu-core-launcher ubuntu-snappy ubuntu-snappy-cli
  30 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 82,8 MB of archives.
  After this operation, 6.298 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Abort.

  
  The "bug" now is that thie "Abort" at the end was not my decision.
  It directly went to that.
  dist-upgrade did the same.

  I was puzzled at first, did an `apt update` to be sure but the problem
  continued to trigger.

  One thing that I found was that on update I saw a message like this:
  E: The repository 'http://ppa.launchpad.net/ci-train-ppa-service/3520/ubuntu 
cosmic Release' no longer has a Release file.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  That is correct this PPA was deleted a while ago, but that should not kill 
the upgrade right?
  I removed the files, updated and now things are working fine:
$ sudo rm 
/etc/apt/sources.list.d/ci-train-ppa-service-ubuntu-3520-cosmic.list*
$ sudo apt update
 [...]
$ sudo apt upgrade (now working)

  This might be an intentional protection against "lost repos" but then
  there should be a better message?

  I'll file it as low prio, let me know what you think.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814243/+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 1814243] [NEW] apt update decides to abort on its own

2019-02-01 Thread Christian Ehrhardt 
Public bug reported:

Hi,
I saw this by accident and I'm not sure if it is a bug or if it just was a bad 
config.
But I wanted to report to be sure this isn't missed.

I happened to do an apt upgrade like this:

$ sudo apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  irqbalance libcaca-dev libcaca0 libmysqlclient20 libvirt-clients 
libvirt-daemon libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvirt0 
psmisc qemu qemu-block-extra qemu-kvm qemu-system qemu-system-arm 
qemu-system-common qemu-system-data qemu-system-gui
  qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-s390x 
qemu-system-sparc qemu-system-x86 qemu-user-static qemu-utils snapd 
ubuntu-core-launcher ubuntu-snappy ubuntu-snappy-cli
30 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 82,8 MB of archives.
After this operation, 6.298 kB of additional disk space will be used.
Do you want to continue? [Y/n] Abort.


The "bug" now is that thie "Abort" at the end was not my decision.
It directly went to that.
dist-upgrade did the same.

I was puzzled at first, did an `apt update` to be sure but the problem
continued to trigger.

One thing that I found was that on update I saw a message like this:
E: The repository 'http://ppa.launchpad.net/ci-train-ppa-service/3520/ubuntu 
cosmic Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.

That is correct this PPA was deleted a while ago, but that should not kill the 
upgrade right?
I removed the files, updated and now things are working fine:
  $ sudo rm 
/etc/apt/sources.list.d/ci-train-ppa-service-ubuntu-3520-cosmic.list*
  $ sudo apt update
   [...]
  $ sudo apt upgrade (now working)

This might be an intentional protection against "lost repos" but then
there should be a better message?

I'll file it as low prio, let me know what you think.

** Affects: apt (Ubuntu)
 Importance: Low
 Status: New

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

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

Title:
  apt update decides to abort on its own

Status in apt package in Ubuntu:
  New

Bug description:
  Hi,
  I saw this by accident and I'm not sure if it is a bug or if it just was a 
bad config.
  But I wanted to report to be sure this isn't missed.

  I happened to do an apt upgrade like this:

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
irqbalance libcaca-dev libcaca0 libmysqlclient20 libvirt-clients 
libvirt-daemon libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvirt0 
psmisc qemu qemu-block-extra qemu-kvm qemu-system qemu-system-arm 
qemu-system-common qemu-system-data qemu-system-gui
qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-s390x 
qemu-system-sparc qemu-system-x86 qemu-user-static qemu-utils snapd 
ubuntu-core-launcher ubuntu-snappy ubuntu-snappy-cli
  30 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 82,8 MB of archives.
  After this operation, 6.298 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Abort.

  
  The "bug" now is that thie "Abort" at the end was not my decision.
  It directly went to that.
  dist-upgrade did the same.

  I was puzzled at first, did an `apt update` to be sure but the problem
  continued to trigger.

  One thing that I found was that on update I saw a message like this:
  E: The repository 'http://ppa.launchpad.net/ci-train-ppa-service/3520/ubuntu 
cosmic Release' no longer has a Release file.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  That is correct this PPA was deleted a while ago, but that should not kill 
the upgrade right?
  I removed the files, updated and now things are working fine:
$ sudo rm 
/etc/apt/sources.list.d/ci-train-ppa-service-ubuntu-3520-cosmic.list*
$ sudo apt update
 [...]
$ sudo apt upgrade (now working)

  This might be an intentional protection against "lost repos" but then
  there should be a better message?

  I'll file it as low prio, let me know what you think.

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

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

[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2019-02-01 Thread Rodrigo Guariento
I forgot... I'm using Ubuntu 18.04 LTS with all updates up to date.

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
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  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:

[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2019-02-01 Thread Rodrigo Guariento
I am facing the same problem with 2 wired connections. No matter what I
do, if I connect with 1st ethernet or switch to 2nd wired, the problem
persists. After boot up, when the problem starts, I switch the cable of
ethernet and temporally the problem finishes.

$ sudo lshw -C network
[sudo] password for rodrigo: 
  *-network 
   description: Ethernet interface
   product: I211 Gigabit Network Connection
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:04:00.0
   logical name: enp4s0
   version: 03
   serial: 1c:1b:0d:63:ab:3b
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi msix pciexpress bus_master cap_list ethernet 
physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=igb 
driverversion=5.4.0-k duplex=full firmware=0. 6-1 ip=192.168.0.106 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
   resources: irq:16 memory:dfd0-dfd1 ioport:d000(size=32) 
memory:dfd2-dfd23fff
  *-network DISABLED
   description: Wireless interface
   product: Wireless 8260
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:05:00.0
   logical name: wlp5s0
   version: 3a
   serial: e4:a4:71:62:32:bb
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=4.15.0-45-generic firmware=34.0.1 latency=0 link=no multicast=yes 
wireless=IEEE 802.11
   resources: irq:131 memory:dfc0-dfc01fff
  *-network
   description: Ethernet interface
   product: Ethernet Connection (2) I219-V
   vendor: Intel Corporation
   physical id: 1f.6
   bus info: pci@:00:1f.6
   logical name: enp0s31f6
   version: 31
   serial: 1c:1b:0d:63:ab:39
   capacity: 1Gbit/s
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=3.2.6-k firmware=0.8-4 latency=0 link=no multicast=yes 
port=twisted pair
   resources: irq:123 memory:dff0-dff1


Here my syslog with the steps: after started the system, connection fine; when 
I started web navigation, the connection failed; I turned off and turned on the 
wired connection using Wired Settings (GUI); connection fine again; connection 
failed again in few seconds; I turned off and turned on the wired connection 
using Wired Settings (GUI) again; connection fine again; connection failed 
again in few seconds; I turned off wired connection, and turned on the wi-fi 
connection; wi-fi working fine during some minutes; I turned off wi-fi and 
turned on wired again; wired connection working fine till now. Here the syslog:

$ cat /var/log/syslog | grep NetworkManager
Feb  1 07:12:08 guari NetworkManager[928]:   [1549012328.4405] manager: 
NetworkManager state is now CONNECTED_GLOBAL
Feb  1 07:12:08 guari dbus-daemon[898]: [system] Activating via systemd: 
service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 
pid=928 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Feb  1 07:12:08 guari whoopsie[1440]: [07:12:08] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/2
Feb  1 07:12:08 guari whoopsie[1440]: [07:12:08] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/2
Feb  1 07:12:08 guari whoopsie[1440]: [07:12:08] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/2
Feb  1 07:54:49 guari NetworkManager[928]:   [1549014889.3226] manager: 
rfkill: WiFi hardware radio set disabled
Feb  1 07:54:49 guari NetworkManager[928]:   [1549014889.3227] device 
(wlp5s0): state change: activated -> unavailable (reason 'none', 
sys-iface-state: 'managed')
Feb  1 07:54:49 guari NetworkManager[928]:   [1549014889.3584] dhcp4 
(wlp5s0): canceled DHCP transaction, DHCP client pid 8049
Feb  1 07:54:49 guari NetworkManager[928]:   [1549014889.3584] dhcp4 
(wlp5s0): state changed bound -> done
Feb  1 07:54:49 guari NetworkManager[928]:   [1549014889.3607] manager: 
NetworkManager state is now CONNECTED_SITE
Feb  1 07:54:49 guari NetworkManager[928]:   [1549014889.3637] manager: 
NetworkManager state is now CONNECTED_LOCAL
Feb  1 07:54:49 guari dbus-daemon[898]: [system] Activating via systemd: 
service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 
pid=928 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Feb  1 07:54:49 guari NetworkManager[928]:   [1549014889.3645] manager: 
NetworkManager state is now DISCONNECTED
Feb  1 07:54:49 guari 

[Touch-packages] [Bug 1814236] [NEW] I find my computer slowing down lately quite a lot

2019-02-01 Thread kobusvw
Public bug reported:

It seems the computer is slowing down and many times come up with a
debug message following.. I'd like a diagnostic and see what is causing
it to slow down so much. it's only a few months old and I thought it
would be much faster, writing emails it would take up to a minute to
show what has been written, changing from one to tab to another it would
power down and come back after some seconds, and my internet speed is
50mb.

I don't know if it is just the CPU, or the HDD or if it is internal,
where it comes from, is it a security risk, or what,.. please help me
out here. Thank you

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
BootLog:
 Scanning for Btrfs filesystems
 UBUNTU: clean, 514825/59645952 files, 40614007/238562048 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Feb  1 10:41:27 2019
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:078c]
InstallationDate: Installed on 2018-04-10 (296 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
MachineType: Dell Inc. Inspiron 15-3567
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic.efi.signed 
root=UUID=1884da87-6e02-4e02-8fb8-2c4d61ffc172 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.3.0
dmi.board.name: 0FGN4M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.0:bd02/06/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 15-3567
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jan 21 17:49:01 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5595 
 vendor CMN
xserver.version: 2:1.18.4-0ubuntu0.8

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


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

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

Title:
  I find my computer slowing down lately quite a lot

Status in xorg package in Ubuntu:
  New

Bug description:
  It seems the computer is slowing down and many times come up with a
  debug message following.. I'd like a diagnostic and see what is
  causing it to slow down so much. it's only a few months old and I
  thought it would be much faster, writing emails it would take up to a
  minute to show what has been written, changing from one to tab to
  another it would power down and come back after some seconds, and my
  internet speed is 50mb.

  I don't know if it is just the CPU, or the HDD or if it is internal,
  where it comes from, is it a security risk, or what,.. please help me
  out here. Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 514825/59645952 files, 40614007/238562048 blocks
  CompizPlugins: No value set for 

[Touch-packages] [Bug 1814235] [NEW] error reports

2019-02-01 Thread ismael jabr
Public bug reported:

Failed to start Process error reports when automatic reporting is
enabled.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.11
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Feb  1 11:49:23 2019
InstallationDate: Installed on 2019-01-08 (23 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Dell System Inspiron N4110
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=ad0093a3-2f77-455d-ae55-b1d6d778d01d ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 05TM8C
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemInspironN4110:pvr:rvnDellInc.:rn05TM8C:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: HuronRiver System
dmi.product.name: Dell System Inspiron N4110
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  error reports

Status in systemd package in Ubuntu:
  New

Bug description:
  Failed to start Process error reports when automatic reporting is
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.11
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Feb  1 11:49:23 2019
  InstallationDate: Installed on 2019-01-08 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Dell System Inspiron N4110
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=ad0093a3-2f77-455d-ae55-b1d6d778d01d ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 05TM8C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemInspironN4110:pvr:rvnDellInc.:rn05TM8C:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System Inspiron N4110
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1814235/+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 1814124] Re: sshd does not start after update

2019-02-01 Thread Christian Ehrhardt 
Hi,
I took a fresh system and it had openssh-server installed right away (as it is 
part of all the base images).
/var/run/sshd was at 0755 root:root already

I was wondering if the package install would kill the permission/ownership, so 
I did
  $ apt install --reinstall openssh-server
But things stayed fine.

Ok, then I purged the package and removed the path to then install it from 
scratch.
  $ apt remove --purge openssh-server
  $ rmdir /var/run/sshd
# ensured that /var/run/sshd really doesn't exist anymore
  $ apt install  openssh-server

The path is back and permissions are ok.

I can't find how you got into this situation :-/
I'm puzzled:
- from what to what do you upgrade trusty -> xenial or just a package version 
in xenial?
- do you have any idea where the bad permissions on /var/run/sshd might come in 
your case?
- if you follow my second example of purge, rmdir, install does the path get 
created correctly on your system?

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

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

Title:
  sshd does not start after update

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  After processing system update by:
  apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update && 
apt-get upgrade && apt-get dist-upgrade && reboot

  ssh server stops starting at system boot.

  It starts after doing:
  mkdir /var/run/sshd
  chmod 0755 /var/run/sshd
  service ssh start

  It happens on fresh Ubuntu-16.04 installs on every VPS provide I have
  tested so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.6
  Uname: Linux 2.6.32-042stab127.2 x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jan 31 10:18:56 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1814124/+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 1812095] Re: console login loop after entering username followed by RETURN

2019-02-01 Thread Florian
I'm also unable to login to my machine anymore. I can confirm the issue
for

linux-image-4.15.0-44-generic

I'm currently booting into linux-image-4.15.0-43-generic where the bug
doesn't exist.

Using Ubuntu 18.04.1 server.

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

Title:
  console login loop after entering username followed by RETURN

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
   login: 
  password:

  Just do nothing. About two seconds later ...

  login:
  password:

  login:
  password:

  login:
  password:

  After this being displayed three times:

  "Too many failure" or so and login is restarting.

  You cant login at all. Only solution: clear the password for the
  account you want to login with.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 16 19:34:30 2019
  InstallationDate: Installed on 2011-10-19 (2645 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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