date:20181206

SRU proposal for bionic.

** Patch added: "bionic_cups_2.2.7-1ubuntu2.2.debdiff"

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219666/+files/bionic_cups_2.2.7-1ubuntu2.2.debdiff

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576

Title:
MaxJobTime=0 results in jobs being cancelled immediately instead of
never

Status in CUPS:
New
Status in cups package in Ubuntu:
Confirmed

Bug description:
[Impact]

Setting the cupsd option MaxJobTime to 0 should make the server wait
indefinitely for the job to be ready for print. Instead, after updating
job-cancel-after option with MaxJobTime=0 value it results in immediate
cancelling.
This leads to problems with using filters that take some time to process -
the user needs to set MaxJobTime to a ridiculously high value to ensure the job
is not going to get cancelled instead of just disabling the cancelling timeout.

[Test Case]

1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
2. Setup a filter that takes at least several seconds to process.
(please find a sample imagetopdf wrapper introducing 5s delay)
3. Submit a print job matching the filter, e.g.
lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

Expected result:
The job is printed after the 5s delay.

Actual result:
The job is cancelled.

[Regression Potential]

The scope of the change is limited to fixing the MaxJobTime handling
in scheduler/job.c and scheduler/printers.c. There should be no
difference in behavior except for the special value of MaxJobTime=0.

[Other Info]
Original bug description:

When using CUPS filters, these filters can take a few seconds to
complete.

In this case no documents are allowed to be lost on printing failures,
so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
14.04.

With cups on 18.04, you get the following message in /var/log/cups/error_log
whenever the filter takes a little longer:
I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

Then, the job is deleted and lost.

"MaxJobTime 0" is documented as "indefinite wait", but apparently cups
treats is as "wait almost not at all".

This issue appears to have also been filed upstream:
https://github.com/apple/cups/issues/5438

Temporary workaround is to set the MaxJobTime to a very large value
instead (e.g. 3 years)

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

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

SRU proposal for Cosmic.

** Patch added: "cosmic_cups_2.2.8-5ubuntu2.debdiff"

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219665/+files/cosmic_cups_2.2.8-5ubuntu2.debdiff

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576

Title:
MaxJobTime=0 results in jobs being cancelled immediately instead of
never

Status in CUPS:
New
Status in cups package in Ubuntu:
Confirmed

Bug description:
[Impact]

[Test Case]

Expected result:
The job is printed after the 5s delay.

Actual result:
The job is cancelled.

[Regression Potential]

[Other Info]
Original bug description:

When using CUPS filters, these filters can take a few seconds to
complete.

In this case no documents are allowed to be lost on printing failures,
so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
14.04.

With cups on 18.04, you get the following message in /var/log/cups/error_log
whenever the filter takes a little longer:
I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

Then, the job is deleted and lost.

"MaxJobTime 0" is documented as "indefinite wait", but apparently cups
treats is as "wait almost not at all".

This issue appears to have also been filed upstream:
https://github.com/apple/cups/issues/5438

Temporary workaround is to set the MaxJobTime to a very large value
instead (e.g. 3 years)

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

SRU proposal for disco.

** Description changed:

+ [Impact]
+
+ Setting the cupsd option MaxJobTime to 0 should make the server wait
indefinitely for the job to be ready for print. Instead, after updating
job-cancel-after option with MaxJobTime=0 value it results in immediate
cancelling.
+ This leads to problems with using filters that take some time to process -
the user needs to set MaxJobTime to a ridiculously high value to ensure the job
is not going to get cancelled instead of just disabling the cancelling timeout.
+
+ [Test Case]
+
+ 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
+ 2. Setup a filter that takes at least several seconds to process.
+ (please find a sample imagetopdf wrapper introducing 5s delay)
+ 3. Submit a print job matching the filter, e.g.
+ lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper
+
+ Expected result:
+ The job is printed after the 5s delay.
+
+ Actual result:
+ The job is cancelled.
+
+ [Regression Potential]
+
+ The scope of the change is limited to fixing the MaxJobTime handling
+ in scheduler/job.c and scheduler/printers.c. There should be no
+ difference in behavior except for the special value of MaxJobTime=0.
+
+
+ [Other Info]
+ Original bug description:
+
When using CUPS filters, these filters can take a few seconds to
complete.

In this case no documents are allowed to be lost on printing failures,
so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
14.04.

With cups on 18.04, you get the following message in /var/log/cups/error_log
whenever the filter takes a little longer:
I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

Then, the job is deleted and lost.

"MaxJobTime 0" is documented as "indefinite wait", but apparently cups
treats is as "wait almost not at all".

This issue appears to have also been filed upstream:
https://github.com/apple/cups/issues/5438

Temporary workaround is to set the MaxJobTime to a very large value
instead (e.g. 3 years)

** Tags added: sts

** Patch added: "disco_cups_2.2.9-3ubuntu1.debdiff"

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219664/+files/disco_cups_2.2.9-3ubuntu1.debdiff

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576

Title:
MaxJobTime=0 results in jobs being cancelled immediately instead of
never

Status in CUPS:
New
Status in cups package in Ubuntu:
Confirmed

Bug description:
[Impact]

[Test Case]

Expected result:
The job is printed after the 5s delay.

Actual result:
The job is cancelled.

[Regression Potential]

[Other Info]
Original bug description:

When using CUPS filters, these filters can take a few seconds to
complete.

In this case no documents are allowed to be lost on printing failures,
so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
14.04.

With cups on 18.04, you get the following message in /var/log/cups/error_log
whenever the filter takes a little longer:
I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

Then, the job is deleted and lost.

"MaxJobTime 0" is documented as "indefinite wait", but apparently cups
treats is as "wait almost not at all".

This issue appears to have also been filed upstream:
https://github.com/apple/cups/issues/5438

Temporary workaround is to set the MaxJobTime to a very large value
instead (e.g. 3 years)

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

SRU proposal for xenial.

** Patch added: "xenial_cups_2.1.3-4ubuntu0.6.debdiff"

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219667/+files/xenial_cups_2.1.3-4ubuntu0.6.debdiff

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576

Title:
MaxJobTime=0 results in jobs being cancelled immediately instead of
never

Status in CUPS:
New
Status in cups package in Ubuntu:
Confirmed

Bug description:
[Impact]

[Test Case]

Expected result:
The job is printed after the 5s delay.

Actual result:
The job is cancelled.

[Regression Potential]

[Other Info]
Original bug description:

When using CUPS filters, these filters can take a few seconds to
complete.

In this case no documents are allowed to be lost on printing failures,
so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
14.04.

With cups on 18.04, you get the following message in /var/log/cups/error_log
whenever the filter takes a little longer:
I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

Then, the job is deleted and lost.

"MaxJobTime 0" is documented as "indefinite wait", but apparently cups
treats is as "wait almost not at all".

This issue appears to have also been filed upstream:
https://github.com/apple/cups/issues/5438

Temporary workaround is to set the MaxJobTime to a very large value
instead (e.g. 3 years)

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

[Desktop-packages] [Bug 1687864] Re: auto-login and "privacy -> auto screen lock -> disable" do not work

2018-12-06 Thread Wolf

It's really annoying that this silly bug still persists!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1687864

Title:
  auto-login and "privacy -> auto screen lock -> disable" do not work

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  On my machine, after booting I always have to type in my password,
  allthough I set "settings -> users -> auto login".

  The same happens after resume from suspend, allthough I set "privacy
  -> auto screen lock" to "disabled". In both cases the screen attached
  appears.

  My system:
  ubuntu 16.10
  gnome desktop
  lightdm

  Cheers,
  Wolf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1687864/+subscriptions

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

[Desktop-packages] [Bug 1806517] Re: Ghostscript segmentation fault on PDF using -dFirstPage and -dLastPage

2018-12-06 Thread Launchpad Bug Tracker

This bug was fixed in the package ghostscript - 9.26~dfsg+0-0ubuntu3

---
ghostscript (9.26~dfsg+0-0ubuntu3) disco; urgency=low

  * Backported upstream patch to prevent crashes when calling Ghostscript
with a PDF file and "-dLastPage=1" (LP: #1806517, upstream bug #700315).

 -- Till Kamppeter   Wed,  5 Dec 2018 16:47:06
+0100

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1806517

Title:
  Ghostscript segmentation fault on PDF using -dFirstPage and -dLastPage

Status in GS-GPL:
  Fix Released
Status in ghostscript package in Ubuntu:
  Fix Released
Status in ghostscript source package in Trusty:
  Confirmed
Status in ghostscript source package in Xenial:
  Confirmed
Status in ghostscript source package in Bionic:
  Confirmed
Status in ghostscript source package in Cosmic:
  Confirmed
Status in ghostscript source package in Disco:
  Fix Released

Bug description:
  In order to convert a PDF file in PNG I use the command:

  » convert "myfile.pdf[0]" test.png

  Which gives this error:

  convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET 
-dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 
-dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 
'-r72x72' -dFirstPage=1 -dLastPage=1 
'-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' 
'-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ 
error/delegate.c/ExternalDelegateCommand/462.
  convert-im6.q16: no images defined `test.png' @ 
error/convert.c/ConvertImageCommand/3258.

  So I tried using ghostscript directly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT
  -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2
  -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72
  -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf'

  Which gives an error:

  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 1.
  Page 1
  [1]10954 segmentation fault (core dumped)  ghostscript -dSAFER -dBATCH 
-dNOPAUSE -dNOPROMPT -dMaxBitmap=5

  If I omit -dFirstPage=1 -dLastPage=1 it works properly:

  » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 
-dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 
-dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf'
  GPL Ghostscript 9.26 (2018-11-20)
  Copyright (C) 2018 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 2.
  Page 1
  Page 2

  Please note that it also affects imagemagick convert command and PHP
  readimage command. I have confirmed the bug on Ubuntu 16.04 too.

  The recent ghostscript 9.26 version is definitely guilty.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec  4 12:59:59 2018
  InstallationDate: Installed on 2018-06-28 (158 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ghostscript
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1806517/+subscriptions

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-06 Thread Till Kamppeter

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

** Also affects: cups (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: cups (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  New
Status in cups package in Ubuntu:
  Confirmed
Status in cups source package in Xenial:
  New
Status in cups source package in Bionic:
  New
Status in cups source package in Cosmic:
  New

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no 
   difference in behavior except for the special value of MaxJobTime=0.
   

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

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

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

[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu

2018-12-06 Thread Bug Watch Updater

** Changed in: mailavenger (Debian)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp in Ubuntu.
https://bugs.launchpad.net/bugs/1802569

Title:
  RM openssl1.0 from Ubuntu

Status in cfengine2 package in Ubuntu:
  Confirmed
Status in ckermit package in Ubuntu:
  Confirmed
Status in conserver package in Ubuntu:
  Confirmed
Status in cqrlog package in Ubuntu:
  Confirmed
Status in freerdp package in Ubuntu:
  New
Status in libpam-ssh package in Ubuntu:
  New
Status in mailavenger package in Ubuntu:
  Confirmed
Status in moonshot-trust-router package in Ubuntu:
  Confirmed
Status in netkit-ftp-ssl package in Ubuntu:
  Confirmed
Status in netty-tcnative-1.1 package in Ubuntu:
  New
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in osslsigncode package in Ubuntu:
  New
Status in pam-ssh-agent-auth package in Ubuntu:
  New
Status in pidentd package in Ubuntu:
  New
Status in qpid-proton package in Ubuntu:
  New
Status in radsecproxy package in Ubuntu:
  New
Status in reconserver package in Ubuntu:
  Confirmed
Status in resiprocate package in Ubuntu:
  New
Status in ruby-eventmachine package in Ubuntu:
  New
Status in stunserver package in Ubuntu:
  New
Status in validns package in Ubuntu:
  New
Status in cfengine2 package in Debian:
  New
Status in ckermit package in Debian:
  New
Status in conserver package in Debian:
  New
Status in cqrlog package in Debian:
  New
Status in freerdp package in Debian:
  Fix Released
Status in libpam-ssh package in Debian:
  New
Status in mailavenger package in Debian:
  Fix Released
Status in moonshot-trust-router package in Debian:
  New
Status in netkit-ftp-ssl package in Debian:
  New
Status in netty-tcnative-1.1 package in Debian:
  New
Status in openssl1.0 package in Debian:
  New
Status in osslsigncode package in Debian:
  New
Status in pam-ssh-agent-auth package in Debian:
  New
Status in pidentd package in Debian:
  New
Status in qpid-proton package in Debian:
  New
Status in radsecproxy package in Debian:
  Confirmed
Status in reconserver package in Debian:
  New
Status in resiprocate package in Debian:
  Confirmed
Status in ruby-eventmachine package in Debian:
  Fix Released
Status in stunserver package in Debian:
  Confirmed
Status in validns package in Debian:
  Confirmed

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  
  freerdp is superseeded by freerdp2.

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

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

[Desktop-packages] [Bug 1806860] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1806860/+attachment/5219675/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1806860

Title:
  Pulseaudio module-jack-source unable to connect to jackd2

Status in jackd2 package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When installing jackd2 in ubuntu 18.04, i am unable to load the
  module-jack-source.

  Syslog gives me:

  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio

  So the path to the shared memory location is not as expected.

  When jackd2 is running i have:

  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system

  
  So it seems module-jack-source / sink are guessing the wrong shared memory 
paths to the jackd2 server..

  Versions:
  jackd2 1.9.12~dfsg-2 
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago)
  UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 042NDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7566
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952
  mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772

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

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

[Desktop-packages] [Bug 1806860] Re: Pulseaudio module-jack-source unable to connect to jackd2

apport information

** Tags added: apport-collected

** Description changed:

  When installing jackd2 in ubuntu 18.04, i am unable to load the module-
  jack-source.
  
  Syslog gives me:
  
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio
  
  So the path to the shared memory location is not as expected.
  
  When jackd2 is running i have:
  
  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system
  
  
  So it seems module-jack-source / sink are guessing the wrong shared memory 
paths to the jackd2 server..
  
  Versions:
  jackd2 1.9.12~dfsg-2 
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 18.04
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: pulseaudio 1:11.1-1ubuntu7.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18
+ Tags:  bionic
+ Uname: Linux 4.15.0-39-lowlatency x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago)
+ UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video 
wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 12/05/2017
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.2.1
+ dmi.board.name: 042NDD
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr:
+ dmi.product.family: Inspiron
+ dmi.product.name: Inspiron 7566
+ dmi.sys.vendor: Dell Inc.
+ modified.conffile..etc.pulse.daemon.conf: [modified]
+ modified.conffile..etc.pulse.default.pa: [modified]
+ mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952
+ mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1806860/+attachment/5219673/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1806860

Title:
  Pulseaudio module-jack-source unable to connect to jackd2

Status in jackd2 package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When installing jackd2 in ubuntu 18.04, i am unable to load the
  module-jack-source.

  Syslog gives me:

  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio

  So the path to the shared memory location is not as expected.

  When jackd2 is running i have:

  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system

  
  So it seems module-jack-source / sink are guessing the wrong shared memory 
paths to the jackd2 server..

  Versions:
  jackd2 1.9.12~dfsg-2 
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: zfs zunicode zavl i

[Desktop-packages] [Bug 1806860] Dependencies.txt

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1806860

Title:
  Pulseaudio module-jack-source unable to connect to jackd2

Status in jackd2 package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When installing jackd2 in ubuntu 18.04, i am unable to load the
  module-jack-source.

  Syslog gives me:

  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio

  So the path to the shared memory location is not as expected.

  When jackd2 is running i have:

  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system

  
  So it seems module-jack-source / sink are guessing the wrong shared memory 
paths to the jackd2 server..

  Versions:
  jackd2 1.9.12~dfsg-2 
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago)
  UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 042NDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7566
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952
  mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772

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

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

[Desktop-packages] [Bug 1806860] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1806860/+attachment/5219679/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1806860

Title:
  Pulseaudio module-jack-source unable to connect to jackd2

Status in jackd2 package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When installing jackd2 in ubuntu 18.04, i am unable to load the
  module-jack-source.

  Syslog gives me:

  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio

  So the path to the shared memory location is not as expected.

  When jackd2 is running i have:

  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system

  
  So it seems module-jack-source / sink are guessing the wrong shared memory 
paths to the jackd2 server..

  Versions:
  jackd2 1.9.12~dfsg-2 
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago)
  UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 042NDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7566
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952
  mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772

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

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

[Desktop-packages] [Bug 1806860] ProcCpuinfoMinimal.txt

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1806860

Title:
  Pulseaudio module-jack-source unable to connect to jackd2

Status in jackd2 package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When installing jackd2 in ubuntu 18.04, i am unable to load the
  module-jack-source.

  Syslog gives me:

  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio

  So the path to the shared memory location is not as expected.

  When jackd2 is running i have:

  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system

  
  So it seems module-jack-source / sink are guessing the wrong shared memory 
paths to the jackd2 server..

  Versions:
  jackd2 1.9.12~dfsg-2 
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago)
  UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 042NDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7566
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952
  mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772

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

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

[Desktop-packages] [Bug 1806860] ProcEnviron.txt

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1806860

Title:
  Pulseaudio module-jack-source unable to connect to jackd2

Status in jackd2 package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When installing jackd2 in ubuntu 18.04, i am unable to load the
  module-jack-source.

  Syslog gives me:

  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio

  So the path to the shared memory location is not as expected.

  When jackd2 is running i have:

  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system

  
  So it seems module-jack-source / sink are guessing the wrong shared memory 
paths to the jackd2 server..

  Versions:
  jackd2 1.9.12~dfsg-2 
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago)
  UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 042NDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7566
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952
  mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772

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

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

[Desktop-packages] [Bug 1806860] AudioDevicesInUse.txt

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1806860/+attachment/5219674/+files/AudioDevicesInUse.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1806860

Title:
  Pulseaudio module-jack-source unable to connect to jackd2

Status in jackd2 package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When installing jackd2 in ubuntu 18.04, i am unable to load the
  module-jack-source.

  Syslog gives me:

  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio

  So the path to the shared memory location is not as expected.

  When jackd2 is running i have:

  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system

  
  So it seems module-jack-source / sink are guessing the wrong shared memory 
paths to the jackd2 server..

  Versions:
  jackd2 1.9.12~dfsg-2 
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago)
  UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 042NDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7566
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952
  mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772

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

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

[Desktop-packages] [Bug 1787008] Re: Disconnecting hdmi connected monitor does not reposition windows

2018-12-06 Thread Launchpad Bug Tracker

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1787008

Title:
  Disconnecting hdmi connected monitor does not reposition windows

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  At time when i disconnect my monitor the windows are occasionally not
  repositioned on the remaining monitor on my laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Aug 14 21:01:33 2018
  DistUpgraded: 2018-04-27 17:12:36,606 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5053]
  InstallationDate: Installed on 2018-03-08 (158 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 20FMS2AV00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9ae4268b-5721-48e8-9702-9fcdfa60f6f6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (109 days ago)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  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:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787008/+subscriptions

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

[Desktop-packages] [Bug 1803230] Re: [MIR] teckit & xxhash, new rdeps of texlive-bin

2018-12-06 Thread Didier Roche

ack for me, seb told me he would take care of the tests.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to teckit in Ubuntu.
https://bugs.launchpad.net/bugs/1803230

Title:
  [MIR] teckit & xxhash, new rdeps of texlive-bin

Status in teckit package in Ubuntu:
  Fix Released
Status in xxhash package in Ubuntu:
  Incomplete

Bug description:
  teckit & xxhash, new rdeps of texlive-bin

  teckit was formerly bundled in texlive-bin (I believe)

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

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

[Desktop-packages] [Bug 1807127] [NEW] Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu

2018-12-06 Thread Eugene Romanenko

Public bug reported:

Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu.

Looks like same issue in upstream -
https://bugzilla.redhat.com/show_bug.cgi?id=1651952


Workaround - use previous version of libgnome-desktop-3-17 without bubblewrap.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic i686
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec  6 12:07:28 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-desktop3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-desktop3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug bionic i386

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1807127

Title:
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu

Status in gnome-desktop3 package in Ubuntu:
  New

Bug description:
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu.

  Looks like same issue in upstream -
  https://bugzilla.redhat.com/show_bug.cgi?id=1651952

  
  Workaround - use previous version of libgnome-desktop-3-17 without bubblewrap.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  6 12:07:28 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-desktop3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+subscriptions

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

[Desktop-packages] [Bug 1795668] Re: Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

2018-12-06 Thread Eugene Romanenko

This change breaks thumbnail creation on 32-bit Ubuntu. Filled bug
#1807127.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1795668

Title:
  Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

Status in bubblewrap package in Ubuntu:
  Fix Released
Status in gnome-desktop3 package in Ubuntu:
  Fix Released

Bug description:
  Impact
  ==
  gnome-desktop 3.26 hardened the thumbnailers with bubblewrap to mitigate 
several vulnerabilities. Ubuntu had to disable that feature until bubblewrap 
could be promoted to main.

  bubblewrap is now in main for 18.10 and the feature is now enabled
  there. The intention has been for that change to be backported to
  18.04 LTS as a security fix.

  The bubblewrap MIR is https://launchpad.net/bugs/1709164

  We'll need to promote bubblewrap to main before this update should be
  pushed to bionic.

  Can you sponsor directly from the git repo instead of with a debdiff?

  gbp clone https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source
  /gnome-desktop3

  git checkout ubuntu/bionic

  gbp clone https://git.launchpad.net/~ubuntu-
  desktop/ubuntu/+source/bubblewrap

  Testing Done
  
  I test built bubblewrap and its autopkgtest passes:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-jbicha-arch/bionic/amd64/b/bubblewrap/20181002_153548_f5821@/log.gz

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

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

imagetopdf filter wrapper I've used for the reproducer:
#!/usr/bin/env python

import sys
import time
import subprocess

def main():
time.sleep(5)
args = ["/usr/lib/cups/filter/imagetopdf.bkp"] + sys.argv[1:]
subprocess.call(args, stdin=sys.stdin, stdout=sys.stdout, stderr=sys.stderr)

if __name__ == "__main__":
main()

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  New
Status in cups package in Ubuntu:
  Confirmed
Status in cups source package in Xenial:
  New
Status in cups source package in Bionic:
  New
Status in cups source package in Cosmic:
  New

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no 
   difference in behavior except for the special value of MaxJobTime=0.
   

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

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

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

[Desktop-packages] [Bug 1799430] Re: Icon dock visible on lock screen

2018-12-06 Thread Thompson Plyler

I just noticed this issue this morning. I can't see previews, but I can
see dock items and their current status (running or not).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1799430

Title:
  Icon dock visible on lock screen

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When locking the machine with alt-L the icon dock is still visible.

  After Login, the dock does not get adjusted to the top menu.

  In rare cases, the dock does not respond any more. This requires a
  reboot of the machine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: mutter 3.30.1-1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 12:59:27 2018
  InstallationDate: Installed on 2018-04-30 (176 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+subscriptions

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

[Desktop-packages] [Bug 1807127] Re: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu

2018-12-06 Thread Eugene Romanenko

** Description changed:

  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu.
  
  Looks like same issue in upstream -
  https://bugzilla.redhat.com/show_bug.cgi?id=1651952
  
  
- Workaround - use previous version of libgnome-desktop-3-17 without bubblewrap.
+ Cause - bubblewrap runs with --ro-bind /lib64 option, then fails.
+ Workaround - create empty /lib64 directory at root.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  6 12:07:28 2018
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-desktop3
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1807127

Title:
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu

Status in gnome-desktop3 package in Ubuntu:
  New

Bug description:
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu.

  Looks like same issue in upstream -
  https://bugzilla.redhat.com/show_bug.cgi?id=1651952

  
  Cause - bubblewrap runs with --ro-bind /lib64 option, then fails.
  Workaround - create empty /lib64 directory at root.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  6 12:07:28 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-desktop3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+subscriptions

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

[Desktop-packages] [Bug 1807127] Re: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu

2018-12-06 Thread Jeremy Bicha

** Tags added: regression-update

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1807127

Title:
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu

Status in gnome-desktop3 package in Ubuntu:
  New

Bug description:
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu.

  Looks like same issue in upstream -
  https://bugzilla.redhat.com/show_bug.cgi?id=1651952

  
  Cause - bubblewrap runs with --ro-bind /lib64 option, then fails.
  Workaround - create empty /lib64 directory at root.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  6 12:07:28 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-desktop3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+subscriptions

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

[Desktop-packages] [Bug 1807132] [NEW] package gdm3 3.28.3-0ubuntu18.04.3 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 1

2018-12-06 Thread Yakov Medovikov

Public bug reported:

First install Ubuntu 18.04LTS,
OS X 10.11.6,
Parallels 11.1.2 (32408))
Macbook Pro 15-inch mid 2015

failed on apt-get upgrade

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.3-0ubuntu18.04.3
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Dec  6 02:42:20 2018
ErrorMessage: installed gdm3 package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2018-12-06 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: gdm3
Title: package gdm3 3.28.3-0ubuntu18.04.3 failed to install/upgrade: installed 
gdm3 package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1807132

Title:
  package gdm3 3.28.3-0ubuntu18.04.3 failed to install/upgrade:
  installed gdm3 package post-installation script subprocess returned
  error exit status 1

Status in gdm3 package in Ubuntu:
  New

Bug description:
  First install Ubuntu 18.04LTS,
  OS X 10.11.6,
  Parallels 11.1.2 (32408))
  Macbook Pro 15-inch mid 2015

  failed on apt-get upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Dec  6 02:42:20 2018
  ErrorMessage: installed gdm3 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-12-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: gdm3
  Title: package gdm3 3.28.3-0ubuntu18.04.3 failed to install/upgrade: 
installed gdm3 package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1807127] Re: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu

2018-12-06 Thread Jeremy Bicha

I have forwarded the issue to GNOME at https://gitlab.gnome.org/GNOME
/gnome-desktop/issues/89

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1807127

Title:
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu

Status in gnome-desktop3 package in Ubuntu:
  New

Bug description:
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu.

  Looks like same issue in upstream -
  https://bugzilla.redhat.com/show_bug.cgi?id=1651952

  
  Cause - bubblewrap runs with --ro-bind /lib64 option, then fails.
  Workaround - create empty /lib64 directory at root.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  6 12:07:28 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-desktop3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+subscriptions

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

[Desktop-packages] [Bug 1806913] Re: [snap] libreoffice 6.1.3.2 crashes on startup on Ubuntu 18.04

2018-12-06 Thread RALOVICH , Kristóf

https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1806913/comments/1

it does not change anything for me to run it like

GTK_IM_MODULE= snap run libreoffice

How would you like me to describe my input method? I use LXDE. I think
it does not start ibus-daemon by default. However starting it manually,
the same crash happens with and without the environment variable set as
you asked for.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1806913

Title:
  [snap] libreoffice 6.1.3.2 crashes on startup on Ubuntu 18.04

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -a
  LSB Version:  core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  $ snap info libreoffice
  name:libreoffice
  summary: LibreOffice is a powerful office suite including word processing and 
creation of spreadsheets,
    slideshows and databases
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bugs?field.tag=snap
  license:   unset
  description: |
    LibreOffice is a powerful office suite – its clean interface and 
feature-rich tools help you
    unleash your creativity and enhance your productivity. LibreOffice includes 
several applications
    that make it the most powerful Free and Open Source office suite on the 
market: Writer (word
    processing), Calc (spreadsheets), Impress (presentations), Draw (vector 
graphics and flowcharts),
    Base (databases), and Math (formula editing).
  commands:
    - libreoffice.base
    - libreoffice.calc
    - libreoffice.draw
    - libreoffice.filebug
    - libreoffice.impress
    - libreoffice
    - libreoffice.math
    - libreoffice.writer
  snap-id:  CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v
  tracking: stable
  refresh-date: 22 days ago, at 13:20 CET
  channels:
    stable:6.1.3.2 (90) 507MB - <
    candidate: 6.1.3.2 (95) 499MB -
    beta:  ↑
    edge:  ↑
  installed:   6.1.3.2 (90) 507MB -

  $ snap run libreoffice
  Fontconfig warning: "/etc/fonts/conf.avail/53-monospace-lcd-filter.conf", 
line 10: Having multiple values in  isn't supported and may not work as 
expected

  (soffice:10375): GLib-GObject-WARNING **: 15:09:09.826: specified class size 
for type 'IBusIMContext' is smaller than the parent type's 'GtkIMContext' class 
size
  *** Error in `/snap/libreoffice/90/lib/libreoffice/program/soffice.bin': 
malloc(): memory corruption: 0x02cef640 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f00cd04c7e5]
  /lib/x86_64-linux-gnu/libc.so.6(+0x8213e)[0x7f00cd05713e]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f00cd059184]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_malloc+0x19)[0x7f00cb28d2c9]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strndup+0x18)[0x7f00cb2a7a98]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strsplit+0x95)[0x7f00cb2a9085]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-ibus.so(+0x4224)[0x7f00b279f224]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_type_class_ref+0x6dd)[0x7f00cb58462d]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new_with_properties+0x2f9)[0x7f00cb56acc9]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new+0xc1)[0x7f00cb56b6d1]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-ibus.so(ibus_im_context_new+0x12)[0x7f00b279fd72]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x11ae6e)[0x7f00bbf1be6e]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x11b7c9)[0x7f00bbf1c7c9]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x11ba05)[0x7f00bbf1ca05]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xc2057)[0x7f00bbec3057]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x145)[0x7f00cb563cd5]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x22065)[0x7f00cb576065]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xfc0)[0x7f00cb57f160]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f00cb57f49f]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_widget_realize+0xd4)[0x7f00bc051bc4]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_widget_set_parent+0x258)[0x7f00bc052ed8]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_fixed_put+0xb3)[0x7f00bbef1a73]
  
/snap/libreoffice/90/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x145)[0x7f00cb563cd5]
  
/snap/libr

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

** Also affects: cups (Ubuntu Disco)
   Importance: Medium
   Status: Confirmed

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

** Changed in: cups (Ubuntu Disco)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

** Changed in: cups (Ubuntu Cosmic)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

** Changed in: cups (Ubuntu Bionic)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

** Changed in: cups (Ubuntu Xenial)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

** Changed in: cups (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: cups (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: cups (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cups (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: cups (Ubuntu Disco)
   Status: Confirmed => In Progress

** Changed in: cups (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: cups (Ubuntu Xenial)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  New
Status in cups package in Ubuntu:
  In Progress
Status in cups source package in Trusty:
  New
Status in cups source package in Xenial:
  In Progress
Status in cups source package in Bionic:
  In Progress
Status in cups source package in Cosmic:
  In Progress
Status in cups source package in Disco:
  In Progress

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no 
   difference in behavior except for the special value of MaxJobTime=0.
   

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

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

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

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

** Description changed:

  [Impact]
  
-  Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
+  Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.
  
  [Test Case]
  
-  1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
-  2. Setup a filter that takes at least several seconds to process.
- (please find a sample imagetopdf wrapper introducing 5s delay)
-  3. Submit a print job matching the filter, e.g.
- lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper
+  1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
+  2. Setup a filter that takes at least several seconds to process.
+ (please find a sample imagetopdf wrapper introducing 5s delay)
+  3. Submit a print job matching the filter, e.g.
+ lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper
  
  Expected result:
  The job is printed after the 5s delay.
  
  Actual result:
  The job is cancelled.
  
  [Regression Potential]
  
-  The scope of the change is limited to fixing the MaxJobTime handling
-  in scheduler/job.c and scheduler/printers.c. There should be no 
-  difference in behavior except for the special value of MaxJobTime=0.
-  
+  The scope of the change is limited to fixing the MaxJobTime handling
+  in scheduler/job.c and scheduler/printers.c. There should be no
+  difference in behavior except for the special value of MaxJobTime=0.
  
  [Other Info]
  Original bug description:
  
  When using CUPS filters, these filters can take a few seconds to
  complete.
  
  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.
  
  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.
  
  Then, the job is deleted and lost.
  
  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".
  
  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438
  
  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)
+ 
+ Trusty is not affected by this bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  New
Status in cups package in Ubuntu:
  In Progress
Status in cups source package in Trusty:
  Invalid
Status in cups source package in Xenial:
  In Progress
Status in cups source package in Bionic:
  In Progress
Status in cups source package in Cosmic:
  In Progress
Status in cups source package in Disco:
  In Progress

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no
   difference in behavior except for the special value of MaxJobTime=0.

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following m

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

SRU proposal for disco (fixed)

** Patch removed: "disco_cups_2.2.9-3ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219664/+files/disco_cups_2.2.9-3ubuntu1.debdiff

** Patch added: "disco_cups_2.2.9-3ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219720/+files/disco_cups_2.2.9-3ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  New
Status in cups package in Ubuntu:
  In Progress
Status in cups source package in Trusty:
  Invalid
Status in cups source package in Xenial:
  In Progress
Status in cups source package in Bionic:
  In Progress
Status in cups source package in Cosmic:
  In Progress
Status in cups source package in Disco:
  In Progress

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no
   difference in behavior except for the special value of MaxJobTime=0.

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

  Trusty is not affected by this bug.

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

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

[Desktop-packages] [Bug 1807138] Re: [HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected

2018-12-06 Thread Arne De Herdt

I've taken a screenshot of the alsamixer.
This configuration currently is the only way for me to get sound out of my 
headset and not the speakers:

* Enable master sound
* Enable headphones, and assign volume
* Enable speakers, but put volume to 0, don't mute
* disable auto-mute

** Attachment added: "alsamixer confiugration"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+attachment/5219727/+files/Screenshot%20from%202018-12-06%2013-15-32.png

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Headphones not automatically
  detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+subscriptions

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

[Desktop-packages] [Bug 1807138] [NEW] [HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected

2018-12-06 Thread Arne De Herdt

Public bug reported:

Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
I haven't rebooted my system yet to see if this is permanent.
But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

➜  ~ lspci -nnk | grep -i -A7 audio
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

➜  ~ cat /proc/asound/card0/codec* | grep Codec 
Codec: Realtek ALC256
Codec: Intel Kabylake HDMI

Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
If I reboot or close pavucontrol, everything is back to the original state and 
only the speakers work.

Additional Information:

➜  ~ lsb_release -rd 
Description:Ubuntu 18.04.1 LTS
Release:18.04

What I expect to happen:

When I plug in my headphones, Ubuntu and the UI should see them and
automatically redirect all sound through them.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
 /dev/snd/controlC0:  olivar 8320 F pulseaudio
CurrentDesktop: X-Cinnamon
Date: Thu Dec  6 13:02:14 2018
InstallationDate: Installed on 2018-11-21 (15 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2018
dmi.bios.vendor: Razer
dmi.bios.version: 01.01
dmi.board.name: DANA_MB
dmi.board.vendor: Razer
dmi.chassis.type: 10
dmi.chassis.vendor: Razer
dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
dmi.product.family: 1A582001 Razer Blade
dmi.product.name: Blade
dmi.product.version: 1.04
dmi.sys.vendor: Razer

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


** Tags: amd64 apport-bug bionic

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Headphones not automatically
  detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  U

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

** Tags added: sts-sponsor sts-sponsor-ddstreet

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  New
Status in cups package in Ubuntu:
  In Progress
Status in cups source package in Trusty:
  Invalid
Status in cups source package in Xenial:
  In Progress
Status in cups source package in Bionic:
  In Progress
Status in cups source package in Cosmic:
  In Progress
Status in cups source package in Disco:
  In Progress

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no
   difference in behavior except for the special value of MaxJobTime=0.

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

  Trusty is not affected by this bug.

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

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

** Changed in: cups (Ubuntu Disco)
 Assignee: Dariusz Gadomski (dgadomski) => Dan Streetman (ddstreet)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  New
Status in cups package in Ubuntu:
  In Progress
Status in cups source package in Trusty:
  Invalid
Status in cups source package in Xenial:
  In Progress
Status in cups source package in Bionic:
  In Progress
Status in cups source package in Cosmic:
  In Progress
Status in cups source package in Disco:
  In Progress
Status in cups package in Debian:
  Unknown

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no
   difference in behavior except for the special value of MaxJobTime=0.

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

  Trusty is not affected by this bug.

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

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never