from:"Will Cooke"

** Attachment added: "E ipp output"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281623/+files/e_ipp.txt

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1837098] Re: Can't print in monochrome, only in colour

** Attachment added: "E PPD"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281616/+files/C43x.ppd

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1839446] Re: When trying to print a test page CUPS crashes

I wasnt able to get a backtrace because there was "no stack".

This is what shows in gdb:


Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) 
Continuing.

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb) 
The program is not being run.
(gdb) 
The program is not being run.
(gdb) backtrace full
No stack.

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

Title:
  When trying to print a test page CUPS crashes

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to get my printer working correctly and when I try and
  print test pages it seems like cups crashes and restarts in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 10:33:49 2019
  InstallationDate: Installed on 2019-07-03 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
  MachineType: LENOVO 20HN0016UK
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET57W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016UK
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+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 1837098] Re: Can't print in monochrome, only in colour

I tested E and that seems to work as expected.

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1839446] Re: When trying to print a test page CUPS crashes

** Attachment added: "error_log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+attachment/5281584/+files/error_log

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

Title:
  When trying to print a test page CUPS crashes

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to get my printer working correctly and when I try and
  print test pages it seems like cups crashes and restarts in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 10:33:49 2019
  InstallationDate: Installed on 2019-07-03 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
  MachineType: LENOVO 20HN0016UK
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET57W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016UK
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+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 1839446] Re: When trying to print a test page CUPS crashes

Sorry, wrong bug, ignore that comment.

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

Title:
  When trying to print a test page CUPS crashes

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to get my printer working correctly and when I try and
  print test pages it seems like cups crashes and restarts in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 10:33:49 2019
  InstallationDate: Installed on 2019-07-03 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
  MachineType: LENOVO 20HN0016UK
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET57W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016UK
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+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 1839446] Re: When trying to print a test page CUPS crashes

I've tested this on E, and I can now print in B and Colour again.

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

Title:
  When trying to print a test page CUPS crashes

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to get my printer working correctly and when I try and
  print test pages it seems like cups crashes and restarts in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 10:33:49 2019
  InstallationDate: Installed on 2019-07-03 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
  MachineType: LENOVO 20HN0016UK
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET57W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016UK
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+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 1839446] [NEW] When trying to print a test page CUPS crashes

Public bug reported:

I'm trying to get my printer working correctly and when I try and print
test pages it seems like cups crashes and restarts in the background.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: cups 2.2.10-4ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Uname: Linux 5.0.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  8 10:33:49 2019
InstallationDate: Installed on 2019-07-03 (35 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
MachineType: LENOVO 20HN0016UK
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0IET57W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HN0016UK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X270
dmi.product.name: 20HN0016UK
dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
dmi.product.version: ThinkPad X270
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug disco

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

Title:
  When trying to print a test page CUPS crashes

Status in cups package in Ubuntu:
  New

Bug description:
  I'm trying to get my printer working correctly and when I try and
  print test pages it seems like cups crashes and restarts in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 10:33:49 2019
  InstallationDate: Installed on 2019-07-03 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
  MachineType: LENOVO 20HN0016UK
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET57W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016UK
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+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 1837098] Re: Can't print in monochrome, only in colour

** Attachment added: "Disco PPD"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281554/+files/Samsung_C43x_Series_printer_.ppd

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1837098] Re: Can't print in monochrome, only in colour

2019-07-18 Thread Will Cooke

To add a bit of clarity, I can't *choose* to print in monochrome from
and of the UI.  The system print dialog shows no options to select
monochrome.

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  New

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1837098] [NEW] Can't print in monochrome, only in colour

2019-07-18 Thread Will Cooke

Public bug reported:

Printer is a Samsung C430W connected over wifi and using driverless
printing.  Everything is discovered and I can print in colour just fine.

In Bionic I was able to toggle in to monochrome, but in Disco I am not.
I now have to print everything in colour.

$ lpoptions -l
PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
ColorModel/Print Color Mode: *RGB
cupsPrintQuality/Print Quality: *4
print-scaling/Print Scaling: *auto auto-fit fill fit none

I have also attached the output of ipptool.

** Affects: cups (Ubuntu)
 Importance: Undecided
 Assignee: Till Kamppeter (till-kamppeter)
 Status: New

** Attachment added: "out.txt"
   https://bugs.launchpad.net/bugs/1837098/+attachment/5277893/+files/out.txt

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  New

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

2019-04-30 Thread Will Cooke

** Changed in: thunderbird (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Tags removed: rls-ee-incoming

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

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 1824103] Re: aplay record file failed always.

2019-04-16 Thread Will Cooke

@infinity has found a fix for this in Debian and is looking at syncing
it now.

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

Title:
  aplay record file failed always.

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Test machine: ThinkPad X1 Carbon
  Image: Ubuntu Disco 19.04
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
  BIOS: N23ET55W (1.30 )

  Steps:
  1. Install image 19.04
  2. Login as default user
  3. Open a terminal and type "$ arecord abc.wav"
  4. Say something and let laptop recorded your words
  5. Cancel the record, please press 'Ctrl + C'
  6. Please type "$ aplay abc.wav" in terminal

  Expected result:
  The voice played smoothly.

  Actual result:
  Step 3, 
  u@u-ThinkPad-X1-Carbon-6th:~$ arecord abc.wav
  Recording WAVE 'abc.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono
  ^CAborted by signal Interrupt...
  arecord: pcm_read:2145: read error: Interrupted system call

  Step 6,
  u@u-ThinkPad-X1-Carbon-6th:~$ aplay abc.wav 
  ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
  aplay: main:828: audio open error: Device or resource busy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1824103/+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 1823426] Re: librsvg ftbfs in disco (i386 only)

2019-04-09 Thread Will Cooke

** Changed in: librsvg (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  librsvg ftbfs in disco (i386 only)

Status in librsvg package in Ubuntu:
  New
Status in librsvg source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
  disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

 Compiling phf_generator v0.7.23
   Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib
 --extern 
rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib 
--cap-lints allow`
  error[E0428]: the name `U1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5
   |
  2110 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
-
 previous definition of the type `U1024` here
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
^
 `U1024` redefined here
   |
   = note: `U1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `P1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   | - previous definition of the type 
`P1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   | ^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `N1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   - 
previous definition of the type `N1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   ^ 
`N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this 
module

 Compiling quote v0.6.8
   Running `rustc --crate-name quote 
/<>/vendor/quote/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' 
--cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C 
metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib
 --cap-lints allow`
  error: aborting due to 3 previous errors

  For more information about this error, try `rustc --explain E0428`.
  error: Could not compile `typenum`.

  Caused by:
process didn't exit successfully: `rustc --crate-name typenum 
/<>/vendor/typenum/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 
-C extra-filename=-373290d68c8bc9c3 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --cap-lints allow` (exit code: 
1)
  warning: build failed, waiting for other jobs to finish...
  error: build failed
  make[3]: *** [Makefile:1955: 
/<>/target/release/librsvg_internals.a] Error 101
  make[3]: Leaving directory '/<>'
  make[2]: *** [Makefile:1457: all-recursive] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [Makefile:940: all] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1823426/+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 1823432] Re: openexr ftbfs in disco (i386 only)

2019-04-09 Thread Will Cooke

** Changed in: openexr (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  openexr ftbfs in disco (i386 only)

Status in openexr package in Ubuntu:
  New
Status in openexr source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417924506/buildlog_ubuntu-
  disco-i386.openexr_2.2.1-4build1_BUILDING.txt.gz

  compression 7, x sampling 2, y sampling 2: writing reading comparing
  compression 8, x sampling 2, y sampling 2: writing reading comparing
  compression 9, x sampling 2, y sampling 2: writing reading comparing
  random bits
  compression 0, x sampling 1, y sampling 1: writing reading 
comparingIlmImfTest: testCompression.cpp:330: void {anonymous}::writeRead(const 
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const 
Imf_2_2::Array2D&, const char*, int, int, int, int, 
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x], 
comp)' failed.
  FAIL IlmImfTest (exit status: 134)

  
  Testsuite summary for OpenEXR 2.2.1
  
  # TOTAL: 1
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See IlmImfTest/test-suite.log
  
  make[5]: *** [Makefile:966: test-suite.log] Error 1
  make[5]: Leaving directory '/<>/IlmImfTest'
  make[4]: *** [Makefile:1074: check-TESTS] Error 2
  make[4]: Leaving directory '/<>/IlmImfTest'
  make[3]: *** [Makefile:1148: check-am] Error 2
  make[3]: Leaving directory '/<>/IlmImfTest'
  make[2]: *** [Makefile:498: check-recursive] Error 1
  make[2]: Leaving directory '/<>'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
  make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:25: build-arch] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1823432/+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 1822073] Re: Bluetooth headset profile forgotten after disconnection

2019-03-28 Thread Will Cooke

Added to Trello: https://trello.com/c/ckCJe76F/292-bug1822073-bluetooth-
headset-profile-forgotten-after-disconnection

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

Title:
  Bluetooth headset profile forgotten after disconnection

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Similar to bug 1283003, after connecting my Bluetooth headset (Sony
  WH-1000X M3) they appear in Gnome Control Centre's Sound tab but are
  not selectable.

  I've narrowed down the circumstances to reproduce the bug as follows:

  1. Start with working sound through Bluetooth to headset
  2. In pavucontrol's Configuration tab, note that headset is listed with A2DP 
profile
  3. Disconnect (power off) the headset
  4. Note that sound comes out of fallback device (as expected)
  5. Power on the headset and reconnect to Bluetooth
  6. Look in Gnome Control Centre and note the headset appears in Sound, but is 
not selectable (buggy)
  7. In pavucontrol's Configuration tab, note headset is listed with "Off"
  8. Manually switch to A2DP
  9. At the point, we have to cycle the connection again (disconnect/reconnect) 
and then sound is once more routed to the headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 10:33:37 2019
  InstallationDate: Installed on 2015-07-04 (1363 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1822073/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

2019-03-28 Thread Will Cooke

Added to Trello: https://trello.com/c/4fDA1uYR/291-bug1773897
-regression-logitech-m337-mice-are-automatically-disconnected-after-
connected

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1773897/+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 1821415] Re: pkexec fails in a non-graphical environment

2019-03-26 Thread Will Cooke

Marking as notfixing for release.  This doesn't mean that it won't get
worked on, and Andrea might have an idea what's going on here, but we
won't block release on this bug.


** Tags removed: rls-dd-incoming
** Tags added: rls-dd-notfixing

** Tags added: desktop-trello-import

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1821415] Automatically added comment

2019-03-26 Thread Will Cooke

Added to Trello: https://trello.com/c/sTIx3fol/288-bug1821415-pkexec-
fails-in-a-non-graphical-environment

** Tags removed: desktop-trello-import

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

2019-03-19 Thread Will Cooke

** Changed in: modemmanager (Ubuntu Bionic)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  In Progress
Status in libqmi source package in Bionic:
  In Progress
Status in modemmanager source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

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

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1819615/+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 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)

2019-03-12 Thread Will Cooke

Added to Trello: https://trello.com/c/XNVW4Tpp/275-bug1817338-hdmi-
sound-output-not-selectable-in-1904-but-works-in-1810

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

Title:
  HDMI sound output not selectable in 19.04 (but works in 18.10)

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in gnome-control-center source package in Disco:
  Confirmed
Status in pulseaudio source package in Disco:
  Invalid

Bug description:
  In 19.04, HDMI sound stopped working after some upgrade.

  The sink is somehow availalbe, but cannot be selected.
  In gnome-control-center, HDMI output device is listed, but if I choose it, no 
configuration list appears (see screen capture attached).

  aplay -l gives me:
  ~$ aplay -l
   Liste des Périphériques Matériels PLAYBACK 
  carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC 
Analog]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  pavucontrol shows HDMI as unplugged.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  franck 5998 F pulseaudio
   /dev/snd/pcmC1D0c:   franck 5998 F...m pulseaudio
   /dev/snd/controlC0:  franck 5998 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 22 16:16:56 2019
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ETA9WW (2.69 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2353CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2353CTO
  dmi.product.sku: LENOVO_MT_2353
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1819572] Re: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction

2019-03-12 Thread Will Cooke

I'm untargetting the specific releases so that this doesn't show up in
our weekly reports.  I would like to see some more debugging and to
better understand why it's just this one machine.  It doesn't yet sound
like this is a release critical bug.


** No longer affects: Ubuntu Cosmic

** No longer affects: Ubuntu Disco

** No longer affects: network-manager (Ubuntu Cosmic)

** No longer affects: network-manager (Ubuntu Disco)

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

Title:
  do-release-upgrade from cosmic to disco make the network of this
  specific machine malfunction

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

Bug description:
  Hardware: Dell Vostro 5568 (CID 201606-22344)

  [Steps To Reproduce]
  1. Install cosmic on this machine
  2. Connect to the internet with ethernet
  3. do-release-upgrade

  [Expected Result]
  Upgrade completes. The wired connection is ready to access the internet.

  [Actual Result]
  - The ethernet interface has an IP address assigned by the associated DHCP 
(checked by "ip -a")
  - "ping 8.8.8.8" will get "Destination Host Unreachable"

  [More Information]
  I tried the same steps on different machine-distro matrix[1]  and could only 
reproduce the issue on this machine.

  [1] distro are: xenial-to-bionic, bionic-to-cosmic, cosmic-to-disco

  
  ---

  [Logs]

  - /var/log tarball of the system: the attachment 201606-22344-network-
  manager-nplusone-190312.var-log.tar.gz

  - Collected by "ubuntu-bug network-manager":
  /media/tai271828/certsd/201606-22344-network-manager-
  nplusone-190312.ubuntu.bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1819572/+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 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-02-28 Thread Will Cooke

Adding Timo who maintainers mesa.

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

Title:
  qemu-system-x86_64 crashed with signal 31 in
  __pthread_setaffinity_new()

Status in Mesa:
  Unknown
Status in QEMU:
  New
Status in mesa package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Triaged

Bug description:
  Unable to launch Default Fedora 29 images in gnome-boxes

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  Date: Thu Feb 14 11:00:45 2019
  ExecutablePath: /usr/bin/qemu-system-x86_64
  KvmCmdLine: COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
  MachineType: Dell Inc. Precision T3610
  ProcEnviron: PATH=(custom, user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1
  Signal: 31
  SourcePackage: qemu
  StacktraceTop:
   __pthread_setaffinity_new (th=, cpusetsize=128, 
cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   start_thread (arg=) at pthread_create.c:486
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: qemu-system-x86_64 crashed with signal 31 in 
__pthread_setaffinity_new()
  UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  dmi.bios.date: 11/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09M8Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3610
  dmi.product.sku: 05D2
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815889/+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 1817662] Re: [SRU] Need to support WWAN module DW5820e

2019-02-26 Thread Will Cooke

** Summary changed:

- Need to support WWAN module DW5820e
+ [SRU] Need to support WWAN module DW5820e

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

Title:
  [SRU] Need to support WWAN module DW5820e

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  New

Bug description:
  * Impact

  New WWAN module like DW5820e is not supported.

  * Test case

  1. Install the new Modem manager on the target machine that have DW5820e 
installed.
  2. Plugged sim card, create a connection and make sure the internet 
connection is working.
  3. Test a few exsting WWAN module and make sure they works.

  * Regression potential

  As far as know (and we've been in communication with Aleksandr), MM 1.10
  should be fully backwards compatible with NM 1.2x.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1817662/+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 1811225] Re: Mesa 18.2.8 stable release

2019-02-05 Thread Will Cooke

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Mesa 18.2.8 stable release

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point 
release of the series. This will also be backported to 18.04 as part of the HWE 
stack update.

  Upstream changes:

  18.2.3
  - Different patches for the DirectX9 and DRI state trackers.
  - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza 
and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky.
  - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, 
anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in
  Radeonsi.
  - State Trackers also get different fixes and corrections.
  - Finally, fixes for GLSL and NIR are also in this queue.

  18.2.4
  - Different fixes for different drivers: freedreno, radeonsi, swr, anv and 
radv.
  - Also there are fixes for ac, gallium, spirv and blorp.

  18.2.5
  - A patch for nine state tracker that fixes several crashes using nine's
  thread_submit feature. There are other patches to other state trackers.
  - A couple of patches for Meson build system, as well as for autotools.
  - In the drivers side, there are a couple of fixes for RADV, one regarding
  subgroups and another regarding conditional rendering. There are also fixes 
for virgl, r600, and i965.
  - Finally, the queue contains a couple of fixes for NIR, Wayland, and other
  components.

  18.2.6
  - Several patches fixing leaks in glsl, winsys and r600.
  - Improvements in the scripts that helps in preparing releases.
  - Added PCI IDs for Amber Lake and Whiskey Lake.
  - Fixes for radv, anv, i965 and vc4 drivers.
  - A couple of fixes in NIR backend.
  - Finally, several fixes in meson build system.

  18.2.7
  - Several patches fixing leaks in glsl, winsys and r600.
  - Improvements in the scripts that helps in preparing releases.
  - Added PCI IDs for Amber Lake and Whiskey Lake.
  - Fixes for radv, anv, i965 and vc4 drivers.
  - A couple of fixes in NIR backend.
  - Finally, several fixes in meson build system.

  18.2.8
  - Several fixes in Meson build system.
  - Also several fixes for st/nine subcomponent.
  - Patch for RADV driver that fixes a hang in Yakuza using DXVK.
  - There are also fixes for Virgl driver.
  - Added PCI IDs for VegaM, Vega20 and Vega10.

  
  [Test Case]
  Check on intel/radeon hw that things still work fine.

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems, this is the last of the 
series so should be safe to update to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1811225/+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 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12

2019-02-04 Thread Will Cooke

** Changed in: libimobiledevice (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Unhandled lockdown error (-2) - iphone ios 12

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on 
the Documents in the file manager, I got this error: Unhandled lockdown error 
(-2). 
  I attached a screenshot about this error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1799913/+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 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12

2019-02-04 Thread Will Cooke

I have tested this on my Disco development machine, and here's what I
found.

Using an iPhone SE running IOS 12.1.2.

Connected the phone using a real cable (using my third party cable only allowed 
me to charge).
Without doing anything further I open Nautilus and browsed to the phone, and 
indeed I did see the error described... "unhandled lock down".


However, on the phone itself I was being asked if I wanted to "Trust this 
computer". I said "Trust this computer" and was then asked to enter my PIN.  
Once I had done this I was able to browse the photos as expected.

Could people reporting this problem please check that the iDevice has
been told to trust the computer and comment here?

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

Title:
  Unhandled lockdown error (-2) - iphone ios 12

Status in libimobiledevice package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on 
the Documents in the file manager, I got this error: Unhandled lockdown error 
(-2). 
  I attached a screenshot about this error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1799913/+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 1813587] Re: libunistring ftbfs on 18.04 LTS

2019-01-29 Thread Will Cooke

** Changed in: libunistring (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
  libunistring ftbfs on 18.04 LTS

Status in libunistring package in Ubuntu:
  Fix Released
Status in libunistring source package in Bionic:
  Triaged

Bug description:
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+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 1718254] Re: please drop url-dispatcher dependencies

2018-12-18 Thread Will Cooke

** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notifixing

** Tags removed: rls-bb-notifixing
** Tags added: rls-bb-notfixing

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

Title:
  please drop url-dispatcher dependencies

Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in unity-greeter-session-broadcast package in Ubuntu:
  New

Bug description:
  please drop url-dispatcher dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1718254/+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 1805857] Re: network-manager dep8 failure blocks dnsmasq proposed migration

2018-12-04 Thread Will Cooke

** Also affects: network-manager (Ubuntu Disco)
   Importance: High
   Status: Triaged

** Changed in: network-manager (Ubuntu Disco)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  network-manager dep8 failure blocks dnsmasq proposed migration

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Disco:
  Triaged

Bug description:
  dnsmasq 2.80-1 is blocked from migrating to the release pocket because
  of, amongst other things, a network-manager dep8 regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1805857/+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 1778767] Re: iPhone doesn't charge when plugged in after disconnect

2018-11-28 Thread Will Cooke

Installed the version from proposed:

$ apt-cache policy usbmuxd
usbmuxd:
  Installed: 1.1.0-2ubuntu0.1
  Candidate: 1.1.0-2ubuntu0.1
  Version table:
 *** 1.1.0-2ubuntu0.1 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1.1.0-2build1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages


Plugged in my phone, it asked me to unlock which I did, and then it started 
charging.
Unplugged the phone.
Plugged the phone back in again and it continued charging.
Repeated this process 3 times and it worked.

Marking as verification done.


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

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

Title:
  iPhone doesn't charge when plugged in after disconnect

Status in usbmuxd package in Ubuntu:
  Fix Released
Status in usbmuxd source package in Bionic:
  Fix Committed
Status in usbmuxd package in Debian:
  New

Bug description:
  * Impact
  the usbmuxd service is not restarted after disconnecting/reconnecting a 
device, which means users need to reboot (or use the command line to activate 
the service) to have their iphone handled a second time in a session

  * Test case
  - open an Ubuntu/GNOME session and connect an iphone
  - disconnect the device
  - connect it again

  -> it should be handled the second time like it was the first time

  * Regression potential
  The changes are in the udev rule, just make sure that idevices are correctly 
detected when connected

  
  

  
  Plugging in the iPhone via usb will charge the iPhone after reboot, but after 
disconnect usbmuxd's systemctl service is inactive and does not start.

  Problem and workaround documented here:

  https://ubuntuforums.org/showthread.php?t=2376741=13779062#post13779062

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1778767/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection

2018-11-28 Thread Will Cooke

Sorry for the delay here.

Is this what you were interested in @cyphermox?

While VPN is up:

$ ls -lha /run/systemd/resolve/
total 16K
drwxr-xr-x  3 systemd-resolve systemd-resolve 140 Nov 28 12:29 .
drwxr-xr-x 20 rootroot460 Nov 28 12:28 ..
drwx--  2 systemd-resolve systemd-resolve  80 Nov 28 12:29 netif
-rw-r--r--  1 systemd-resolve systemd-resolve 647 Nov 28 12:29 resolv.conf
-rw-r--r--  1 systemd-resolve systemd-resolve 712 Nov 28 12:29 stub-resolv.conf
-rw---  1 rootroot712 Nov 28 12:27 
stub-resolv.conf.pppd-backup.ppp0
-rw-r--r--  1 rootroot728 Nov 28 12:29 
stub-resolv.conf.tmp


After VPN is closed:


$ ls -lha /run/systemd/resolve/
total 12K
drwxr-xr-x  3 systemd-resolve systemd-resolve 120 Nov 28 12:32 .
drwxr-xr-x 20 rootroot460 Nov 28 12:28 ..
drwx--  2 systemd-resolve systemd-resolve  60 Nov 28 12:32 netif
-rw-r--r--  1 systemd-resolve systemd-resolve 647 Nov 28 12:32 resolv.conf
-rw---  1 rootroot712 Nov 28 12:27 stub-resolv.conf
-rw-r--r--  1 rootroot728 Nov 28 12:29 
stub-resolv.conf.tmp


Attached are the files after the VPN is shutdown.



** Attachment added: "systemd_resolve.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+attachment/5216985/+files/systemd_resolve.tgz

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   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 (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

2018-11-20 Thread Will Cooke

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
  _mesa_reference_renderbuffer_() [often when running Skype or Slack
  snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca
  https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 16 18:18:18 2017
  xserver.configfile: default
  xserver.devices:

  xserver.logfile:

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

2018-10-31 Thread Will Cooke

Also confirming that installing resolvconf makes DNS work once the VPN
is disconnected.

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   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 (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection

I spoke to stgraber a bit, he said that the resolvconf thing is probably
a red herring.

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   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 (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection

This upstream bug suggests that the problem can be resolved by installing 
resolvconf:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378363

I will test this, but I'm having problems with VPNs on this network atm.


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

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   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 (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1800055] Re: iwd does not work with network manager

Just so I understand, did you try and rebuild n-m with iwd enabled, or
did you try and enable it at run time?

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

Title:
  iwd does not work with network manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I configured network manager to use iwd, unfortunately it doesn't
  work:

  Oct 25 15:12:23 malefic NetworkManager[17004]:   [1540501943.4358] 
device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'external')
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_type: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_type_is_subtype_of: 
assertion 'g_variant_type_check (type)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_boolean: 
assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_string: 
assertion 'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]:   [1540501943.7492] 
device (wlp4s0): new IWD device state is (null)
  Oct 25 15:12:23 malefic NetworkManager[17004]:  [1540501943.7492] 
device (wlp4s0): State (null) unknown
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_dbus_proxy_call_internal: 
assertion 'G_IS_DBUS_PROXY (proxy)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800055/+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 1800055] Re: iwd does not work with network manager

Added to Trello: https://trello.com/c/CsmiAkqj/119-bug1800055-iwd-does-
not-work-with-network-manager

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  iwd does not work with network manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I configured network manager to use iwd, unfortunately it doesn't
  work:

  Oct 25 15:12:23 malefic NetworkManager[17004]:   [1540501943.4358] 
device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'external')
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_type: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_type_is_subtype_of: 
assertion 'g_variant_type_check (type)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_boolean: 
assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_string: 
assertion 'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]:   [1540501943.7492] 
device (wlp4s0): new IWD device state is (null)
  Oct 25 15:12:23 malefic NetworkManager[17004]:  [1540501943.7492] 
device (wlp4s0): State (null) unknown
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 
'value != NULL' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_dbus_proxy_call_internal: 
assertion 'G_IS_DBUS_PROXY (proxy)' failed
  Oct 25 15:12:23 malefic NetworkManager[17004]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800055/+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 1800171] [NEW] n-m doesn't support iwd as a backend

Public bug reported:

iwd is an alternative to wpa_supplicant.

It can be enabled as backend for n-m at run time, but n-m needs to be
built with support for it.

iwd is in universe in Cosmic.

It would be good to get this switched on for DD so that we can test and
think about making it the default for EE before the next LTS.

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

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

Title:
  n-m doesn't support iwd as a backend

Status in network-manager package in Ubuntu:
  New

Bug description:
  iwd is an alternative to wpa_supplicant.

  It can be enabled as backend for n-m at run time, but n-m needs to be
  built with support for it.

  iwd is in universe in Cosmic.

  It would be good to get this switched on for DD so that we can test
  and think about making it the default for EE before the next LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800171/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection

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

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   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 (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection

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

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  New

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   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 (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection

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

** No longer affects: openvpn-systemd-resolved (Ubuntu)

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   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 (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1797415] Re: DNS stops working when disconnecting PPTP VPN on desktop

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

Yeah, I think so.  Thanks.


** This bug has been marked a duplicate of bug 1778946
   No dns resolution after closing a vpn/pptp connection

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

Title:
  DNS stops working when disconnecting PPTP VPN on desktop

Status in systemd package in Ubuntu:
  New

Bug description:
  On Cosmic I was testing some VPN setups.  I created a PPTP VPN connection to 
my server.
  Everything connected and worked as it should.

  When I disconnect the VPN, DNS resolution stops working.

  Looking at "systemd-resolve --status" shows that the correct DNS
  server is listed for the interface  when the connection is torn down,
  and I can ping it.  Doing a nslookup setting the server to the IP
  address shown in --status shows that DNS resolution is working
  correctly.

  resolv.conf says nameserver 127.0.0.53

  Restart resolved makes things work again.
  (Also, restarting Network Manager makes it work again.)

  Trying to ping a hostname from the cli when in the broken state yields
  zero output from resolved logs when in debug mode.  Almost like it's
  not even hitting resolved, so this bug could very well be somewhere
  else.

  I've checked, and I can ping 127.0.0.1 and the default routes look OK,
  although there is a route to the VPN server left over.

  I'm all out of ideas.  Any ideas?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797415/+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 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)

2018-10-16 Thread Will Cooke

Not a release blocker.  Seb will look to SRU.


** Tags removed: rls-cc-incoming
** Tags added: rls-cc-notfixing

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

Title:
  [regression] Keyboard brightness control keys (down/up) don't work in
  cosmic (upower 0.99.8)

Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.freedesktop.org/upower/upower/issues/73

  ---

  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit
  keyboard is displayed but no progress bar and no actual effect to the
  backlight. Almost as if the shell only understands laptops with a
  single key for controlling the keyboard backlight...

  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air

  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it
  directly. This seems to be a problem with Gnome Shell only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  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/linux/+bug/1796550/+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 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk

2018-10-12 Thread Will Cooke

It should be yes, but I'd like to look at the changes needed before
going any further.  Looking at the diff, it doesnt look too bad for the
current version on n-m.  With some luck it will be backported by
upstream, if not we'll take a look.

Release of Cosmic is next week, so I dont think this will get any
traction until that's out the door, but then we will get on the case.


** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  NetworkManager IPv6 DAD lifetime behavior introduce security risk

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in DD-Series:
  New

Bug description:
  Description:
  When performing IPv6 certification test, two DAD test cases (3.2.5c and d) 
check the remaining lifetime feature of the IPv6 packets.  The Network trace 
shows that the remaining lifetime becomes infinite when running these test 
cases.  Hence when running in IPv6 environment with Network Manager enabled, 
there is a risk of packets travelling in network which has valid lifetime 
always. If these packets are snooped by a hacker he can reply to these packets 
and they can send legitimate packets which are actually not.  

  According to https://tools.ietf.org/search/rfc4862, page 19:
  "The above rules address a specific denial-of-service attack in which a bogus 
advertisement could contain prefixes with very small Valid Lifetimes.  Without 
the above rules, a single unauthenticated advertisement containing bogus Prefix 
Information options with short Valid Lifetimes could cause all of a node's 
addresses to expire prematurely.  The above rules ensure that legitimate 
advertisements (which are sent periodically) will "cancel" the short Valid 
Lifetimes before they actually take effect."

  Other notes:
  - 2 test cases pass without NetworkManager.
  - Tested with different Linux Desktop Distributions, as long as 
NetworkManager is running, those DAD test cases fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796622/+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 1797415] Re: DNS stops working when disconnecting PPTP VPN on desktop

** Attachment added: "and when the VPN is down again"

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797415/+attachment/5200104/+files/vpn_down.log

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

Title:
DNS stops working when disconnecting PPTP VPN on desktop

Status in systemd package in Ubuntu:
New

Bug description:
On Cosmic I was testing some VPN setups. I created a PPTP VPN connection to
my server.
Everything connected and worked as it should.

When I disconnect the VPN, DNS resolution stops working.

Looking at "systemd-resolve --status" shows that the correct DNS
server is listed for the interface when the connection is torn down,
and I can ping it. Doing a nslookup setting the server to the IP
address shown in --status shows that DNS resolution is working
correctly.

resolv.conf says nameserver 127.0.0.53

Restart resolved makes things work again.
(Also, restarting Network Manager makes it work again.)

Trying to ping a hostname from the cli when in the broken state yields
zero output from resolved logs when in debug mode. Almost like it's
not even hitting resolved, so this bug could very well be somewhere
else.

I've checked, and I can ping 127.0.0.1 and the default routes look OK,
although there is a route to the VPN server left over.

I'm all out of ideas. Any ideas?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797415/+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 1797415] [NEW] DNS stops working when disconnecting PPTP VPN on desktop

Public bug reported:

On Cosmic I was testing some VPN setups.  I created a PPTP VPN connection to my 
server.
Everything connected and worked as it should.

When I disconnect the VPN, DNS resolution stops working.

Looking at "systemd-resolve --status" shows that the correct DNS server
is listed for the interface  when the connection is torn down, and I can
ping it.  Doing a nslookup setting the server to the IP address shown in
--status shows that DNS resolution is working correctly.

resolv.conf says nameserver 127.0.0.53

Restart resolved makes things work again.
(Also, restarting Network Manager makes it work again.)

Trying to ping a hostname from the cli when in the broken state yields
zero output from resolved logs when in debug mode.  Almost like it's not
even hitting resolved, so this bug could very well be somewhere else.

I've checked, and I can ping 127.0.0.1 and the default routes look OK,
although there is a route to the VPN server left over.

I'm all out of ideas.  Any ideas?

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

** Attachment added: "When the VPN is up"
   https://bugs.launchpad.net/bugs/1797415/+attachment/5200103/+files/vpn_up.log

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

Title:
  DNS stops working when disconnecting PPTP VPN on desktop

Status in systemd package in Ubuntu:
  New

Bug description:
  On Cosmic I was testing some VPN setups.  I created a PPTP VPN connection to 
my server.
  Everything connected and worked as it should.

  When I disconnect the VPN, DNS resolution stops working.

  Looking at "systemd-resolve --status" shows that the correct DNS
  server is listed for the interface  when the connection is torn down,
  and I can ping it.  Doing a nslookup setting the server to the IP
  address shown in --status shows that DNS resolution is working
  correctly.

  resolv.conf says nameserver 127.0.0.53

  Restart resolved makes things work again.
  (Also, restarting Network Manager makes it work again.)

  Trying to ping a hostname from the cli when in the broken state yields
  zero output from resolved logs when in debug mode.  Almost like it's
  not even hitting resolved, so this bug could very well be somewhere
  else.

  I've checked, and I can ping 127.0.0.1 and the default routes look OK,
  although there is a route to the VPN server left over.

  I'm all out of ideas.  Any ideas?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797415/+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 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk

Upstream fix:  https://github.com/NetworkManager/NetworkManager/pull/228

This will be ported to all supported releases soon, so we should be able
to pick that up easily enough.

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

Title:
  NetworkManager IPv6 DAD lifetime behavior introduce security risk

Status in network-manager package in Ubuntu:
  New

Bug description:
  Description:
  When performing IPv6 certification test, two DAD test cases (3.2.5c and d) 
check the remaining lifetime feature of the IPv6 packets.  The Network trace 
shows that the remaining lifetime becomes infinite when running these test 
cases.  Hence when running in IPv6 environment with Network Manager enabled, 
there is a risk of packets travelling in network which has valid lifetime 
always. If these packets are snooped by a hacker he can reply to these packets 
and they can send legitimate packets which are actually not.  

  According to https://tools.ietf.org/search/rfc4862, page 19:
  "The above rules address a specific denial-of-service attack in which a bogus 
advertisement could contain prefixes with very small Valid Lifetimes.  Without 
the above rules, a single unauthenticated advertisement containing bogus Prefix 
Information options with short Valid Lifetimes could cause all of a node's 
addresses to expire prematurely.  The above rules ensure that legitimate 
advertisements (which are sent periodically) will "cancel" the short Valid 
Lifetimes before they actually take effect."

  Other notes:
  - 2 test cases pass without NetworkManager.
  - Tested with different Linux Desktop Distributions, as long as 
NetworkManager is running, those DAD test cases fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796622/+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 1796822] Re: Desktop live cd boots corrupted screen in Virtualbox on Bionic

Confirming that todays pending ISO boots correctly on Vbox.

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

Title:
  Desktop live cd boots corrupted screen in Virtualbox on Bionic

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Fix Released
Status in xorg-server source package in Cosmic:
  Confirmed

Bug description:
  On a Bionic host running the standard archive version of Virtualbox
  and the daily ISO of Cosmic, the live session starts with a corrupted
  graphical display, as can be seen here:

  https://imgur.com/a/rkTId4S

  (also attached)

  Switching VTs to 2 and back to 1 clears the display and things work
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1796822/+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 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk

Spoke to upstream.  They will look in to this and get it fixed.  I've
asked David to log it upstream and we can link to that here.

We should look at backport the fixes and SRUing to Bionic.

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

Title:
  NetworkManager IPv6 DAD lifetime behavior introduce security risk

Status in network-manager package in Ubuntu:
  New

Bug description:
  Description:
  When performing IPv6 certification test, two DAD test cases (3.2.5c and d) 
check the remaining lifetime feature of the IPv6 packets.  The Network trace 
shows that the remaining lifetime becomes infinite when running these test 
cases.  Hence when running in IPv6 environment with Network Manager enabled, 
there is a risk of packets travelling in network which has valid lifetime 
always. If these packets are snooped by a hacker he can reply to these packets 
and they can send legitimate packets which are actually not.  

  According to https://tools.ietf.org/search/rfc4862, page 19:
  "The above rules address a specific denial-of-service attack in which a bogus 
advertisement could contain prefixes with very small Valid Lifetimes.  Without 
the above rules, a single unauthenticated advertisement containing bogus Prefix 
Information options with short Valid Lifetimes could cause all of a node's 
addresses to expire prematurely.  The above rules ensure that legitimate 
advertisements (which are sent periodically) will "cancel" the short Valid 
Lifetimes before they actually take effect."

  Other notes:
  - 2 test cases pass without NetworkManager.
  - Tested with different Linux Desktop Distributions, as long as 
NetworkManager is running, those DAD test cases fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796622/+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 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

2018-10-09 Thread Will Cooke

Could be related to this:
https://gitlab.gnome.org/GNOME/gdm/merge_requests/37

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in kmod package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-fbdev package in Ubuntu:
  Fix Released
Status in gdm3 source package in Cosmic:
  Won't Fix
Status in kmod source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in xorg-server source package in Cosmic:
  Confirmed
Status in xserver-xorg-video-fbdev source package in Cosmic:
  Fix Released

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty

  When this issue happens there is a plymouth crash reported in bug
  1794292


  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+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 1743216] Re: perl crashed with SIGABRT in _dbus_abort()

2018-09-25 Thread Will Cooke

** Changed in: xdg-utils (Ubuntu)
 Assignee: Canonical Desktop Team (canonical-desktop-team) => Iain Lane 
(laney)

** Also affects: perl (Ubuntu Cosmic)
   Importance: High
   Status: Confirmed

** Also affects: xdg-utils (Ubuntu Cosmic)
   Importance: High
 Assignee: Iain Lane (laney)
   Status: Confirmed

** Tags removed: rls-cc-incoming
** Tags added: rls-cc-tracking

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

Title:
  perl crashed with SIGABRT in _dbus_abort()

Status in perl package in Ubuntu:
  Confirmed
Status in xdg-utils package in Ubuntu:
  Confirmed
Status in perl source package in Cosmic:
  Confirmed
Status in xdg-utils source package in Cosmic:
  Confirmed

Bug description:
  Errors Bucket
  -
  https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52

  crashed after launching the software updater

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: perl-base 5.26.1-4
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 14 13:30:52 2018
  ExecutablePath: /usr/bin/perl
  InstallationDate: Installed on 2017-12-28 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171201)
  Signal: 6SourcePackage: perl
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so
   Perl_pp_entersub ()
  Title: perl crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1743216/+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 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager

2018-07-03 Thread Will Cooke

We will get this fix as part of the next stable updated.


** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notfixing

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

Title:
  Ubuntu 18.04 mounted network shares not appearing under devices in
  file manager

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Apologies if this is not the correct package to file this
  bug/regression against.

  On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when
  mounting network shares (SMB and NFS) they no longer appear under
  Devices in file manager (Nautilus or Caja), the mounts do succeed and
  are accessible at their mount points.

  In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of
  mounted network shares on Ubuntu Mate 17.10 attached)

  I am using the following code to mount NFS shares

  `sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup
  /media/philroche/photobackup`

  and for SMB shares

  `sudo mount.cifs //192.168.2.123/photobackup
  /media/philroche/photobackup`

  Is this a bug/regression, or perhaps it is an intentional change?

  I did ask this on IRC in #ubuntu and askubuntu.com but no reply.

  Expected behaviour:

  I expected the mounted network shares to appear under Devices in File
  manager

  Actual behaviour:

  Mounting network shares does succeed as expected but does not appear
  under Devices in File manager as it did in previous releases.

  Requested details:

  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  udisks2:
Installed: 2.7.6-3
Candidate: 2.7.6-3
Version table:
   *** 2.7.6-3 500
  500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1773334/+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 1773213] Re: U1 login dialog missing link to the privacy policy

2018-05-24 Thread Will Cooke

** Changed in: gnome-online-accounts (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  U1 login dialog missing link to the privacy policy

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  The U1 login for g-o-a is missing a link to the privacy policy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+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 1773213] Re: U1 login dialog missing link to the privacy policy

2018-05-24 Thread Will Cooke

** Attachment added: "g-o-a.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+attachment/5143922/+files/g-o-a.png

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

Title:
  U1 login dialog missing link to the privacy policy

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  The U1 login for g-o-a is missing a link to the privacy policy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+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 1773213] [NEW] U1 login dialog missing link to the privacy policy

2018-05-24 Thread Will Cooke

Public bug reported:

The U1 login for g-o-a is missing a link to the privacy policy.

** Affects: gnome-online-accounts (Ubuntu)
 Importance: High
 Status: Confirmed

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Confirmed

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

Title:
  U1 login dialog missing link to the privacy policy

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  The U1 login for g-o-a is missing a link to the privacy policy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+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 1768797] Re: LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

2018-05-08 Thread Will Cooke

Ah yeah, you're right. It is still checked, but is greyed out.

However, I think that is still misleading as, to me at least, it implies
that LivePatch isn't working because I'm not signed in.

Am I right in thinking that you can still disabled LP if the u1 account
has expired? If so I think that if LP is active and can be disabled in
this state, then it should be possible to disable it without having to
refresh the u1 creds.

But, we should get input from design.

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

Title:
LivePatch in Software & Updates shows that LP is not enabled when the
U1 account has expired in g-o-a

Status in gnome-online-accounts package in Ubuntu:
Incomplete

Bug description:
I enabled LivePatch via gnome-initial-setup and added my U1 account to
g-o-a.

My U1 account gets marked as expired quite often. When it's expired
the LP entry in Software & Updates is not ticked to show that LP is
running. When my u1 account is re-authenticated then everything shows
correctly.

This could make it seem that LivePatch does not run if your account
expires, which is not the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1768797/+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 1768797] Re: LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

2018-05-03 Thread Will Cooke

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: High => Medium

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

Title:
  LivePatch in Software & Updates shows that LP is not enabled when the
  U1 account has expired in g-o-a

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I enabled LivePatch via gnome-initial-setup and added my U1 account to
  g-o-a.

  My U1 account gets marked as expired quite often.  When it's expired
  the LP entry in Software & Updates is not ticked to show that LP is
  running.  When my u1 account is re-authenticated then everything shows
  correctly.

  This could make it seem that LivePatch does not run if your account
  expires, which is not the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1768797/+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 1768797] [NEW] LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

2018-05-03 Thread Will Cooke

Public bug reported:

I enabled LivePatch via gnome-initial-setup and added my U1 account to
g-o-a.

My U1 account gets marked as expired quite often. When it's expired the
LP entry in Software & Updates is not ticked to show that LP is running.
When my u1 account is re-authenticated then everything shows correctly.

This could make it seem that LivePatch does not run if your account
expires, which is not the case.

** Affects: gnome-online-accounts (Ubuntu)
Importance: High
Assignee: Andrea Azzarone (azzar1)
Status: New

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

Title:
LivePatch in Software & Updates shows that LP is not enabled when the
U1 account has expired in g-o-a

Status in gnome-online-accounts package in Ubuntu:
New

Bug description:
I enabled LivePatch via gnome-initial-setup and added my U1 account to
g-o-a.

This could make it seem that LivePatch does not run if your account
expires, which is not the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1768797/+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 1767089] Re: totem cannot play h.264 on 18.04

2018-04-30 Thread Will Cooke

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

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

Title:
  totem cannot play h.264 on 18.04

Status in gstreamer1.0 package in Ubuntu:
  Invalid

Bug description:
  On a fresh install of 18.04, Totem fails to play recent h.264 video
  (audio is fine). Obviously, that means failed thumbnails, too.

  I have the whole set of gstreamer plugins installed (version
  1.14.0-1ubuntu1), including the libav plugin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1767089/+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 1767089] Re: totem cannot play h.264 on 18.04

2018-04-30 Thread Will Cooke

Cool, thanks for the update!  We'll keep an eye on this problem as we've
seen other reports, but for now closing this bug.

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

Title:
  totem cannot play h.264 on 18.04

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  On a fresh install of 18.04, Totem fails to play recent h.264 video
  (audio is fine). Obviously, that means failed thumbnails, too.

  I have the whole set of gstreamer plugins installed (version
  1.14.0-1ubuntu1), including the libav plugin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1767089/+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 1767089] Re: totem cannot play h.264 on 18.04

2018-04-30 Thread Will Cooke

I've tested that clip here and was asked to install the "bad" codecs
which I did, and then restarted Totem and it played back ok.

That video clip appears a bit strange, in that it's h264 video and mp4
aac audio inside an MPEG2 TS.


Do you have Nvidia graphics hardware?

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

Title:
  totem cannot play h.264 on 18.04

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  On a fresh install of 18.04, Totem fails to play recent h.264 video
  (audio is fine). Obviously, that means failed thumbnails, too.

  I have the whole set of gstreamer plugins installed (version
  1.14.0-1ubuntu1), including the libav plugin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1767089/+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 1766694] Re: If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install

2018-04-24 Thread Will Cooke

Worth noting that if you go to Software & Updates and enable LP from
there you are prompted to select the pre existing U1 g-o-a account and
set up completes.


** Changed in: ubuntu-release-notes
   Status: New => Fix Released

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

Title:
  If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Set up a fresh 18.04 machine
  2. Login
  3. While g-i-s is open, go to gnome-control-center and add a U1 account
  4. Close g-c-c
  5. Proceed through g-i-s and enable LivePatch
  6. You are asked to log in to U1 again (which might be a bug in itself, if 
there's already an account there, we should prompt to use it)
  7. Go through the login process
  8. Click Connect
  9. The g-o-a window closes and you're back to g-i-s but no action is taken to 
install LivePatch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1766694/+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 1766694] [NEW] If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install

2018-04-24 Thread Will Cooke

Public bug reported:

Steps to reproduce:

1. Set up a fresh 18.04 machine
2. Login
3. While g-i-s is open, go to gnome-control-center and add a U1 account
4. Close g-c-c
5. Proceed through g-i-s and enable LivePatch
6. You are asked to log in to U1 again (which might be a bug in itself, if 
there's already an account there, we should prompt to use it)
7. Go through the login process
8. Click Connect
9. The g-o-a window closes and you're back to g-i-s but no action is taken to 
install LivePatch

** Affects: ubuntu-release-notes
 Importance: Undecided
 Status: Fix Released

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Confirmed

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: High => Medium

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

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

Title:
  If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Set up a fresh 18.04 machine
  2. Login
  3. While g-i-s is open, go to gnome-control-center and add a U1 account
  4. Close g-c-c
  5. Proceed through g-i-s and enable LivePatch
  6. You are asked to log in to U1 again (which might be a bug in itself, if 
there's already an account there, we should prompt to use it)
  7. Go through the login process
  8. Click Connect
  9. The g-o-a window closes and you're back to g-i-s but no action is taken to 
install LivePatch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1766694/+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 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete()

2018-04-24 Thread Will Cooke

On an up-to-date 18.04 machine today I can no longer reproduce this
crash.  Could someone else confirm the same?

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete()

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 16 18:18:18 2017
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.3-1ubuntu1.2

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

--

[Touch-packages] [Bug 1763446] Re: LIvepatch says I need to sign in after completing Ubuntu Welcome

2018-04-16 Thread Will Cooke

** Changed in: software-properties (Ubuntu)
   Importance: Low => High

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

Title:
  LIvepatch says I need to sign in after completing Ubuntu Welcome

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  Test Case
  =
  From a clean Ubuntu 18.04 install,

  1. Install gnome-initial-setup
  2. Log out then log back in.
  3. Complete the Welcome to Ubuntu wizard, making sure to enable Livepatch.
  4. Afterwards, run the Software & Updates app (software-properties-gtk).
  5. Switch to the Updates tab.

  The page says "To use Livepatch you need to sign in."

  Workaround
  ==
  Click Sign In and then click your Ubuntu One account to get Software & 
Updates to correctly recognize your account.

  Screenshot attached. (Sorry about the blue colors; that should be
  fixed in mutter 3.28.1 available in Ubuntu 18.04 "soon".)

  Other Info
  ==
  gnome-initial-setup 3.28.0-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1763446/+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 1749546] Re: Booting a live session is slow - fontconfig regenerates its font cache

2018-04-04 Thread Will Cooke

** Tags removed: rls-bb-incoming

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

Title:
  Booting a live session is slow - fontconfig regenerates its font cache

Status in Fontconfig:
  Confirmed
Status in fontconfig package in Ubuntu:
  In Progress
Status in fontconfig source package in Bionic:
  In Progress

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1749546/+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 1749546] Re: Booting a live session is slow

2018-04-04 Thread Will Cooke

Thanks to ali1234 this was tracked down to font-config rebuilding the
cache at the start of the live session.  Something changed in the way
fontconfig validates the caches and so they are being rebuilt at the
start of the live session.

This bug is likely related:
https://bugs.freedesktop.org/show_bug.cgi?id=103652


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

** Also affects: fontconfig (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: casper (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Canonical Desktop Team (canonical-desktop-team)
   Status: New

** No longer affects: casper (Ubuntu)

** No longer affects: casper (Ubuntu Bionic)

** Changed in: fontconfig (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)

** Bug watch added: freedesktop.org Bugzilla #103652
   https://bugs.freedesktop.org/show_bug.cgi?id=103652

** Changed in: fontconfig (Ubuntu Bionic)
 Assignee: Canonical Desktop Team (canonical-desktop-team) => Iain Lane 
(laney)

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

Title:
  Booting a live session is slow

Status in fontconfig package in Ubuntu:
  In Progress
Status in fontconfig source package in Bionic:
  In Progress

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1749546/+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 1735415] Re: VNC client does not exits after logout

2018-04-03 Thread Will Cooke

** Changed in: lightdm (Ubuntu Bionic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  VNC client does not exits after logout

Status in Light Display Manager:
  Fix Committed
Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Trusty:
  New
Status in lightdm source package in Xenial:
  New
Status in lightdm source package in Zesty:
  New
Status in lightdm source package in Artful:
  New
Status in lightdm source package in Bionic:
  New

Bug description:
  I have setup the remote desktop using the "[VNCServer]" configuration section.
  When I log in using a VNC client and log out with the desktop panel menu,
  the VNC client(remmina) does not exits.

  I found that a VNC connection(TCP 5900) remains alive even though the Xvnc 
server exits.
  I also found the cause, GSocket instance is leaking in the "src/vnc-server.c".

  static gboolean
  read_cb (GSocket *socket, GIOCondition condition, VNCServer *server)
  {
  ...
  client_socket = g_socket_accept (socket, NULL, );
  ...
  if (client_socket)
  {
  ...
  g_signal_emit (server, signals[NEW_CONNECTION], 0, client_socket);
  }
  return TRUE;
  }

  I think that "g_object_unref(client_socket)" should be called after
  g_signal_emit().

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1735415/+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 1760308] Re: Unicode input not working on Bionic with CTRL-SHIFT-U

2018-04-03 Thread Will Cooke

** Also affects: ibus (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

** Changed in: ibus (Ubuntu Bionic)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Tags removed: rls-bb-incoming

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

Title:
  Unicode input not working on Bionic with CTRL-SHIFT-U

Status in ibus package in Ubuntu:
  Confirmed
Status in ibus source package in Bionic:
  Confirmed

Bug description:
  I need to enter Unicode with Unicode escape codes and the Ubuntu
  prescribed way is to use CTRL-SHIFT-U and then enter some numbers to
  input.  This doesn't do anything in the Ubuntu Bionic beta.

  Potentially related the ALT-TAB window switching is delayed in
  recognizing the occurrence of the keys being pressed such that I have
  to hold ALT-TAB instead of quickly hitting both simultaneously.

  This is from a system that was upgraded from a previous Ubuntu version
  without any issues.

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

  The "Affects" package may not be accurate as I don't know what the
  cause application is for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1760308/+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 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

2018-04-03 Thread Will Cooke

** Tags added: rls-bb-incoming

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Confirmed
Status in laptop-mode-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send

[Touch-packages] [Bug 1759601] Re: [UIFe] 18.04 LTS Bionic Beaver Mascot

2018-03-29 Thread Will Cooke

** Description changed:

  The mascots for this release needed adding to the welcome page of the
  slideshow.  The final versions of the mascots arrived after UIF and I
  updated the slideshow yesterday.
  
  As part of that updated I changed the string describing what software
  was available to include mention of the snap store.  Since snaps are
  core component of the desktop and GNOME Software (promoted snaps
  appearing on the front page of Software for example) I think this is an
  important change.
  
  The string changes are:
  
  -Say goodbye to searching the web for new software. With access to
  the Ubuntu Software Store, you can find and install new apps with ease.
  Just type in what you’re looking for, or explore categories such as
  Science, Education and Games, alongside helpful reviews from other
  users.
  
  +Say goodbye to searching the web for new software. With access to
  the Snap Store and the Ubuntu software archive, you can find and install
  new apps with ease. Just type in what you’re looking for, or explore
  categories such as Games, Graphics & Photography and Productivity,
  alongside helpful reviews from other users.
  
  
+ Post to doc-team: 
https://lists.ubuntu.com/archives/ubuntu-doc/2018-March/020580.html
+ Post to translators: 
https://lists.ubuntu.com/archives/ubuntu-translators/2018-March/007454.html
+ 
+ 
  Beavers and branch attached.

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

Title:
  [UIFe] 18.04 LTS Bionic Beaver Mascot

Status in Ubuntu theme:
  New
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  The mascots for this release needed adding to the welcome page of the
  slideshow.  The final versions of the mascots arrived after UIF and I
  updated the slideshow yesterday.

  As part of that updated I changed the string describing what software
  was available to include mention of the snap store.  Since snaps are
  core component of the desktop and GNOME Software (promoted snaps
  appearing on the front page of Software for example) I think this is
  an important change.

  The string changes are:

  -Say goodbye to searching the web for new software. With access to
  the Ubuntu Software Store, you can find and install new apps with
  ease. Just type in what you’re looking for, or explore categories such
  as Science, Education and Games, alongside helpful reviews from other
  users.

  +Say goodbye to searching the web for new software. With access to
  the Snap Store and the Ubuntu software archive, you can find and
  install new apps with ease. Just type in what you’re looking for, or
  explore categories such as Games, Graphics & Photography and
  Productivity, alongside helpful reviews from other users.

  
  Post to doc-team: 
https://lists.ubuntu.com/archives/ubuntu-doc/2018-March/020580.html
  Post to translators: 
https://lists.ubuntu.com/archives/ubuntu-translators/2018-March/007454.html

  
  Beavers and branch attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1759601/+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 1759601] Re: [UIFe] 18.04 LTS Bionic Beaver Mascot

2018-03-29 Thread Will Cooke

** Description changed:

- Beavers attached.
+ The mascots for this release needed adding to the welcome page of the
+ slideshow.  The final versions of the mascots arrived after UIF and I
+ updated the slideshow yesterday.
+ 
+ As part of that updated I changed the string describing what software
+ was available to include mention of the snap store.  Since snaps are
+ core component of the desktop and GNOME Software (promoted snaps
+ appearing on the front page of Software for example) I think this is an
+ important change.
+ 
+ The string changes are:
+ 
+ -Say goodbye to searching the web for new software. With access to
+ the Ubuntu Software Store, you can find and install new apps with ease.
+ Just type in what you’re looking for, or explore categories such as
+ Science, Education and Games, alongside helpful reviews from other
+ users.
+ 
+ +Say goodbye to searching the web for new software. With access to
+ the Snap Store and the Ubuntu software archive, you can find and install
+ new apps with ease. Just type in what you’re looking for, or explore
+ categories such as Games, Graphics & Photography and Productivity,
+ alongside helpful reviews from other users.
+ 
+ 
+ Beavers and branch attached.

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

Title:
  [UIFe] 18.04 LTS Bionic Beaver Mascot

Status in Ubuntu theme:
  New
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  The mascots for this release needed adding to the welcome page of the
  slideshow.  The final versions of the mascots arrived after UIF and I
  updated the slideshow yesterday.

  As part of that updated I changed the string describing what software
  was available to include mention of the snap store.  Since snaps are
  core component of the desktop and GNOME Software (promoted snaps
  appearing on the front page of Software for example) I think this is
  an important change.

  The string changes are:

  -Say goodbye to searching the web for new software. With access to
  the Ubuntu Software Store, you can find and install new apps with
  ease. Just type in what you’re looking for, or explore categories such
  as Science, Education and Games, alongside helpful reviews from other
  users.

  +Say goodbye to searching the web for new software. With access to
  the Snap Store and the Ubuntu software archive, you can find and
  install new apps with ease. Just type in what you’re looking for, or
  explore categories such as Games, Graphics & Photography and
  Productivity, alongside helpful reviews from other users.


  Beavers and branch attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1759601/+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 1759601] Re: [UIFe] 18.04 LTS Bionic Beaver Mascot

2018-03-29 Thread Will Cooke

** Summary changed:

- 18.04 LTS Bionic Beaver Mascot
+ [UIFe] 18.04 LTS Bionic Beaver Mascot

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

Title:
  [UIFe] 18.04 LTS Bionic Beaver Mascot

Status in Ubuntu theme:
  New
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Beavers attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1759601/+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 1759601] Re: 18.04 LTS Bionic Beaver Mascot

2018-03-28 Thread Will Cooke

** Also affects: ubiquity-slideshow-ubuntu
   Importance: Undecided
   Status: New

** No longer affects: ubiquity-slideshow-ubuntu

** Also affects: ubiquity-slideshow-ubuntu
   Importance: Undecided
   Status: New

** No longer affects: ubiquity-slideshow-ubuntu

** Also affects: ubiquity-slideshow-ubuntu (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Branch linked: lp:~willcooke/ubiquity-slideshow-ubuntu/ubiquity-
slideshow-ubuntu

** Branch unlinked: lp:~willcooke/ubiquity-slideshow-ubuntu/ubiquity-
slideshow-ubuntu

** Branch linked: lp:~willcooke/ubiquity-slideshow-ubuntu/ubiquity-
slideshow-ubuntu

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

Title:
  18.04 LTS Bionic Beaver Mascot

Status in Ubuntu theme:
  New
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Beavers attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1759601/+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 1759460] Re: RM: obsolete product click

2018-03-28 Thread Will Cooke

Thanks.  I thought we had already dropped this.  Anyway, thanks for
removing.

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

Title:
  RM: obsolete product click

Status in click package in Ubuntu:
  Fix Released

Bug description:
  $ for i in click click-dev click-doc gir1.2-click-0.4 gir1.2-click-0.4
  libclick-0.4-0 libclick-0.4-dev python3-click-package; do echo = $i =;
  reverse-depends $i; reverse-depends -b $i; done

  = click =
  No reverse dependencies found
  No reverse dependencies found

  = click-dev =
  No reverse dependencies found
  No reverse dependencies found

  = click-doc =
  No reverse dependencies found
  No reverse dependencies found

  = gir1.2-click-0.4 =
  Reverse-Depends
  ===
  * python3-click-package

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  No reverse dependencies found

  = gir1.2-click-0.4 =
  Reverse-Depends
  ===
  * python3-click-package

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  No reverse dependencies found

  = libclick-0.4-0 =
  Reverse-Depends
  ===
  * gir1.2-click-0.4
  * libclick-0.4-dev

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  No reverse dependencies found

  = libclick-0.4-dev =
  No reverse dependencies found
  No reverse dependencies found

  = python3-click-package =
  Reverse-Depends
  ===
  * click
  * click-dev

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  No reverse dependencies found

  Note that a "standard" search for $ reverse-depends src:click gets
  confused by the fact that src:click used to ship python3-click, but
  doesn't anymore due to a naming conflict with an unrelated
  python3-click.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1759460/+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 1759008] Re: Revert automatic suspend by default for bionic?

2018-03-27 Thread Will Cooke

** Also affects: ubuntu-settings (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

** Tags removed: rls-bb-incoming

** Changed in: ubuntu-settings (Ubuntu Bionic)
 Assignee: (unassigned) => Will Cooke (willcooke)

** Changed in: ubuntu-settings (Ubuntu Bionic)
 Assignee: Will Cooke (willcooke) => Jeremy Bicha (jbicha)

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

Title:
  Revert automatic suspend by default for bionic?

Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in ubuntu-settings source package in Bionic:
  Confirmed

Bug description:
  GNOME 3.28 has turned Automatic Suspend on by default and set it to 20
  minutes:

  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/2fdb48fa

  I generally think this is a good thing. There are a few issues though.

  1. The computer will still suspend even if there are remote users
  logged in or the computer is being used as a server for files,
  printers, etc.

  2. Some software doesn't set inhibit correctly. ~ahasenack mentioned
  he was using the Spotify Snap and the computer suspend after 20
  minutes. (Maybe Spotify needs to use the screen-inhibit-control snap
  interface.)

  3. Even if it does set inhibit, there is a report that the computer will 
suspend as soon as the inhibit is removed if there is no other activity. 
(Imagine a movie playing. At the end of the movie, the computer goes to sleep 
immediately.) More details and proposed fix at
  https://bugzilla.gnome.org/show_bug.cgi?id=705942#c21

  4. There is no GUI way to change this setting for the login screen yet.
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/22

  5. Some users think that desktop computers should be always running
  unless told otherwise. Personally, I don't give this argument much
  weight at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1759008/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

2018-03-26 Thread Will Cooke

** Tags added: rls-bb-incoming

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

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Confirmed
Status in d-conf package in Ubuntu:
  Triaged
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Triaged
Status in session-migration package in Ubuntu:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1735929/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

2018-03-26 Thread Will Cooke

** Tags added: incoming rs-bb-

** Tags removed: incoming rs-bb-
** Tags added: rls-bb-incoming

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1754671/+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 1755585] Re: Please remove indicator-network

2018-03-15 Thread Will Cooke

+1 to drop U8's indicator-network.  Confirmed with saviq.


** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  Please remove indicator-network

Status in indicator-network package in Ubuntu:
  New

Bug description:
  indicator-network has no remaining reverse dependencies in bionic.
  Please remove it from bionic.

  This is split off from LP: #1718254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1755585/+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 1755585] Re: Please remove indicator-network

2018-03-15 Thread Will Cooke

unity-greet-session-broadcast is being dealt with here:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter-session-broadcast/+bug/1747146

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

Title:
  Please remove indicator-network

Status in indicator-network package in Ubuntu:
  New

Bug description:
  indicator-network has no remaining reverse dependencies in bionic.
  Please remove it from bionic.

  This is split off from LP: #1718254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1755585/+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 1755184] Re: RM: obsolete product

2018-03-12 Thread Will Cooke

Assigning to vorlon as advised by xnox.


** Changed in: net-cpp (Ubuntu)
 Assignee: Will Cooke (willcooke) => Steve Langasek (vorlon)

** Changed in: unity-scopes-api (Ubuntu)
 Assignee: Will Cooke (willcooke) => Steve Langasek (vorlon)

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

Title:
  RM: obsolete product

Status in net-cpp package in Ubuntu:
  Triaged
Status in unity-scopes-api package in Ubuntu:
  Triaged

Bug description:
  unity-scopes-api was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:unity-scopes-api
  No reverse dependencies found

  $ reverse-depends -b src:unity-scopes-api
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-cpp/+bug/1755184/+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 1755184] Re: RM: obsolete product

2018-03-12 Thread Will Cooke

+1 good for removal.

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

Title:
  RM: obsolete product

Status in net-cpp package in Ubuntu:
  Triaged
Status in unity-scopes-api package in Ubuntu:
  Triaged

Bug description:
  unity-scopes-api was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:unity-scopes-api
  No reverse dependencies found

  $ reverse-depends -b src:unity-scopes-api
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-cpp/+bug/1755184/+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 1644323] Re: Installing unity8-session-snap adversely effects unity7

2018-03-07 Thread Will Cooke

** Changed in: canonical-devices-system-image
 Assignee: Will Cooke (willcooke) => (unassigned)

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in unity-gtk-module source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1647148] Re: Implement CUPS server snapd interface

2018-03-07 Thread Will Cooke

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

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

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

Title:
  Implement CUPS server snapd interface

Status in Canonical System Image:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released

Bug description:
  The CUPS server is an helpful feature, needed if you want to get
  convergence. Thanks for all your work, see you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1647148/+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 1539995] Re: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notfixing

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

Title:
  apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

Status in apport package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Partial Upgrade failed (crash)
  Ubuntu Mate 16 Alpha install testing on different machines.
  This machine Dell Optiplex 960

  linuxpusher@linuxpusher-OptiPlex-960:~$ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  
  linuxpusher@linuxpusher-OptiPlex-960:~$ sudo lshw
  [sudo] password for linuxpusher: 
  linuxpusher-optiplex-960  
  description: Computer
  width: 64 bits
  capabilities: smbios-2.5 vsyscall32
*-core
 description: Motherboard
 physical id: 0
   *-memory
description: System memory
physical id: 0
size: 7819MiB
   *-cpu
product: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
vendor: Intel Corp.
physical id: 1
bus info: cpu@0
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl 
aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 xsave lahf_lm dtherm tpr_shadow vnmi flexpriority
   *-pci
description: Host bridge
product: 4 Series Chipset DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 03
width: 32 bits
clock: 33MHz
configuration: driver=agpgart-intel
resources: irq:0
  *-display:0
   description: VGA compatible controller
   product: 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:33 memory:fe80-febf 
memory:d000-dfff ioport:ecb0(size=8)
  *-display:1 UNCLAIMED
   description: Display controller
   product: 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2.1
   bus info: pci@:00:02.1
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: pm bus_master cap_list
   configuration: latency=0
   resources: memory:fe70-fe7f
  *-communication:0
   description: Communication controller
   product: 4 Series Chipset HECI Controller
   vendor: Intel Corporation
   physical id: 3
   bus info: pci@:00:03.0
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list
   configuration: driver=mei_me latency=0
   resources: irq:34 memory:feda6000-feda600f
  *-ide
   description: IDE interface
   product: 4 Series Chipset PT IDER Controller
   vendor: Intel Corporation
   physical id: 3.2
   bus info: pci@:00:03.2
   version: 03
   width: 32 bits
   clock: 66MHz
   capabilities: ide pm msi bus_master cap_list
   configuration: driver=ata_generic latency=0
   resources: irq:18 ioport:fe80(size=8) ioport:fe90(size=4) 
ioport:fea0(size=8) ioport:feb0(size=4) ioport:fef0(size=16)
  *-communication:1
   description: Serial controller
   product: 4 Series Chipset Serial KT Controller
   vendor: Intel Corporation
   physical id: 3.3
   bus info: pci@:00:03.3
   version: 03
   width: 32 bits
   clock: 66MHz
   capabilities: pm msi 16550 bus_master cap_list
   configuration: driver=serial latency=0
   resources: irq:17 ioport:ecb8(size=8) memory:fe6d8000-fe6d8fff
  *-network
   description: Ethernet interface
   product: 82567LM-3 Gigabit Network Connection
   vendor: Intel Corporation
   physical id: 19
   bus info: pci@:00:19.0
   logical name: enp0s25
   version:

[Touch-packages] [Bug 1750514] Re: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest

** Also affects: cups (Ubuntu Bionic)
   Importance: High
 Assignee: Till Kamppeter (till-kamppeter)
   Status: Confirmed

** Tags removed: rls-bb-incoming

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

Title:
  cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs →
  get_printer_attrs → cupsdProcessIPPRequest

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  Confirmed
Status in cups source package in Bionic:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups.  This problem was most recently seen with package version 2.2.6-5, the 
problem page at 
https://errors.ubuntu.com/problem/1b152bc770a7f1c23d7cae98db205bf7a7f45feb 
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/cups/+bug/1750514/+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 1726124] Re: DNS domain search paths not updated when VPN started

We won't be able to add the option to select between the two options
this cycle.

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  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.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3: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

[Touch-packages] [Bug 1725921] Re: [regression] Combobox menus have gray text on gray background

** Also affects: ubuntu-themes (Ubuntu Bionic)
   Importance: High
 Assignee: Daniel van Vugt (vanvugt)
   Status: In Progress

** Tags removed: rls-bb-incoming

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

Title:
  [regression] Combobox menus have gray text on gray background

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress
Status in ubuntu-themes source package in Bionic:
  In Progress

Bug description:
  See pictures.

  Application: pcbnew
  Version: no-vcs-found-0b1eb56~60~ubuntu17.04.1, release build
  Libraries:
  wxWidgets 3.0.3
  libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 
(+libidn2/2.0.2) librtmp/2.3
  Platform: Linux 4.13.0-16-generic x86_64, 64 bit, Little endian, wxGTK
  Build Info:
  wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
  Boost: 1.62.0
  Curl: 7.52.1
  Compiler: GCC 6.3.0 with C++ ABI 1010

  Build settings:
  USE_WX_GRAPHICS_CONTEXT=OFF
  USE_WX_OVERLAY=OFF
  KICAD_SCRIPTING=ON
  KICAD_SCRIPTING_MODULES=ON
  KICAD_SCRIPTING_WXPYTHON=ON
  KICAD_SCRIPTING_ACTION_MENU=ON
  BUILD_GITHUB_PLUGIN=ON
  KICAD_USE_OCE=ON
  KICAD_SPICE=ON

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1725921/+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 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"