date:20180913

OK.

Please:

1. Open 'Settings'. If you can't find it just tap the Windows key and
type 'Settings'.

2. In Settings go to 'Sound' and choose the 'Applications' tab.

3. Reduce the volume for the affected app (while the app is running),
and if that doesn't work then reduce the main 'Output volume' slider.

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

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

Title:
  Pulse audio problems

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  murtyvonna@Asuscomp:~$ pulseaudio -v
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  I: [pulseaudio] core-util.c: Successfully gained nice level -11.
  I: [pulseaudio] main.c: This is PulseAudio 11.1
  I: [pulseaudio] main.c: Page size is 4096 bytes
  I: [pulseaudio] main.c: Machine ID is 03451321bb634f75a15b69d305fd15fe.
  I: [pulseaudio] main.c: Session ID is 2.
  I: [pulseaudio] main.c: Using runtime directory /run/user/1000/pulse.
  I: [pulseaudio] main.c: Using state directory /home/murtyvonna/.config/pulse.
  I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-11.1/modules.
  I: [pulseaudio] main.c: Running in system mode: no
  E: [pulseaudio] pid.c: Daemon already running.
  E: [pulseaudio] main.c: pa_pid_file_create() failed.
  murtyvonna@Asuscomp:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  murtyvonna   3169 F pulseaudio
   /dev/snd/controlC0:  murtyvonna   3169 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 13 13:32:21 2018
  InstallationDate: Installed on 2018-08-06 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1402:bd03/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2018-09-13 Thread Jan-Jonas Sämann

This stupid behavior isn't only inconvinient,

-> this really BREAKS FUNCTIONALITY if you work on network resources.

Especially in Germany where possible internet speeds in many locations
do not exeed well known dialup connection speeds.

What happens then is a complete lockup on nautilus while the filelists
are queried again from the remote site. This usually takes minutes to
complete.

-- 
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 878986] Re: amixer -q sset Master toggle does mute, but does not unmute!

2018-09-13 Thread jimbo1qaz

I need this bug to be fixed. The issue is I am routing Pulseaudio
through JACK plugin, and "amixer -D pulse" only mutes apps playing
through PulseAudio but not JACK Audio, and is consequently not a working
solution for me.

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

Title:
  amixer -q sset Master toggle does mute, but does not unmute!

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  I am using keyboard shortcuts to increase/decrease/mute volume by executing:
  amixer -q sset Master 5+
  amixer -q sset Master 5-
  amixer -q sset Master toggle

  From when I have updated to Ubuntu 11.10, 'amixer sset Master toggle'
  does mute the volume, but when i execute it again it does not unmute
  it. In command line, it looks fine:

  :~$ amixer sset Master toggle
  Simple mixer control 'Master',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
Playback channels: Mono
Limits: Playback 0 - 31
Mono: Playback 16 [52%] [-22.50dB] [off]

  :~$ amixer sset Master toggle
  Simple mixer control 'Master',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
Playback channels: Mono
Limits: Playback 0 - 31
Mono: Playback 16 [52%] [-22.50dB] [on]

  but it remains muted. I use pavucontrol to unmute sound from the GUI.

  
  Info:
  :~$ apt-cache policy alsa-utils
  alsa-utils:
Installed: 1.0.24.2-0ubuntu8
Candidate: 1.0.24.2-0ubuntu8
Version table:
   *** 1.0.24.2-0ubuntu8 0
  500 http://rs.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status

  :~$ lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  instructor  19328 F pulseaudio
   /dev/snd/pcmC0D0p:   instructor  19328 F...m pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe9f8000 irq 43'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,1043829f,0012'
 Controls  : 37
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfeafc000 irq 44'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,0010'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Thu Oct 20 19:31:13 2011
  HibernationDevice: RESUME=UUID=cf6e9ff7-a63e-457c-aba4-706765c58de1
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer P5K
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=5611c46a-40ee-4ded-bbda-b8365335826b ro acpi_enforce_resources=lax 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (3 days ago)
  dmi.bios.date: 07/03/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0603
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0603:bd07/03/2007:svnSystemmanufacturer:pnP5K:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5K
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  instructor  19328 F pulseaudio
   /dev/snd/pcmC0D0p:   instructor  19328 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe9f8000 irq 43'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,1043829f,0012'
 Controls  : 37
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfeafc000 irq 44'
 Mixer name :

[Touch-packages] [Bug 1791324] Re: /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-gtk@598:run_argv:run_crashes:run_crash

2018-09-13 Thread Brian Murray

Ah actually, I think my apport versions were mismatched. As we can see
below python3-apport was updated but apport-gtk and apport were not.


105 Start-Date: 2018-09-13  11:00:45
106 Commandline: apt install apport-retrace
107 Requested-By: bdmurray (1000)
108 Install: apport-retrace:amd64 (2.20.9-0ubuntu7.3)
109 Upgrade: python3-apport:amd64 (2.20.9-0ubuntu7.2, 2.20.9-0ubuntu7.3)
110 End-Date: 2018-09-13  11:00:47
111 
112 Start-Date: 2018-09-13  15:25:13
113 Commandline: apt-get install apport-gtk
114 Requested-By: bdmurray (1000)
115 Upgrade: apport-gtk:amd64 (2.20.9-0ubuntu7.2, 2.20.9-0ubuntu7.3)
116 End-Date: 2018-09-13  15:25:13
117 
118 Start-Date: 2018-09-13  15:26:03
119 Commandline: apt-get install apport
120 Requested-By: bdmurray (1000)
121 Upgrade: apport:amd64 (2.20.9-0ubuntu7.2, 2.20.9-0ubuntu7.3)
122 End-Date: 2018-09-13  15:26:08

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

Title:
  /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-
  gtk@598:run_argv:run_crashes:run_crash

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

Bug description:
  [Impact]
   * The Ubuntu Error Tracker has been receiving reports about a problem 
regarding apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu5, the problem page at 
https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee
   * The theory is that those crashes are trigger by reports generated (but not 
send) pre apport 2.20.9-0ubuntu7.3. They don't hafe thus the "remember" key, 
and thus, the new apport, when reporting, is crashing.
   * We now ignore if the key isn't present and just consider the answer as 
"false", which is a no-op.

  [Test Case]
   * Install apport 2.20.9-0ubuntu7.1
   * Generate a crash but don't report it.
   * Upgrade to apport apport 2.20.9-0ubuntu7.3
   * Report this crash.
     -> No apport crash should be triggered

  [Regression Potential]
   * We are doing a python2 compatible try/except to ignore the KeyError which 
was the regression. It doesn't seem it can trigger other regressions.

  ---

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1791324/+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 1791324] Re: /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-gtk@598:run_argv:run_crashes:run_crash

2018-09-13 Thread Brian Murray

I received this crash today and I believe it happened because I had
closed a previous apport crash dialog by using the "x" in the upper
right hand corner.

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

Title:
  /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport-
  gtk@598:run_argv:run_crashes:run_crash

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

Bug description:
  [Impact]
   * The Ubuntu Error Tracker has been receiving reports about a problem 
regarding apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu5, the problem page at 
https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee
   * The theory is that those crashes are trigger by reports generated (but not 
send) pre apport 2.20.9-0ubuntu7.3. They don't hafe thus the "remember" key, 
and thus, the new apport, when reporting, is crashing.
   * We now ignore if the key isn't present and just consider the answer as 
"false", which is a no-op.

  [Test Case]
   * Install apport 2.20.9-0ubuntu7.1
   * Generate a crash but don't report it.
   * Upgrade to apport apport 2.20.9-0ubuntu7.3
   * Report this crash.
     -> No apport crash should be triggered

  [Regression Potential]
   * We are doing a python2 compatible try/except to ignore the KeyError which 
was the regression. It doesn't seem it can trigger other regressions.

  ---

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1791324/+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 1639513] Re: Pango-WARNING **: shaping failure, expect ugly output

2018-09-13 Thread Tong Sun

That's an entirely different issue, as Manfred has put it,

This is support for Ubuntu only, and not for other operating systems
"based on Ubuntu" like elementary OS.

No matter how close you think yours is to Ubuntu, if it is not then it
is not.

Please don't spill your own problem over to other unrelated issues.
Thanks.

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

Title:
  Pango-WARNING **: shaping failure, expect ugly output

Status in pango1.0 package in Ubuntu:
  Confirmed

Bug description:
  Exactly as reported in
  https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1396048, which
  was marked as "Invalid" because it is reporting to the wrong package.

  The problem from that post:

  Console:

  $ evince

  (evince:8959): Pango-WARNING **: failed to create cairo scaled font, expect 
ugly output. the offending font is 'Ubuntu 11'
  (evince:8959): Pango-WARNING **: font_face status is: out of memory
  (evince:8959): Pango-WARNING **: scaled_font status is: out of memory
  (evince:8959): Pango-WARNING **: shaping failure, expect ugly output. 
shape-engine='BasicEngineFc', font='Ubuntu 11', text='●'

  As for mine, it is basically the same:

  (process:13924): Pango-WARNING **: failed to create cairo scaled font, expect 
ugly output. the offending font is '微软雅黑 9'
  (process:13924): Pango-WARNING **: font_face status is: file not found
  (process:13924): Pango-WARNING **: scaled_font status is: file not found
  (process:13924): Pango-WARNING **: shaping failure, expect ugly output. 
shape-engine='PangoFcShapeEngine', font='微软雅黑 9', text='Ayg'

  As the result,

  For the original reported, "some font and only displays squares in
  menus, text is displayed okay,", but for me, everything are displays
  as squares in menus, including English texts.

  However, my rxvt-unicode, which uses the 微软雅黑 font, display correctly
  without any problem.

  The cause of the problem, is also exactly as described in the original
  post:

  It happens because of symlinks from /usr/share/fonts to a different
  partition. For the original reporter, some fonts are symlinked, and
  for me 微软雅黑 is symlinked to a different partition. Thus his is missing
  some text, while I'm missing everything.

  symlinking fonts to a different partition is quite harmless in my
  view, and Pango should not treat them any differently.

  This only happens since Ubuntu 16.04. In Ubuntu 15.10, it was OK.

  My current Pango related packages that exhibit such problem:

   gir1.2-pango-1.0:amd64_1.38.1-1
   libcogl-pango20:amd64_1.22.0-2
   libpango-1.0-0:amd64_1.38.1-1
   libpango-perl_1.227-1
   libpango1.0-0:amd64_1.38.1-1
   libpangocairo-1.0-0:amd64_1.38.1-1
   libpangoft2-1.0-0:amd64_1.38.1-1
   libpangomm-1.4-1v5:amd64_2.38.1-1
   libpangox-1.0-0:amd64_0.0.2-5
   libpangoxft-1.0-0:amd64_1.38.1-1

  Please look into it. Thx.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1639513/+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 1792464] [NEW] package linux-image-4.15.0-1017-oem 4.15.0-1017.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2018-09-13 Thread Tomasz Dudziak

Public bug reported:

installation failed

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1017-oem 4.15.0-1017.20
ProcVersionSignature: Ubuntu 4.15.0-1017.20-oem 4.15.18
Uname: Linux 4.15.0-1017-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Tue Sep 11 00:43:51 2018
Df:
 
Dmesg:
 
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
InstallationDate: Installed on 2018-08-30 (14 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
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.3ubuntu0.1
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-1017-oem 4.15.0-1017.20 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-1017-oem 4.15.0-1017.20 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  installation failed

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1017-oem 4.15.0-1017.20
  ProcVersionSignature: Ubuntu 4.15.0-1017.20-oem 4.15.18
  Uname: Linux 4.15.0-1017-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Tue Sep 11 00:43:51 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  InstallationDate: Installed on 2018-08-30 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  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.3ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-1017-oem 4.15.0-1017.20 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1792464/+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 1792464] Re: package linux-image-4.15.0-1017-oem 4.15.0-1017.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2018-09-13 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.15.0-1017-oem 4.15.0-1017.20 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  installation failed

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1017-oem 4.15.0-1017.20
  ProcVersionSignature: Ubuntu 4.15.0-1017.20-oem 4.15.18
  Uname: Linux 4.15.0-1017-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Tue Sep 11 00:43:51 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  InstallationDate: Installed on 2018-08-30 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  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.3ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-1017-oem 4.15.0-1017.20 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1792464/+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 1792458] [NEW] [HP 655 Notebook PC, ATI R6xx HDMI, Digital Out, HDMI] No sound at all

2018-09-13 Thread James Reinholm

Public bug reported:

Hi, The sound didn't work in Windows 10 either, so I reinstalled the
sound driver (RealTime), and it worked. Bu when I switch to Ubuntu, it
still sees the old sound driver, which was a Digital Audio (S/PDIF)
device, and sound still doesn't work. I tried various things with
pulseaudio and pavucontrol, but it didn't help.

Thanks,
James R.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jreinholm   2171 F pulseaudio
 /dev/snd/controlC0:  jreinholm   2171 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 13 16:28:08 2018
InstallationDate: Installed on 2018-08-21 (23 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Built-in Audio - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm 992 F pulseaudio
  jreinholm   2171 F pulseaudio
 /dev/snd/controlC0:  gdm 992 F pulseaudio
  jreinholm   2171 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [HP 655 Notebook PC, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.29
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1885
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 66.34
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.29:bd05/08/2014:svnHewlett-Packard:pnHP655NotebookPC:pvr087F11305B10002620110:rvnHewlett-Packard:rn1885:rvr66.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=655
dmi.product.name: HP 655 Notebook PC
dmi.product.version: 087F11305B10002620110
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug bionic

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

Title:
  [HP 655 Notebook PC, ATI R6xx HDMI, Digital Out, HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, The sound didn't work in Windows 10 either, so I reinstalled the
  sound driver (RealTime), and it worked. Bu when I switch to Ubuntu, it
  still sees the old sound driver, which was a Digital Audio (S/PDIF)
  device, and sound still doesn't work. I tried various things with
  pulseaudio and pavucontrol, but it didn't help.

  Thanks,
  James R.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jreinholm   2171 F pulseaudio
   /dev/snd/controlC0:  jreinholm   2171 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 13 16:28:08 2018
  InstallationDate: Installed on 2018-08-21 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm 992 F pulseaudio
jreinholm   2171 F pulseaudio
   /dev/snd/controlC0:  gdm 992 F pulseaudio
jreinholm   2171 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [HP 655 Notebook PC, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1885
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 66.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard

[Touch-packages] [Bug 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css

2018-09-13 Thread John Avery

I see this problem when running gio open of a Google maps location query
URL.

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

Title:
  Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
  builder.css

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
  line

  @import url("apps/gnome-builder.css");

  But this file does not exist in this package or any other, as far as I
  can tell from apt-file.  This triggers an annoying warning when
  running various applications (e.g. evince):

  (evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
  gtk-main.css:73:38: Failed to import: Error opening file
  /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
  file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 18:58:41 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+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 520546] Re: Alt-f2 switches to virtual terminal 2

2018-09-13 Thread Tuomas Suutari

I can reproduce the bug in Ubuntu 18.04.1 by re-configuring keyboard-
configuration package (version 1.178ubuntu2.7) with DISPLAY being
unset/empty, e.g.:

tuomas@matta:~ 0 $ sudo DISPLAY= DEBIAN_FRONTEND=noninteractive \
   dpkg-reconfigure keyboard-configuration
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-33-generic

And after running this Alt+F2 switches to VT2 even from X11.  When
switching back to X11 (with Alt+F1), it appears that the Alt+F2 also
goes to X11, since the krunner popup opens (bound to Alt+F2).

Running "sudo kbd_mode -s" in a terminal window within X11 makes the
Alt+Fx keys act normally again.

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+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 1639513] Re: Pango-WARNING **: shaping failure, expect ugly output

2018-09-13 Thread Sapa Holliday

I am using libpango-1.0-0, version 1.38.1-1 and can't open or convert a
.swf adobe flash file.

I notice that you are using ... libpango1.0-0:amd64_1.38.1-1

Yet you are also using  libpango-1.0-0:amd64_1.38.1-1

You might have a conflict there

I have linked mine to your bug report at -
https://answers.launchpad.net/ubuntu/+source/pango1.0/+question/673809

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

Title:
  Pango-WARNING **: shaping failure, expect ugly output

Status in pango1.0 package in Ubuntu:
  Confirmed

Bug description:
  Exactly as reported in
  https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1396048, which
  was marked as "Invalid" because it is reporting to the wrong package.

  The problem from that post:

  Console:

  $ evince

  (evince:8959): Pango-WARNING **: failed to create cairo scaled font, expect 
ugly output. the offending font is 'Ubuntu 11'
  (evince:8959): Pango-WARNING **: font_face status is: out of memory
  (evince:8959): Pango-WARNING **: scaled_font status is: out of memory
  (evince:8959): Pango-WARNING **: shaping failure, expect ugly output. 
shape-engine='BasicEngineFc', font='Ubuntu 11', text='●'

  As for mine, it is basically the same:

  (process:13924): Pango-WARNING **: failed to create cairo scaled font, expect 
ugly output. the offending font is '微软雅黑 9'
  (process:13924): Pango-WARNING **: font_face status is: file not found
  (process:13924): Pango-WARNING **: scaled_font status is: file not found
  (process:13924): Pango-WARNING **: shaping failure, expect ugly output. 
shape-engine='PangoFcShapeEngine', font='微软雅黑 9', text='Ayg'

  As the result,

  For the original reported, "some font and only displays squares in
  menus, text is displayed okay,", but for me, everything are displays
  as squares in menus, including English texts.

  However, my rxvt-unicode, which uses the 微软雅黑 font, display correctly
  without any problem.

  The cause of the problem, is also exactly as described in the original
  post:

  It happens because of symlinks from /usr/share/fonts to a different
  partition. For the original reporter, some fonts are symlinked, and
  for me 微软雅黑 is symlinked to a different partition. Thus his is missing
  some text, while I'm missing everything.

  symlinking fonts to a different partition is quite harmless in my
  view, and Pango should not treat them any differently.

  This only happens since Ubuntu 16.04. In Ubuntu 15.10, it was OK.

  My current Pango related packages that exhibit such problem:

   gir1.2-pango-1.0:amd64_1.38.1-1
   libcogl-pango20:amd64_1.22.0-2
   libpango-1.0-0:amd64_1.38.1-1
   libpango-perl_1.227-1
   libpango1.0-0:amd64_1.38.1-1
   libpangocairo-1.0-0:amd64_1.38.1-1
   libpangoft2-1.0-0:amd64_1.38.1-1
   libpangomm-1.4-1v5:amd64_2.38.1-1
   libpangox-1.0-0:amd64_0.0.2-5
   libpangoxft-1.0-0:amd64_1.38.1-1

  Please look into it. Thx.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1639513/+subscriptions

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

[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

2018-09-13 Thread Steve Langasek

Marked verification-failed for clarity due to the build failures.
Andrea, are you blocked on sponsorship for fixing protobuf?

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  Fix Committed
Status in py-macaroon-bakery source package in Xenial:
  In Progress
Status in pymacaroons source package in Xenial:
  Fix Committed
Status in httmock source package in Artful:
  Invalid
Status in protobuf source package in Artful:
  Invalid
Status in py-macaroon-bakery source package in Artful:
  In Progress
Status in pymacaroons source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

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

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

[Touch-packages] [Bug 1763098] Re: Multiple memory corruption in gprof (binuitils-2.30-15ubuntu1)

This bug is already fixed in the latest version present in bionic-
security - marking as verified.

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

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

Title:
  Multiple memory corruption in gprof (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Committed

Bug description:
  Dear all,
  The following binutils gprof memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  Run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./gprof $file
  ```

  
  We can verify those issues for gprof binuitils-2.30-15ubuntu1 (Ubuntu 16.04.4 
LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763098/+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 1769657] Re: update toolchain packages for bionic

Hello Matthias, or anyone else affected,

Accepted binutils into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.30-21ubuntu1~18.04 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!

** Changed in: binutils (Ubuntu Bionic)
   Status: New => Fix Committed

** 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 binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1769657

Title:
  update toolchain packages for bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in build-essential package in Ubuntu:
  New
Status in cross-toolchain-base package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New
Status in binutils source package in Bionic:
  Fix Committed

Bug description:
  I'd like to update the toolchain packages in bionic, to state which we
  have in cosmic on May 07:

   - LP: #1771635: binutils updates from the branch
   - gcc-8, update to the final 8.1.0 release
   - gcc-7, updates to the gcc-7-branch up to the time of the
     8.1.0 release.
   - gcc-defaults to bump the 8.1 version, and add some provides
   - build-essential to add cross packages for amd64 and i386
   - corresponding gcc-cross packages

  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages

  [Impact]
  Provide an upstream release for GCC 8, and update GCC 7 fixes to the
  date of the corresponding GCC 8 updates.

  [Regression Potential]
  There is regression potential, however with a test rebuild of the main 
portion of the archive no regressions were found.

  [Test Case]
  No regressions in the GCC test suite, and no regressions in the test
  rebuild of the main component of the archive (all architectures)

  As a test, a complete archive rebuild (main only) was performed, and
  no regressions were found with this new package. The archive rebuild
  also contained updated versions of gcc-7, gcc-8, binutils, python3.6
  and python3.7. The GCC and Python packages should not infer with each
  other.

  [Validation]
  Analyze the build logs for regressions.
  For the cross builds, just make sure that the packages build using
  the updated sources.

  Summary of the test rebuilds:
  file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html

  No regressions are shown with the test rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+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 1763096] Re: Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1)

This bug is already fixed in the latest version present in bionic-
security - marking as verified.

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

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

Title:
  Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Committed

Bug description:
  Dear all,
  The following binutils as-new memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./as-new $file
  ```

  We can verify those issues for as-new binuitils-2.30-15ubuntu1 (Ubuntu
  16.04.4 LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763096/+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 1763096] Re: Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1)

Hello Sergej, or anyone else affected,

Accepted binutils into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.30-21ubuntu1~18.04 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!

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

** 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 binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1763096

Title:
  Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Committed

Bug description:
  Dear all,
  The following binutils as-new memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./as-new $file
  ```

  We can verify those issues for as-new binuitils-2.30-15ubuntu1 (Ubuntu
  16.04.4 LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763096/+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 1763094] Re: Multiple memory corruption in ld-new (binuitils-2.30-15ubuntu1)

Hello Sergej, or anyone else affected,

Accepted binutils into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.30-21ubuntu1~18.04 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!

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

** 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 binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1763094

Title:
  Multiple memory corruption in ld-new (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Committed

Bug description:
  Dear all,
  The following binutils ld-new memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  Run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./ld-new $file
  ```

  We can verify those issues for ld-new binuitils-2.30-15ubuntu1 (Ubuntu
  16.04.4 LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763094/+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 1763094] Re: Multiple memory corruption in ld-new (binuitils-2.30-15ubuntu1)

This bug is already fixed in the latest version present in bionic-
security - marking as verified.

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

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

Title:
  Multiple memory corruption in ld-new (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Committed

Bug description:
  Dear all,
  The following binutils ld-new memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  Run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./ld-new $file
  ```

  We can verify those issues for ld-new binuitils-2.30-15ubuntu1 (Ubuntu
  16.04.4 LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763094/+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 1763098] Re: Multiple memory corruption in gprof (binuitils-2.30-15ubuntu1)

Hello Sergej, or anyone else affected,

Accepted binutils into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.30-21ubuntu1~18.04 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!

** Changed in: binutils (Ubuntu Bionic)
   Status: New => Fix Committed

** 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 binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1763098

Title:
  Multiple memory corruption in gprof (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Committed

Bug description:
  Dear all,
  The following binutils gprof memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  Run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./gprof $file
  ```

  
  We can verify those issues for gprof binuitils-2.30-15ubuntu1 (Ubuntu 16.04.4 
LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763098/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2018-09-13 Thread Balint Reczey

@kudalufi If apt-get does not remove the kernels they must have been set
o manually installed which prevents u-u and update-manager from removing
them, too. Please remove the ones set manually installed manually.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

2018-09-13 Thread Balint Reczey

Fixed update-manager is stuck in phasing because it triggered old bugs
like LP: #1791931 with the removals.

If you run sudo apt-get install update-manager to bypass phasing it will
remove the old kernels which are not marked manually installed.

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  New
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  New
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+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 1769657] Re: update toolchain packages for bionic

2018-09-13 Thread Matthias Klose

** Description changed:

  I'd like to update the toolchain packages in bionic, to state which we
  have in cosmic on May 07:
  
   - LP: #1771635: binutils updates from the branch
   - gcc-8, update to the final 8.1.0 release
   - gcc-7, updates to the gcc-7-branch up to the time of the
     8.1.0 release.
   - gcc-defaults to bump the 8.1 version, and add some provides
   - build-essential to add cross packages for amd64 and i386
   - corresponding gcc-cross packages
  
  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages
  
- There is regression potential, however with a test rebuild of the main
- portion of the archive no regressions were found.
+ [Impact]
+ Provide an upstream release for GCC 8, and update GCC 7 fixes to the
+ date of the corresponding GCC 8 updates.
+ 
+ [Regression Potential]
+ There is regression potential, however with a test rebuild of the main 
portion of the archive no regressions were found.
+ 
+ [Test Case]
+ No regressions in the GCC test suite, and no regressions in the test
+ rebuild of the main component of the archive (all architectures)
  
  As a test, a complete archive rebuild (main only) was performed, and no
  regressions were found with this new package. The archive rebuild also
  contained updated versions of gcc-7, gcc-8, binutils, python3.6 and
  python3.7. The GCC and Python packages should not infer with each other.
  
+ [Validation]
+ Analyze the build logs for regressions.
+ For the cross builds, just make sure that the packages build using
+ the updated sources.
+ 
  Summary of the test rebuilds:
  file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html
  
  No regressions are shown with the test rebuild.

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

Title:
  update toolchain packages for bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in build-essential package in Ubuntu:
  New
Status in cross-toolchain-base package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New

Bug description:
  I'd like to update the toolchain packages in bionic, to state which we
  have in cosmic on May 07:

   - LP: #1771635: binutils updates from the branch
   - gcc-8, update to the final 8.1.0 release
   - gcc-7, updates to the gcc-7-branch up to the time of the
     8.1.0 release.
   - gcc-defaults to bump the 8.1 version, and add some provides
   - build-essential to add cross packages for amd64 and i386
   - corresponding gcc-cross packages

  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages

  [Impact]
  Provide an upstream release for GCC 8, and update GCC 7 fixes to the
  date of the corresponding GCC 8 updates.

  [Regression Potential]
  There is regression potential, however with a test rebuild of the main 
portion of the archive no regressions were found.

  [Test Case]
  No regressions in the GCC test suite, and no regressions in the test
  rebuild of the main component of the archive (all architectures)

  As a test, a complete archive rebuild (main only) was performed, and
  no regressions were found with this new package. The archive rebuild
  also contained updated versions of gcc-7, gcc-8, binutils, python3.6
  and python3.7. The GCC and Python packages should not infer with each
  other.

  [Validation]
  Analyze the build logs for regressions.
  For the cross builds, just make sure that the packages build using
  the updated sources.

  Summary of the test rebuilds:
  file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html

  No regressions are shown with the test rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+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 1767950] Re: /lib/systemd/systemd-journald:6:fsync:journal_file_set_online:journal_file_append_object:journal_file_append_data:journal_file_append_entry

2018-09-13 Thread Brian Murray

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

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

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

Title:
  /lib/systemd/systemd-
  
journald:6:fsync:journal_file_set_online:journal_file_append_object:journal_file_append_data:journal_file_append_entry

Status in systemd package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1767950/+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 1792358] Re: Update to 2.0.0 (next cycle or ffe)

2018-09-13 Thread Matthias Klose

Usually it's good enough to update the Ubuntu packaging with a new
upstream version.  In any case Debian and Ubuntu will always have a
delta because of the different JPEG version support (6 vs 8).

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

Title:
  Update to 2.0.0 (next cycle or ffe)

Status in libjpeg-turbo package in Ubuntu:
  Triaged

Bug description:
  The new version would be nice to get but it's not in Debian yet and it
  has quite some non trivial changes, it would require a ffe if we
  wanted to update this cycle. Tagging as blocked by ff for now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1792358/+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 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails

2018-09-13 Thread Dimitri John Ledkov

I'm not sure what vaultlocker is.

trigger might be appropriate together with a '--settle' flag, if/where
available.

instead of manually opening things, i'd expect crypttab to be adjusted
with `systemctl daemon-reload` re-run to regenerated systemd-cryptsetup@
units and "open" the encrytped device using systemd-cryptsetup@ instance
unit However that might be "too" systemd specific for vaultcrypt
upstream...

If one injects uuid onto a drive, it might not generate any kernel udev
events for udevd to react to and create/update symlinks.

It would be nice to have an interleaved log of udev events from udevadm
monitor, to see if there are any events emitted after "format" action is
done. If there are none, then vaultlocker needs to be fixed to trigger
things.

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

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

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

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

Title:
  vaultlocker does not ensure that udev is triggered to create /dev/disk
  /by-uuid/ symlink and fails

Status in vaultlocker:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When an encrypted device is setup up a UUID (osd_fsid) is passed from
  the charm to be used in the cryptsetup command which accepts a UUID to
  place into the LUKS header (shown in cryptsetup luksDump ).

  
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
 
  UUID comes from osd_fsid

  
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
  # else statement is used here
   block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid

   dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS 
header
  # ...
   dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper 
decrypting it via dmcrypt

  https://github.com/openstack-
  
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56

  This UUID is visible in blkid output

  /dev/sdc: UUID="" TYPE="crypto_LUKS"

  and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
  resolution)

  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
  ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

  
  Where vaultlocker fails is in luks_open command (right after luks_format) 

   # cryptsetup --batch-mode --key-file - open UUID=
  crypt- --type luks

  because it tries to access /dev/disk/by-uuid/ which
  does not exist.

  This happens since udev rules are not re-triggered to create this
  symlink after a LUKS device is created.

  Solution: call the command below after luks_format before luks_open

  udevadm settle --exit-if-exists=/dev/disk/by-uuid/

To manage notifications about this bug go to:
https://bugs.launchpad.net/vaultlocker/+bug/1780332/+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 1792231] Re: openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding'

I wanted to check if other releases are affected as well, but it was
interesting as it didn't show up even on a Trusty container ssh'ing to
itself.


ubuntu@t:~$ unset DISPLAY ; ssh -X ubuntu@localhost 'dpkg -l openssh-client | 
grep ii'
ubuntu@localhost's password: 
ii  openssh-client 1:7.2p2-4ubuntu2.4 amd64secure shell (SSH) client, 
for secure access to remote machines

No issue, to be seen.

@Santiago - do you know what the secret ingredient to trigger the bug
might be?

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

** Also affects: openssh (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908652
   Importance: Unknown
   Status: Unknown

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

Title:
  openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding'

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Triaged
Status in openssh package in Debian:
  Unknown

Bug description:
   affects ubuntu/openssh

  Hi,

  This bug is present in openssh in ubuntu trusty, I haven't tested other
  releases. When X11 forwarding is enabled (via ssh_config, or via -X),
  but no DISPLAY is available, ssh client produces this warning:

  DISPLAY "(null)" invalid; disabling X11 forwarding

  
  root@ubuntu-trusty:/# unset DISPLAY ; ssh -X ubuntu@localhost 'dpkg -l 
openssh-client | grep ii'
  ubuntu@localhost's password: 
  DISPLAY "(null)" invalid; disabling X11 forwarding
  ii  openssh-client  1:6.6p1-2ubuntu2.10   
 amd64secure shell (SSH) client, for secure access to remote machines

  The bug was introduced by the changes to fix CVE-2016-1908.
  This upstream change fixes it:

  
https://anongit.mindrot.org/openssh.git/commit/?id=5658ef2501e785fbbdf5de2dc33b1ff7a4dca73a

  See https://bugs.debian.org/908652

  Cheers,

   -- S

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1792231/+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 1792231] Re: openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding'

Ok, some magic affects containers int hat case (even ssh to the LXD and then 
re-ssh to itelf would not work).
But in a KVM guest I could recreate it.

$ ssh -X ubuntu@localhost uname -a
ubuntu@localhost's password: 
DISPLAY "(null)" invalid; disabling X11 forwarding
Linux t1 3.13.0-157-generic #207-Ubuntu SMP Mon Aug 20 16:44:59 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding'

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Triaged
Status in openssh package in Debian:
  Unknown

Bug description:
   affects ubuntu/openssh

  Hi,

  This bug is present in openssh in ubuntu trusty, I haven't tested other
  releases. When X11 forwarding is enabled (via ssh_config, or via -X),
  but no DISPLAY is available, ssh client produces this warning:

  DISPLAY "(null)" invalid; disabling X11 forwarding

  
  root@ubuntu-trusty:/# unset DISPLAY ; ssh -X ubuntu@localhost 'dpkg -l 
openssh-client | grep ii'
  ubuntu@localhost's password: 
  DISPLAY "(null)" invalid; disabling X11 forwarding
  ii  openssh-client  1:6.6p1-2ubuntu2.10   
 amd64secure shell (SSH) client, for secure access to remote machines

  The bug was introduced by the changes to fix CVE-2016-1908.
  This upstream change fixes it:

  
https://anongit.mindrot.org/openssh.git/commit/?id=5658ef2501e785fbbdf5de2dc33b1ff7a4dca73a

  See https://bugs.debian.org/908652

  Cheers,

   -- S

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1792231/+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 1788188] Re: transient systemd ordering cycle in boot with overlayroot

2018-09-13 Thread Scott Moser

@xnox,
Are you suggesting the /media/root-ro entry in /etc/fstab line for
/media/root-ro should have x-systemd.DefaultDependencies=no ?

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

Title:
  transient systemd ordering cycle in boot with overlayroot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  open-iscsi test utilizes overlayroot to boot a cloud-image with root
  filesystem on a read-only iscsi server.

  The /etc/fstab file in the image looks like this:
    LABEL=cloudimg-rootfs   /ext4   defaults0 0
    #LABEL=UEFI /boot/efi   vfatdefaults0 0

  when init takes over from the initramfs, we have

    /proc/cmdline:
  nomodeset iscsi_initiator=maas-enlist
  iscsi_target_name=tgt-boot-test-2abbnj iscsi_target_ip=10.0.12.2
  iscsi_target_port=3260 iscsi_initiator=maas-enlist
  ip=maas-enlist:BOOTIF ro net.ifnames=0 BOOTIF_DEFAULT=eth0
  
root=/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1
  overlayroot=tmpfs console=ttyS0
  ds=nocloud-net;seedfrom=http://10.0.12.2:32600/ init=/bin/bash

    /etc/fstab:
  # cat /etc/fstab
  #
  #  This fstab is in an overlay. The real one can be found at
  #  /media/root-ro/etc/fstab
  #  The original entry for '/' and other mounts have been updated to be 
placed
  #  under /media/root-ro.
  #  To permanently modify this (or any other file), you should change-root 
into
  #  a writable view of the underlying filesystem using:
  #  sudo overlayroot-chroot
  #
  #LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
  /media/root-ro/ / overlay 
lowerdir=/media/root-ro/,upperdir=/media/root-rw/over0
  #LABEL=UEFI /boot/efi vfat defaults 0 0

   /root/root-ro/etc/fstab:
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  #LABEL=UEFI /boot/efi   vfatdefaults0 0

   /proc/mounts:
     sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
     proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
     udev /dev devtmpfs 
rw,nosuid,relatime,size=233748k,nr_inodes=58437,mode=755 0 0
     devpts /dev/pts devpts 
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
     tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=49288k,mode=755 0 0
     /dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 
/media/root-ro ext4 ro,relatime 0 0
     tmpfs-root /media/root-rw tmpfs rw,relatime 0 0
     overlayroot / overlay 
ro,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
 0 0

   /proc/1/mountinfo:
     21 28 0:20 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
     22 28 0:4 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
     23 28 0:6 / /dev rw,nosuid,relatime - devtmpfs udev 
rw,size=233748k,nr_inodes=58437,mode=755
     24 23 0:21 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts 
rw,gid=5,mode=620,ptmxmode=000
     25 28 0:22 / /run rw,nosuid,noexec,relatime - tmpfs tmpfs 
rw,size=49288k,mode=755
     26 28 8:1 / /media/root-ro ro,relatime - ext4 
/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 ro
     27 28 0:23 / /media/root-rw rw,relatime - tmpfs tmpfs-root rw
     28 0 0:24 / / ro,relatime - overlay overlayroot 
ro,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_

  overlayroot's scripts/init-bottom/overlayroot script [1] inherits a
  read-only mount of block device on mount point '$ROOTMNT'
  (ROOTMNT=/root). In order to set up the overlayroot, it does the
  following:

   mkdir /media/root-ro /media/root-rw # in the initramfs
   mount -t tmpfs tmpfs-root /media/root-rw
   mkdir /media/root-rw/overlay-workdir/_
   mount --move $ROOTMNT /media/root-ro
   mount -t overlay -o 
lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
 overlayroot /root
   mkdir $ROOTMNT/media/root-ro
   mkdir $ROOTMNT/media/root-rw
   mount --move /media/root-ro "${ROOTMNT}/media/root-ro"
   mount --move /media/root-rw "${ROOTMNT}/media/root-rw"

   # then, if 'ro' on the command line, it mounts /root read-only.
   mount -o remount,ro $ROOTMNT

  The script then exits, as ROOTMNT is now set up with a read-only mount
  of the overlayroot.  All the mounts it has done have been moved
  under ROOTMNT.

  On failure systemd reports:
     [  104.098833] systemd[1]: media-root\x2dro.mount: Found ordering cycle on 
-.mount/start
     [  104.109897] systemd[1]: media-root\x2dro.mount: Found dependency on 
media-root\x2dro.mount/start
     [  104.121386] systemd[1]: media-root\x2dro.mount: Unable to break cycle 
starting with media-root\x2dro.mount/start
     [  104.137591] systemd[1]: Requested transaction contains an unfixable 
cyclic ordering

[Touch-packages] [Bug 1792231] Re: openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding'

2018-09-13 Thread Bug Watch Updater

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

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

Title:
  openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding'

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Triaged
Status in openssh package in Debian:
  Fix Released

Bug description:
   affects ubuntu/openssh

  Hi,

  This bug is present in openssh in ubuntu trusty, I haven't tested other
  releases. When X11 forwarding is enabled (via ssh_config, or via -X),
  but no DISPLAY is available, ssh client produces this warning:

  DISPLAY "(null)" invalid; disabling X11 forwarding

  
  root@ubuntu-trusty:/# unset DISPLAY ; ssh -X ubuntu@localhost 'dpkg -l 
openssh-client | grep ii'
  ubuntu@localhost's password: 
  DISPLAY "(null)" invalid; disabling X11 forwarding
  ii  openssh-client  1:6.6p1-2ubuntu2.10   
 amd64secure shell (SSH) client, for secure access to remote machines

  The bug was introduced by the changes to fix CVE-2016-1908.
  This upstream change fixes it:

  
https://anongit.mindrot.org/openssh.git/commit/?id=5658ef2501e785fbbdf5de2dc33b1ff7a4dca73a

  See https://bugs.debian.org/908652

  Cheers,

   -- S

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1792231/+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 1773693] Re: xserver-xorg-video-nouveau requires reboot to apply changes

2018-09-13 Thread Balint Reczey

The package itself needs to place /var/run/reboot-required.

** Package changed: update-manager (Ubuntu) => xserver-xorg-video-
nouveau (Ubuntu)

** No longer affects: synaptic (Ubuntu)

** No longer affects: software-properties (Ubuntu)

** No longer affects: plasma-discover (Ubuntu)

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

Title:
  xserver-xorg-video-nouveau requires reboot to apply changes

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Using update-manager to install or update xserver-xorg-video-nouveau
  should prompt to reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1773693/+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 1792231] Re: openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding'

Xenial and Bionic are not affected, only Trusty

** Also affects: openssh (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Changed in: openssh (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding'

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Triaged
Status in openssh package in Debian:
  Unknown

Bug description:
   affects ubuntu/openssh

  Hi,

  This bug is present in openssh in ubuntu trusty, I haven't tested other
  releases. When X11 forwarding is enabled (via ssh_config, or via -X),
  but no DISPLAY is available, ssh client produces this warning:

  DISPLAY "(null)" invalid; disabling X11 forwarding

  
  root@ubuntu-trusty:/# unset DISPLAY ; ssh -X ubuntu@localhost 'dpkg -l 
openssh-client | grep ii'
  ubuntu@localhost's password: 
  DISPLAY "(null)" invalid; disabling X11 forwarding
  ii  openssh-client  1:6.6p1-2ubuntu2.10   
 amd64secure shell (SSH) client, for secure access to remote machines

  The bug was introduced by the changes to fix CVE-2016-1908.
  This upstream change fixes it:

  
https://anongit.mindrot.org/openssh.git/commit/?id=5658ef2501e785fbbdf5de2dc33b1ff7a4dca73a

  See https://bugs.debian.org/908652

  Cheers,

   -- S

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1792231/+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 1764779] Re: Nautilus crashed open Windows-partition [assertion failed: (location != NULL)]

Hello Lukas, or anyone else affected,

Accepted nautilus into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.26.4-0~ubuntu18.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!

** Changed in: nautilus (Ubuntu Bionic)
   Status: New => Fix Committed

** 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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1764779

Title:
  Nautilus crashed open Windows-partition [assertion failed: (location
  != NULL)]

Status in glib2.0 package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released
Status in nautilus source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  if I open a new partition from the Hard-drive (Windows in this case)
  Nautilus crash, report him self and after reopen it, the partition is
  normal available as nothing would be

  https://errors.ubuntu.com/problem/f49deb51a98d691e3e040d7f7334ad08d1e0e54c
  https://errors.ubuntu.com/problem/868bb572668dceedfb0e3acd9b17197ca0208938
  https://errors.ubuntu.com/problem/00db9958203affb0a98a2842bb2bd91547e6bd5a
  https://errors.ubuntu.com/problem/818d3ad2d9fe9f9f64f32fcb5f10da4126d3827d

  [ Test case ]

  * Open nautilus and select an external hd that is not mounted from the sidebar
  * Nautilus sould not crash (in case showing an error message)

  [ Regression potential ]

  Partitions that have been actually mounted, are not shown or an error
  is prompted.

  -

  Issue from the log:

  Apr 17 16:45:29 hostname udisksd[1014]: Failed to setup systemd-based mount 
point cleanup: Process reported exit code 5: Failed to start 
clean-mount-point@media-username-12F6CC77F6CC5D1B.service: Unit 
media-username-12F6CC77F6CC5D1B.mount not found.
  Apr 17 16:45:29 hostname nautilus[11486]: g_mount_get_default_location: 
assertion 'G_IS_MOUNT (mount)' failed
  Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: **
  Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: 
ERROR:../src/nautilus-file.c:721:nautilus_file_get_internal: assertion failed: 
(location != NULL)

  -

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 16:45:30 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' 
b'show-move-to-trash-shortcut-changed-dialog' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'927x1011+926+27'"
  InstallationDate: Installed on 2018-03-16 (32 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=de_DE.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1764779/+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 1788188] Re: transient systemd ordering cycle in boot with overlayroot

2018-09-13 Thread Dimitri John Ledkov

Note to self.

   umount.target
   A special target unit that unmounts all mount and automount points 
on system shutdown.

   Mounts that shall be unmounted on system shutdown shall add 
Conflicts dependencies to this unit for their mount unit, which is implicitly 
done
   when DefaultDependencies=yes is set (the default).

Given that /media/root-ro is a pre-requisite for /, imho it should be
declared with DefaultDependencies=no.

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

Title:
  transient systemd ordering cycle in boot with overlayroot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  open-iscsi test utilizes overlayroot to boot a cloud-image with root
  filesystem on a read-only iscsi server.

  The /etc/fstab file in the image looks like this:
    LABEL=cloudimg-rootfs   /ext4   defaults0 0
    #LABEL=UEFI /boot/efi   vfatdefaults0 0

  when init takes over from the initramfs, we have

    /proc/cmdline:
  nomodeset iscsi_initiator=maas-enlist
  iscsi_target_name=tgt-boot-test-2abbnj iscsi_target_ip=10.0.12.2
  iscsi_target_port=3260 iscsi_initiator=maas-enlist
  ip=maas-enlist:BOOTIF ro net.ifnames=0 BOOTIF_DEFAULT=eth0
  
root=/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1
  overlayroot=tmpfs console=ttyS0
  ds=nocloud-net;seedfrom=http://10.0.12.2:32600/ init=/bin/bash

    /etc/fstab:
  # cat /etc/fstab
  #
  #  This fstab is in an overlay. The real one can be found at
  #  /media/root-ro/etc/fstab
  #  The original entry for '/' and other mounts have been updated to be 
placed
  #  under /media/root-ro.
  #  To permanently modify this (or any other file), you should change-root 
into
  #  a writable view of the underlying filesystem using:
  #  sudo overlayroot-chroot
  #
  #LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
  /media/root-ro/ / overlay 
lowerdir=/media/root-ro/,upperdir=/media/root-rw/over0
  #LABEL=UEFI /boot/efi vfat defaults 0 0

   /root/root-ro/etc/fstab:
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  #LABEL=UEFI /boot/efi   vfatdefaults0 0

   /proc/mounts:
     sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
     proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
     udev /dev devtmpfs 
rw,nosuid,relatime,size=233748k,nr_inodes=58437,mode=755 0 0
     devpts /dev/pts devpts 
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
     tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=49288k,mode=755 0 0
     /dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 
/media/root-ro ext4 ro,relatime 0 0
     tmpfs-root /media/root-rw tmpfs rw,relatime 0 0
     overlayroot / overlay 
ro,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
 0 0

   /proc/1/mountinfo:
     21 28 0:20 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
     22 28 0:4 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
     23 28 0:6 / /dev rw,nosuid,relatime - devtmpfs udev 
rw,size=233748k,nr_inodes=58437,mode=755
     24 23 0:21 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts 
rw,gid=5,mode=620,ptmxmode=000
     25 28 0:22 / /run rw,nosuid,noexec,relatime - tmpfs tmpfs 
rw,size=49288k,mode=755
     26 28 8:1 / /media/root-ro ro,relatime - ext4 
/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 ro
     27 28 0:23 / /media/root-rw rw,relatime - tmpfs tmpfs-root rw
     28 0 0:24 / / ro,relatime - overlay overlayroot 
ro,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_

  overlayroot's scripts/init-bottom/overlayroot script [1] inherits a
  read-only mount of block device on mount point '$ROOTMNT'
  (ROOTMNT=/root). In order to set up the overlayroot, it does the
  following:

   mkdir /media/root-ro /media/root-rw # in the initramfs
   mount -t tmpfs tmpfs-root /media/root-rw
   mkdir /media/root-rw/overlay-workdir/_
   mount --move $ROOTMNT /media/root-ro
   mount -t overlay -o 
lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
 overlayroot /root
   mkdir $ROOTMNT/media/root-ro
   mkdir $ROOTMNT/media/root-rw
   mount --move /media/root-ro "${ROOTMNT}/media/root-ro"
   mount --move /media/root-rw "${ROOTMNT}/media/root-rw"

   # then, if 'ro' on the command line, it mounts /root read-only.
   mount -o remount,ro $ROOTMNT

  The script then exits, as ROOTMNT is now set up with a read-only mount
  of the overlayroot.  All the mounts it has done have been moved
  under ROOTMNT.

  On failure systemd reports:
     [  104.098833] systemd[1]: media-root\x2dro.mount: Found ordering cycle on 
-.mount/start

[Touch-packages] [Bug 1792231] Re: openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding'

Broken since security update on Thu, 05 May 2016
Fixed in Debian in openssh/1:6.7p1-5+deb8u7
Per the Debian bug they were affected as well re-using our CVE fixes in Debian.

I think we can use the changes taken for openssh/1:6.7p1-5+deb8u7 when they are 
visible.
Right now I don't see more yet, so it waits to be released there.

The fix looks rather trivial (thanks for linking) and we should take a
look at this soon.

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

** Tags added: server-next

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

Title:
  openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding'

Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  Unknown

Bug description:
   affects ubuntu/openssh

  Hi,

  This bug is present in openssh in ubuntu trusty, I haven't tested other
  releases. When X11 forwarding is enabled (via ssh_config, or via -X),
  but no DISPLAY is available, ssh client produces this warning:

  DISPLAY "(null)" invalid; disabling X11 forwarding

  
  root@ubuntu-trusty:/# unset DISPLAY ; ssh -X ubuntu@localhost 'dpkg -l 
openssh-client | grep ii'
  ubuntu@localhost's password: 
  DISPLAY "(null)" invalid; disabling X11 forwarding
  ii  openssh-client  1:6.6p1-2ubuntu2.10   
 amd64secure shell (SSH) client, for secure access to remote machines

  The bug was introduced by the changes to fix CVE-2016-1908.
  This upstream change fixes it:

  
https://anongit.mindrot.org/openssh.git/commit/?id=5658ef2501e785fbbdf5de2dc33b1ff7a4dca73a

  See https://bugs.debian.org/908652

  Cheers,

   -- S

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1792231/+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 1792370] Re: Broken links to libmircookie packages

2018-09-13 Thread Piotr Dabrowski

Most likely that's proxy problem. 'Cookie' keyword is scrambled in every
request. Tryig to figure this out.

** Changed in: mir (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Broken links to libmircookie packages

Status in mir package in Ubuntu:
  Invalid

Bug description:
  Can't install libmircookie via apt or dawnload from
  https://packages.ubuntu.com/xenial/libmircookie-dev. Every link to
  libmircookie package at
  http://security.ubuntu.com/ubuntu/pool/main/m/mir/ seems to be broken.
  Its wrong filename at server: libmircoieok instead libmircookie.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1792370/+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 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable

2018-09-13 Thread Peter I. Linkp

Can confirm this bug. After activating Bluetooth via Setting menu in
Ubuntu 18.04.1 the computer stay in a permanent bluetooth discoverable
mode and is connectable by external bluetooth devices until the next
system reboot.

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

Title:
  Ubuntu 18.04 LTS bluetooth left discoverable

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays
  discoverable which opens up unnecessary vulnerability surface. There
  should be a separate UI switch for discoverability with auto timeout.
  Leaving bluetooth on (using a Bluetooth mouse) should not leave the
  computer always discoverable.

  Current behavior does not match documentation
  https://help.ubuntu.com/stable/ubuntu-help/bluetooth-
  visibility.html.en, even without Bluetooth panel open, the computer is
  still discoverable.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

2018-09-13 Thread Nicorac

@Marcos: ebtables is ininfluent on my side.
It is installed with server version and the bug persists both with and without 
it.

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0

  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

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

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

  [Link]
  Name=myiface3

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

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

  The device is not renamed.

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

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

  === Original Bug ==

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

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

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

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

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

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

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

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

  So names are successfully changed with netplan apply.

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

  This

[Touch-packages] [Bug 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable

2018-09-13 Thread Launchpad Bug Tracker

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

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu 18.04 LTS bluetooth left discoverable

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays
  discoverable which opens up unnecessary vulnerability surface. There
  should be a separate UI switch for discoverability with auto timeout.
  Leaving bluetooth on (using a Bluetooth mouse) should not leave the
  computer always discoverable.

  Current behavior does not match documentation
  https://help.ubuntu.com/stable/ubuntu-help/bluetooth-
  visibility.html.en, even without Bluetooth panel open, the computer is
  still discoverable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+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 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option

2018-09-13 Thread Thadeu Lima de Souza Cascardo

** Patch added: "fix for cosmic"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+attachment/5188455/+files/initramfs-tools_0.131ubuntu11.debdiff

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

Title:
  initramfs-tools ignores the FRAMEBUFFER option

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Xenial:
  New
Status in initramfs-tools source package in Bionic:
  New

Bug description:
  initramfs-tools ignores the FRAMEBUFFER option. This means that the
  framebuffer hook will always include the drm modules, regardless of
  whether it is dealing with an encrypted system or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 24 18:06:24 2016
  InstallationDate: Installed on 2016-02-16 (37 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+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 1792326] Re: Pulse audio problems

2018-09-13 Thread murtyvo...@gmail.com

Thank you for the advice. When I was getting very very low sound in the
browsers while playing online, I googled and followed the guideline. I
do not find problem while playing anything from the hard disk with
installed apllications (with players), the problem is with online .

Regards

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

Title:
  Pulse audio problems

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  murtyvonna@Asuscomp:~$ pulseaudio -v
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  I: [pulseaudio] core-util.c: Successfully gained nice level -11.
  I: [pulseaudio] main.c: This is PulseAudio 11.1
  I: [pulseaudio] main.c: Page size is 4096 bytes
  I: [pulseaudio] main.c: Machine ID is 03451321bb634f75a15b69d305fd15fe.
  I: [pulseaudio] main.c: Session ID is 2.
  I: [pulseaudio] main.c: Using runtime directory /run/user/1000/pulse.
  I: [pulseaudio] main.c: Using state directory /home/murtyvonna/.config/pulse.
  I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-11.1/modules.
  I: [pulseaudio] main.c: Running in system mode: no
  E: [pulseaudio] pid.c: Daemon already running.
  E: [pulseaudio] main.c: pa_pid_file_create() failed.
  murtyvonna@Asuscomp:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  murtyvonna   3169 F pulseaudio
   /dev/snd/controlC0:  murtyvonna   3169 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 13 13:32:21 2018
  InstallationDate: Installed on 2018-08-06 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1402:bd03/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1792326/+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 1771749] Re: Ethernet connection lost after few minutes since starting

2018-09-13 Thread Kent Lion

XUbuntu 18.04 has been doing this since I upgraded a few days ago. No
error messages or any other sign that the Ethernet network connection
has been dropped. I first notice it when I try to do something on the
network and it times out. I haven't changed any network settings for
over a year, but this never happened with Xenial LTS, and I haven't
noticed any pattern to the occurrence vs what I happen to be doing at
the time, so I can't reproduce it at will.

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

Title:
  Ethernet connection lost after few minutes since starting

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

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion:

[Touch-packages] [Bug 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option

2018-09-13 Thread Dimitri John Ledkov

** Also affects: initramfs-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  initramfs-tools ignores the FRAMEBUFFER option

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Xenial:
  New
Status in initramfs-tools source package in Bionic:
  New

Bug description:
  initramfs-tools ignores the FRAMEBUFFER option. This means that the
  framebuffer hook will always include the drm modules, regardless of
  whether it is dealing with an encrypted system or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 24 18:06:24 2016
  InstallationDate: Installed on 2016-02-16 (37 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+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 1792370] Re: Broken links to libmircookie packages

2018-09-13 Thread Michał Sawicz

I can download them fine from here:

https://packages.ubuntu.com/xenial/amd64/libmircookie-dev/download

Also, http://security.ubuntu.com/ubuntu/pool/main/m/mir/ lists
libmircookie-dev and libmircookie2...

Any chance you have a mirror or proxy that does something weird?

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

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

Title:
  Broken links to libmircookie packages

Status in mir package in Ubuntu:
  Incomplete

Bug description:
  Can't install libmircookie via apt or dawnload from
  https://packages.ubuntu.com/xenial/libmircookie-dev. Every link to
  libmircookie package at
  http://security.ubuntu.com/ubuntu/pool/main/m/mir/ seems to be broken.
  Its wrong filename at server: libmircoieok instead libmircookie.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1792370/+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 1792370] [NEW] Broken links to libmircookie packages

2018-09-13 Thread Piotr Dabrowski

Public bug reported:

Can't install libmircookie via apt or dawnload from
https://packages.ubuntu.com/xenial/libmircookie-dev. Every link to
libmircookie package at
http://security.ubuntu.com/ubuntu/pool/main/m/mir/ seems to be broken.
Its wrong filename at server: libmircoieok instead libmircookie.

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


** Tags: libmircookie sdl

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

Title:
  Broken links to libmircookie packages

Status in mir package in Ubuntu:
  New

Bug description:
  Can't install libmircookie via apt or dawnload from
  https://packages.ubuntu.com/xenial/libmircookie-dev. Every link to
  libmircookie package at
  http://security.ubuntu.com/ubuntu/pool/main/m/mir/ seems to be broken.
  Its wrong filename at server: libmircoieok instead libmircookie.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1792370/+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 1785629] Re: [MIR] gupnp-av

2018-09-13 Thread Matthias Klose

** Changed in: gupnp-av (Ubuntu)
 Assignee: (unassigned) => Didier Roche (didrocks)

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

Title:
  [MIR] gupnp-av

Status in gupnp-av package in Ubuntu:
  New

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries, including the gupnp-dlna one

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is not being used during build, we are going 
to look at changing that

  * Dependendies

  The package uses standard desktop libraries that are already in main
  (gstreamer, glib)

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 3.9.8, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp-av/+bug/1785629/+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 1715376] Re: ip link add command return: Error: either "dev" is duplicate, or "enp1s0" is a garbage.

2018-09-13 Thread Po-Hsu Lin

It looks like this issue has been fixed by Seth in bug 1789566

I tried to run the ubuntu_cts_kernel test on a KVM node and it passed.
Mark this as Fix released.

Thanks

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Fix Released

** Changed in: iproute2 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  ip link add command return: Error: either "dev" is duplicate, or
  "enp1s0" is a garbage.

Status in ubuntu-kernel-tests:
  Fix Released
Status in iproute2 package in Ubuntu:
  Invalid

Bug description:
  With iproute2 3.12 on Trusty, command:
  sudo ip link add type veth peer enp1s0 name testveth0

  Will return:
  Error: either "dev" is duplicate, or "enp1s0" is a garbage.

  However, this command works fine since Xenial (iproute2 4.3.0)

  As we will need this for kenrel SRU testing, it will be great to have
  this fixed on Trusty.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: iproute2 3.12.0-2ubuntu1
  ProcVersionSignature: User Name 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic aarch64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: arm64
  Date: Wed Sep  6 10:54:47 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1715376/+subscriptions

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

2018-09-13 Thread Nicorac

Just tried with a fresh installed Ubuntu SERVER 18.04.1.
The interface now got renamed but IP address is not applied, both static and 
DHCP.

If I run "netplan apply" just after reboot+login, network interface is
configured correctly (again, both with static/DHCP address).

--
Just after reboot + login
--
# ifconfig -a
eth_lan: flags=4098  mtu 1500
ether 08:00:27:6b:d8:91  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 14  bytes 910 (910.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 14  bytes 910 (910.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

--
After netplan apply
--
# netplan apply
# ifconfig -a
eth_lan: flags=4163  mtu 1500
inet 10.0.3.200  netmask 255.255.0.0  broadcast 10.0.255.255
inet6 fe80::a00:27ff:fe6b:d891  prefixlen 64  scopeid 0x20
ether 08:00:27:6b:d8:91  txqueuelen 1000  (Ethernet)
RX packets 28739  bytes 2625648 (2.6 MB)
RX errors 0  dropped 3379  overruns 0  frame 0
TX packets 186  bytes 19916 (19.9 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 197  bytes 14182 (14.1 KB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 197  bytes 14182 (14.1 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

--
netplan config
--
# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
id0:
  match:
macaddress: 08:00:27:6b:d8:91
  set-name: eth_lan
#  dhcp4: true
  addresses: [ 10.0.3.200/16 ]
  gateway4: 10.0.0.1
  nameservers:
  addresses:
  - 8.8.4.4

I'm going to remove all of this netplan stuff and get back to old
working /ets/network/interface...

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0

  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

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

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

  [Link]
  Name=myiface3

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

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

  The device is not renamed.

  This

[Touch-packages] [Bug 1792355] [NEW] [ffe] Update to 1.4.3

2018-09-13 Thread Sebastien Bacher

Public bug reported:

Debian got the new version, it would be nice to have in cosmic now

** Affects: colord (Ubuntu)
 Importance: Wishlist
 Status: Invalid


** Tags: upgrade-software-version

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

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

Title:
  [ffe] Update to 1.4.3

Status in colord package in Ubuntu:
  Invalid

Bug description:
  Debian got the new version, it would be nice to have in cosmic now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1792355/+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 1792356] [NEW] [ffe] Update to 1.4.3

2018-09-13 Thread Sebastien Bacher

Public bug reported:

Debian got the new version, it would be nice to have in cosmic now

** Affects: colord (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: upgrade-software-version

** Changed in: colord (Ubuntu)
   Status: New => Triaged

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

Title:
  [ffe] Update to 1.4.3

Status in colord package in Ubuntu:
  Triaged

Bug description:
  Debian got the new version, it would be nice to have in cosmic now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1792356/+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 1792358] [NEW] Update to 2.0.0 (next cycle or ffe)

2018-09-13 Thread Sebastien Bacher

Public bug reported:

The new version would be nice to get but it's not in Debian yet and it
has quite some non trivial changes, it would require a ffe if we wanted
to update this cycle. Tagging as blocked by ff for now

** Affects: libjpeg-turbo (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: upgrade-software-version version-blocked-ff

** Tags added: version-blocked-ff

** Changed in: libjpeg-turbo (Ubuntu)
   Status: New => Triaged

** Summary changed:

- Update to 2.0.0
+ Update to 2.0.0 (next cycle or ffe)

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

Title:
  Update to 2.0.0 (next cycle or ffe)

Status in libjpeg-turbo package in Ubuntu:
  Triaged

Bug description:
  The new version would be nice to get but it's not in Debian yet and it
  has quite some non trivial changes, it would require a ffe if we
  wanted to update this cycle. Tagging as blocked by ff for now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1792358/+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 1792353] [NEW] package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

2018-09-13 Thread Dragoneye

Public bug reported:

Fresh install from live cd

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.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
Architecture: amd64
Date: Thu Sep 13 10:09:02 2018
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
PackageArchitecture: all
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: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Fresh install from live cd

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.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
  Architecture: amd64
  Date: Thu Sep 13 10:09:02 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  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: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: 
installed initramfs-tools 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/initramfs-tools/+bug/1792353/+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 1792353] Re: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2018-09-13 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Fresh install from live cd

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.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
  Architecture: amd64
  Date: Thu Sep 13 10:09:02 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  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: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: 
installed initramfs-tools 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/initramfs-tools/+bug/1792353/+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 1792326] Re: Pulse audio problems

The command 'pulseaudio -v' is not something you should be running. That
command attempts to start a new copy of pulseaudio (verbosely), which
will fail because you already have one running. So the 'pulseaudio -v'
command failing is not an error. Just don't run it.

What is wrong the machine that motivated you to run that command?
Also, what do you see in Settings (under Sound)?

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

Title:
  Pulse audio problems

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  murtyvonna@Asuscomp:~$ pulseaudio -v
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  I: [pulseaudio] core-util.c: Successfully gained nice level -11.
  I: [pulseaudio] main.c: This is PulseAudio 11.1
  I: [pulseaudio] main.c: Page size is 4096 bytes
  I: [pulseaudio] main.c: Machine ID is 03451321bb634f75a15b69d305fd15fe.
  I: [pulseaudio] main.c: Session ID is 2.
  I: [pulseaudio] main.c: Using runtime directory /run/user/1000/pulse.
  I: [pulseaudio] main.c: Using state directory /home/murtyvonna/.config/pulse.
  I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-11.1/modules.
  I: [pulseaudio] main.c: Running in system mode: no
  E: [pulseaudio] pid.c: Daemon already running.
  E: [pulseaudio] main.c: pa_pid_file_create() failed.
  murtyvonna@Asuscomp:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  murtyvonna   3169 F pulseaudio
   /dev/snd/controlC0:  murtyvonna   3169 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 13 13:32:21 2018
  InstallationDate: Installed on 2018-08-06 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1402:bd03/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1792326/+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 1792326] Re: Pulse audio problems

2018-09-13 Thread murtyvo...@gmail.com

when I open pulse audio volume control it will not open instantly. When I type 
in the terminal the out put is here:
murtyvonna@Asuscomp:~$ pulseaudio -v
I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not 
permitted
I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not 
permitted
I: [pulseaudio] core-util.c: Successfully gained nice level -11.
I: [pulseaudio] main.c: This is PulseAudio 11.1
I: [pulseaudio] main.c: Page size is 4096 bytes
I: [pulseaudio] main.c: Machine ID is 03451321bb634f75a15b69d305fd15fe.
I: [pulseaudio] main.c: Session ID is 2.
I: [pulseaudio] main.c: Using runtime directory /run/user/1000/pulse.
I: [pulseaudio] main.c: Using state directory /home/murtyvonna/.config/pulse.
I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-11.1/modules.
I: [pulseaudio] main.c: Running in system mode: no
I: [pulseaudio] main.c: System supports high resolution timers
I: [pulseaudio] cpu-x86.c: CPU flags: CMOV MMX SSE SSE2 SSE3 SSSE3 SSE4_1 
SSE4_2 
I: [pulseaudio] svolume_mmx.c: Initialising MMX optimized volume functions.
I: [pulseaudio] remap_mmx.c: Initialising MMX optimized remappers.
I: [pulseaudio] svolume_sse.c: Initialising SSE2 optimized volume functions.
I: [pulseaudio] remap_sse.c: Initialising SSE2 optimized remappers.
I: [pulseaudio] sconv_sse.c: Initialising SSE2 optimized conversions.
I: [pulseaudio] svolume_orc.c: Initialising ORC optimized volume functions.
I: [pulseaudio] module-device-restore.c: Successfully opened database file 
'/home/murtyvonna/.config/pulse/03451321bb634f75a15b69d305fd15fe-device-volumes'.
I: [pulseaudio] module.c: Loaded "module-device-restore" (index: #0; argument: 
"").
I: [pulseaudio] module-stream-restore.c: Successfully opened database file 
'/home/murtyvonna/.config/pulse/03451321bb634f75a15b69d305fd15fe-stream-volumes'.
I: [pulseaudio] module.c: Loaded "module-stream-restore" (index: #1; argument: 
"").
I: [pulseaudio] module-card-restore.c: Successfully opened database file 
'/home/murtyvonna/.config/pulse/03451321bb634f75a15b69d305fd15fe-card-database'.
I: [pulseaudio] module.c: Loaded "module-card-restore" (index: #2; argument: 
"").
I: [pulseaudio] module.c: Loaded "module-augment-properties" (index: #3; 
argument: "").
I: [pulseaudio] module.c: Loaded "module-switch-on-port-available" (index: #4; 
argument: "").
I: [pulseaudio] module.c: Loaded "module-switch-on-connect" (index: #5; 
argument: "").
I: [pulseaudio] (alsa-lib)utils.c: could not open configuration file 
/usr/share/alsa/ucm/USB Device 0x46d:0x825 at usb-:00:14.0-1, high 
speed/USB Device 0x46d:0x825 at usb-:00:14.0-1, high speed.conf
I: [pulseaudio] (alsa-lib)parser.c: error: could not parse configuration for 
card USB Device 0x46d:0x825 at usb-:00:14.0-1, high speed
I: [pulseaudio] (alsa-lib)utils.c: could not open configuration file 
/usr/share/alsa/ucm/USB Device 0x46d:0x825/USB Device 0x46d:0x825.conf
I: [pulseaudio] (alsa-lib)parser.c: error: could not parse configuration for 
card USB Device 0x46d:0x825
I: [pulseaudio] (alsa-lib)main.c: error: failed to import USB Device 
0x46d:0x825 use case configuration -2
I: [pulseaudio] alsa-ucm.c: UCM not available for card USB Device 0x46d:0x825
I: [pulseaudio] alsa-util.c: Device hw:1 doesn't support 44100 Hz, changed to 
48000 Hz.
I: [pulseaudio] alsa-util.c: Successfully attached to mixer 'hw:1'
I: [pulseaudio] alsa-util.c: Failed to set hardware parameters on plug:front:1: 
Invalid argument
I: [pulseaudio] alsa-util.c: Failed to set hardware parameters on 
plug:iec958:1: Invalid argument
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device hw:1: No such file or 
directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device front:1: No such file or 
directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device surround21:1: No such 
file or directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device surround40:1: No such 
file or directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device surround41:1: No such 
file or directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device surround50:1: No such 
file or directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device surround51:1: No such 
file or directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device surround71:1: No such 
file or directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed

[Touch-packages] [Bug 1563110]

2018-09-13 Thread bill.666

Hi is not merged on 4.16 / 4.17 / 4.18 / 4.19 for what ?


https://forum.manjaro.org/t/asus-e200ha-no-sound/44205/17
marcin19883 say : Kernel 4.19 RC1 Audio not working. No codec include. :(

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1563110]

2018-09-13 Thread bill.666

(In reply to Caitlyn Martin from comment #98)
> It is fixed in the 4.18 kernel but more than an updated kerne is
> required.  You also need an up to date version of alsa and the new
> codec to be included when the kernel is compiled.  The problem with
> Manjaro is almost certainly a Manjaro problem, not an upstream
> problem.
> 
> On Sat, Jul 14, 2018 at 4:15 AM,  
> wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=115531
> >
> > liberodark (bill@live.fr) changed:
> >
> >What|Removed |Added
> >
> 
> >  CC||bill@live.fr
> >
> > --- Comment #97 from liberodark (bill@live.fr) ---
> > Hi,
> >
> > But not work on manjaro 17.1.11 !
> > The bug is not fixed is not integrated to kernel no ?
> > Have possibility to merge driver on kernel 4.18 ?
> >
> > https://www.manjaro.fr/forum/viewtopic.php?f=19=8812=asus
> > https://forum.manjaro.org/t/asus-e200ha-no-sound/44205/7
> > https://bugzilla.kernel.org/show_bug.cgi?id=200491
> >
> > Cordialy
> >
> > --
> > You are receiving this mail because:
> > You are on the CC list for the bug.

And have view is not officialy merged arch and majanro is not implicated
for this problem.

Please make a official merge to add audio codec.

Cordialy

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1792167] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1792167/+attachment/5188325/+files/ProcCpuinfoMinimal.txt

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  Since Ubuntu switched to Gnome, display scaling does not work
  correctly. This is because my external monitor is detected as 7"
  although it is 32". All applications which use Qt auto scaling have
  huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+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 1792326] Re: Pulse audio problems

I don't see any real errors there.

What's not working?

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

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

Title:
  Pulse audio problems

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  murtyvonna@Asuscomp:~$ pulseaudio -v
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  I: [pulseaudio] core-util.c: Successfully gained nice level -11.
  I: [pulseaudio] main.c: This is PulseAudio 11.1
  I: [pulseaudio] main.c: Page size is 4096 bytes
  I: [pulseaudio] main.c: Machine ID is 03451321bb634f75a15b69d305fd15fe.
  I: [pulseaudio] main.c: Session ID is 2.
  I: [pulseaudio] main.c: Using runtime directory /run/user/1000/pulse.
  I: [pulseaudio] main.c: Using state directory /home/murtyvonna/.config/pulse.
  I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-11.1/modules.
  I: [pulseaudio] main.c: Running in system mode: no
  E: [pulseaudio] pid.c: Daemon already running.
  E: [pulseaudio] main.c: pa_pid_file_create() failed.
  murtyvonna@Asuscomp:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  murtyvonna   3169 F pulseaudio
   /dev/snd/controlC0:  murtyvonna   3169 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 13 13:32:21 2018
  InstallationDate: Installed on 2018-08-06 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1402:bd03/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1792326/+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 1792326] [NEW] Pulse audio problems

2018-09-13 Thread murtyvo...@gmail.com

Public bug reported:

murtyvonna@Asuscomp:~$ pulseaudio -v
I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not 
permitted
I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not 
permitted
I: [pulseaudio] core-util.c: Successfully gained nice level -11.
I: [pulseaudio] main.c: This is PulseAudio 11.1
I: [pulseaudio] main.c: Page size is 4096 bytes
I: [pulseaudio] main.c: Machine ID is 03451321bb634f75a15b69d305fd15fe.
I: [pulseaudio] main.c: Session ID is 2.
I: [pulseaudio] main.c: Using runtime directory /run/user/1000/pulse.
I: [pulseaudio] main.c: Using state directory /home/murtyvonna/.config/pulse.
I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-11.1/modules.
I: [pulseaudio] main.c: Running in system mode: no
E: [pulseaudio] pid.c: Daemon already running.
E: [pulseaudio] main.c: pa_pid_file_create() failed.
murtyvonna@Asuscomp:~$

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  murtyvonna   3169 F pulseaudio
 /dev/snd/controlC0:  murtyvonna   3169 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 13 13:32:21 2018
InstallationDate: Installed on 2018-08-06 (38 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1402
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V LK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1402:bd03/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug bionic

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

Title:
  Pulse audio problems

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  murtyvonna@Asuscomp:~$ pulseaudio -v
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  I: [pulseaudio] core-util.c: Successfully gained nice level -11.
  I: [pulseaudio] main.c: This is PulseAudio 11.1
  I: [pulseaudio] main.c: Page size is 4096 bytes
  I: [pulseaudio] main.c: Machine ID is 03451321bb634f75a15b69d305fd15fe.
  I: [pulseaudio] main.c: Session ID is 2.
  I: [pulseaudio] main.c: Using runtime directory /run/user/1000/pulse.
  I: [pulseaudio] main.c: Using state directory /home/murtyvonna/.config/pulse.
  I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-11.1/modules.
  I: [pulseaudio] main.c: Running in system mode: no
  E: [pulseaudio] pid.c: Daemon already running.
  E: [pulseaudio] main.c: pa_pid_file_create() failed.
  murtyvonna@Asuscomp:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  murtyvonna   3169 F pulseaudio
   /dev/snd/controlC0:  murtyvonna   3169 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 13 13:32:21 2018
  InstallationDate: Installed on 2018-08-06 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Touch-packages] [Bug 972198] Re: I cannot cannot "choose a download server"

2018-09-13 Thread Paul White

John,

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

I cannot reproduce your issue using Ubuntu 18.04. Do you still see a
problem related to the one that you reported

Please let us know if you do otherwise this bug report will expire in
approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

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

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

Title:
  I cannot cannot "choose a download server"

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  I open the "Choose a Download Server" window in the Ubuntu Software
  Center (12.04 beta 2, x64). I then click on Australia expecting an
  ftp.iinet.net.au option to appear but nothing happens except
  highlighting the Australia option. The "Choose Server" button in the
  lower right corner remains greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: software-center 5.1.13.2
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.312
  Date: Tue Apr  3 07:33:23 2012
  LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   LANG=en_US.UTF-8
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/972198/+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 1792167] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1792167/+attachment/5188326/+files/ProcEnviron.txt

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  Since Ubuntu switched to Gnome, display scaling does not work
  correctly. This is because my external monitor is detected as 7"
  although it is 32". All applications which use Qt auto scaling have
  huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+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 1221957] Re: Can't change the update server

2018-09-13 Thread Paul White

Miguel,

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Do you still see a problem related to the one that you reported as I
can't reproduce the issue using Ubuntu 18.04.

Please let us know if you do otherwise this bug report will expire in
approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

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

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

Title:
  Can't change the update server

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Hi
  I'm traying to change the server from Portugal to main server and the 
update-manager, siftware center or synaptic don't make the change. I select the 
main server but it stays in the Portugal Server

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: update-manager 1:0.186.2
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Fri Sep  6 23:31:05 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'launch-time' b'1378505564'
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'761'
   b'com.ubuntu.update-manager' b'window-width' b'948'
  InstallationDate: Installed on 2012-04-30 (494 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: update-manager
  UpgradeStatus: Upgraded to raring on 2013-09-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1221957/+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 1792167] Re: Display size detected incorrectly

apport information

** Tags added: apport-collected bionic

** Description changed:

  Since Ubuntu switched to Gnome, display scaling does not work correctly.
  This is because my external monitor is detected as 7" although it is
  32". All applications which use Qt auto scaling have huge controls!
  
  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt
  auto scaling. I think the solution should be to fix the size detection
  instead.
  
  Further, it seems not related to graphics driver, since I personally use
  the open source driver with my internal Intel card, whereas someone else
  uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).
  
  If it is in the wrong category, please move it / add the corresponding
  packages.
  
  If you need any further information to tackle the problem, just tell me!
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.3
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-09-05 (372 days ago)
+ InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ Package: qtbase-opensource-src
+ PackageArchitecture: amd64
+ Tags:  bionic
+ Uname: Linux 4.18.7-041807-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1792167/+attachment/5188324/+files/Dependencies.txt

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  Since Ubuntu switched to Gnome, display scaling does not work
  correctly. This is because my external monitor is detected as 7"
  although it is 32". All applications which use Qt auto scaling have
  huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+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 1792167] Re: Display size detected incorrectly

1. xrandr

I generated the output and attached the section for the external
display. I guess the first line already shows the problem:

HDMI-1 connected 1920x1080+1366+0 (0x8b) normal (normal left
inverted right x axis y axis) 160mm x 90mm

It includes "160mm x 90mm" which probably translates to 7".

2. apport

I generated the requested log. I installed Ubuntu 17.04, upgraded to
17.10 and now upgraded to 18.04. I use the latest kernel from
kernel.ubuntu.com.

** Attachment added: "xrandr output for external display"

https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+attachment/5188367/+files/xrandr.log

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

Title:
Display size detected incorrectly

Status in mutter package in Ubuntu:
Incomplete
Status in qtbase-opensource-src package in Ubuntu:
Incomplete

Bug description:
Since Ubuntu switched to Gnome, display scaling does not work
correctly. This is because my external monitor is detected as 7"
although it is 32". All applications which use Qt auto scaling have
huge controls!

It seems like many users have the same problem
(https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
Qt auto scaling. I think the solution should be to fix the size
detection instead.

Further, it seems not related to graphics driver, since I personally
use the open source driver with my internal Intel card, whereas
someone else uses a proprietary Nvidia driver
(https://askubuntu.com/q/1066879/206608).

If it is in the wrong category, please move it / add the corresponding
packages.

If you need any further information to tackle the problem, just tell me!
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-09-05 (372 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Package: qtbase-opensource-src
PackageArchitecture: amd64
Tags: bionic
Uname: Linux 4.18.7-041807-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo
vboxusers video voice
_MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+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 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused

2018-09-13 Thread James Pic

Breaks importing firefox data into brave browser.

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

Title:
  Unable to connect to ibus: Could not connect: Connection refused

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761382/+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 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.

** Changed in: snapd (Ubuntu)
 Assignee: (unassigned) => Michael Vogt (mvo)

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

Title:
  snapd on cosmic never finishes installing/updating. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776622/+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 778236] Re: bluetooth adapter not found after wakeup

2018-09-13 Thread ligang1840

I have the same bug.

when computer wakeup, the bluetooth mouse disconnected everytime.
and I must make a pair of them, but after wakeup again, the bug returned.

the hardwares are tested and no problems.

thanks.

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

Title:
  bluetooth adapter not found after wakeup

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Kubuntu 11.04 amd64
  Microstar GX623
  When laptop wakes up from sleep mode it cannot see the bluetooth adapter 
anymore and bluetooth mouse does not work.
  This worked with Kubuntu 9.04, 9.10, 10.10 and does not work after upgrade to 
11.04.
  After wake up the bluetooth adapter is on, when I do 'lsusb' I can see:
  ...
  Bus 007 Device 002: ID 0db0:a97a Micro Star International Bluetooth EDR Device
  ...
  but the graphic configurator tells "No bluetooth adapter found".
  Bluetooth works well after normal boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/778236/+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 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.

2018-09-13 Thread Sergey Zolotarev

Same issue here, I do "sudo pkill snapd" every time dpkg gets stuck on
setting up snapd, at least this lets other packages to continue
installing/updating.

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

Title:
  snapd on cosmic never finishes installing/updating. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776622/+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 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics