[Touch-packages] [Bug 1945645] Re: cups-pdf prints blank pages

2021-10-04 Thread Till Kamppeter
Two confirmations that the problem is solved, so I close this bug as
fixed.

Thanks for the bug report and the confirmations that it is fixed.

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

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

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

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

Title:
  cups-pdf prints blank pages

Status in cups package in Ubuntu:
  Invalid
Status in cups-pdf package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Invalid
Status in ghostscript package in Debian:
  New

Bug description:
  after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf
  printer started to print blank pages (to create washed pdf files)

  printer-driver-cups-pdf, version 3.0.1-10

  Description:Ubuntu Impish Indri (development branch)
  Release:21.10

  printer-driver-cups-pdf:
Installed: 3.0.1-10
Candidate: 3.0.1-10
Version table:
   *** 3.0.1-10 500
  500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: printer-driver-cups-pdf 3.0.1-10
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Sep 30 15:56:51 2021
  InstallationDate: Installed on 2020-03-17 (561 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205)
  Lpstat: device for PDF: cups-pdf:/
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  SourcePackage: cups-pdf
  UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago)

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


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


[Touch-packages] [Bug 1945645] Re: cups-pdf prints blank pages

2021-10-04 Thread Till Kamppeter
I have synced cups-pdf 3.0.1-13 into Ubuntu Impish now (see bug
1945939).

As soon as you get this version with your updates, please re-test and
tell us here how far it solves your problems. Thanks.

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

Title:
  cups-pdf prints blank pages

Status in cups package in Ubuntu:
  Confirmed
Status in cups-pdf package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Confirmed
Status in ghostscript package in Debian:
  New

Bug description:
  after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf
  printer started to print blank pages (to create washed pdf files)

  printer-driver-cups-pdf, version 3.0.1-10

  Description:Ubuntu Impish Indri (development branch)
  Release:21.10

  printer-driver-cups-pdf:
Installed: 3.0.1-10
Candidate: 3.0.1-10
Version table:
   *** 3.0.1-10 500
  500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: printer-driver-cups-pdf 3.0.1-10
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Sep 30 15:56:51 2021
  InstallationDate: Installed on 2020-03-17 (561 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205)
  Lpstat: device for PDF: cups-pdf:/
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  SourcePackage: cups-pdf
  UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago)

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


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


[Touch-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected

2021-04-12 Thread Till Kamppeter
Please report on the new GitHub of CUPS on OpenPrinting:

https://github.com/OpenPrinting/cups/issues

On Apple the CUPS project is dead and bug reports probably not read any
more.

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```

  It's also easy to test by invoking the backend by hand:

  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take hours to complete.

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

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


[Touch-packages] [Bug 1917074] Re: cups ppi parameter should be a string

2021-02-26 Thread Till Kamppeter
Thank you very much.

** Changed in: cups
   Importance: Undecided => Unknown

** Changed in: cups
   Status: New => Unknown

** Changed in: cups
 Remote watch: None => github.com/OpenPrinting/cups/issues #115

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

Title:
  cups ppi parameter should be a string

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  New
Status in cups-filters package in Ubuntu:
  New

Bug description:
  cups encode.c treats parameter ppi as an integer, but it should be a
  string.

  the image filter drivers expect the form ppi=300x600
  to specify source image dpi for images where it is asymmetric.

  I encountered this issue trying to print full-sized images without scaling on 
a dymo 450 label printer.
  This bug causes images to print across 2 labels when trying to use the 
300x600dpi graphics mode.

  This should print a single label:
  lpr -o ppi=300x600 -o scaling=0 -o PageSize=w167h288 -o PageRegion=w167h288 
-o Resolution=300x600dpi -o DymoHalftoning=Default -o DymoPrintDensity=Medium 
-o DymoPrintQuality=Graphics -o MediaDimensions=w167h288 
~/Desktop/test_Graphics_portrait.png

  where the png is a 664*2224 image without any dpi metadata.
  Instead the ppi option gets sanitized to 300, and the image gets printed 
across 2 labels.

  
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
   *** 2.3.1-9ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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


[Touch-packages] [Bug 1917074] Re: cups ppi parameter should be a string

2021-02-26 Thread Till Kamppeter
Please report this upstream on

https://github.com/OpenPrinting/cups

as this is not only concerning Ubuntu, but any OS which uses CUPS.

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

Title:
  cups ppi parameter should be a string

Status in CUPS:
  New
Status in cups package in Ubuntu:
  New
Status in cups-filters package in Ubuntu:
  New

Bug description:
  cups encode.c treats parameter ppi as an integer, but it should be a
  string.

  the image filter drivers expect the form ppi=300x600
  to specify source image dpi for images where it is asymmetric.

  I encountered this issue trying to print full-sized images without scaling on 
a dymo 450 label printer.
  This bug causes images to print across 2 labels when trying to use the 
300x600dpi graphics mode.

  This should print a single label:
  lpr -o ppi=300x600 -o scaling=0 -o PageSize=w167h288 -o PageRegion=w167h288 
-o Resolution=300x600dpi -o DymoHalftoning=Default -o DymoPrintDensity=Medium 
-o DymoPrintQuality=Graphics -o MediaDimensions=w167h288 
~/Desktop/test_Graphics_portrait.png

  where the png is a 664*2224 image without any dpi metadata.
  Instead the ppi option gets sanitized to 300, and the image gets printed 
across 2 labels.

  
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
   *** 2.3.1-9ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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


[Touch-packages] [Bug 1846334] Re: cupsd assert failure: free(): invalid pointer

2020-12-14 Thread Till Kamppeter
Hirsute has now the newest CUPS (2.3.3op1) with all fixes and patches.
This should also include the patch mentioned.

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

Title:
  cupsd assert failure: free(): invalid pointer

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Just running in the background, no user action (printing)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-daemon 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: free(): invalid pointer
  Date: Tue Oct  1 19:41:35 2019
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2019-02-09 (234 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: letter
  PpdFiles:
   HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere
   Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at 
malloc.c:5332
   _int_free (av=, p=, have_lock=0) at 
malloc.c:4173
   ?? () from /lib/x86_64-linux-gnu/libcups.so.2
   ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2
  Title: cupsd assert failure: free(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  separator:

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

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


[Touch-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

2020-12-01 Thread Till Kamppeter
I have searched the code of cups-browsed and libcupsfilters and did not
find any call of the mentioned functions which require CAP_SYS_NICE.
Most probably some of the library functions cups-browsed is using
contains such calls.

As cups-browsed works correctly I suggest to add the "deny capability
sys_nice," to silence the log messages.

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

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

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


[Touch-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

2020-12-01 Thread Till Kamppeter
I did not have anything to control the priority in the source code of
cups-browsed, I also did not find anything in the packaging of cups-
filters. I also do not see any security risk in priority changing, it
can only make the system faster or slower.

Perhaps systemd does the nice level change? How do I investigate this?

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

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

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


[Touch-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

2020-12-01 Thread Till Kamppeter
Anyone of the security team, does allowing the "sys_nice" capability for
cups-browsed cause any possible security risk?

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

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

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


[Touch-packages] [Bug 1900348] Re: Canon TS705 printer stopped working

2020-11-18 Thread Till Kamppeter
This is not a problem of CUPS, Turboprint also uses CUPS. This is a
problem of the printer driver.

For me it looks like a problem of Canon's proprietary driver which you
have used before you switched to Turboprint. With an update of your
Ubuntu system some library or other file needed by Canon's driver got
removed.

Before paying for Turboprint you can try to create a new print queue for
you printer, using another driver. Remove Canon's driver before trying
this to not get your new print queue set up with Canon's driver again.


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

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

Title:
  Canon TS705 printer stopped working

Status in cups package in Ubuntu:
  Invalid

Bug description:
  My Canon TS705 printer stopped working in Ubuntu. Last time I used it
  was over a week ago so it could be something with the updates
  installed in the last two weeks. The printer queue says "filter
  failed". I've attached the cups log of the last print job.

  I already tried (besides rebooting) removing / installing the printer
  and reinstalling the canon driver package.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 18 20:42:50 2020
  InstallationDate: Installed on 2019-09-20 (394 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190919)
  Lpstat: Gerät für CanonTS705: cnijbe2://canon/?port=usb=10746E
  MachineType: Dell Inc. Latitude 5591
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/CanonTS705.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/CanonTS705.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-51-generic 
root=UUID=c0cdf9a7-59c9-4ce4-8dfa-06ad760e34a5 ro quiet splash 
usbcore.autosuspend=-1 vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0CGP1G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd05/23/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0CGP1G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5591
  dmi.product.sku: 0819
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1891987] Re: epson stylus photo rx560 is detected, added, but when printing, task is ending up immediatelly with success

2020-10-19 Thread Till Kamppeter
I think best is that you go through all applicable parts of

https://wiki.ubuntu.com/DebuggingPrintingProblems

Especially I need

- How is your printer connected (USB, network)
- All info about the healthiness of the connection (see the USB and network 
connection sections)
- The PPD file(s) of your print queues (in /etc/cups/ppd/)
- Thew CUPS error_log (in debug mode) from an execution of a print job
- Input files you tried to print without success

The output of the command

driverless

(to see whether there are alternative approaches to use the printer)

Please attach all logs, files, ... one by one, do not compress them and
do not package them together (so one can navigate through everything of
the bug report inside the browser).

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

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

Title:
  epson stylus photo rx560 is detected, added, but when printing, task
  is ending up immediatelly with success

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Tried with both manufacturer and gutenprint driver:

  1. plug an epson stylus photo rx560 via usb
  2. add the driver (manufacturer first, retried with gutenprint) autodetected 
our gtk ubuntu specific application.
  3. Tried to print with multiple apps: the task is queued and then immediately 
terminated with success. Nothing is printed.

  
  $ lsmod | grep usb
  usb_storage77824  1 uas
  usblp  24576  0
  btusb  57344  0
  btrtl  24576  1 btusb
  btbcm  16384  1 btusb
  btintel24576  1 btusb
  bluetooth 581632  31 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  usbhid 57344  0
  hid   131072  2 usbhid,hid_generic

  Logs when adding the printer:
  $ tail -f /var/log/syslog 
  Aug 18 09:36:00 casanier kernel: [ 2570.342143] usb 1-1: new high-speed USB 
device number 10 using xhci_hcd
  Aug 18 09:36:00 casanier kernel: [ 2570.501144] usb 1-1: New USB device 
found, idVendor=04b8, idProduct=0827, bcdDevice= 1.00
  Aug 18 09:36:00 casanier kernel: [ 2570.501150] usb 1-1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Aug 18 09:36:00 casanier kernel: [ 2570.501154] usb 1-1: Product: USB2.0 
MFP(Hi-Speed)
  Aug 18 09:36:00 casanier kernel: [ 2570.501157] usb 1-1: Manufacturer: EPSON
  Aug 18 09:36:00 casanier kernel: [ 2570.501159] usb 1-1: SerialNumber: 
LH1010609180813040
  Aug 18 09:36:00 casanier kernel: [ 2570.514421] usblp 1-1:1.1: usblp0: USB 
Bidirectional printer dev 10 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0827
  Aug 18 09:36:00 casanier kernel: [ 2570.516384] usb-storage 1-1:1.2: USB Mass 
Storage device detected
  Aug 18 09:36:00 casanier kernel: [ 2570.516676] scsi host5: usb-storage 
1-1:1.2
  Aug 18 09:36:00 casanier systemd[1]: Started Configure Plugged-In Printer.
  Aug 18 09:36:00 casanier udev-configure-printer: add usb-001-010
  Aug 18 09:36:00 casanier udev-configure-printer: device devpath is 
/devices/pci:00/:00:14.0/usb1/1-1
  Aug 18 09:36:00 casanier udev-configure-printer: Device already handled
  Aug 18 09:36:00 casanier systemd[1]: configure-printer@usb-001-010.service: 
Main process exited, code=exited, status=1/FAILURE
  Aug 18 09:36:00 casanier systemd[1]: configure-printer@usb-001-010.service: 
Failed with result 'exit-code'.
  Aug 18 09:36:01 casanier kernel: [ 2571.538832] scsi 5:0:0:0: Direct-Access   
  EPSONStylus Storage   1.00 PQ: 0 ANSI: 2
  Aug 18 09:36:01 casanier kernel: [ 2571.539702] sd 5:0:0:0: Attached scsi 
generic sg0 type 0
  Aug 18 09:36:01 casanier kernel: [ 2571.545241] sd 5:0:0:0: Power-on or 
device reset occurred
  Aug 18 09:36:01 casanier kernel: [ 2571.601212] sd 5:0:0:0: [sda] Attached 
SCSI removable disk
  ^C
  $ ls -l /dev/usb/lp0 
  crw-rw 1 root lp 180, 0 août  18 09:36 /dev/usb/lp0
  $ ls -l /dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 août  18 08:53 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   1 août  18 08:53 /dev/bus/usb/001/002
  crw-rw-r--  1 root root189,   2 août  18 08:53 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 août  18 08:53 /dev/bus/usb/001/004
  crw-rw  1 root plugdev 189,   4 août  18 08:53 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 août  18 08:53 /dev/bus/usb/001/006
  crw-rw-r--+ 1 root lp  189,   9 août  18 09:36 /dev/bus/usb/001/010
  crw-rw-r--  1 root root189, 128 août  18 08:53 /dev/bus/usb/002/001
  $ sudo usb_printerid /dev/usb/lp0
  GET_DEVICE_ID string:
  MFG:EPSON;CMD:ESCPL2,BDC,D4,D4PX,ESCPR1;MDL:Stylus Photo 
RX560;CLS:PRINTER;DES:EPSON Stylus Photo RX560;
  $ lpinfo -v
  file cups-brf:/
  network socket
  network lpd
  network http
  network beh
  network https
  network ipp
  direct hp
  network ipps
  direct 

[Touch-packages] [Bug 1895265] Re: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)

2020-09-11 Thread Till Kamppeter
*** This bug is a duplicate of bug 1894452 ***
https://bugs.launchpad.net/bugs/1894452

** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)

** This bug has been marked a duplicate of bug 1894452
   shutdown delay because of cups

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups-filters package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1895265/+subscriptions

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


[Touch-packages] [Bug 1894452] Re: shutdown delay because of cups

2020-09-07 Thread Till Kamppeter
The shutdown problem of cups-browsed was already identified and is fixed
in the GitHub repository of cups-filters. This fix will be included in
cups-filters 1.28.2 which will get released soon.

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

** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)

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

Title:
  shutdown delay because of cups

Status in cups-filters package in Ubuntu:
  Triaged

Bug description:
  Both my desktop and laptop running 20.10 have a 90 second delay
  shutting down (power off or restart).  Getting message;

  A stop job is Running for Make remote CUPS printers available locally

  After 90 seconds the shutdown continues to completion.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: cups 2.3.3-2ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sun Sep  6 18:10:20 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  KernLog:
   
  Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131
  MachineType: CLEVO CO. W35_37ET
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ENVY_4500.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1894452/+subscriptions

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


[Touch-packages] [Bug 1873429] Re: Problem with printing in 20.04 version

2020-08-14 Thread Till Kamppeter
Andrew Bell, Alex Tasin, please provide an error_log of CUPS in debug
mode of a failing job. see
https://wiki.ubuntu.com/DebuggingPrintingProblems#CUPS_error_log for
instructions. Also provide the PPD file of your printer (from
/etc/cups/ppd/).

Please attach the files on by one, do not compress them and do not
package them together. Thanks.

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

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

Title:
  Problem with printing in 20.04 version

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  In previous 19.10 my Epson Stylus CX3600 both prints & scans fine.

  In 20.04 it scans fine, but in print mode the process banners show the
  job is sent to the printer, then printing is complete. However there
  is no print output. I reinstalled the Epson print drivers but without
  success.

  I'm staying on 20.04, but by running Ubuntu 19.10 from a USB drive the
  printing issue is solved. The Epson is recognised and my documents
  print and scan fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 17 10:59:10 2020
  InstallationDate: Installed on 2019-12-10 (128 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-01 (15 days ago)

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

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


[Touch-packages] [Bug 1875673] Re: printer canon ip4600 only generic text mode

2020-07-15 Thread Till Kamppeter
printer-driver-gutenprint should be seeded. Adding ubuntu-meta task.

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

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

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

Title:
  printer canon ip4600 only generic text mode

Status in cups package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  with ubuntu 19.10, my printer was working fine.
  after upgrade to 20.04, cups cannot find the correct driver and install a 
generic text only driver.

  now, to be able to print pictures and pdf's, I only have 2 solutions:
  - boot windows 10 (through my grub multiboot)
  - boot an ubuntu 19.10 iso file (through grub -> loop) --> ubuntu 19.10 iso 
(it still works fine)

  the linux 64 driver is not available any more on canon site (only
  windows and mac)

  please indicate driver location and installation instructions. thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:25:41 2020
  InstallationDate: Installed on 2020-04-27 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for iP4600: usb://Canon/iP4600%20series?serial=910778
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/iP4600.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/iP4600.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=810543d2-304c-4499-bd10-0e45cc37d01a ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0507
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2A74-AM SE
  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.:bvr0507:bd04/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A74-AMSE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Touch-packages] [Bug 1885111] Re: 3 ports disabled

2020-06-26 Thread Till Kamppeter
Thank you very much, I have closed the bug now.

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

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

Title:
  3 ports disabled

Status in cups package in Ubuntu:
  Invalid

Bug description:
  The printer (which is now broken) we used seem to disable the ports.
  I don't know how to fix this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18
  Uname: Linux 4.15.0-106-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Jun 25 09:53:44 2020
  DistUpgraded: 2019-01-03 13:59:44,209 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a2a] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GT216M [GeForce GT 230M] [104d:905e]
  InstallationDate: Installed on 2016-12-22 (1281 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Sony Corporation VPCCW1AGG
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic 
root=UUID=a904e50d-625f-4d72-929f-b72fcad907ef ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-01-03 (538 days ago)
  dmi.bios.date: 09/22/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0190Y5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y5:bd09/22/2009:svnSonyCorporation:pnVPCCW1AGG:pvrC6031Z7V:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCCW1AGG
  dmi.product.version: C6031Z7V
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Jan  3 08:58:12 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.3
  xserver.video_driver: nouveau

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

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


[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

2020-06-17 Thread Till Kamppeter
** Changed in: network-manager (Ubuntu)
 Assignee: Till Kamppeter (till-kamppeter) => (unassigned)

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

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

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


[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight

2020-06-16 Thread Till Kamppeter
I have already found a solution for this and applied it upstream
(1.27.5, already in Grrovy).

The problem is that near midnight, for the log rotate cups-browsed is
stopped and restarted. Stopping cups-browsed makes the cups-browsed-
generated print queues getting removed and when re-starting cups-browsed
afterwards they are generated again. This causes the notifications.

My approach is to let cups-browsed not remove the queues on shut-down,
on re-start cups-browsed connects to these queues again (as I have
designed cups-browsed to cope with crashes) and so no queue-creation
happens.

Zdenek Dohnal from Red Hat suggests modifying gnome-settings-daemon to
identify queues coming from cups-browsed and not notifying then. See

https://github.com/OpenPrinting/cups-filters/issues/241

Marking as fixed as my approach has made it into Groovy already.

** Bug watch added: github.com/OpenPrinting/cups-filters/issues #241
   https://github.com/OpenPrinting/cups-filters/issues/241

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

** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)

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

Title:
  Printer notification every day at midnight

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1869981/+subscriptions

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


[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight

2020-06-05 Thread Till Kamppeter
** Changed in: cups (Ubuntu)
   Status: Expired => Triaged

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Triaged

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-25 Thread Till Kamppeter
Stefano, thanks for the Mate forum link, I have tried to make up the sum
of the tips to help users get HPLIP working again.

So anyone here, please try to clean up any HPLIP mess on your system
using the following steps:

1. Remove HPLIP deb-packages

sudo dpkg -P --force-depends hplip hplip-data hplip-doc hplip-gui \
libsane-hpaio printer-driver-hpcups printer-driver-hpijs 
printer-driver-postscript-hp \
hpijs-ppds libhpmud0

2. Remove upstream-installed HPLIP using HPLIP binary uninstaller

wget https://nchc.dl.sourceforge.net/project/hplip/hplip/3.20.3/hplip-3.20.3.run
sh hplip-3.20.3.run --noexec
cd hplip-3.20.3
sudo python3 ./uninstall.py
sudo rm -rf /usr/share/hplip/

3. Reinstall deb-packages with:

sudo apt install -f hplip-gui printer-driver-hpcups printer-driver-
postscript-hp libsane-hpaio

Then try to create a print queue with hp-setup and, if needed load the
proprietary plugin with hp-plugin. Also printer setup with GNOME Control
Center or system-config-printer should work again.

DO NOT install printer-driver-hpijs and hpijs-ppds. These packages are
deprecated and not maintained any more, and they also have no benefit
compared to printer-driver-hpcups.

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-25 Thread Till Kamppeter
Could you try

lpadmin -p DJ3630 -E -v ipp://localhost:6/ipp/print -m everywhere

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-22 Thread Till Kamppeter
Could you try:

lpadmin -p DJ3630 -E -v
ipp://DeskJet%203630%20series%20%5BCN8AM7H3230658%5D._ipp._tcp.local/ -m
everywhere

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-22 Thread Till Kamppeter
Please

- Remove the .snap of HPLIP, it is experimental

- Remove any HPLIP version installed directly from HP

- Re-install Ubuntu's HPLIP via the command:

  sudo apt install --reinstall printer-driver-hpcups printer-driver-
postscript-hp libsane-hpaio hplip-gui hplip hplip-data libhpmud0

  Please post the output of this command here.

- Remove your current print queues with the commands:

  lpadmin -x DeskJet_3630
  lpadmin -x HP_DeskJet_3630_series

- Unplug the printer from USB and re-plug it. Does a new print queue get
created ("lpstat -v" should show it)? Can you print using this queue?

- Could you create a driverless print queue (this queue does not use
HPLIP but common, manufacturer-independent communication protocols of
the printer)? Use the command

  lpadmin -p DJ3630 -E -v
ipp://HP%20DeskJet%203630%20series%20%5B9B20BB%5D._ipp._tcp.local/ -m
everywhere

  Can you print with this print queue?

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-21 Thread Till Kamppeter
On the machine where you still have the problem could you remove your
print queue and then unplug and re-plug the printer? Does a new print
queue get automatically created?

What is the output of the following commands and post the output here:

lpstat -v
driverless
ps auxwww | grep ippusbxd

If a queue actually got auto-created for your printer, couls you attach
the queue's PPD file from /etc/cups/ppd/ here?

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

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

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1721704] Re: Printer settings stuck on loading drivers database

2020-05-19 Thread Till Kamppeter
*** This bug is a duplicate of bug 1872564 ***
https://bugs.launchpad.net/bugs/1872564

** This bug has been marked a duplicate of bug 1872564
   /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

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

Title:
  Printer settings stuck on loading drivers database

Status in apparmor package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Incomplete

Bug description:
  1) Description:   Ubuntu Artful Aardvark (development branch)
 Release:   17.10
  2) ubuntu-settings:
 Installed: 17.10.17
 Candidate: 17.10.17
  3) The printer configuration goes fine and I can print
  4) Printer settings stuck on loading drivers database and finally no drivers 
list available. Only 'cancel' button active.

  Note: I'm trying to configure a Brother HL-2030 connected to Network
  through a FritzBox 7940 router. The printer works fine both on Fedora
  and macOS X systems. I opened 'System Settings', then select 'Devices'
  > 'Printers' > 'Add a Printer'. I entered the router address and the
  window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I
  selected the printer and pressed the 'Add' button, a window 'Select
  Printer Driver' appears and stuck with 'Loading drivers database...'.
  After about 2 minutes, stopped loading and remains blank. No drivers
  selection is available and I can only push the 'Cancel' button.

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

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


[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-19 Thread Till Kamppeter
Where did you get a .snap from HPLIP?

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1721704] Re: Printer settings stuck on loading drivers database

2020-05-19 Thread Till Kamppeter
Seems that some of the general AppArmor rules needs to get updated.

Access to /proc/sys/kernel/random/boot_id seems to be needed now.

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

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

Title:
  Printer settings stuck on loading drivers database

Status in apparmor package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Incomplete

Bug description:
  1) Description:   Ubuntu Artful Aardvark (development branch)
 Release:   17.10
  2) ubuntu-settings:
 Installed: 17.10.17
 Candidate: 17.10.17
  3) The printer configuration goes fine and I can print
  4) Printer settings stuck on loading drivers database and finally no drivers 
list available. Only 'cancel' button active.

  Note: I'm trying to configure a Brother HL-2030 connected to Network
  through a FritzBox 7940 router. The printer works fine both on Fedora
  and macOS X systems. I opened 'System Settings', then select 'Devices'
  > 'Printers' > 'Add a Printer'. I entered the router address and the
  window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I
  selected the printer and pressed the 'Add' button, a window 'Select
  Printer Driver' appears and stuck with 'Loading drivers database...'.
  After about 2 minutes, stopped loading and remains blank. No drivers
  selection is available and I can only push the 'Cancel' button.

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

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


[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-19 Thread Till Kamppeter
Is the hplip package installed on your system?

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-19 Thread Till Kamppeter
Please run the command

dpkg -l | grep hplip

and post the output here.

Also did you ever try to install HPLIP from the upstream site? Did you
ever try to remove such an installation?

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

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-19 Thread Till Kamppeter
** Also affects: hplip (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1878322] Re: cupsaddsmb

2020-05-14 Thread Till Kamppeter
cupsaddsmb got discontinued upstream. It is not part of the CUPS package
any more.

This happened in Dec 2018 already.

Closing ...


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

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

Title:
  cupsaddsmb

Status in cups package in Ubuntu:
  Invalid

Bug description:
  this app is not into this package !

  ubuntu server 20.04

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

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


[Touch-packages] [Bug 1878482] Re: EPSON WF 3520 driver problem - PpdFiles: Error

2020-05-14 Thread Till Kamppeter
What is the actual problem here? Is the printer model not found during
setup? Are you not able to print?

Could you follow the instructions on

https://wiki.ubuntu.com/DebuggingPrintingProblems

Thanks.

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

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

Title:
  EPSON WF 3520 driver problem - PpdFiles: Error

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  doesn't work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 23:17:35 2020
  InstallationDate: Installed on 2020-05-06 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for Generic-ESC-P-Dot-Matrix: lpd://192.168.1.133:515/PASSTHRU
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b413 Chicony Electronics Co., Ltd FJ Camera
   Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=85a6cbd6-a8d0-4ee5-ac82-9f54acbb0106 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2016
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.21
  dmi.board.name: FJNBB3E
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.21:bd05/31/2016:svnFUJITSU:pnLIFEBOOKA555:pvr:rvnFUJITSU:rnFJNBB3E:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A555
  dmi.sys.vendor: FUJITSU

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

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


[Touch-packages] [Bug 1877528] Re: Applet does not terminate at end of X desktop session

2020-05-13 Thread Till Kamppeter
Added systemd task because of the this comment on the upstream but by
the original poster of this Ubuntu bug report:

https://github.com/OpenPrinting/system-config-
printer/issues/175#issuecomment-627870677


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

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

Title:
  Applet does not terminate at end of X desktop session

Status in System Config Printer:
  New
Status in lightdm package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in system-config-printer package in Debian:
  Unknown

Bug description:
  This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal.

  I log into the Xfce desktop, and then logout. The screen returns to
  the LightDM login screen.

  A few minutes later, "loginctl list-sessions" shows the following:

  SESSION  UID USERSEAT  TTY  
90 root   
   c2 1000 skunk   seat0  
   c3  116 lightdm seat0  

  3 sessions listed.

  Output from "loginctl session-status c2":

  c2 - skunk (1000)
 Since: Fri 2020-05-08 03:09:05 EDT; 9min ago
Leader: 2530
  Seat: seat0; vc7
   Display: :0
   Service: lightdm; type x11; class user
   Desktop: xubuntu
 State: closing
  Unit: session-c2.scope
└─2856 /usr/bin/python3 
/usr/share/system-config-printer/applet.py

  This process sticks around forever until I kill it, or its parent
  "systemd --user" process. Only then does the session disappear from
  list-sessions.

  When I run "session-status" while I'm logged in, I see a list of
  nearly 30 desktop-related processes. All of them except this one go
  away on logout. This one should too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1877528/+subscriptions

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


[Touch-packages] [Bug 1877528] Re: Applet does not terminate at end of X desktop session

2020-05-13 Thread Till Kamppeter
I did not find the package which contains kdm (probably the desktop
manager of KDE), if someone could add the appropriate task for this one
would be great.

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

Title:
  Applet does not terminate at end of X desktop session

Status in System Config Printer:
  New
Status in lightdm package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Triaged

Bug description:
  This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal.

  I log into the Xfce desktop, and then logout. The screen returns to
  the LightDM login screen.

  A few minutes later, "loginctl list-sessions" shows the following:

  SESSION  UID USERSEAT  TTY  
90 root   
   c2 1000 skunk   seat0  
   c3  116 lightdm seat0  

  3 sessions listed.

  Output from "loginctl session-status c2":

  c2 - skunk (1000)
 Since: Fri 2020-05-08 03:09:05 EDT; 9min ago
Leader: 2530
  Seat: seat0; vc7
   Display: :0
   Service: lightdm; type x11; class user
   Desktop: xubuntu
 State: closing
  Unit: session-c2.scope
└─2856 /usr/bin/python3 
/usr/share/system-config-printer/applet.py

  This process sticks around forever until I kill it, or its parent
  "systemd --user" process. Only then does the session disappear from
  list-sessions.

  When I run "session-status" while I'm logged in, I see a list of
  nearly 30 desktop-related processes. All of them except this one go
  away on logout. This one should too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1877528/+subscriptions

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


[Touch-packages] [Bug 1877528] Re: Applet does not terminate at end of X desktop session

2020-05-13 Thread Till Kamppeter
The upstream author has tested and found out that the problem only
occurs with lightdm and not with gdm as desktop manager, especially the
ones showing the problem are sddm, kdm, lightdm and the ones not showing
the problem are gdm and lxdm. Adding desktop manager tasks ...

See this comment and following:

https://github.com/OpenPrinting/system-config-
printer/issues/175#issuecomment-627771765

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

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

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

Title:
  Applet does not terminate at end of X desktop session

Status in System Config Printer:
  New
Status in lightdm package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Triaged

Bug description:
  This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal.

  I log into the Xfce desktop, and then logout. The screen returns to
  the LightDM login screen.

  A few minutes later, "loginctl list-sessions" shows the following:

  SESSION  UID USERSEAT  TTY  
90 root   
   c2 1000 skunk   seat0  
   c3  116 lightdm seat0  

  3 sessions listed.

  Output from "loginctl session-status c2":

  c2 - skunk (1000)
 Since: Fri 2020-05-08 03:09:05 EDT; 9min ago
Leader: 2530
  Seat: seat0; vc7
   Display: :0
   Service: lightdm; type x11; class user
   Desktop: xubuntu
 State: closing
  Unit: session-c2.scope
└─2856 /usr/bin/python3 
/usr/share/system-config-printer/applet.py

  This process sticks around forever until I kill it, or its parent
  "systemd --user" process. Only then does the session disappear from
  list-sessions.

  When I run "session-status" while I'm logged in, I see a list of
  nearly 30 desktop-related processes. All of them except this one go
  away on logout. This one should too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1877528/+subscriptions

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


[Touch-packages] [Bug 1864207] Re: Update request: 0.8.0 released

2020-04-08 Thread Till Kamppeter
 Bischoff, James Rudd, Jan Alexander
  Steffens (heftig), Karl Cronburg, Krzesimir Nowak, Mario Blättermann, Martin
  Blanchard, Michal Sekletar, msk-nightingale, Philip Prindeville, Piotr Drąg,
  Rafael Fontenelle, scootergrisen, Simon Lauser, Simon McVittie, Thomas 
Jollans,
  Till Kamppeter, Tony Garnock-Jones, Trent Lloyd, wisd0me, Yclept Nemo, Zlopez,
  Дамјан Георгиевски.

  This release is backwards compatible with Avahi 0.6.x and 0.7.

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

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


[Touch-packages] [Bug 1864207] Re: Update request: 0.8.0 released

2020-04-08 Thread Till Kamppeter
s. It is suggested that clients may wish to
  either check for and fallback to the older API version, or continue to use the
  OLD API and rely on the 10ms timer to resolve the issue.

  Big thank-you to everyone contributing to the project through issues & pull
  requests, including the the following people who contributed changes to this
  release: Daniel S, David Kerr, Eric Bischoff, James Rudd, Jan Alexander
  Steffens (heftig), Karl Cronburg, Krzesimir Nowak, Mario Blättermann, Martin
  Blanchard, Michal Sekletar, msk-nightingale, Philip Prindeville, Piotr Drąg,
  Rafael Fontenelle, scootergrisen, Simon Lauser, Simon McVittie, Thomas 
Jollans,
  Till Kamppeter, Tony Garnock-Jones, Trent Lloyd, wisd0me, Yclept Nemo, Zlopez,
  Дамјан Георгиевски.

  This release is backwards compatible with Avahi 0.6.x and 0.7.

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

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


[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight

2020-04-01 Thread Till Kamppeter
This thread started with 20.04, so I thought you have 20.04, too. 20.04
comes with cups-browsed 1.27.3 and this version would not create this
extra queue any more about which you are complaining.

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight

2020-04-01 Thread Till Kamppeter
Could you check which version of cups-browsed are you using?

dpkg -l cups-browsed

Looking into your cups-browsed_log it seems that you have an old
version.

To clean up any possible mess you could try

sudo apt install --reinstall cups-browsed

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight

2020-04-01 Thread Till Kamppeter
Could you stp cups-browsed, then run

lpstat -v

post the output here, then run

lpadmin -x HP_OfficeJet_Pro_7740_series_7646EB_@HP40B0347646EB.local

Now start cups-browsed again and wait until you get a notification, or
if there does not show any, for something like two minutes.

Now run

lpstat -v

again and post the output. Also attach /var/log/cups/cups-browsed_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/1869981

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight

2020-04-01 Thread Till Kamppeter
Please run the command

lpstat -v

and post the output here. Thanks.

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight

2020-04-01 Thread Till Kamppeter
Could you edit /etc/cups/cups-browsed.conf to have a line

DebugLogging file

and then restart cups-browsed?

Once done, restart CUPS and wait until you get the notification. Then
attach /var/log/cups/cups-browsed_log to this bug report.

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight

2020-04-01 Thread Till Kamppeter
@mdeslaur, could you attach your /etc/cups/cups-browsed.conf file to
this bug report? Thanks.

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight

2020-04-01 Thread Till Kamppeter
When did the notifications start to occur? Are you running 20.04 already
for longer and suddenly, probably after an update, the notifications
started? Or did you switch from an older Ubuntu version (18.04, 19.10)
to 20.04 and after this upgrade the notifications started? Or did you
even observe the notifications on an Ubuntu version older than 20.04?

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

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-03-25 Thread Till Kamppeter
Also reported to Debian

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954885

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

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

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid
Status in libmtp package in Debian:
  Unknown

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-03-21 Thread Till Kamppeter
Attached debdiff fixes this bug in the libmtp package, applying
effectively the patch of the previous comment.

** Patch added: "libmtp_1.1.17-2_1.1.17-2ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1863239/+attachment/5339786/+files/libmtp_1.1.17-2_1.1.17-2ubuntu1.debdiff

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

** Changed in: libmtp (Ubuntu)
   Status: Fix Committed => In Progress

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-03-19 Thread Till Kamppeter
Correction for the patch, please use this one.

** Patch added: "69-libmtp.rules.patch"
   
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1863239/+attachment/5339060/+files/69-libmtp.rules.patch

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-03-19 Thread Till Kamppeter
The attached patch would fix this bug. It adds two rules to skip
printers. The second skips all kinds of printers by checking whether the
standard interface of a printer is present in the USB device. The first
skips HP printers, it is the same rule as HPLIP uses. I have added it
because it covers a second interface, which is probably of some weird
proprietary HP printer devices. For my printer the bug goes away with
this patch, also with any one of the two rules commented out.

I think one can assume that there is no printer available which doubles
as a media player.

** Patch added: "69-libmtp.rules.patch"
   
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1863239/+attachment/5339056/+files/69-libmtp.rules.patch

** Tags added: patch

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-03-19 Thread Till Kamppeter
There was already a measure against wrongly identifying HP printers as
media players, but it is a rather dirty workaround which does not work
any more (therefore this bug). The rule in the end of 69-libmtp.rules
checks the absence of the env variable libsane_matched and this variable
is set for all HP printers by HPLIP. First, this rule fails miserably if
HPLIP is not installed, and I cannot imagine that the libmtp package
depends on HPLIP only to identify unsupported devices. Also the libmtp
rules are applied for both "add" and "bind" actions, whereas the rules
of HPLIP (56-hpmud.rules) are only applied for "add" and so the bug
happens on a "bind" action, here the HPLIP rules do not set said env
variable and so the libmtp rules probe the HP printers.

One can theoretically work around this problem by mucking with the UDEV
rules of HPLIP, but this is a REALLY DIRTY workaround, so please DO NOT
add an hplip task to this bug report.

In addition, HPLIP will not be installed by default any more in the not
too far future, as prnting and scanning will get snapped. Also we want
printer driver Snaps (Printer Applications) not to run as root if
possible, so we need to be sure that USB printer device files always
belong to the group "lp" for all printer manufacturers and without
HPLIP.

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-03-19 Thread Till Kamppeter
** Tags added: rls-ff-incoming

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-03-19 Thread Till Kamppeter
Now I tried to investigate from which UDEV rule the wrong setting comes
from. First I searched all UDEV rules for the word "audio":

till@till-x1yoga:~$ grep -l '\baudio\b' /*/udev/rules.d/*.rules
/lib/udev/rules.d/50-udev-default.rules
/lib/udev/rules.d/60-persistent-v4l.rules
/lib/udev/rules.d/69-libmtp.rules
/lib/udev/rules.d/70-uaccess.rules
/lib/udev/rules.d/90-pulseaudio.rules
till@till-x1yoga:~$ 


So I expect only one of these can be the culprit. Actually a 'GROUP="audio"' 
setting exists only in

/lib/udev/rules.d/50-udev-default.rules

and

/lib/udev/rules.d/69-libmtp.rules

The former is probably no problem as it assigns this group only to
devices of 'SUBSYSTEM=="sound"" where the latter seems to be actually
the culprit.

First it includes some devices explicitly and then it lists thousands of
supported devices. In the end there is some rule for passing a wide
range of devices through an auto-probing:

-
# Autoprobe vendor-specific, communication and PTP devices
ENV{ID_MTP_DEVICE}!="1", ENV{MTP_NO_PROBE}!="1", 
ENV{COLOR_MEASUREMENT_DEVICE}!="1", ENV{ID_GPHOTO}!="1", 
ENV{libsane_matched}!="yes", ATTR{bDeviceClass}=="00|02|06|ef|ff", 
PROGRAM="mtp-probe /sys$env{DEVPATH} $attr{busnum} $attr{devnum}", RESULT=="1", 
SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", 
ENV{ID_MEDIA_PLAYER}="1"
-

And this auto-probing tests positive on my printer:

till@till-x1yoga:~$ /lib/udev/mtp-probe 
/sys/devices/pci:00/:00:14.0/usb1/1-1 001 012
1
till@till-x1yoga:~$ 

The device path of the printer I have taken from the blob in the udevadm
output (attached to previous comment) which also contains
"ID_MEDIA_PLAYER=1". So mtp-probe identifies my printer as a media
player and assigns the device file to the "audio" group.

I assume that this happens to most or even all HP printers, so an
exclusion of only my device via Vendor and Product ID would not be the
correct solution.

Either mtp-probe needs to get fixed or before said rule in the end of
the 69-libmtp.rules file and after the lines explicitly identifying
media players from HP, there should be placed a line to exclude further
HP devices, like

--
...
# Exclude any further, not explicitly specified HP devices
ATTR{idVendor}=="03f0", GOTO="libmtp_rules_end"
# Autoprobe vendor-specific, communication and PTP devices
ENV{ID_MTP_DEVICE}!="1", ENV{MTP_NO_PROBE}!="1", 
ENV{COLOR_MEASUREMENT_DEVICE}!="1", ENV{ID_GPHOTO}!="1", 
ENV{libsane_matched}!="yes", ATTR{bDeviceClass}=="00|02|06|ef|ff", 
PROGRAM="mtp-probe /sys$env{DEVPATH} $attr{busnum} $attr{devnum}", RESULT=="1", 
SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", 
ENV{ID_MEDIA_PLAYER}="1"

LABEL="libmtp_rules_end"
--


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

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

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch 

[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-03-19 Thread Till Kamppeter
Attached is the output of

sudo udevadm monitor -e

Output of lsusb:

till@till-x1yoga:~$ lsusb
Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
Bus 001 Device 012: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
till@till-x1yoga:~$ 

Device is on Bus 001, Device 012, the HP OfficeJet Pro 8730

Here one sees that it is assigned to the "audio" group:

till@till-x1yoga:~$ ls -l /dev/bus/usb/*/*
crw-rw-r--  1 root root189,   0 Mar 17 11:45 /dev/bus/usb/001/001
crw-rw-r--  1 root root189,   2 Mar 17 11:45 /dev/bus/usb/001/003
crw-rw-r--  1 root root189,   3 Mar 17 11:45 /dev/bus/usb/001/004
crw-rw  1 root plugdev 189,   4 Mar 18 14:04 /dev/bus/usb/001/005
crw-rw-r--  1 root root189,   5 Mar 17 11:45 /dev/bus/usb/001/006
crw-rw+ 1 root audio   189,  11 Mar 19 18:55 /dev/bus/usb/001/012
crw-rw-r--  1 root root189, 128 Mar 17 11:45 /dev/bus/usb/002/001
crw-rw-r--  1 root root189, 130 Mar 17 11:45 /dev/bus/usb/002/003
till@till-x1yoga:~$ 


** Attachment added: 
"udevadm-monitor-e-plug-hp-officejet-pro-8730-20200319-log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1863239/+attachment/5338953/+files/udevadm-monitor-e-plug-hp-officejet-pro-8730-20200319-log.txt

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete
Status in udev package in Ubuntu:
  Invalid

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-03-17 Thread Till Kamppeter
An additional remark:

If a Focal system is booted with the printer plugged in and turned on,
the group ownership gets correctly set to "lp", but if the printer is
only plugged in and/or turned on after boot, it gets "audio" group
ownership.

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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


[Touch-packages] [Bug 1368147] Re: Lenovo Thinkpad Twist: Mobile Broadbad not working any more

2020-03-15 Thread Till Kamppeter
I do not use this laptop any more. So I am closing this bug.

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

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

Title:
  Lenovo Thinkpad Twist: Mobile Broadbad not working any more

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  It seems that something has changed and now the functionality for
  mobile broadband support got completely lost.

  I can create a new connection, enteringtheoperator and so on, but I
  cannot establish a connection.

  First, I click "Enable Mobile Broadband" in the network manager menu.
  Then I open the meu again and click the entry for my operator. Then I
  get a pop-up window saying "Connection activation failed, (32) The
  connection was not supportedby oFono".

  I am using Utopic.

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-03-13 Thread Till Kamppeter
** Changed in: libmtp (Ubuntu)
   Importance: High => Critical

** Changed in: pulseaudio (Ubuntu)
   Importance: High => Critical

** Changed in: systemd (Ubuntu)
   Importance: High => Critical

** Changed in: udev (Ubuntu)
   Importance: High => Critical

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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


[Touch-packages] [Bug 1864207] Re: Update request: 0.8.0 released

2020-02-27 Thread Till Kamppeter
schoff, James Rudd, Jan Alexander
  Steffens (heftig), Karl Cronburg, Krzesimir Nowak, Mario Blättermann, Martin
  Blanchard, Michal Sekletar, msk-nightingale, Philip Prindeville, Piotr Drąg,
  Rafael Fontenelle, scootergrisen, Simon Lauser, Simon McVittie, Thomas 
Jollans,
  Till Kamppeter, Tony Garnock-Jones, Trent Lloyd, wisd0me, Yclept Nemo, Zlopez,
  Дамјан Георгиевски.

  This release is backwards compatible with Avahi 0.6.x and 0.7.

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

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


[Touch-packages] [Bug 1864207] [NEW] Update request: 0.8.0 released

2020-02-21 Thread Till Kamppeter
Public bug reported:

Version 0.8.0 of Avahi got released:

https://github.com/lathiat/avahi/releases/tag/v0.8

Would be great to have this in Ubuntu 20.04 LTS (Focal)

--

The Avahi 0.8 release brings a number of new features and bug fix changes
including a backward-compatible addition to the D-Bus API and the avahi-core
API.

The existing API is still fully supported however clients using the new
API will not work with older Avahi releases. The avahi-client library is not
affected. See the "API Changes" section for further details.

New Features:

New options for filtering reflected queries between networks (reflect-filter)
New mainloop integration for Qt5 and libevent
docs/THREADS: Information for multi-threaded avahi-client apps
Listen on loopback interfaces by default, allowing local-only services to be
consumed by the local machine
New D-Bus V2 API and additions to the avahi-core API for splitting "New"
calls into "Prepare" and "Start". See "API Changes" for more details.
Notable Changes:

avahi-autoipd: Initial IP selection based on MAC previously ignored first
octet - this will cause all hosts to select a different link-local IP than
previous versions based on the same MAC address
avahi-daemon: Delay sending results on an object for 10ms in an attempt to
give clients enough time to subscribe to signals from the new object after
receiving it's path in response so the New call. See "API Changes" for more
info
Bug Fixes:

avahi-python: Various Python 3 enhancements including encoding unicode
strings as UTF-8
avahi-common: avahi_string_list_to_string will now escape embedded quotes,
backslashes and control characters.
avahi-daemon: Fix a crash when txt records have an empty value in .xml
service files
avahi-daemon: reflector: do not incorrectly cache responses on outgoing
interfaces. Previously we would incorrectly cache responses reflected from
one interface on the outgoing interface. These responses were later sent to
clients on that network even if the original client had disappeared and could
cause those clients to have a hostname conflict with themselves on restart.
We no longer incorrectly cache such traffic.
Security Fixes:

Drop legacy unicast queries from address not on local link which can lead to
UDP traffic amplification attacks (CVE-2017-6519)
API Changes: The avahi-core API and D-Bus API have implemented a new API where
a call to the "New" method can now be split into a "Prepare" and then "Start"
method for some objects. The previous "New" API is still fully supported and
there is no intention to deprecate it.

This change affects the the following objects: AsyncAddressResolver,
AsyncHostNameResolver, AsyncServiceResolver, DomainBrowser, RecordBrowser,
ServiceBrowser, ServiceTypeBrowser

This is because the D-Bus implementation in some languages would only bind to
signals of an object after it was created and had received the new object's
path. This led to such languages missing the initial results sent between the
time the object was created and it had setup a filter to receive it's signals.
This primarily occured in languages that create dynamic bindings for D-Bus
objects using introspection such as Python. The avahi-client C api was not
affected as it globally binds to all avahi signals without specifying
individual object paths and still makes use of the V1 API.

The v2 Prepare/Start API is available under the new
org.freedesktop.Avahi.Server2 D-Bus interface and also has corresponding
avahi_s_* calls for users of the embedded avahi-core library.

The old org.freedesktop.Avahi.Server interface is still supported and there is
no intention to remove this API. Additionally this problem has also been solved
for old clients by adding a very small 10ms delay before we start sending
results to give the client time to bind to the signals which should silently
fix the issue in most cases without introducing a noticable or impactful delay.

Clients implementing the new org.freedesktop.Avahi.Server2 D-Bus interface will
not work with older Avahi daemons. It is suggested that clients may wish to
either check for and fallback to the older API version, or continue to use the
OLD API and rely on the 10ms timer to resolve the issue.

Big thank-you to everyone contributing to the project through issues & pull
requests, including the the following people who contributed changes to this
release: Daniel S, David Kerr, Eric Bischoff, James Rudd, Jan Alexander
Steffens (heftig), Karl Cronburg, Krzesimir Nowak, Mario Blättermann, Martin
Blanchard, Michal Sekletar, msk-nightingale, Philip Prindeville, Piotr Drąg,
Rafael Fontenelle, scootergrisen, Simon Lauser, Simon McVittie, Thomas Jollans,
Till Kamppeter, Tony Garnock-Jones, Trent Lloyd, wisd0me, Yclept Nemo, Zlopez,
Дамјан Георгиевски.

This release is backwards compatible with Avahi 0.6.x and 0.7.

** Affects: avahi (Ubuntu)
 Importan

[Touch-packages] [Bug 1849859] Re: smb printing fails

2020-02-17 Thread Till Kamppeter
Do not edit /etc/cups/printers.conf while cupsd is running, as cupsd is
modifying it. So first stop cupsd:

sudo systemctl stop cupsd

then edit the file and after that start cupsd again:

sudo systemctl start cupsd

Note that you only can edit the properties of permanent print queues.
Queues which get temporarily created by CUPS or cups-browsed will loose
the changes once they get removed and re-created.

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-02-14 Thread Till Kamppeter
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-20.04

** Changed in: pulseaudio (Ubuntu)
Milestone: None => ubuntu-20.04

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

** Changed in: libmtp (Ubuntu)
Milestone: None => ubuntu-20.04

** Changed in: libmtp (Ubuntu)
   Importance: Undecided => High

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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


[Touch-packages] [Bug 1863239] [NEW] /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-02-14 Thread Till Kamppeter
Public bug reported:

When testing HPLIP I found out that CUPS backends can access my printer
only when they are running as root, when they are running as the special
user lp, as it is usually the case, they cannot access the printer.

So I tried to find out why and saw that the /dev/bus/usb/*/* device file
for the printer has group ownership "audio" and not "lp":

till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

The printer is the device /dev/bus/usb/001/063:

till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

There must be a bug somewhere in the UDEV rules.

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

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

** Affects: udev (Ubuntu)
 Importance: High
 Status: New

** Description changed:

  When testing HPLIP I found out that CUPS backends can access my printer
  only when they are running as root, when they are running as the special
  user lp, as it is usually the case, they cannot access the printer.
  
  So I tried to find out why and saw that the /dev/bus/usb/*/* device file
  for the printer has group ownership "audio" and not "lp":
  
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
+ till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$
+ 
+ The printer is the device /dev/bus/usb/001/063:
+ 
+ till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
+ Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
+ Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
+ Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
+ Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
+ Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 
  
  There must be a bug somewhere in the UDEV rules.

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

** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

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

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => High

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in pulseaudio package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  

[Touch-packages] [Bug 1826648] Re: cupds crashes with core dump

2020-01-10 Thread Till Kamppeter
August Rydberg (august-rydberg), if you are using Focal, the cups-
browsed crash is possibly caused by bug 1857815. Please follow the
instructions I have given there for a debug log of cups-browsed, but
please post your answer there, not in this bug report.

If you are not using Focal, your bug seems to be something different and
most probably not the bug which was reported here originally. Please
open a new bug report then.

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

Title:
  cupds crashes with core dump

Status in cups package in Ubuntu:
  Expired

Bug description:
  At home my cupsd daemon crashes all the time.

  Sometimes I'm able to print a few pages but in most cases it ends-up
  restarting and sending tons of crap to my printer resulting in
  multiple wasted pages with non-sense characters printed on it.

  I ended-up manually creating a core dump by launching it from root with:
  # cupsd -f -c /etc/cups/cupsd.conf
  (will attach core in post)

  I tried using the default drivers for my printer then using the
  Samsung provided ones with same result.  My printer is a Samsung
  C460W.

  Here is the systemd status:
  $ sudo systemctl status cups
  ● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: core-dump) since Sat 2019-04-27 09:49:09 EDT; 
12min ago
   Docs: man:cupsd(8)
Process: 15292 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=ABRT)
   Main PID: 15292 (code=dumped, signal=ABRT)

  avr 27 09:49:01 eclipse systemd[1]: Started CUPS Scheduler.
  avr 27 09:49:02 eclipse cupsd[15292]: free(): invalid pointer
  avr 27 09:49:02 eclipse systemd[1]: cups.service: Main process exited, 
code=dumped, status=6/ABRT
  avr 27 09:49:09 eclipse systemd[1]: cups.service: Failed with result 
'core-dump'.
  avr 27 09:49:09 eclipse systemd[1]: Stopped CUPS Scheduler.

  I wasn't able to find the core dump it refers to so that's why I
  ended-up generating one by invoking cupsd manually then launching
  ubuntu-bug against the cups package.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Sat Apr 27 09:54:21 2019
  InstallationDate: Installed on 2019-04-05 (21 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: LENOVO 20L6SF1000
  Papersize: letter
  PpdFiles:
   Samsung_C460_Series_th0ma7_print_: Samsung C460 Series PS
   Samsung-C460: Samsung C460 Series PS
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-13-generic 
root=UUID=f575ceec-b2a1-4507-ae3b-8487236a2c54 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to disco on 2019-04-05 (21 days ago)
  dmi.bios.date: 02/20/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET48W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6SF1000
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET48W(1.23):bd02/20/2019:svnLENOVO:pn20L6SF1000:pvrThinkPadT480:rvnLENOVO:rn20L6SF1000:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6SF1000
  dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2019-12-16 Thread Till Kamppeter
** Changed in: network-manager (Ubuntu Bionic)
 Assignee: Till Kamppeter (till-kamppeter) => (unassigned)

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.
   
  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
 valid_lft 353sec preferred_lft 353sec
  inet6 fe80::ff:feb3:b522/64 scope link 
 valid_lft forever preferred_lft forever

  
  
+++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in 
/var/log/syslog
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute 
 valid_lft forever preferred_lft forever

  
  ==> Correct LP-Package need to be assigned...!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions

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


[Touch-packages] [Bug 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication

2019-12-13 Thread Till Kamppeter
** Changed in: network-manager (Ubuntu Bionic)
 Assignee: Till Kamppeter (till-kamppeter) => (unassigned)

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

Title:
  NetworkManager does not support AES-encrypted private keys for WPA
  802.1x authentication

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  In Progress

Bug description:
  * Impact

  Selecting AES-{192,256}-CBC keys to connect isn't working

  * Test case

  1. Start with a working (cleartext or DES-3) private key/cert for a network.  
Set up a connection and verify that everything works.
  2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in 
working-key.pem -out aes-key.pem -aes256" (the output should have a line 
starting with "DEK-Info: AES-256-CBC,")
  3. Delete the settings for the test network and attempt to reconnect using 
the new key. 

  That should work

  * Regression potential

  That's new code for an extra type of keys, it shouldn't impact
  existing options

  --

  NetworkManager does not appear to support private keys encrypted with
  AES.  At the very least, it will not validate such a key in nm-util
  when setting up a WPA 802.1x TLS wifi connection.

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

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


[Touch-packages] [Bug 1809132] Re: Updated bionic to the current 1.10 stable version

2019-12-13 Thread Till Kamppeter
** Changed in: network-manager (Ubuntu)
 Assignee: Till Kamppeter (till-kamppeter) => (unassigned)

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

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

Title:
  Updated bionic to the current 1.10 stable version

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  In Progress

Bug description:
  * Impact

  The updates in the stable serie include several fixes for
  misbehaviour, segfaults and security issues, those are the sort of
  improvements that should be in the LTS

  The detail of the changes can be seen in the NEWS entry
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS

  * Test case

  There is no specific test case for the update, the changelog includes
  some specific bugs which have their own test case, otherwise it's
  important to get testing/feedback from users on desktop & server,
  using IPv4, IPv6, VPN, wifi, eth connections, etc.

  * Regression potential

  The update is non trivial, there are several changes are IPv6 and DNS
  (especially in the context of VPNs) handling so it would be good to
  give those extra testing

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

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


[Touch-packages] [Bug 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages

2019-12-12 Thread Till Kamppeter
Did you use the web interface of CUPS?

Does the same problem occur when using the "lpadmin" command in a
terminal?

Does it also occur when using the printer part of the GNOME Control
Center or system-config-printer?

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

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

Title:
  Trying to delete a printer will fill up the filesystem with
  logmessages

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Trying to delete a printer will fill up the filesystem with log messages ala
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok
  localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 
CUPS-Delete-Printer successful-ok

  150GiByte lines except of data  and time the same as given above after
  trying to delete one printer.

  Found the same on two ubuntu installations. Both 19.10 eoan ermine.

  NB: the printer was not deleted at all!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CupsErrorLog:
   E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away.
   E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A 
TLS fatal alert has been received.
   E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: 
A TLS fatal alert has been received.
   E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: 
A TLS fatal alert has been received.
  Date: Thu Dec 12 14:29:01 2019
  InstallationDate: Installed on 2019-09-09 (93 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat:
   device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: 
smb://srvmfg02-muc.bfs.de/drucker-muc
   device for PDF: cups-pdf:/
  Lsusb:
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  

[Touch-packages] [Bug 1850032] Re: scanbd prevents HP printers to work correctly with HPLIP

2019-12-11 Thread Till Kamppeter
** Also affects: hplip
   Importance: Undecided
   Status: New

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

Title:
  scanbd prevents HP printers to work correctly with HPLIP

Status in HPLIP:
  New
Status in cups package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  New
Status in scanbd package in Ubuntu:
  New

Bug description:
  scandb installs a new udev rule with /lib/udev/rules.d/99-saned.rules

  This rule changes the permissions for hplip command hp-check -r
  _from_:
  --
  | PERMISSION |
  --

  USB None   Required-
  -OK   Node:'/dev/bus/usb/006/004' Perm:'  root  lp rw- rw-
  rw- rw- r--'

  _to_:
  --
  | PERMISSION |
  --

  USB None   Required-
  -OK   Node:'/dev/bus/usb/006/004' Perm:'  root  saned rw-
  rw- rw- rw- r--'

  The CONSEQUENCE is, that the HP printer doesn't print anymore.

  For more details please refer to
  https://forum.ubuntuusers.de/post/9107204/

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

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


[Touch-packages] [Bug 1849859] Re: smb printing fails

2019-12-09 Thread Till Kamppeter
@Andreas Hasenack, eu também falo Alemão, se tiver um problema com CUPS,
cups-filters, ... :)

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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


[Touch-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

2019-11-30 Thread Till Kamppeter
Please attach both

/etc/cups/ppd/Brother_HL_L2375DW_series.ppd

and

/etc/cups/ppd/brother_hl_l2375dw_ser...@brw0c96e67e441e.local.ppd


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

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

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

2019-11-28 Thread Till Kamppeter
Could you please attach the PPD files of your printer, once of a Ubuntu
version in which the duplex works correctly (19.04 for example) and once
for a Ubuntu version where duplex printing does not work correctly
(19.10 for example). Could you also supply a CUPS error_log for one
working job (from 19.04 for example) and one non-working job (from 19.10
for example). Follow the instructions of the section "CUPS error_log" on
https://wiki.ubuntu.com/DebuggingPrintingProblems.

Also run the command

driverless

to get your printer's IPP URI and then run

ipptool -tv  get-printer-attributes-2.0.test > attrs.txt

If attrs.txt contains only a few lines or is empty, run

ipptool -tv  get-printer-attributes.test > attrs.txt

This you only need to do on 19.10, not on both systems.

Please attach your PPDs, error_logs, and attrs.txt, one by one. Do not
compress them and do not package them together.

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

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

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 

[Touch-packages] [Bug 1849859] Re: error when connecting to smb server

2019-11-20 Thread Till Kamppeter
Can this perhaps have to do with this bug in Fedora 30:
https://bugzilla.redhat.com/show_bug.cgi?id=1706090 ?

See also bug 1853242.

** Bug watch added: Red Hat Bugzilla #1706090
   https://bugzilla.redhat.com/show_bug.cgi?id=1706090

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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


[Touch-packages] [Bug 1849859] Re: error when connecting to smb server

2019-11-13 Thread Till Kamppeter
For me it looks like that something changed in Samba. Printing on such a
server is done via the /usr/lib/cups/backend/smb CUPS backend which is
part of the smbclient package.

Is there no way to access the printer on the NAS via IPP?

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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


[Touch-packages] [Bug 1851385] Re: ubuntu 19.10 / print bug : requires authentication

2019-11-13 Thread Till Kamppeter
*** This bug is a duplicate of bug 1849859 ***
https://bugs.launchpad.net/bugs/1849859

** This bug has been marked a duplicate of bug 1849859
   error when connecting to smb server

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

Title:
  ubuntu 19.10 / print bug : requires authentication

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 2 computers(one laptop and one desktop) which have a dual boot
  Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
  USB port from my modem on which my computers are connected using Wi-
  Fi.

  Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
  computers I get the same message : [The printer] requires
  authentication / credentials required in order to print.

  With Ubuntu 19.04, I had absolutely no problem. I tried with a live
  USB with Ubuntu 19.04, there is no problem, the printer works. With a
  Ubuntu live 19.10, it doesn't work.

  If I plug the printer directly on a USB port on my computer, I get the
  same error message : [The printer] requires authentication /
  credentials required in order to print.

  It's the same behaviour on both computers, no I guess it must be a
  bug. Anyway I don't know which authentication I could do, with which
  ID and password ?

  Thank you very much

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:12:07 2019
  Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
  MachineType: Acer Aspire V5-571
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: Aspire V5-571
  dmi.product.name: Aspire V5-571
  dmi.product.sku: Aspire V5-571_072A_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

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

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


[Touch-packages] [Bug 1850127] Re: Unable to print with Brother printer since upgrade to Ubuntu 19.10

2019-11-13 Thread Till Kamppeter
As your printer is working again now and we are not able to investigate
the original problem I am closing this bug now.

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

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

Title:
  Unable to print with Brother printer since upgrade to Ubuntu 19.10

Status in cups package in Ubuntu:
  Invalid

Bug description:
  I have recently bought a new color laser printer (Brother HL-
  L8260CDW), which is connected through wLAN. It works like a charm
  under Ubuntu 19.04, but refuses to print since the upgrade to stock
  Ubuntu 19.10. I can reach it via ping and through its HTTP config page
  from the same computer.

  During my collection of relevant bug information I discovered the
  following error messages:

  1. Some print filter was unable to grep 
/etc/cups/ppd/Brother_HL_L8260CDW_series.ppd
  This file was rw for user "root" and r for group "lp", but not accessible 
to others.
  I have made it world readable for testing purposes, but I still can't 
print.

  2. I checked /var/log/syslog for app-armour errors but found none which would 
be related
  to cups and/or printing

  3. After fixing the permission issue, the new error message is "File \'\' not 
found" and
  "Unable to add document to print job.", both of which are too cryptic for 
me to dig
  further into this by myself.

  
  Attached to this bug report I send the following pieces of information:
  - output from "/usr/lib/cups/backend/snmp 10.0.0.14" (snmp.txt)
  - output from "lpinfo -v" (lpinfo.txt)
  - output from "avahi-browse -a -v -t -r" and "avahi-browse -a -v -c -r" 
(avahi.txt)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CupsErrorLog:
   E [28/Oct/2019:10:40:04 +0100] [Job 112] File \'\' not found
   E [28/Oct/2019:10:40:12 +0100] [Job 112] Unable to add document to print job.
   E [28/Oct/2019:10:45:59 +0100] [Job 113] File \'\' not found
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 10:50:05 2019
  InstallationDate: Installed on 2015-11-11 (1446 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: device for Brother_HL_L8260CDW_series: 
implicitclass://Brother_HL_L8260CDW_series/
  MachineType: MSI MS-7982
  Papersize: a4
  PpdFiles: Brother_HL_L8260CDW_series: HL-L8260CDW series - IPP Everywhere
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=64458150-bde5-4ffc-8eb1-038fae855347 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.10
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M PRO-DH (MS-7982)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.10:bd07/08/2015:svnMSI:pnMS-7982:pvr1.0:rvnMSI:rnB150MPRO-DH(MS-7982):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7982
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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


[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

2019-10-31 Thread Till Kamppeter
Jean, does this mean that 1.10.6-2ubuntu1.1 works perfectly for you and
1.10.6-2ubuntu1.2 shows the problem you mention?

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

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

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


[Touch-packages] [Bug 1850775] Re: DNS info is not loaded by dhclient

2019-10-31 Thread Till Kamppeter
Looks like that during boot time components get fired up in wrong order,
some dependency in the systemd service files is needed.

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

Title:
  DNS info is not loaded by dhclient

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi Team,

  Could you please help to confirm if this is an issue on Ubuntu19.10
  Desktop?

  1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
 supersede domain-name "vmware.com";
 supersede domain-name-servers 10.117.0.1;

  2. Reboot

  3. check DNS info by "systemd-resolve --status", the DNS domain and
  server is not set. But /run/systemd/resolved.conf.d/isc-
  dhcp-v4-ens160.conf contains the new DNS domain and server.

  4. Manually run "systemctl try-reload-or-restart systemd-
  resolved.service" and then DNS is set correctly, "systemd-resolve
  --status" output have the new DNS domain and server.

  
  I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

  Thanks,
  Pengpeng

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

-- 
Mailing list: https://launchpad.net/~touch-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

2019-10-28 Thread Till Kamppeter
No worries about my previous comment, it is solved.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  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/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 1829913] Re: openconnect VPN is not propagating internal DNS anymore

2019-10-28 Thread Till Kamppeter
Joe_Bishop, a new Bionic SRU for bug 1754671 got issued, now much less
invasive simply backporting the fixes and not being a full upstream
update. Please follow the instructions in bug 1754671. If you are still
running 1.10.14 (the old SRU) please downgrade to the old network-
manager and then do the updsate to get the new SRU.

Please check and report here whether the regressions you observed in
1.10.14 do not occur in the new SRU. Thanks.

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

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

Title:
  openconnect VPN is not propagating internal DNS anymore

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Openconnect VPN stopped propagating DNSes to the system.

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

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


[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

2019-10-28 Thread Till Kamppeter
Jean, a new Bionic SRU for bug 1754671 got issued, now much less
invasive simply backporting the fixes and not being a full upstream
update. Please follow the instructions in bug 1754671. If you are still
running 1.10.14 (the old SRU) please downgrade to the old network-
manager and then do the updsate to get the new SRU.

Please check and report here whether the regressions you observed in
1.10.14 do not occur in the new SRU. Thanks.

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

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

-- 
Mailing list: https://launchpad.net/~touch-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

2019-10-28 Thread Till Kamppeter
Now network-manager is hanging on (all autopkg tests passed):

Not touching package due to block request by freeze (contact #ubuntu-
release if update is needed)

Which freeze do we currently have on Bionic?

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  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/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 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-10-22 Thread Till Kamppeter
Sorry for the late reply, I was on a conference last week.

I installed the PPA now and tested with the reproducer of the initial
posting. This works for me. Also the machine in general seems to work OK
with this version of network-manager.

Thank you very much Dariusz for packaging this version.

So now the 1.10.14 should be removed from -proposed (to avoid need of an
epoch), and the version from the PPA of Dariusz should get uploaded into
-proposed, and then the reporters of the regressions in the 1.10.14 SRU
informed (by comments in their bug reports) for the new SRU being
verified.

Could someone from the release team initiate the process by removing
1.10.14 from -proposed? Thanks.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  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/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 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-10-10 Thread Till Kamppeter
Great work, thank you very much!

It will need some testing of which I can only test the reproducer in the
initial description of this bug report, not any regressions which the
first attempt of upstream-update-based SRU, as I could not reproduce
these by myself.

So I would say to take this as a new proposed SRU and also ask the
reporters of the regressions whether this version does not cause them.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  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/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 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu

2019-10-06 Thread Till Kamppeter
For me it looks more like a kernel issue, as the Wi-Fi principally works
(network-manager must have set it up correctly). The weak signal issue
looks more like something in the driver.

** Also affects: linux (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/1846140

Title:
  Realtek RTL8723BU doesn't work well in ubuntu

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

Bug description:
  I have one laptop with Realtek RTL8723BU wifi card. It runs, but
  signal is weak (it only works if the router is less than a meter
  away), and even if it gets signal it's slow and it gets interrupted
  frequently. In windows it works normally, and with a much stronger
  signal. I tested it on Ubuntu 18.04.3 and 19.04.

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

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


[Touch-packages] [Bug 1846334] Re: cupsd assert failure: free(): invalid pointer

2019-10-02 Thread Till Kamppeter
** Information type changed from Private to Public

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

Title:
  cupsd assert failure: free(): invalid pointer

Status in cups package in Ubuntu:
  New

Bug description:
  Just running in the background, no user action (printing)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-daemon 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: free(): invalid pointer
  Date: Tue Oct  1 19:41:35 2019
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2019-02-09 (234 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: letter
  PpdFiles:
   HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere
   Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at 
malloc.c:5332
   _int_free (av=, p=, have_lock=0) at 
malloc.c:4173
   ?? () from /lib/x86_64-linux-gnu/libcups.so.2
   ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2
  Title: cupsd assert failure: free(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  separator:

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

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


[Touch-packages] [Bug 1841295] Re: Update to 2.3.0?

2019-08-24 Thread Till Kamppeter
New features of 2.3.x are also listed in the 2018 presentation

https://ftp.pwg.org/pub/pwg/liaison/openprinting/presentations/cups-
plenary-may-18.pdf


and updated in the 2019 presentation:

https://ftp.pwg.org/pub/pwg/liaison/openprinting/presentations/cups-
plenary-april-19.pdf

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

Title:
  Update to 2.3.0?

Status in cups package in Ubuntu:
  Triaged

Bug description:
  There is a new cups version out, likely not for this cycle though?

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

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


[Touch-packages] [Bug 1841295] Re: Update to 2.3.0?

2019-08-24 Thread Till Kamppeter
The 2.3.x line got only a stable release on Fri, Aug 23, one day after
Feature Freeze for Eoan. As I was watching for software updates before
FF there was 2.3rc1 for a very long time without getting final, so I
ended up using 2.2.12 for Eoan.

The reason why CUPS 2.3.x did not get forward quickly and why I did not
try to make Mike Sweet (author of CUPS) releasing 2.3.0 in time for our
FF is due to a license conflict.

According to Mike's presentation on the OpenPrinting Sunmmit 2018 (May)

https://ftp.pwg.org/pub/pwg/liaison/openprinting/presentations/cups-
plenary-may-18.pdf

CUPS 2.3.0 should have been released in June/July 2018 under the Apache
License 2.0 (Apple changed the license to fit better with Mac OS X). As
the license is not compatible with the (L)GPL2 licenses of a part of
cups-filters and other software in non-Mac-OS systems Mike told me that
I would not need to change any licenses in cups-filters and he will let
the case be solved by the law department of Apple. In the time being he
would backport all bug fixes into the 2.2.x line which is still under
the old license and I should use this line for Debian and Ubuntu.

Now since then more than one year, one more OpenPrinting Summit, and 3
Feature Freezes of Ubuntu have passed until finally Apple solved the
problem (I assume) and Mike released 2.3.0. The solution is in the
NOTICE file which makes an exception to the Apache license in the
LICENSE file:

--
-- CUPS Exceptions to the Apache 2.0 License --

As an exception, if, as a result of your compiling your source code, portions
of this Software are embedded into an Object form of such source code, you
may redistribute such embedded portions in such Object form without complying
with the conditions of Sections 4(a), 4(b) and 4(d) of the License.

In addition, if you combine or link compiled forms of this Software with
software that is licensed under the GPLv2 ("Combined Software") and if a
court of competent jurisdiction determines that the patent provision (Section
3), the indemnity provision (Section 9) or other Section of the License
conflicts with the conditions of the GPLv2, you may retroactively and
prospectively choose to deem waived or otherwise exclude such Section(s) of
the License, but only in their entirety and only with respect to the Combined
Software.
--

https://github.com/apple/cups/blob/v2.3.0/NOTICE
https://github.com/apple/cups/blob/v2.3.0/LICENSE

This means that we now can advance to the 2.3.x line of CUPS in Ubuntu.

The question is now whether we would do a FFe to still land this in Eoan
or simply leave it for next cycle.

Except new features (which I have to find out which they are, Mike does
not make this very easy) advantage is that we will better test it before
the next LTS (20.04), 19.10 is the "dress rehearsal" of the LTS, Some
basic testing to judge CUPS 2.3.0 at least as usable and to have any
packaging problem already solved is done by 2.3rc1 already being in
Debian Experimental.

For getting the new CUPS into Eoan we can probably sync the package from
Debian within the coming week, at least if Debian accepts the license
solution, otherwise OdyX will upload it to Debian stable quickly.

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

Title:
  Update to 2.3.0?

Status in cups package in Ubuntu:
  Triaged

Bug description:
  There is a new cups version out, likely not for this cycle though?

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

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


[Touch-packages] [Bug 1839603] Re: Wifi breaks and needs restart after Laptop's wake up

2019-08-09 Thread Till Kamppeter
Please have a look at

https://wiki.ubuntu.com/DebuggingNetworkManager

and supply us with debug logs of NetworkManager and wpasupplicant,

You say "But I'm getting tired of this after years of doing it.". Does
this mean that you are suffering this bug already with older versions of
Ubuntu?

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

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

Title:
  Wifi breaks and needs restart after Laptop's wake up

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  This is constant struggle for me, it seems that in the initial days
  after installation of Ubuntu 19.10 this problem of Wifi stopping to
  work after wake up does not happen. I'm sure, I reinstalled Ubuntu
  many times, the issue still persist.

  Breaking of Wifi after computer wake up starts to appear, on average,
  after a week of computer usage.

  On my laptop, this Wifi problem existed in the previous Ubuntu
  versions as well.

  What works: It seems a simple Wifi turn off and turn on is sufficient,
  for the bug to go away. But I'm getting tired of this after years of
  doing it.

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

-- 
Mailing list: https://launchpad.net/~touch-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-08-08 Thread Till Kamppeter
The PPD you have now is completely different, it is not auto-generated
based on a get-printer-attributes IPP request but it is a generic PPD
which is part of the cups-filters package.

How did you set up your printer under Disco? How did you set it up under
Eoan? Does your printer actually print under Eoan?

-- 
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-08-08 Thread Till Kamppeter
Could you also attach the ipptool output of Eoan, to see whether this is
different?

-- 
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-08-08 Thread Till Kamppeter
Could you post the PPD file of Eoan then, so tat I can compare?

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

2019-08-08 Thread Till Kamppeter
Could you follow the instructions of the section "CUPS error_log" on
https://wiki.ubuntu.com/DebuggingPrintingProblems to get an error_log in
debug mode from the CUPS crash?

Also some form of backtrace of the crashing CUPS daemon would be great
(apport record? cupsd run in a way that one can capture a core file,
...).

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

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

2019-08-07 Thread Till Kamppeter
Can you attach the PPD file (from /etc/cups/ppd/) of your printer of the
Disco machine and if possble also the one from your Bionic machine?

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

-- 
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 1837233] Re: [bionic] Manual IPv6 routes are not set

2019-08-07 Thread Till Kamppeter
pitti, have you already tried network-manager 1.10.14 from bionic-
proposed (bug 1754671)? It did not make it to -updates as there appeared
two regression reports (bug 1829838 and bug 1829913), but if these
regressions do not affect your use case you could try it. I would like
to know whether it perhaps fixes your manual route problem.

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

Title:
  [bionic] Manual IPv6 routes are not set

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Won't Fix

Bug description:
  I have a system connection like this:

  -- /etc/NetworkManager/system-connections/eth2  ---
  [connection]
  id=eth2
  uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
  type=ethernet
  gateway-ping-timeout=12
  interface-name=eth2
  permissions=
  timestamp=1563551266

  [ethernet]
  mac-address-blacklist=

  [ipv4]
  dns-search=
  method=shared

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  ignore-auto-routes=true
  method=auto
  route1=1:2::/60,1:2::3,42
  -- 8< -

  In particular, the last line (route1=) which sets a manual IPv6 route.
  Of course this is rather bogus,  I'm just using this to test cockpit's
  web UI.

  On Ubuntu 19.04, Debian 10, and Debian testing this works just fine:

  # nmcli c show eth2
  ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42 
}
  IP6.ROUTE[1]:   dst = fe80::/64, nh = ::, mt = 101
  IP6.ROUTE[2]:   dst = ff00::/8, nh = ::, mt = 256, 
table=255
  IP6.ROUTE[3]:   dst = 1:2::3/128, nh = ::, mt = 42
  IP6.ROUTE[4]:   dst = 1:2::/60, nh = 1:2::3, mt = 42
  [...]
  # ip -6 route show dev eth2
  1:2::3 proto static metric 42 pref medium
  1:2::/60 via 1:2::3 proto static metric 42 pref medium
  fe80::/64 proto kernel metric 101 pref medium

  (There, the file is called eth2.nmconnection, but same difference)

  On Ubuntu 18.04 however, the route manual is ignored, and only the
  automatic link-local one exists:

  # nmcli c show eth2
  ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42 
}
  IP6.ROUTE[1]:   dst = ff00::/8, nh = ::, mt = 256, 
table=255
  IP6.ROUTE[2]:   dst = fe80::/64, nh = ::, mt = 256
  IP6.ROUTE[3]:   dst = fe80::/64, nh = ::, mt = 101

  # ip -6 route show dev eth2
  fe80::/64 proto kernel metric 101 pref medium
  fe80::/64 proto kernel metric 256 pref medium

  Restarting NetworkManager does not help, nor does rebooting.

  DistroRelease: Ubuntu 18.04
  Package: 1.10.6-2ubuntu1.1
  Architecture: amd64

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

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


[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently

2019-08-06 Thread Till Kamppeter
I do not really see in the log snippets where the Wi-Fi does not
actually work, or which step of the Wi-Fi connection attempt fails.
Perhaps the relevant part is not included.

You write:

--
Jul 16 19:20:34 serval NetworkManager[617]:  [1563330034.2504] device 
(p2p-dev-wlp62s0): supplicant management interface state: associating -> 
associated
```
...snip...
```
Jul 16 19:20:45 serval NetworkManager[617]:  [1563330045.2179] 
supplicant: wpa_supplicant die count reset
--

Could you also post the part which you have cut away here?

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

Title:
  network-manager needs to be restarted frequently

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops
  working frequently and the network-manager service needs to be
  restarted. It will die on its own, but can be triggered by switching
  wifi 3 times (sometimes more, sometimes fewer)!

  When it is working, I have:
  ```
  % usr/bin/sudo nmcli device
  DEVICE   TYPE  STATE CONNECTION 
  wlp62s0  wifi  connected ATT964 
  p2p-dev-wlp62s0  wifi-p2p  disconnected  -- 
  enp59s0  ethernet  unavailable   -- 
  lo   loopback  unmanaged --   
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
 description: Wireless interface
 product: Wireless 8260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:3e:00.0
 logical name: wlp62s0
 version: 3a
 serial: e4:b3:18:e3:11:e7
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:133 memory:dc20-dc201fff
  % /usr/bin/sudo lspci -vnnn | grep -A 9 Network
  3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 
[8086:24f3] (rev 3a)
Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010]
Flags: bus master, fast devsel, latency 0, IRQ 133
Memory at dc20 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7
Capabilities: [14c] Latency Tolerance Reporting
  ```
  If I switch between my two wifi routers three times (sometimes more times) 
using the Select Network command on the taskbar, wifi stops working.

  Issuing the commands above yields the following differences:
  ```
  % /usr/bin/sudo nmcli device
  DEVICE   TYPE  STATECONNECTION 
  enp59s0  ethernet  unavailable  -- 
  wlp62s0  wifi  unavailable  -- 
  p2p-dev-wlp62s0  wifi-p2p  unavailable  -- 
  lo   loopback  unmanaged
  
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
   ...snip...
  configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
  ```
  /var/log/syslog reports the following after failing to switch wifi networks:
  ```
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): disconnecting for new activation request.
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): state change: activated -> deactivating (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5485] 
manager: NetworkManager state is now DISCONNECTING
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5548] 
audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" 
name="ATT964" pid=21476 uid=1010 result="success"
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5550] 
device (wlp62s0): state change: deactivating -> disconnected (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): state changed bound -> done
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5572] 
dhcp6 (wlp62s0): 

[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently

2019-08-06 Thread Till Kamppeter
Can you tell where in the log Wi-Fi is failing? I see only a lot of
errors of GNOME shell, not of Wi-Fi.

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

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

Title:
  network-manager needs to be restarted frequently

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops
  working frequently and the network-manager service needs to be
  restarted. It will die on its own, but can be triggered by switching
  wifi 3 times (sometimes more, sometimes fewer)!

  When it is working, I have:
  ```
  % usr/bin/sudo nmcli device
  DEVICE   TYPE  STATE CONNECTION 
  wlp62s0  wifi  connected ATT964 
  p2p-dev-wlp62s0  wifi-p2p  disconnected  -- 
  enp59s0  ethernet  unavailable   -- 
  lo   loopback  unmanaged --   
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
 description: Wireless interface
 product: Wireless 8260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:3e:00.0
 logical name: wlp62s0
 version: 3a
 serial: e4:b3:18:e3:11:e7
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:133 memory:dc20-dc201fff
  % /usr/bin/sudo lspci -vnnn | grep -A 9 Network
  3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 
[8086:24f3] (rev 3a)
Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010]
Flags: bus master, fast devsel, latency 0, IRQ 133
Memory at dc20 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7
Capabilities: [14c] Latency Tolerance Reporting
  ```
  If I switch between my two wifi routers three times (sometimes more times) 
using the Select Network command on the taskbar, wifi stops working.

  Issuing the commands above yields the following differences:
  ```
  % /usr/bin/sudo nmcli device
  DEVICE   TYPE  STATECONNECTION 
  enp59s0  ethernet  unavailable  -- 
  wlp62s0  wifi  unavailable  -- 
  p2p-dev-wlp62s0  wifi-p2p  unavailable  -- 
  lo   loopback  unmanaged
  
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
   ...snip...
  configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
  ```
  /var/log/syslog reports the following after failing to switch wifi networks:
  ```
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): disconnecting for new activation request.
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): state change: activated -> deactivating (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5485] 
manager: NetworkManager state is now DISCONNECTING
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5548] 
audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" 
name="ATT964" pid=21476 uid=1010 result="success"
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5550] 
device (wlp62s0): state change: deactivating -> disconnected (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): state changed bound -> done
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5572] 
dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5572] 
dhcp6 (wlp62s0): state changed bound -> done
  Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating 
from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING)
  Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: 

[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

2019-08-05 Thread Till Kamppeter
The shorter one ends at Jul 1, long before I asked you for the tests, and also 
its last line looks broken. It is mot probably incomplete, somehow a part of it 
got lost during upload.
In the longer one I have found one of your two tests. I have cut it at the 
beginning of that test and uploaded the resulting log to this bug report as 
attachment of comment #22.

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

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

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


[Touch-packages] [Bug 1836209] Re: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9

2019-08-05 Thread Till Kamppeter
NM 1.18.0-1ubuntu6 with the above-mentioned merge request merged has
been uploaded and in the -proposed -> -release migration the
autopkgtests have all passed now. Closing as fixed.

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/n/network-manager/20190710_160945_9116e@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/n/network-manager/20190710_110735_e5ce3@/log.gz

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

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


[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

2019-08-04 Thread Till Kamppeter
The longer of your two attached log files, log-network-manager-without-
segmentation.txt, seems to contain at least one of your two tests, so I
extracted the part from your test starting (last start of network-
manager, with log verbosity set to contain  and  messages)
up to the end. I have attached this part to this posting as log-network-
manager-without-segmentation-2.txt.

When one searches for the string "current configuration:" one finds
where DNS configuration is changed due to network interfaces being added
or removed. The last of these occurrences is the only place where your
VPN (with your office's DNSes 172.27.0.42 and 172.27.0.33) gets added to
your phone's internet access (with DNS 192.168.42.129). Only in this
acase you get an error with pacrunner (PAC = Proxy Auto Configuration,
see https://wiki.gnome.org/Projects/NetworkManager/Proxies) but seems to
succeed later. There are also some other errors visible. Here are some
lines of the log:

--
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4886] 
dns-mgr: current configuration: [{'nameservers': <['172.27.0.42', 
'172.27.0.33']>, 'interface': <'tun2'>, 'priority': <50>, 'vpn': }, 
{'nameservers': <['192.168.42.129']>, 'interface': <'enp0s20f0u2'>, 'priority': 
<100>, 'vpn': }]
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4895] 
dispatcher: (32) (tun2) dispatching action 'vpn-up'
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4900] 
pacrunner: call[0x563b6899bc30]: send: new config ({'Interface': <'tun2'>, 
'Method': <'direct'>, 'BrowserOnly': , 'Domains': <['172.31.252.244/24', 
'172.27.0.0/24', '172.27.240.0/20', '192.168.222.0/24', '185.48.32.186/32', 
'80.247.66.0/24', '87.248.32.84/32', '178.239.180.149/32', '80.247.66.96/32', 
'87.248.32.223/32', '10.6.0.0/16', '172.31.252.0/24']>},)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4900] 
pacrunner: call[0x563b6899bc30]: sending...
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4907] 
pacrunner: call[0x563b6899bc30]: sending failed: 
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.pacrunner" 
does not exist
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4907] prope
rties-changed[0x563b688b9c10]: type NMDeviceTun, iface NMDBusDeviceStatisticsSke
leton: {'TxBytes': }
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4908] prope
rties-changed[0x563b688b9c10]: type NMDeviceTun, iface NMDBusDeviceTunSkeleton: 
{'Dhcp4Config': , 'Dhcp6Config': , 'Ip4Address':
 , 'Ip4Config': , 'Ip6Config': , 'IpInterface': <''>, 'Managed': , 'State': , 
'StateReason': <(uint32 20, uint32 41)>}
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4909] 
device[0x563b688b9c10] (tun2): ip4-config: update (commit=0, 
new-config=0x563b688ab4a0)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4910] 
device[0x563b688b9c10] (tun2): ip6-config: update (commit=0, 
new-config=0x563b688b4940)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4912] 
manager: (tun2): assume: generated connection 'tun2' 
(7ddca237-b609-4f44-bf54-9f3705d663ce)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4917] 
settings: Failed to add 7ddca237-b609-4f44-bf54-9f3705d663ce/'tun2': Plugin 
does not support adding connections
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4922] 
settings-connection[0x563b68793a80]: constructed (NMSKeyfileConnection)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4929] 
settings-connection[0x563b68793a80,7ddca237-b609-4f44-bf54-9f3705d663ce]: 
update settings-connection flags to visible (was none)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4929] 
settings-connection[0x563b68793a80,7ddca237-b609-4f44-bf54-9f3705d663ce]: 
update settings-connection flags to unsaved,visible (was visible)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:   [1564066391.4929] 
keyfile: add connection in-memory (7ddca237-b609-4f44-bf54-9f3705d663ce,"tun2")
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.4935] 
settings-connection[0x563b68793a80,7ddca237-b609-4f44-bf54-9f3705d663ce]: 
failed to read connection timestamp: Il file chiavi non presenta alcuna chiave 
«7ddca237-b609-4f44-bf54-9f3705d663ce» nel gruppo «timestamps»
[...]
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.5344] 
dns-mgr: (device_state_changed): no DNS changes to commit (0)
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:   [1564066391.5344] 
device (tun2): Activation: successful, device activated.
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.5344] 
device[0x563b688b9c10] (tun2): set metered value 4
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.5345] 
dispatcher: (34) (tun2) dispatching action 'up'
lug 25 16:53:11 CLIFMI085 NetworkManager[21584]:  [1564066391.5350] 
pacrunner: call[0x563b689a10c0]: send: new config ({'Interface': <'tun2'>, 
'Method': <'direct'>, 'BrowserOnly': },)
lug 

[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

2019-08-04 Thread Till Kamppeter
Sorru for the late reply, I had a lot to do.

I am not sure whether you have correctly taken the logs.

Both are taken on July 25 but when you look into them, they span the
following time frames:

log-network-manager-with-segmentation.txt:Jan 31 - July  1
log-network-manager-without-segmentation.txt: Jan 31 - July 25

A "diff" shows also that all content of of the first is also in the
second. It seems that the first got cut off during the upload.

As they contain all history back to January, is it possible that the
longer one (log-network-manager-without-segmentation.txt) contains both
tests? Could you tell in which order you did the tests and which parts
of the log reflect which test?

Or could you re-test but this time reading the time stamps in the log
before and after each test and upload only the logs of these time spans?

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

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

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


[Touch-packages] [Bug 1828102] Re: Regression in ModemManager

2019-07-26 Thread Till Kamppeter
@ddstreet, unfortunately, I cannot verify this as the bug only occured
for CDMA phones and the CDMA system is only available in the US where
the rest of the world only uses GSM and UMTS systems for cell phones. So
we need someone in the US to verify this fix.

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

Title:
  Regression in ModemManager

Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Bionic:
  Fix Released
Status in modemmanager source package in Cosmic:
  Won't Fix
Status in modemmanager source package in Disco:
  Fix Committed
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  ModemManager disconnects from CDMA modem after 30 sec failing to check
  signal status due to incorrect error handling

  [Test case]

  connect to a cdma device without an extra AT channel (Eg. Samsung
  brightside phone) and modemmanager will terminate the connection

  [Regression potential]

  The patch is tiny, fixing an obvious overlook, and it only affects
  CDMA broadband modems, so the risk of a regression is very low.

  [Original description]

  ModemManager disconnects after ~30 sec

  caused by a typo in 1.8

  see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615
  and
  https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
  for details

  needs a SRU for cosmic and dingo

  patch attached

  yechiel

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

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


[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

2019-07-25 Thread Till Kamppeter
Jean, thank you for the input, could you retest these two cases (with
and without split connection) but create debug logs of Network Manager
and systemd-resolved, following the instructions on
https://wiki.ubuntu.com/DebuggingNetworkManager (and/or of my comment
#10)?

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

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

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


  1   2   3   4   5   6   7   8   9   10   >