[Desktop-packages] [Bug 1801566] Re: package install-info 6.1.0.dfsg.1-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2018-11-03 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package install-info 6.1.0.dfsg.1-5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in texinfo package in Ubuntu:
  New

Bug description:
  restarted my system.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: install-info 6.1.0.dfsg.1-5
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Nov  4 00:34:15 2018
  DuplicateSignature:
   package:install-info:6.1.0.dfsg.1-5
   Processing triggers for install-info (6.1.0.dfsg.1-5) ...
   /usr/sbin/update-info-dir: 3: export: JAVA_HOME.: bad variable name
   dpkg: error processing package install-info (--unpack):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-02-09 (633 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: texinfo
  Title: package install-info 6.1.0.dfsg.1-5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1801566/+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 1801566] [NEW] package install-info 6.1.0.dfsg.1-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2018-11-03 Thread Abhay Koradiya
Public bug reported:

restarted my system.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: install-info 6.1.0.dfsg.1-5
ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
Uname: Linux 4.4.0-135-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun Nov  4 00:34:15 2018
DuplicateSignature:
 package:install-info:6.1.0.dfsg.1-5
 Processing triggers for install-info (6.1.0.dfsg.1-5) ...
 /usr/sbin/update-info-dir: 3: export: JAVA_HOME.: bad variable name
 dpkg: error processing package install-info (--unpack):
  subprocess installed post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2017-02-09 (633 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: texinfo
Title: package install-info 6.1.0.dfsg.1-5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package install-info 6.1.0.dfsg.1-5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in texinfo package in Ubuntu:
  New

Bug description:
  restarted my system.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: install-info 6.1.0.dfsg.1-5
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Nov  4 00:34:15 2018
  DuplicateSignature:
   package:install-info:6.1.0.dfsg.1-5
   Processing triggers for install-info (6.1.0.dfsg.1-5) ...
   /usr/sbin/update-info-dir: 3: export: JAVA_HOME.: bad variable name
   dpkg: error processing package install-info (--unpack):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-02-09 (633 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: texinfo
  Title: package install-info 6.1.0.dfsg.1-5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1801566/+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 1187559] Re: can't print using hplip 3.13.5. Keep getting text with "@PJL SET JOBATTR="JobAcct3..."

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  can't print using hplip 3.13.5.  Keep getting text with "@PJL SET
  JOBATTR="JobAcct3..."

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Expired

Bug description:
  ran both hp-check -t and hp-doctor -- Here is the hp-check report:

  Check types:  
  
  a. EXTERNALDEP - External Dependencies
  
  b. GENERALDEP - General Dependencies (required both at compile and run time)  
  
  c. COMPILEDEP - Compile time Dependencies 
  
  d. [All are run-time checks]  
  
  PYEXT SCANCONF QUEUES PERMISSION  
  

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible dependency-version or Plugin-version

  
  ---
  | SYSTEM INFO |
  ---

   Kernel: 3.2.0-45-generic-pae #70-Ubuntu SMP Wed May 29 20:31:05 UTC 2013 
GNU/Linux
   Host: ralph-GC668AA-ABA-SR5110NX
  localhost
   Proc: 3.2.0-45-generic-pae #70-Ubuntu SMP Wed May 29 20:31:05 UTC 2013 
GNU/Linux
   Distribution: ubuntu 12.04
   Bitness: 32 bit

  
  ---
  | HPLIP CONFIGURATION |
  ---

  HPLIP-Version: HPLIP 3.13.5
  HPLIP-Home: /usr/share/hplip
  HPLIP-Installation: Auto installation is supported for ubuntu distro  12.04 
version 

  Current contents of '/etc/hp/hplip.conf' file:
  # hplip.conf.  Generated from hplip.conf.in by configure.

  [hplip]
  version=3.13.5

  [dirs]
  home=/usr/share/hplip
  run=/var/run
  ppd=/usr/share/ppd/HP
  ppdbase=/usr/share/ppd
  doc=/usr/share/doc/hplip-3.13.5
  icon=/usr/share/applications
  cupsbackend=/usr/lib/cups/backend
  cupsfilter=/usr/lib/cups/filter
  drv=/usr/share/cups/drv/hp
  bin=/usr/bin

  # Following values are determined at configure time and cannot be changed.
  [configure]
  network-build=yes
  libusb01-build=no
  pp-build=no
  gui-build=yes
  scanner-build=yes
  fax-build=yes
  dbus-build=yes
  cups11-build=no
  doc-build=yes
  shadow-build=no
  hpijs-install=no
  foomatic-drv-install=no
  foomatic-ppd-install=no
  foomatic-rip-hplip-install=no
  hpcups-install=yes
  cups-drv-install=yes
  cups-ppd-install=no
  internal-tag=3.13.5
  restricted-build=no
  ui-toolkit=qt4
  qt3=no
  qt4=yes
  policy-kit=no
  hpijs-only-build=no
  lite-build=no
  udev-acl-rules=yes
  udev_sysfs_rules=no
  hpcups-only-build=no
  hpijs-only-build=no

  
  Current contents of '/var/lib/hp/hplip.state' file:
  [plugin]
  installed = 1
  eula = 1
  version = 3.13.5


  Current contents of '~/.hplip/hplip.conf' file:
  [upgrade]
  notify_upgrade = true
  last_upgraded_time = 1370229886
  pending_upgrade_time = 0
  latest_available_version = 3.13.5

  [settings]
  systray_visible = 0
  systray_messages = 1

  [last_used]
  device_uri = "hpfax:/usb/Officejet_6600?serial=CN25N2H1GC05RN"
  printer_name = Officejet_6600
  working_dir = .

  [commands]
  scan = /usr/bin/xsane -V %SANE_URI%

  [refresh]
  rate = 30
  enable = false
  type = 1

  [polling]
  enable = false
  interval = 5
  device_list = 

  [fax]
  voice_phone = 
  email_address = 

  [installation]
  date_time = 06/04/2013 14:14:54
  version = 3.13.5

  
   


  --
  |  External Dependencies |
  --

   gs   Ghostscript   REQUIRED7.05  
  9.05OK -
   network  Network-wget  OPTIONAL- 
  1.13.4  OK -
   dbus DBus  REQUIRED- 
  1.4.18  OK -
   scanimageShell-ScanningOPTIONAL1.0   
  1.0.22  OK -
   policykitAdmin-Policy-frameworkOPTIONAL- 
  0.104   OK -
   xsaneSANE-GUI  OPTIONAL0.9   
  0.998   OK -
   cups CUPS  REQUIRED1.1   
  1.5.3   OK 'CUPS Scheduler is running'

  -
  |  General Dependencies |
  -

   reportlabPython-PDF-LibOPTIONAL2.0   
  2.5 OK -
   libcryptoOpenSSL-Crypto-LibREQUIRED- 
  1.0.1   OK -
   pil  Python-Image-Lib  OPTIONAL- 
  1.1.7   OK -
 

[Desktop-packages] [Bug 1050015] Re: package hplip 3.12.2-1ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package hplip 3.12.2-1ubuntu3.1 failed to install/upgrade: подпроцесс
  установлен сценарий post-installation возвратил код ошибки 1

Status in hplip package in Ubuntu:
  Expired

Bug description:
  the system detects an error in the package

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
  Uname: Linux 3.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  AptOrdering:
   hplip: Configure
   printer-driver-postscript-hp: Configure
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Sep 12 21:04:32 2012
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-30-generic 
root=UUID=aab7fb5a-e8d6-4bbc-942d-66b75d03741f ro quiet splash vt.handoff=7
  SourcePackage: hplip
  Title: package hplip 3.12.2-1ubuntu3.1 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: Upgraded to precise on 2012-04-27 (137 days ago)
  dmi.bios.date: 08/25/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68C-S UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd08/25/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1050015/+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 1036722] Re: HP Photosmart 1215 won't print landscape

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  HP Photosmart 1215 won't print landscape

Status in hplip package in Ubuntu:
  Expired

Bug description:
  When I try to print landscape to the HP Photosmart 1215, I can set
  that as appropriate, but it prints in Potrait instead. Found in
  Firefox and LibreOffice writer.

  Ubunto 11.10

  Installed hplip but problem still occurs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1036722/+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 1024901] Re: hpcups does not use black ink in full-bleed mode

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  hpcups does not use black ink in full-bleed mode

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Expired

Bug description:
  When printing in full-bleed mode with hpcups on my HP photosmart 2610, the 
black parts of the image are rendered using color ink, while I would expect 
using black ink instead.
  When going back to normal print mode (not full-bleed) the black parts are 
rendered using black ink.

  As a comparison, when the hpijs driver in both full-bleed and normal
  mode, black is rendered correctly using black ink, when choosing the
  "black+color" printing option (no such option is available in hpcups).

  I am using Ubuntu 12.04 LTS, amd64.

  Attached is the ouput from hp-check.

  Best regards,
  Martin

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1024901/+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 1085444] Re: HP Laserjet P2015dn : only .pdf files are printed double-sided

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  HP Laserjet P2015dn : only .pdf files are printed double-sided

Status in hplip package in Ubuntu:
  Expired

Bug description:
  Hello, My HP Laserjet P2015dn is well installed  with HPLIP and works almost 
fine :
  With pdf files : I can only print both sides of the paper. The dialog box for 
single-sided printing does not appear.
  With other files (.doc, .xls, .odt, .html, etc.) only single-sided printing 
is available. The dialogue box for double-sided printing does not appear.
  Also, when a document includes landscape and portrait pages, the driver 
detects a default although it doesn't stop the printing process. Installed 
system is Ubuntu 12.04 LTS, 32 bits. Thank you for your help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1085444/+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 1153071] Re: User not added to scanner and lp groups + unhelpful errors

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  User not added to scanner and lp groups + unhelpful errors

Status in hplip package in Ubuntu:
  Expired

Bug description:
  On a fresh install of 12.04.2 I tried using Simple Scan and received a
  number of unhelpful error messages trying to scan from a USB-attached
  HP CM1312nfi MFP color printer/scanner.  Xsane and the hp-scan and hp-
  info also reported extremely unhelpful messages similar to "I/O
  error=9"

  It turns out the issue is that the default user is not added to the
  scanner or lp (and possibly other) user groups.  I propose that either
  the error message be clarified to something that indicates the user
  doesn't have permissions, or better, the user account be granted
  access to lp and scanner on a default install, since they're already
  granted access to admin.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1153071/+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 1080569] Re: Firefox 16.0.2 ubuntu 12.10 cannot delete bookmarks/Right clik takes me to the page/ delete key does not work/ cant find places.sqlite anywhere on the system

2018-11-03 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Firefox 16.0.2 ubuntu 12.10 cannot delete bookmarks/Right clik takes
  me to the page/ delete key does not work/ cant find places.sqlite
  anywhere on the system

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Went to answers.launchpad.net/ubuntu and searched for "cannot delete
  bookmarks" but found very little. Posted a question there as well..TIA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1080569/+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 1071501] Re: Firefox emaI stuck, cannot enter into text or attach or cancel or delete

2018-11-03 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Firefox emaI stuck, cannot enter into text or attach or cancel or
  delete

Status in firefox package in Ubuntu:
  Expired

Bug description:
  AOL email opens can enter address and subject, cannot enter anything into 
text box, cannot attach, cannot delete or cancel,.  Happens intermittently with 
12.10 for months.  This is:
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04
  Codename: raring
  Linux version 3.5.0-17-generic (buildd@allspice) (gcc version 4.7.2 
(Ubuntu/Linaro 4.7.2-2ubuntu1) ) #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012

  yahoo, opera both email fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: firefox 16.0.1+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jerry  1572 F pulseaudio
   /dev/snd/controlC0:  jerry  1572 F pulseaudio
  BuildID: 20121010223843
  Channel: Unavailable
  Date: Thu Oct 25 17:14:04 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-25 (0 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.8  metric 9
  MarkForUpload: True
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=16.0.1/20121010223843 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 2.97-1ubuntu5
   totem-mozilla 3.4.3-0ubuntu4
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.name: Aspire 5253
  dmi.board.vendor: Acer
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd01/06/2011:svnAcer:pnAspire5253:pvrV1.05:rvnAcer:rnAspire5253:rvrV1.05:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 5253
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1071501/+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 1027186] Re: HP Deskjet (880C) Wrong Colors in Precise

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  HP Deskjet (880C) Wrong Colors in Precise

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Expired

Bug description:
  Precise 12.04 with Gnome Fallback

  After a fresh install of Precise with all of its auto detection and
  configuration, HP 880C Deskjet printer prints wrong colors- teal skin
  tones for example.  If I boot Lucid instead, output for same photo is
  perfect. Searching Synaptic for HP brings up multiple drivers and apps
  Precise put on my system based (I assume) on the printer it
  autodetected. I have no clue where to begin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1027186/+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 1153987] Re: In ubuntu 12.04 hplip-3.12.2 version and above it does not detect and print with HP Laserjet P1566 and HP Laserjet P2055dn give printing errors

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  In ubuntu 12.04 hplip-3.12.2 version and above it does not detect and
  print with HP Laserjet P1566 and HP Laserjet P2055dn give printing
  errors

Status in hplip package in Ubuntu:
  Expired

Bug description:
  in Ubuntu 12.04 hplip-3.12.2 version and above it, hp-setup does not
  detect HP Laserjet P1566 on usb. HP Laserjet P2055dn prints one time
  and second time does not print and thrid time print some internal
  printer command log on the page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1153987/+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 1801564] [NEW] Can't connect second monitor on NVidia over adapter DVI->VGA

2018-11-03 Thread Andr-NL
Public bug reported:

NVidia GF108 (10de:0df8) Quadro 600 
xserver-xorg-video-nouveau,nvidia-graphics-drivers
:
  DisplayPort=Samsung 27"
  DVI->VGA=Acer V193HQ

INTEL
:
  DVI=BenQ FP93G X

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
Date: Sun Nov  4 07:43:17 2018
DistUpgraded: 2018-10-29 18:00:47,682 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694]
 NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation GF108GL [Quadro 600] [10de:0835]
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic 
root=UUID=bc343c51-118f-49ba-a3a5-283e6bbd0290 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-10-29 (5 days ago)
dmi.bios.date: 09/08/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0810
dmi.board.asset.tag: Default string
dmi.board.name: STRIX B250F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0810:bd09/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXB250FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sun Nov  4 07:41:21 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu

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

Title:
  Can't connect second monitor on NVidia over adapter DVI->VGA

Status in xorg package in Ubuntu:
  New

Bug description:
  NVidia GF108 (10de:0df8) Quadro 600 
xserver-xorg-video-nouveau,nvidia-graphics-drivers
  :
DisplayPort=Samsung 27"
DVI->VGA=Acer V193HQ

  INTEL
  :
DVI=BenQ FP93G X

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Nov  4 07:43:17 2018
  DistUpgraded: 2018-10-29 18:00:47,682 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694]
   NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 
[VGA 

[Desktop-packages] [Bug 1168997] Re: Download of Hplip has multiple errors, system reads Unable to open device hp:/par/HP_LaserJet_5Si?device=/dev/parport0.

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Download of Hplip has multiple errors, system reads Unable to open
  device hp:/par/HP_LaserJet_5Si?device=/dev/parport0.

Status in hplip package in Ubuntu:
  Expired

Bug description:
  Using Ubuntu 12.04 LTS

  Printer is HP 5si

  Direct connection

  Downloaded from Ubuntu Software as well as from other sites

  I'm using a fresh install of 12.04LTS from factory disk onto a Dell
  Optiplex 755 with 2 gig Ram and 300+- gig HD.

  I've downloaded three times with the same results.  Errors.

  Using DSL connection.

  Also received " Unable to open device
  hp:/par/HP_LaserJet_5Si?device=/dev/parport0. "

  http://hplipopensource.com/ is no longer an active page

  The computer does communicate with the printer causing the printer to
  print one line at the top of the page as follows

  %!PS-Adobe-3.0%Produced by poppler pdftops version: 0.18.4
  (http://poppler.freed

  Printer reacts by pushing all the paper in the tray through the
  printer without printing anything additional.  It is necessary to shut
  off the printer to stop the printing.  Yes I did go into the printer
  control and delet the job as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1168997/+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 1270296] Re: package libhpmud0 (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package libhpmud0 (not installed) failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 2

Status in hplip package in Ubuntu:
  Expired

Bug description:
  This prevented the partial upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libhpmud0 (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-45.68~precise1-generic 3.5.7.26
  Uname: Linux 3.5.0-45-generic i686
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Fri Jan 17 20:49:30 2014
  DuplicateSignature: package:libhpmud0:(not installed):subprocess installed 
pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  SourcePackage: hplip
  Title: package libhpmud0 (not installed) failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1270296/+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 1260234] Re: CUPS gets disabled occasionally

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  CUPS gets disabled occasionally

Status in hplip package in Ubuntu:
  Expired

Bug description:
  Hi!

  I'm running Ubuntu 12.04.3 and have a lot of HP-Laserjet network
  printers in my office. Occasionally (hell knows why) the printer,
  which is setup as the default printer, becomes disabled. After
  realizing that I'm not getting anything printed, I must then open
  printing preferences and click on "enabled". Then it prints happily
  until the next time that it becomes disabled...

  Now I use ugly solution of this old problem:
  
http://askubuntu.com/questions/23503/network-printer-gets-disabled-occasionally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1260234/+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 1229344] Re: package hplip-data 3.13.3-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package hplip-data 3.13.3-1ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in hplip package in Ubuntu:
  Expired

Bug description:
  Errors cropped up three times at least during installation of ubuntu from 
live USB.
  Applications open were Ubuntu Software Center and Firefox browser while 
installation was in progress.
  Actual cause unknown.

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: hplip-data 3.13.3-1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  CupsErrorLog: E [23/Sep/2013:23:40:47 +0530] [cups-driverd] Bad driver 
information file "/usr/share/cups/drv/cupsfilters.drv"!
  Date: Mon Sep 23 23:42:15 2013
  DuplicateSignature: package:hplip-data:3.13.3-1ubuntu0.1:subprocess installed 
post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2013-09-23 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=5a4e0354-e9cf-47ed-aff2-fce8d5ecce11 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  Title: package hplip-data 3.13.3-1ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0408
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QPL-AM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0408:bd03/16/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QPL-AM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1229344/+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 1222221] Re: first time connection/driver download problem. printer hp 1006

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  first time connection/driver download problem. printer hp 1006

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Expired

Bug description:
  After first connection of the printer to laptop via usb, we see notify in top 
right corner, something like: downloading proprietary file for hp 1006 
printer...
  And nothing happened next. I were obligated to do manually 'sudo hp-setup' 
and add printer.

  As i remember, in older versions of Ubuntu, after first plug in of the
  printer, were pop-up window, were you need to press several times
  'enter', agree with license and finally hear nice sound of the printer
  witch signalize that all is OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-printers 0.1.7daily13.03.01-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Sat Sep  7 21:21:06 2013
  InstallationDate: Installed on 2013-09-01 (6 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-printers
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/121/+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 1235563] Re: HP DeskJet 930C fails during print; USB-to-Parallel - not detected by HPLIP

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  HP DeskJet 930C fails during print; USB-to-Parallel - not detected by
  HPLIP

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Expired

Bug description:
  Hello,
  This printer is detected in Ubuntu/CUPS, however it will not actually print 
anything succesfully. It prints about half the page and then has an error and 
stops printing altogther leaving the page in a half-inky mess. The printer 
works perfectly on Windows XP etc. 
  I ran hp-check and was unable to get this device detected properly by HPLIP 
after a considerable amount of trying; the device is plugged in via a 
USB-to-Parellel port: Bus 004 Device 002: ID 067b:2305 Prolific Technology, 
Inc. PL2305 Parallel Port

  Useful config files attached.  HP-Check Notes: dbus and libusb are
  installed but not detected. I also added my username to the lp and
  lpadmin group, which appears perfeclty in users & groups but keeps
  throwing an error on lp group for me regardless.

  I read here: http://unix.stackexchange.com/questions/62523/how-to-
  install-a-printer-that-is-connected-via-an-usb-to-parallel-port-
  adapter -- that it may be possible to do some hardcoding to make it
  work, but it didn't look like the correct way of doing it. So I am
  hoping someone will be able to properly debug this issue.

  Thanks in advanced! :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1235563/+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 1189271] Re: hplip ubuntu 13.04 no print

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  hplip ubuntu 13.04 no print

Status in hplip package in Ubuntu:
  Expired

Bug description:
  Hello,
  I've a problem with hplip on ubuntu 13.04.
  My printer HP Deskjet d4260 don't print but the test print page is OK.
  I installed hplip with "logithèque software center canonical", no print.
  After I uninstalled hplip-gui and I installed the latest version with command 
"sh hplip-3.13.5.run", no print.

  I try these commands:
  ls -la /var/lib/hp/
  hp-diagnose_plugin -g
  sudo hp-setup
  hp-check
  hp-doctor

  Everything is apparently OK and I've the message "print job has completed" 
but no page is printed.
  I uninstall with command "sudo make uninstall" and re-install, same problem.

  I try on another PC with ubuntu 12.04, it's OK.

  Have a solution please ?
  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1189271/+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 1261142] Re: package hplip-data 3.12.2-1ubuntu3.1 failed to install/upgrade: ErrorMessage: package hplip-data is not ready for configuration cannot configure (current status `h

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package hplip-data 3.12.2-1ubuntu3.1 failed to install/upgrade:
  ErrorMessage: package hplip-data is not ready for configuration
  cannot configure (current status `half-installed')

Status in hplip package in Ubuntu:
  Expired

Bug description:
  the program shout down

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: hplip-data 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52
  Uname: Linux 3.2.0-57-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sat Dec 14 19:39:09 2013
  ErrorMessage: ErrorMessage: package hplip-data is not ready for configuration 
 cannot configure (current status `half-installed')
  InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer Aspire 5315
  MarkForUpload: True
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-57-generic 
root=UUID=1EF6AF25F6AEFC61 loop=/hostname/disks/root.disk ro quiet splash 
vt.handoff=7
  SourcePackage: hplip
  Title: package hplip-data 3.12.2-1ubuntu3.1 failed to install/upgrade: 
ErrorMessage: package hplip-data is not ready for configuration  cannot 
configure (current status `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2007
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.17
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Acadia
  dmi.board.vendor: Acer
  dmi.board.version: V1.17
  dmi.chassis.asset.tag: Le david
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.17
  dmi.modalias: 
dmi:bvnAcer:bvrV1.17:bd09/14/2007:svnAcer:pnAspire5315:pvrV1.17:rvnAcer:rnAcadia:rvrV1.17:cvnAcer:ct1:cvrV1.17:
  dmi.product.name: Aspire 5315
  dmi.product.version: V1.17
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1261142/+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 1405382] Re: no color if using "print Quality" = "High resolution Photo"

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  no color if using "print Quality" = "High resolution Photo"

Status in hplip package in Ubuntu:
  Expired

Bug description:
  If I'm chosing the option "print Quality" = "High resolution Photo" in
  the print dialoge (accessed from pdf-Viewer), only black color is used
  for printing. The option "Normal Color" is working well.

  other options in the dialog, which I was using (and probably important
  for the bug):

  papertype = photo paper
  installed cartridges = black and TriColor
  printerprofile = (no profile selected)

  Systeminformations:

  Ubuntu 14.04.1 LTS
  Linux version 3.16.1-031601-generic
  Printer: hp deskjet F375

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1405382/+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 1297221] Re: /usr/share/hplip/config_usb_printer.py:ImportError:/usr/bin/hp-config_usb_printer@38:/usr/share/hplip/base/device.py@43:/usr/share/hplip/base/status.py@59

2018-11-03 Thread Launchpad Bug Tracker
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  /usr/share/hplip/config_usb_printer.py:ImportError:/usr/bin/hp-
  
config_usb_printer@38:/usr/share/hplip/base/device.py@43:/usr/share/hplip/base/status.py@59

Status in hplip package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding hplip.  This problem was most recently seen with version
  3.13.9-1ubuntu0.1, the problem page at
  https://errors.ubuntu.com/problem/dae59d0805bf3202f10977ead46c964a07bb53be
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1297221/+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 1411290] Re: Firefox 35 does not restore previous session / tabs

2018-11-03 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Firefox 35 does not restore previous session / tabs

Status in firefox package in Ubuntu:
  Expired

Bug description:
  On trusty I updated firefox to 35.0+build3-0ubuntu0.14.04.2

  After the update firefox no longer restored my previous session, it
  starts with a single blank tab. Also on the "New tab" window all tiles
  are empty. I gave a look to the sessionstore.js file and firefox isn't
  touching when closing.

  I tested with two different profiles and the same happened for both.

  Reverting to 34.0+build2-0ubuntu0.14.04.1 got session store working
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1411290/+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 1772578] Re: [Nvidia HDA] audio crackling

2018-11-03 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [Nvidia HDA] audio crackling

Status in gnome-shell package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Hello,

  on Ubuntu this bug regularly appearing: audio suddenly crackling for all 
softwares.
  If I restart pulseaudio, it changes nothing.
  But if I restart gnome-shell ("alt+F2", type "r"), the audio no more 
crackling.
  I had this bug for Ubuntu 17.10 and perhaps 17.04 too.

  Thank you for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   romain 3648 F...m pulseaudio
   /dev/snd/controlC0:  romain 3648 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May 22 07:56:34 2018
  InstallationDate: Installed on 2012-07-07 (2144 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2018-04-05 (47 days ago)
  dmi.bios.date: 09/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G45 (MS-7752)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd09/29/2013:svnMSI:pnMS-7752:pvr1.0:rvnMSI:rnZ77A-G45(MS-7752):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7752
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772578/+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 1772578] Re: [Nvidia HDA] audio crackling

2018-11-03 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [Nvidia HDA] audio crackling

Status in gnome-shell package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Hello,

  on Ubuntu this bug regularly appearing: audio suddenly crackling for all 
softwares.
  If I restart pulseaudio, it changes nothing.
  But if I restart gnome-shell ("alt+F2", type "r"), the audio no more 
crackling.
  I had this bug for Ubuntu 17.10 and perhaps 17.04 too.

  Thank you for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   romain 3648 F...m pulseaudio
   /dev/snd/controlC0:  romain 3648 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May 22 07:56:34 2018
  InstallationDate: Installed on 2012-07-07 (2144 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2018-04-05 (47 days ago)
  dmi.bios.date: 09/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G45 (MS-7752)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd09/29/2013:svnMSI:pnMS-7752:pvr1.0:rvnMSI:rnZ77A-G45(MS-7752):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7752
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772578/+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 1790596] Re: [Wishlist] add workspaces switching grid icon by default

2018-11-03 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [Wishlist] add workspaces switching grid icon by default

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Ubuntu-desktop 18.04.1 up to date to latest @ 4/9/2018

  Can we have the workspaces switcher icon grid back like on unity by default
  for faster workspaces switching?

  the users choice to enable or disable it, or add to dock or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  4 10:31:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-15 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1790596/+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 1775212] Re: Windows not painted completely since 18.04

2018-11-03 Thread Launchpad Bug Tracker
[Expired for xfwm4 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Windows not painted completely since 18.04

Status in xfwm4 package in Ubuntu:
  Expired
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Expired

Bug description:
  Since upgrading to Xubuntu 18.04, the graphics on my desktop are
  broken. It seems to affect all windows and menus, which are painted
  incompletely, or with the wrong colours. It seems to get progressively
  worse, to the point of making programs unusable because entire
  sections of the user interface are missing, so this should have high
  priority IMHO. I will attach a few screenshots as examples.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xfwm4 4.12.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  5 17:29:02 2018
  InstallationDate: Installed on 2017-03-23 (439 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  SourcePackage: xfwm4
  UpgradeStatus: Upgraded to bionic on 2018-05-14 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1775212/+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 1775212] Re: Windows not painted completely since 18.04

2018-11-03 Thread Launchpad Bug Tracker
[Expired for xserver-xorg-video-nouveau (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Windows not painted completely since 18.04

Status in xfwm4 package in Ubuntu:
  Expired
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Expired

Bug description:
  Since upgrading to Xubuntu 18.04, the graphics on my desktop are
  broken. It seems to affect all windows and menus, which are painted
  incompletely, or with the wrong colours. It seems to get progressively
  worse, to the point of making programs unusable because entire
  sections of the user interface are missing, so this should have high
  priority IMHO. I will attach a few screenshots as examples.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xfwm4 4.12.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  5 17:29:02 2018
  InstallationDate: Installed on 2017-03-23 (439 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  SourcePackage: xfwm4
  UpgradeStatus: Upgraded to bionic on 2018-05-14 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1775212/+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 1789105] Re: freezes ubuntu on fullscreen.

2018-11-03 Thread Launchpad Bug Tracker
[Expired for xserver-xorg-video-nouveau (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  freezes ubuntu on fullscreen.

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

Bug description:
  When playing a video on fullscreen ubuntu freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vlc 3.0.3-1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 26 22:31:46 2018
  InstallationDate: Installed on 2018-08-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1789105/+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 1797147] Re: Backport PRIME switching fixes to Ubuntu 18.04

2018-11-03 Thread Josh Holland
I tested with LightDM, ubuntu-drivers-common 1:0.5.2.2, and nvidia-prime
0.8.8.2, doing various combinations of `prime-select intel` and `prime-
select nvidia`; everything seems to work as described in the original
description.

Thank you Alberto for your work on this!

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

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

Title:
  Backport PRIME switching fixes to Ubuntu 18.04

Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  A recent update (LP: #1778011) in 18.04 has restored the PRIME switching 
mechanism in Gdm 3 only, while still leaving out support for other login 
managers (such as Lightdm, and SDDM).

  In addition to this, we should restore the default pci power control
  profile for the dGPU when re-enabling performance mode, as we do in
  Ubuntu 18.10.

  [Test Case]
  1) Make sure that you are using a login manager such as Lightdm or SDDM.

  2) Enable the bionic-proposed repository, and install the new "ubuntu-
  drivers-common", and the new nvidia-prime.

  3) Make sure the nvidia packages are installed and working, and enable power 
saving mode:
  sudo prime-select intel

  4) Log out, log back in, and check that the nvidia kernel module is not 
loaded:
  lsmod | grep nvidia

  5) Select performance mode:
  sudo prime-select nvidia

  6) Log out, and log back in

  7) Check if the nvidia driver loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as switching already fails in 18.04, since X is started before udev adds 
back the dGPU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1797147/+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 1801494] Re: dock missing

2018-11-03 Thread Philip Rego
I read through that thread. Not sure if there is much more I can add
now. When I restart the computer it comes back but this has happened a
few times before. Someone mentioned thunderbird i was using that. A
screen dimming app. Ill post again if i notice anything.

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

Title:
  dock missing

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 18.04.1 LTS
  Release:  18.04
  2) $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 0.9.1ubuntu18.04.1
Candidate: 0.9.1ubuntu18.04.1
Version table:
   *** 0.9.1ubuntu18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.9.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  4) dock is there
  5) dock is not there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+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 1724070] Re: Dock appears in GNOME lock screen when monitor powers off (and screen lock is disabled)

2018-11-03 Thread Ads20000
Francois I get this issue on Ubuntu 18.10 and the output of `journalctl
-f` when experiencing the bug is here:
https://paste.ubuntu.com/p/Y3MxnXzqXq/ , though this is now effectively
a duplicate of bug 1769383 (which is more active).

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

Title:
  Dock appears in GNOME lock screen when monitor powers off (and screen
  lock is disabled)

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Expired

Bug description:
  BEHAVIOR
  There's no place to upload a photo, but I can provide one upon request. I 
turned screen lock off in the Privacy section of System Settings. Now, when the 
monitor powers off, and I wiggle the mouse or press a keyboard key to awaken 
Ubuntu 17.10, it shows the lock screen, but the Ubuntu dock was present on the 
left side. (Unsure if this happened when my monitor powered off when Activities 
Overview was active or not).

  EXPECTED BEHAVIOR
  For the Ubuntu dock to not be showing in the lock screen at all.

  BUG DISCOVERED USING
  Ubuntu 17.10 beta 2
  GNOME 3.26.1 (ubuntu-modified shell)
  Nvidia 384.90 proprietary driver (single monitor)
  X.org 1.19.5
  Linux kernel 4.13.0-16-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1724070/+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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen

2018-11-03 Thread Ads20000
Sebastien, here's the journal output (`journalctl -f` that's produced
when I lock my screen on Ubuntu 18.10 and I reproduce this bug):
https://paste.ubuntu.com/p/Y3MxnXzqXq/

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

Title:
  Ubuntu dock/launcher is shown on the lock screen

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  After an update from ubuntu 16.04 to 18.04 the dock is aviable on the 
lockscreen after user login.
  I did not configure this knowingly. Also i can start every application which 
is available on the dock.
  Settings, virtual box, visualstudio code and so on.

  After the update to 18.04 i just configure the screen frequency to
  144Hz and the night mode on. And attach the dock on bottom.

  I later undid these customizations back to configuration before, but
  the dock is stil aviable on lockscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:30:16 2018
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell-extension-ubuntu-dock 0.9.1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+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 1730211] Re: Unable to type capital letters using onscreen keyboard

2018-11-03 Thread Mathew Hodson
** Tags added: regression-release

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

Title:
  Unable to type capital letters using onscreen keyboard

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Unable to type capital letters using onscreen keyboard:

  [Test Case]
  1. Launch a program where you can type text (gedit for example).
  2. Activate on screen keyboard (by touching the screen, foe example).
  3. Notice all the keys on the on screen keyboard display lowercase letters.

  4. Begin typing.  Lowercase characters are typed into the text area.

  5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the 
on screen keyboard.
  6. Notice all the keys on the on screen keyboard now display capital letters.
  7. Begin typing.
  8. A lowercase character will be typed into the text area.

  This is not expected behavior.
  Instead, a capital letter should have been typed.

  (All the keys on the on screen keyboard revert to lower case. This is
  expected, since the on screen shift key would need to be pressed again
  in order to attempt to type another capital character).

  [Regression Potential]
  Please make sure that osk correctly revert to lower case. Also make sure
  the physical keyboard correctly works after using the osk.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: caribou 0.4.21-2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 10:57:04 2017
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: caribou
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1730211/+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 1730211] Re: Unable to type capital letters using onscreen keyboard

2018-11-03 Thread Mathew Hodson
** Changed in: mutter (Ubuntu Bionic)
   Importance: Undecided => Low

** Tags added: a11y

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

Title:
  Unable to type capital letters using onscreen keyboard

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Unable to type capital letters using onscreen keyboard:

  [Test Case]
  1. Launch a program where you can type text (gedit for example).
  2. Activate on screen keyboard (by touching the screen, foe example).
  3. Notice all the keys on the on screen keyboard display lowercase letters.

  4. Begin typing.  Lowercase characters are typed into the text area.

  5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the 
on screen keyboard.
  6. Notice all the keys on the on screen keyboard now display capital letters.
  7. Begin typing.
  8. A lowercase character will be typed into the text area.

  This is not expected behavior.
  Instead, a capital letter should have been typed.

  (All the keys on the on screen keyboard revert to lower case. This is
  expected, since the on screen shift key would need to be pressed again
  in order to attempt to type another capital character).

  [Regression Potential]
  Please make sure that osk correctly revert to lower case. Also make sure
  the physical keyboard correctly works after using the osk.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: caribou 0.4.21-2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 10:57:04 2017
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: caribou
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1730211/+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 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

2018-11-03 Thread Mathew Hodson
** Tags added: regression-release

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1792745/+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 1781597] Re: [SRU] WoWLAN settings are not supported

2018-11-03 Thread Mathew Hodson
** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [SRU] WoWLAN settings are not supported

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  WoWLAN lets us wake up the system by sending wake packages over the
  wifi connection. This is something requested by some OEM projects, for
  bionic server images.

  NM 1.12 supports configuring this feature, so this can be achieved by
  backporting that support to 1.10 (bionic version). These are the MPs
  for cosmic and bionic:

  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468
  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465

  [Test Case]

  First, the wifi card must support WoWLAN. This can be checked by
  running

  $ iw phy

  and searching for "WoWLAN support:" in the output. If it is supported,
  with the patch applied a connection configured with wowlan can be
  created with:

  $ sudo nmcli d wifi connect  password 
  $ sudo nmcli c modify  802-11-wireless.wake-on-wlan 8
  $ sudo nmcli c down 
  $ sudo nmcli c up 

  We can check with 'iw' that WoWLAN is active for the connection:

  $ iw phy phy0 wowlan show
  WoWLAN is enabled:
   * wake up on magic packet

  In this case we have configured the connection to wake up the system
  when a 'magic' packet is received. We can then suspend the system with

  $ sudo systemctl suspend

  And we should be able to wake the system from another device with the
  command

  $ sudo etherwake -i  

  [Regression Potential]

  Although the patch is not especially small, it is a backport of
  changes that have been merged upstream, with very little modifications
  to make it compile in 1.10. It is also a rather isolated feature that
  should not conflict with existing ones. The feature will be activated
  only if configured from the command line, so the risk of regressions
  should be small. Note also that the patch will be removed as soon as
  Ubuntu moves to NM 1.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+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 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

2018-11-03 Thread Mathew Hodson
** Changed in: pulseaudio (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  The patch will check all ports under each profile, if a profile only
  contains unavailable ports, this profile will be set to unavailable as
  well. Without this patch, all profiles are always available, then if a
  profile includes a unusable hdmi-output, and pulseaudio select this
  profile to be active (since its priority is the highest), the kernel
  audio driver will crash.

  I think this patch will not introduce regression:
  1) It is a correct logic to set a profile to be unavailable if it only 
contains unavailable ports.
  2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
  3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop 
and 1 dell desktop, all worked well as before
  4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

2018-11-03 Thread Mathew Hodson
** Changed in: pulseaudio (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do
  not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even
  there is no internal speaker and nothing plugged in the audio jack,
  the profile is still set available, then the active profile is analog-
  stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to
  unavailable, and the active profile is off, after users plug sth in
  the audio jack, the active profile will not switch automatically, need
  users to switch manually, this change is unfriendly to users.

  [Test Case]

  On the machines without internal speaker, open sound-setting and check
  if there is some output devices in the UI, and play sound from the UI.
  Under 1:8.0-0ubuntu3.9 there is no output device, and can't play
  sound; under 1:8.0-0ubuntu3.8 there is output device, and can play
  sound.

  [Regression Potential]

  This is a revert, after reverting, the content of pulseaudio is
  exactly same as 1:8.0-0ubuntu3.8

  [Other Info]

  none

  
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not 
showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 326582] Re: sort order of files listings in nautilus is not alphabetical

2018-11-03 Thread Lucio Crusca
Talk about zombies! This report is so old I couldn't even realize I was
the one who created it in the first place, until I read that information
above the comments.

I've now took the time to read all the comments again.

@Chris Billington: I really don't know what kind of drugs I was on when
I wrote my comments here, but now I wish I never wrote most of that
shit. Sebastien was absolutely right, this is not the place to discuss
such feature requests. At that time I used to use Ubuntu, and I recall I
was quite fed up with Gnome user experience. I can only guess I used the
wrong tool to let off steam. Ubuntu provided me with the right tool
shortly after when it switched to Unity, which led me to switch back to
Debian...

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

Title:
  sort order of files listings in nautilus is not alphabetical

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  I'd like to have an option to see the files and directories in
  alphabetical order in nautilus. For example, if I have the following
  directories:

  20050501
  200607
  200901

  the 'ls' command lists them in alphabetical order, just like above,
  but nautilus shows them in numerical order:

  200607
  200901
  20050501

  which is not always the desired behavior (in this example it is not,
  obviously).

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  Package: nautilus 1:2.24.1-0ubuntu2
  ProcEnviron:
   SHELL=/bin/bash
   PATH=/home/User 
Name/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=it_IT.UTF-8
  SourcePackage: nautilus
  Uname: Linux 2.6.28.1-thinkpad i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/326582/+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 1801540] Re: Microphone distorted sound on ALC892

2018-11-03 Thread Luca Mastromatteo
Uhm yes I know that, but apport-collect is just not working as I already
said...

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

Title:
  Microphone distorted sound on ALC892

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

2018-11-03 Thread Mathew Hodson
** No longer affects: snapd (Ubuntu)

** No longer affects: snapd (Ubuntu Xenial)

** Project changed: snappy => ubuntu-translations

** No longer affects: ubuntu-translations

** Project changed: qt => ubuntu-translations

** No longer affects: ubuntu-translations

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in sni-qt package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Fix Released
Status in libappindicator source package in Xenial:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Confirmed
Status in sni-qt source package in Xenial:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator

  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.

  When snaps are generated in non updated systems, the icon will be
  still missing.

  [Regression potential]

  If $SNAP is defined for an app not running in snap confinement the
  icons couldn't be properly visible

  


  SRU bug for appmenu-qt5:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run qt5-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

  


  SRU bug for sni-qt:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as 
snapcraft.yaml
in any folder you want
  * Run:
- snapcraft prime
- sudo snap try prime
- snap run qt4-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1600136/+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 1801540] Re: Microphone distorted sound on ALC892

2018-11-03 Thread Cristian Aravena Romero
https://help.ubuntu.com/community/ReportingBugs
--
Cristian Aravena Romero (caravena)

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

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

Title:
  Microphone distorted sound on ALC892

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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


Re: [Desktop-packages] [Bug 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04

2018-11-03 Thread Thomas Schweikle
*** This bug is a duplicate of bug 210472 ***
https://bugs.launchpad.net/bugs/210472

Yes, that is it!

systemctl stop timidity.service
systemctl disable timidity.service

solves the problem.
On Sat, Nov 3, 2018 at 9:30 PM Cristian Aravena Romero
 wrote:
>
> *** This bug is a duplicate of bug 210472 ***
> https://bugs.launchpad.net/bugs/210472
>
> ** This bug has been marked a duplicate of bug 210472
>Timidity daemon doesn't play nice with pulse audio
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1801538
>
> Title:
>   no sound after upgrading to ubuntu 18.10 from 18.04
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+subscriptions


-- 
Thomas

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

Title:
  no sound after upgrading to ubuntu 18.10 from 18.04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 18.10 does not recognize sound devices. After upgrading there
  is only a dummy device known. All others are gone. In tune there is no
  sound output to nowhere.

  It does not mater it headphones are plugged or not while booting. It
  does not matter if any usb-sound device is plugged or not. The only
  device show for output in mixer is "Dummy device".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   8931 F timidity
   /dev/snd/pcmC0D0p:   timidity   8931 F...m timidity
   /dev/snd/seq:timidity   8931 F timidity
   /dev/snd/timer:  timidity   8931 f timidity
  Date: Sat Nov  3 17:25:55 2018
  InstallationDate: Installed on 2011-10-19 (2571 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)
  dmi.bios.date: 10/21/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P643-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: TravelMate P643-M
  dmi.product.name: TravelMate P643-M
  dmi.product.sku: TravelMate P643-M_0681_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1306849] Re: Printing error

2018-11-03 Thread Bill Duetschler
Still occurring on Bionic in November 2018.

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

Title:
  Printing error

Status in foomatic-db package in Ubuntu:
  Confirmed

Bug description:
  I get the message ERROR NAME; stackunderflow COMMAND; pop OPERAND
  STACK; when I try to print from Firefox or anything that has a picture
  as part of the file.  I am running saucy on an AMD64 system. so far I
  have tried deleting the printer and setting it up again. No change.
  Ubuntu 13.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1306849/+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 1683445] Re: E6430 brightness control not working

2018-11-03 Thread Mathew Hodson
** Changed in: gnome-settings-daemon (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: unity-settings-daemon (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: unity-settings-daemon (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  E6430 brightness control not working

Status in GNOME Settings Daemon:
  Fix Released
Status in Nouveau Xorg driver:
  Won't Fix
Status in OEM Priority Project:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in gnome-settings-daemon source package in Zesty:
  Fix Released
Status in unity-settings-daemon source package in Zesty:
  Won't Fix
Status in unity-settings-daemon source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.

  Test Case
  -
  From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
  Restart.
  Does the brightness control now work correctly?

  Regression Potential
  
  This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.

  Original Bug Report
  ---
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

2018-11-03 Thread Mathew Hodson
** Changed in: xdg-utils (Ubuntu Bionic)
   Importance: Undecided => High

** No longer affects: perl (Ubuntu)

** No longer affects: perl (Ubuntu Bionic)

** No longer affects: perl (Ubuntu Cosmic)

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

Title:
  perl crashed with SIGABRT in _dbus_abort()

Status in xdg-utils package in Ubuntu:
  Fix Released
Status in xdg-utils source package in Bionic:
  Fix Committed
Status in xdg-utils source package in Cosmic:
  Fix Released
Status in xdg-utils package in Debian:
  Unknown

Bug description:
  [ Description ]

  When xdg-screensaver suspend  refers to a window with invalid
  UTF-8 in its title, it will spawn a perl process that crashes with an
  assertion:

    dbus[19455]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2754.
    This is normally a bug in some application using the D-Bus library.

  [ Fix ]

  Use decode() from the Encode module to replace invalid character
  sequences with U+FFFD, the replacement symbol. This is not a new
  dependency as Encode has been a perl core module since 5.8.

  [ QA ]

  I don't know how to get a window with such a title, so we can do two
  things.

  1)

  1. $ sudo -e $(which xdg-screensaver) # hack the script
  2. Find the line "# Inhibit idle detection (flags = 8) with window name and 
ID."
  3. Find the } on its own above that.  Insert a new line afterwards and set 
the window name to be the same as the one in this bug, by pasting the code
    $window_name = "\253\062\065 Meter fehlten bis zur Katastrophe\273 - News 
Panorama: Vermischtes - tagesanzeiger.ch - Mozilla Firefox";
  4. Save and exit
  5. $ xwininfo
  6. click some window, and copy the "Window id", which will be 0x
  7. $ xdg-screensaver suspend 

  In the bad case (before this bug is fixed) it should crash, and in the
  good case it should work.

  8. Undo what you just did by running $ xdg-screensaver resume 

  2)

  Observe that the error bucket

  https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52

  has a reduction in report rate with the new versions.

  [ Regression potential ]

  If the code is bad then the window name passed to Inhibit() could be
  wrong. That shouldn't matter too much.

  If it is really bad then the program might crash for everybody and
  we'll see an increase in errors.

  [ Original description ]

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

  crashed after launching the software updater

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1743216/+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 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04

2018-11-03 Thread Cristian Aravena Romero
*** This bug is a duplicate of bug 210472 ***
https://bugs.launchpad.net/bugs/210472

** This bug has been marked a duplicate of bug 210472
   Timidity daemon doesn't play nice with pulse audio

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

Title:
  no sound after upgrading to ubuntu 18.10 from 18.04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 18.10 does not recognize sound devices. After upgrading there
  is only a dummy device known. All others are gone. In tune there is no
  sound output to nowhere.

  It does not mater it headphones are plugged or not while booting. It
  does not matter if any usb-sound device is plugged or not. The only
  device show for output in mixer is "Dummy device".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   8931 F timidity
   /dev/snd/pcmC0D0p:   timidity   8931 F...m timidity
   /dev/snd/seq:timidity   8931 F timidity
   /dev/snd/timer:  timidity   8931 f timidity
  Date: Sat Nov  3 17:25:55 2018
  InstallationDate: Installed on 2011-10-19 (2571 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)
  dmi.bios.date: 10/21/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P643-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: TravelMate P643-M
  dmi.product.name: TravelMate P643-M
  dmi.product.sku: TravelMate P643-M_0681_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1801540] Re: Microphone distorted sound on ALC892

2018-11-03 Thread Luca Mastromatteo
I tried running it, I don't know honestly if that worked because when I
clicked on that link a browser page just appeared showing nothing
relevant

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

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

Title:
  Microphone distorted sound on ALC892

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+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 326582] Re: sort order of files listings in nautilus is not alphabetical

2018-11-03 Thread Chris Billington
On major problem with this search order is that it conflicts with the
order of files in Nautilius in the non-search view.

In my home folder I have 'thesis' and 'tmp' subfolders, and they are
shown in that order. I type 't' expecting 'thesis' to be the first
result so that I can hit enter and navigate to the 'thesis' folder.
However 'tmp' comes up first because Nautilus's search view is sorting
by length before aphabetically, or something (not sure what the exact
algorithm is). This is one of the behaviours preventing the new search
interface from being used for keyboard navigation as a replacement for
the removed typeahead functionality.

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

Title:
  sort order of files listings in nautilus is not alphabetical

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  I'd like to have an option to see the files and directories in
  alphabetical order in nautilus. For example, if I have the following
  directories:

  20050501
  200607
  200901

  the 'ls' command lists them in alphabetical order, just like above,
  but nautilus shows them in numerical order:

  200607
  200901
  20050501

  which is not always the desired behavior (in this example it is not,
  obviously).

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  Package: nautilus 1:2.24.1-0ubuntu2
  ProcEnviron:
   SHELL=/bin/bash
   PATH=/home/User 
Name/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=it_IT.UTF-8
  SourcePackage: nautilus
  Uname: Linux 2.6.28.1-thinkpad i686

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

2018-11-03 Thread zhanghongce
One more vote for a type-ahead navigation rather than a search. The
search is stupid.

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

Title:
  restore type-ahead find

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

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

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

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

  Would Ubuntu consider patching type-ahead find back in?

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

-- 
Mailing list: https://launchpad.net/~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 1801540] Re: Microphone distorted sound on ALC892

2018-11-03 Thread Cristian Aravena Romero
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1801540

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

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

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

Title:
  Microphone distorted sound on ALC892

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+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 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04

2018-11-03 Thread Libor Šedivý
I found solution with command: "sudo apt purge timidity-daemon", and
then reboot. After this, sound works like sharm.

Source: https://askubuntu.com/questions/1085174/no-sound-after-upgrade-
to-18-10-only-a-dummy-device-is-shown/1085992#1085992

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

Title:
  no sound after upgrading to ubuntu 18.10 from 18.04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 18.10 does not recognize sound devices. After upgrading there
  is only a dummy device known. All others are gone. In tune there is no
  sound output to nowhere.

  It does not mater it headphones are plugged or not while booting. It
  does not matter if any usb-sound device is plugged or not. The only
  device show for output in mixer is "Dummy device".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   8931 F timidity
   /dev/snd/pcmC0D0p:   timidity   8931 F...m timidity
   /dev/snd/seq:timidity   8931 F timidity
   /dev/snd/timer:  timidity   8931 f timidity
  Date: Sat Nov  3 17:25:55 2018
  InstallationDate: Installed on 2011-10-19 (2571 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)
  dmi.bios.date: 10/21/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P643-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: TravelMate P643-M
  dmi.product.name: TravelMate P643-M
  dmi.product.sku: TravelMate P643-M_0681_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1801540] [NEW] Microphone distorted sound on ALC892

2018-11-03 Thread Luca Mastromatteo
Public bug reported:

Not sure if I'll report this upstream but there is definitely an issue
with microphone recording on my desktop, this is not happening on my
laptop which has a different codec.

Already tried all workarounds possible, no luck. Only with my desktop
with this particular motherboard. No issues in Windows, the sound
recorded in there is distorted and has some static and robotic tone on
high-pitch.

alsa-info on the attachments

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

** Attachment added: "alsa-info"
   https://bugs.launchpad.net/bugs/1801540/+attachment/5208845/+files/alsa-info

** Package changed: alsa-lib (Ubuntu) => alsa-driver (Ubuntu)

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

Title:
  Microphone distorted sound on ALC892

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1801540/+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 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04

2018-11-03 Thread Libor Šedivý
I have this problem too, how can I fix it? I have Acer Aspire V Nitro
II.

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

Title:
  no sound after upgrading to ubuntu 18.10 from 18.04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 18.10 does not recognize sound devices. After upgrading there
  is only a dummy device known. All others are gone. In tune there is no
  sound output to nowhere.

  It does not mater it headphones are plugged or not while booting. It
  does not matter if any usb-sound device is plugged or not. The only
  device show for output in mixer is "Dummy device".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   8931 F timidity
   /dev/snd/pcmC0D0p:   timidity   8931 F...m timidity
   /dev/snd/seq:timidity   8931 F timidity
   /dev/snd/timer:  timidity   8931 f timidity
  Date: Sat Nov  3 17:25:55 2018
  InstallationDate: Installed on 2011-10-19 (2571 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)
  dmi.bios.date: 10/21/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P643-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: TravelMate P643-M
  dmi.product.name: TravelMate P643-M
  dmi.product.sku: TravelMate P643-M_0681_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1801540] [NEW] Microphone distorted sound on ALC892

2018-11-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Not sure if I'll report this upstream but there is definitely an issue
with microphone recording on my desktop, this is not happening on my
laptop which has a different codec.

Already tried all workarounds possible, no luck. Only with my desktop
with this particular motherboard. No issues in Windows, the sound
recorded in there is distorted and has some static and robotic tone on
high-pitch.

alsa-info on the attachments

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

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

-- 
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 1801538] [NEW] no sound after upgrading to ubuntu 18.10 from 18.04

2018-11-03 Thread Thomas Schweikle
Public bug reported:

Ubuntu 18.10 does not recognize sound devices. After upgrading there is
only a dummy device known. All others are gone. In tune there is no
sound output to nowhere.

It does not mater it headphones are plugged or not while booting. It
does not matter if any usb-sound device is plugged or not. The only
device show for output in mixer is "Dummy device".

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: pulseaudio 1:12.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  timidity   8931 F timidity
 /dev/snd/pcmC0D0p:   timidity   8931 F...m timidity
 /dev/snd/seq:timidity   8931 F timidity
 /dev/snd/timer:  timidity   8931 f timidity
Date: Sat Nov  3 17:25:55 2018
InstallationDate: Installed on 2011-10-19 (2571 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)
dmi.bios.date: 10/21/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.15
dmi.board.asset.tag: No Asset Tag
dmi.board.name: TravelMate P643-M
dmi.board.vendor: Acer
dmi.board.version: V2.15
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.15
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:
dmi.product.family: TravelMate P643-M
dmi.product.name: TravelMate P643-M
dmi.product.sku: TravelMate P643-M_0681_2.15
dmi.product.version: V2.15
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug cosmic

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

Title:
  no sound after upgrading to ubuntu 18.10 from 18.04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 18.10 does not recognize sound devices. After upgrading there
  is only a dummy device known. All others are gone. In tune there is no
  sound output to nowhere.

  It does not mater it headphones are plugged or not while booting. It
  does not matter if any usb-sound device is plugged or not. The only
  device show for output in mixer is "Dummy device".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   8931 F timidity
   /dev/snd/pcmC0D0p:   timidity   8931 F...m timidity
   /dev/snd/seq:timidity   8931 F timidity
   /dev/snd/timer:  timidity   8931 f timidity
  Date: Sat Nov  3 17:25:55 2018
  InstallationDate: Installed on 2011-10-19 (2571 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)
  dmi.bios.date: 10/21/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P643-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: TravelMate P643-M
  dmi.product.name: TravelMate P643-M
  dmi.product.sku: TravelMate P643-M_0681_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1801533] Re: lightdm does not start

2018-11-03 Thread Thomas Schweikle
This bug exists since 16.10 – we are at 18.10 now it is now two years
with this monitor killing bug.

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

Title:
  lightdm does not start

Status in lightdm package in Ubuntu:
  New

Bug description:
  lightdm tries to initialize screen output, fails, tries again, fails
  until the backlight electronics break, killing the monitor.

  lightdm fails initializing screen. This turns on backlight,
  initializes graphics, then lightdm stops with an error message.
  systemd starts lightdm again. Lightdm tries to initialize graphics.
  This turns on backlight. Lightdm fails, exausts an error message,
  backlight turns off again. systemd starts lightdm, lightdm tries to
  initialize graphics. Turns on backlight. Exausts an error message.
  Backlight is turned off again. ...

  After doing so more than twice a second backlight breaks. Electronics
  broke down.

  Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors
  by lightdm not able to initialize screens and breaking, then beeing
  restarted by systemd.

  Since this can kill hardware it is a no go! It is a bad bad bad bad
  bad bad bad bad bad bad bad bad bad bad bug!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Sat Nov  3 17:03:19 2018
  InstallationDate: Installed on 2011-10-19 (2571 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1801533] Re: lightdm does not start

2018-11-03 Thread Thomas Schweikle
Same problem: it does not matter if upgraded from 18.04 or installed new
with 18.10. lightdm might not allways be capable initializing graphics
leeding to some loop together with systemd turning on backlight, turning
it off again, then restarting.

Backlight is turned on, then off about twice a second. After some time
backlight electronics break down, killing the monitor.

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

Title:
  lightdm does not start

Status in lightdm package in Ubuntu:
  New

Bug description:
  lightdm tries to initialize screen output, fails, tries again, fails
  until the backlight electronics break, killing the monitor.

  lightdm fails initializing screen. This turns on backlight,
  initializes graphics, then lightdm stops with an error message.
  systemd starts lightdm again. Lightdm tries to initialize graphics.
  This turns on backlight. Lightdm fails, exausts an error message,
  backlight turns off again. systemd starts lightdm, lightdm tries to
  initialize graphics. Turns on backlight. Exausts an error message.
  Backlight is turned off again. ...

  After doing so more than twice a second backlight breaks. Electronics
  broke down.

  Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors
  by lightdm not able to initialize screens and breaking, then beeing
  restarted by systemd.

  Since this can kill hardware it is a no go! It is a bad bad bad bad
  bad bad bad bad bad bad bad bad bad bad bug!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Sat Nov  3 17:03:19 2018
  InstallationDate: Installed on 2011-10-19 (2571 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1801533] [NEW] lightdm does not start

2018-11-03 Thread Thomas Schweikle
Public bug reported:

lightdm tries to initialize screen output, fails, tries again, fails
until the backlight electronics break, killing the monitor.

lightdm fails initializing screen. This turns on backlight, initializes
graphics, then lightdm stops with an error message. systemd starts
lightdm again. Lightdm tries to initialize graphics. This turns on
backlight. Lightdm fails, exausts an error message, backlight turns off
again. systemd starts lightdm, lightdm tries to initialize graphics.
Turns on backlight. Exausts an error message. Backlight is turned off
again. ...

After doing so more than twice a second backlight breaks. Electronics
broke down.

Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors by
lightdm not able to initialize screens and breaking, then beeing
restarted by systemd.

Since this can kill hardware it is a no go! It is a bad bad bad bad bad
bad bad bad bad bad bad bad bad bad bug!

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: lightdm 1.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Sat Nov  3 17:03:19 2018
InstallationDate: Installed on 2011-10-19 (2571 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: lightdm
UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  lightdm does not start

Status in lightdm package in Ubuntu:
  New

Bug description:
  lightdm tries to initialize screen output, fails, tries again, fails
  until the backlight electronics break, killing the monitor.

  lightdm fails initializing screen. This turns on backlight,
  initializes graphics, then lightdm stops with an error message.
  systemd starts lightdm again. Lightdm tries to initialize graphics.
  This turns on backlight. Lightdm fails, exausts an error message,
  backlight turns off again. systemd starts lightdm, lightdm tries to
  initialize graphics. Turns on backlight. Exausts an error message.
  Backlight is turned off again. ...

  After doing so more than twice a second backlight breaks. Electronics
  broke down.

  Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors
  by lightdm not able to initialize screens and breaking, then beeing
  restarted by systemd.

  Since this can kill hardware it is a no go! It is a bad bad bad bad
  bad bad bad bad bad bad bad bad bad bad bug!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Sat Nov  3 17:03:19 2018
  InstallationDate: Installed on 2011-10-19 (2571 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1801533] Re: lightdm does not start

2018-11-03 Thread Thomas Schweikle
This schouldn't happen. lightdm should only be started about 10 times,
then disabled.

BTW: no errors are readable on screen. Logs only show lightdm restarted
by systemd after terminatating. Errors can be seen by disabling lightdm,
then starting it from commandline. But this isn't helpful either: "Could
not initialize screen. Terminating."

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

Title:
  lightdm does not start

Status in lightdm package in Ubuntu:
  New

Bug description:
  lightdm tries to initialize screen output, fails, tries again, fails
  until the backlight electronics break, killing the monitor.

  lightdm fails initializing screen. This turns on backlight,
  initializes graphics, then lightdm stops with an error message.
  systemd starts lightdm again. Lightdm tries to initialize graphics.
  This turns on backlight. Lightdm fails, exausts an error message,
  backlight turns off again. systemd starts lightdm, lightdm tries to
  initialize graphics. Turns on backlight. Exausts an error message.
  Backlight is turned off again. ...

  After doing so more than twice a second backlight breaks. Electronics
  broke down.

  Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors
  by lightdm not able to initialize screens and breaking, then beeing
  restarted by systemd.

  Since this can kill hardware it is a no go! It is a bad bad bad bad
  bad bad bad bad bad bad bad bad bad bad bug!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Sat Nov  3 17:03:19 2018
  InstallationDate: Installed on 2011-10-19 (2571 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1801532] Re: pulseaudio crashing when publishing sound devices to zeroconf

2018-11-03 Thread Owen Williams
checking for !s->userdata seems to fix it

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

Title:
  pulseaudio crashing when publishing sound devices to zeroconf

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04

  pulseaudio crashes after 5-10 if advertising sound devices is enabled:

  logs leading up to the crash:

  [New Thread 0x7fffe7fff700 (LWP 9068)]
  D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 /  46% / 
-20.00 dB,   front-right: 30419 /  46% / -20.00 dB
  D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Thread starting up
  I: [alsa-sink-ALC887-VD Analog] core-util.c: Failed to acquire real-time 
scheduling: Permission denied
  I: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Starting playback.
  D: [alsa-sink-ALC887-VD Analog] ratelimit.c: 27 events suppressed
  D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the 
initial iterations by half.
  I: [pulseaudio] core.c: default_source: 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor -> 
alsa_output.pci-_00_1f.3.analog-stereo.monitor
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] module-device-restore.c: Could not set format on sink 
alsa_output.pci-_00_1f.3.analog-stereo
  D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1f.3.analog-stereo becomes idle, timeout in 5 seconds.
  I: [pulseaudio] core.c: default_sink: 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1 -> 
alsa_output.pci-_00_1f.3.analog-stereo
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  I: [pulseaudio] card.c: Changed profile of card 2 
"alsa_card.pci-_00_1f.3" to output:analog-stereo
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile 
output:analog-stereo to availability status unknown
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile 
output:analog-stereo+input:analog-stereo to availability status unknown
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  I: [pulseaudio] core.c: default_sink: 
alsa_output.pci-_00_1f.3.analog-stereo -> 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1
  I: [pulseaudio] core.c: default_source: 
alsa_output.pci-_00_1f.3.analog-stereo.monitor -> 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] module-switch-on-port-available.c: Trying to switch away from 
port analog-output-headphones, found iec958-stereo-output
  D: [pulseaudio] module-switch-on-port-available.c: Trying to switch to port 
iec958-stereo-output
  D: [pulseaudio] module-switch-on-port-available.c: Finding best profile for 
port iec958-stereo-output, preferred = iec958-stereo
  D: [pulseaudio] module-rescue-streams.c: No sink inputs to move away.
  D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the 
initial iterations by half.

  
  backtrace:
  #0  0x7fffe67c135f in publish_service (api=0x55816b48, 
service=0x558d00d0) at modules/module-zeroconf-publish.c:298
  #1  0x773fd548 in once_callback (m=0x55816b48, e=0x558a15b0, 
userdata=) at pulse/mainloop-api.c:45
  #2  0x7740027d in dispatch_defer (m=0x55816af0) at 
pulse/mainloop.c:680
  #3  pa_mainloop_dispatch (m=m@entry=0x55816af0) at pulse/mainloop.c:889
  #4  0x774004ae in pa_mainloop_iterate (m=0x55816af0, 
block=, retval=0x0) at pulse/mainloop.c:929
  #5  0x77400530 in pa_mainloop_run (m=0x55816af0, 
retval=retval@entry=0x0) at pulse/mainloop.c:944
  #6  0x7740e399 in thread (userdata=0x55837a30) at 
pulse/thread-mainloop.c:100
  #7  0x7767e2a8 in internal_thread_func (userdata=0x55874bf0) at 
pulsecore/thread-posix.c:81
  #8  0x76b676db in start_thread (arg=0x7fffe619d700) at 
pthread_create.c:463
  #9  0x760e688f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  
  In general the stream is pretty skippy, so I wonder if there's some sort of 
periodic restarting issue happening

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 1801515] Re: package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-11-03 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: fsys-tarfile-error

** Changed in: chromium-browser (Ubuntu)
   Status: New => Invalid

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

Title:
  package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
  failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned
  error exit status 2

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  The crash notification window popped up after logging in.

  It appears chromium was running in background using ffmpeg codecs.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   chromium-codecs-ffmpeg-extra:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Oct 29 07:51:15 2018
  DpkgTerminalLog:
   Preparing to unpack 
.../chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb ...
   Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  DuplicateSignature:
   package:chromium-codecs-ffmpeg-extra:70.0.3538.77-0ubuntu0.18.04.1
   Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: chromium-browser
  Title: package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 
failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1801515/+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 1801532] Re: pulseaudio crashing when publishing sound devices to zeroconf

2018-11-03 Thread Owen Williams
the line in question is, I think:

if (!s->userdata->client || avahi_client_get_state(s->userdata->client) != 
AVAHI_CLIENT_S_RUNNING)
return;


something here is null, probably because there's a restart happening?

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

Title:
  pulseaudio crashing when publishing sound devices to zeroconf

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04

  pulseaudio crashes after 5-10 if advertising sound devices is enabled:

  logs leading up to the crash:

  [New Thread 0x7fffe7fff700 (LWP 9068)]
  D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 /  46% / 
-20.00 dB,   front-right: 30419 /  46% / -20.00 dB
  D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Thread starting up
  I: [alsa-sink-ALC887-VD Analog] core-util.c: Failed to acquire real-time 
scheduling: Permission denied
  I: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Starting playback.
  D: [alsa-sink-ALC887-VD Analog] ratelimit.c: 27 events suppressed
  D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the 
initial iterations by half.
  I: [pulseaudio] core.c: default_source: 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor -> 
alsa_output.pci-_00_1f.3.analog-stereo.monitor
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] module-device-restore.c: Could not set format on sink 
alsa_output.pci-_00_1f.3.analog-stereo
  D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1f.3.analog-stereo becomes idle, timeout in 5 seconds.
  I: [pulseaudio] core.c: default_sink: 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1 -> 
alsa_output.pci-_00_1f.3.analog-stereo
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  I: [pulseaudio] card.c: Changed profile of card 2 
"alsa_card.pci-_00_1f.3" to output:analog-stereo
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile 
output:analog-stereo to availability status unknown
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile 
output:analog-stereo+input:analog-stereo to availability status unknown
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  I: [pulseaudio] core.c: default_sink: 
alsa_output.pci-_00_1f.3.analog-stereo -> 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1
  I: [pulseaudio] core.c: default_source: 
alsa_output.pci-_00_1f.3.analog-stereo.monitor -> 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
  D: [pulseaudio] module-switch-on-port-available.c: Trying to switch away from 
port analog-output-headphones, found iec958-stereo-output
  D: [pulseaudio] module-switch-on-port-available.c: Trying to switch to port 
iec958-stereo-output
  D: [pulseaudio] module-switch-on-port-available.c: Finding best profile for 
port iec958-stereo-output, preferred = iec958-stereo
  D: [pulseaudio] module-rescue-streams.c: No sink inputs to move away.
  D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the 
initial iterations by half.

  
  backtrace:
  #0  0x7fffe67c135f in publish_service (api=0x55816b48, 
service=0x558d00d0) at modules/module-zeroconf-publish.c:298
  #1  0x773fd548 in once_callback (m=0x55816b48, e=0x558a15b0, 
userdata=) at pulse/mainloop-api.c:45
  #2  0x7740027d in dispatch_defer (m=0x55816af0) at 
pulse/mainloop.c:680
  #3  pa_mainloop_dispatch (m=m@entry=0x55816af0) at pulse/mainloop.c:889
  #4  0x774004ae in pa_mainloop_iterate (m=0x55816af0, 
block=, retval=0x0) at pulse/mainloop.c:929
  #5  0x77400530 in pa_mainloop_run (m=0x55816af0, 
retval=retval@entry=0x0) at pulse/mainloop.c:944
  #6  0x7740e399 in thread (userdata=0x55837a30) at 
pulse/thread-mainloop.c:100
  #7  0x7767e2a8 in internal_thread_func (userdata=0x55874bf0) at 
pulsecore/thread-posix.c:81
  #8  0x76b676db in start_thread (arg=0x7fffe619d700) at 
pthread_create.c:463
  #9  0x760e688f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  
  In general the stream is pretty skippy, so I wonder if there's some sort of 
periodic restarting issue happening

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1801532] [NEW] pulseaudio crashing when publishing sound devices to zeroconf

2018-11-03 Thread Owen Williams
Public bug reported:

Ubuntu 18.04

pulseaudio crashes after 5-10 if advertising sound devices is enabled:

logs leading up to the crash:

[New Thread 0x7fffe7fff700 (LWP 9068)]
D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 /  46% / 
-20.00 dB,   front-right: 30419 /  46% / -20.00 dB
D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Thread starting up
I: [alsa-sink-ALC887-VD Analog] core-util.c: Failed to acquire real-time 
scheduling: Permission denied
I: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Starting playback.
D: [alsa-sink-ALC887-VD Analog] ratelimit.c: 27 events suppressed
D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial 
iterations by half.
I: [pulseaudio] core.c: default_source: 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor -> 
alsa_output.pci-_00_1f.3.analog-stereo.monitor
D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
D: [pulseaudio] module-device-restore.c: Could not set format on sink 
alsa_output.pci-_00_1f.3.analog-stereo
D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1f.3.analog-stereo becomes idle, timeout in 5 seconds.
I: [pulseaudio] core.c: default_sink: 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1 -> 
alsa_output.pci-_00_1f.3.analog-stereo
D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
I: [pulseaudio] card.c: Changed profile of card 2 "alsa_card.pci-_00_1f.3" 
to output:analog-stereo
D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile 
output:analog-stereo to availability status unknown
D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile 
output:analog-stereo+input:analog-stereo to availability status unknown
D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
I: [pulseaudio] core.c: default_sink: 
alsa_output.pci-_00_1f.3.analog-stereo -> 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1
I: [pulseaudio] core.c: default_source: 
alsa_output.pci-_00_1f.3.analog-stereo.monitor -> 
alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor
D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
D: [pulseaudio] module-switch-on-port-available.c: Trying to switch away from 
port analog-output-headphones, found iec958-stereo-output
D: [pulseaudio] module-switch-on-port-available.c: Trying to switch to port 
iec958-stereo-output
D: [pulseaudio] module-switch-on-port-available.c: Finding best profile for 
port iec958-stereo-output, preferred = iec958-stereo
D: [pulseaudio] module-rescue-streams.c: No sink inputs to move away.
D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial 
iterations by half.


backtrace:
#0  0x7fffe67c135f in publish_service (api=0x55816b48, 
service=0x558d00d0) at modules/module-zeroconf-publish.c:298
#1  0x773fd548 in once_callback (m=0x55816b48, e=0x558a15b0, 
userdata=) at pulse/mainloop-api.c:45
#2  0x7740027d in dispatch_defer (m=0x55816af0) at 
pulse/mainloop.c:680
#3  pa_mainloop_dispatch (m=m@entry=0x55816af0) at pulse/mainloop.c:889
#4  0x774004ae in pa_mainloop_iterate (m=0x55816af0, 
block=, retval=0x0) at pulse/mainloop.c:929
#5  0x77400530 in pa_mainloop_run (m=0x55816af0, 
retval=retval@entry=0x0) at pulse/mainloop.c:944
#6  0x7740e399 in thread (userdata=0x55837a30) at 
pulse/thread-mainloop.c:100
#7  0x7767e2a8 in internal_thread_func (userdata=0x55874bf0) at 
pulsecore/thread-posix.c:81
#8  0x76b676db in start_thread (arg=0x7fffe619d700) at 
pthread_create.c:463
#9  0x760e688f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


In general the stream is pretty skippy, so I wonder if there's some sort of 
periodic restarting issue happening

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

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

Title:
  pulseaudio crashing when publishing sound devices to zeroconf

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04

  pulseaudio crashes after 5-10 if advertising sound devices is enabled:

  logs leading up to the crash:

  [New Thread 0x7fffe7fff700 (LWP 9068)]
  D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 /  46% / 
-20.00 dB,   

[Desktop-packages] [Bug 1801527] [NEW] Windows printer via SAMBA - Time out

2018-11-03 Thread Ra
Public bug reported:

Package: system-config-printer
Ubuntu 18.10
system-config-printer: Installed: 1.5.11-2ubuntu1

I am trying to install a Windows printer shared via SAMBA.
I run `system-config-printer`, click on "Add", then "Network printer", then 
Windows printer via SAMBA", then on the "Browse" button on the right. A new 
window opo-up titled "SMB Browse", and thw workgroup named "WORKGROUP" is 
shows. When I click on it, the arrow on its left disappear, and the following 
error is issued in the command line

system-config-printer
got no contact to IPC$
Caught non-fatal exception.  Traceback:
File "/usr/share/system-config-printer/newprinter.py", line 2646, in 
on_tvSMBBrowser_row_expanded
smbc_auth.failed (e)
File "/usr/share/system-config-printer/pysmb.py", line 180, in failed
raise exc
File "/usr/share/system-config-printer/newprinter.py", line 2644, in 
on_tvSMBBrowser_row_expanded
entries = ctx.opendir (uri).getdents ()
smbc.TimedOutError: (110, 'Connection timed out')
Continuing anyway..

** Affects: system-config-printer (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Windows printer via SAMBA - Time out

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

Bug description:
  Package: system-config-printer
  Ubuntu 18.10
  system-config-printer: Installed: 1.5.11-2ubuntu1

  I am trying to install a Windows printer shared via SAMBA.
  I run `system-config-printer`, click on "Add", then "Network printer", then 
Windows printer via SAMBA", then on the "Browse" button on the right. A new 
window opo-up titled "SMB Browse", and thw workgroup named "WORKGROUP" is 
shows. When I click on it, the arrow on its left disappear, and the following 
error is issued in the command line

  system-config-printer
  got no contact to IPC$
  Caught non-fatal exception.  Traceback:
  File "/usr/share/system-config-printer/newprinter.py", line 2646, in 
on_tvSMBBrowser_row_expanded
  smbc_auth.failed (e)
  File "/usr/share/system-config-printer/pysmb.py", line 180, in failed
  raise exc
  File "/usr/share/system-config-printer/newprinter.py", line 2644, in 
on_tvSMBBrowser_row_expanded
  entries = ctx.opendir (uri).getdents ()
  smbc.TimedOutError: (110, 'Connection timed out')
  Continuing anyway..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1801527/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-11-03 Thread Wei
I had the same problem after upgrading to 18.10. Uncommenting
"WaylandEnable=false" worked.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1801524] Re: package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 60 to 2

2018-11-03 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1364642 ***
https://bugs.launchpad.net/bugs/1364642

You can probably fix it this way:

sudo apt-get purge gnome-user-guide
sudo apt-get install gnome-user-guide

** This bug has been marked a duplicate of bug 1364642
   package ubuntu-docs 12.04.6 failed to install/upgrade: symbolic link 
'/usr/share/help/ja/ubuntu-help/music-player-notrecognized.page' size has 
changed from 69 to 4

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

Title:
  package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic
  link '/usr/share/help/ca/gnome-help/documents-previews.page' size has
  changed from 60 to 2

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  Got this error message while software updater was installing
  downloaded packages.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gnome-user-guide 3.8.2-1
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Sat Nov  3 14:08:16 2018
  DuplicateSignature: package:gnome-user-guide:3.8.2-1:symbolic link 
'/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 
60 to 2
  ErrorMessage: symbolic link 
'/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 
60 to 2
  InstallationDate: Installed on 2014-12-02 (1431 days ago)
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.18
  SourcePackage: gnome-user-docs
  Title: package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic 
link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed 
from 60 to 2
  UpgradeStatus: Upgraded to trusty on 2015-12-20 (1048 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1801524/+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 1778422] Re: evince responds to mouse location when it does not have focus. Scrolls wildly up or down.

2018-11-03 Thread Jani Uusitalo
This happens in 18.04 too. Bug #1650076 does also, and I'm not 100 %
sure if these are two different issues or the same. I was able to
reproduce #1650076 with the steps listed there, but just before that I
had Evince following my scroll wheel despite being unfocussed, and I had
not selected anything in the PDF before that (at least not knowingly). I
haven't found the steps to reproduce this without the selection though.

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

Title:
  evince responds to mouse location when it does not have focus. Scrolls
  wildly up or down.

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Evince sometimes gets into a state when it scrolls all the way up or
  all the way down in a document, based on where the mouse cursor is,
  even though evince does not have the focus, and any of the other
  windows is actively receiving input / etc, ie obviously has focus.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 24 11:57:21 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (218 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1778422/+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 1801494] Re: dock missing

2018-11-03 Thread Paul White
@philrego, please can you expand on your points 4 and 5 in the bug
description: dock is/is not there.

Other users are reporting similar issues but we need confirmation of how
the bug might appear.

See https://ubuntuforums.org/showthread.php?t=2391588 for further
discussion.

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

Title:
  dock missing

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 18.04.1 LTS
  Release:  18.04
  2) $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 0.9.1ubuntu18.04.1
Candidate: 0.9.1ubuntu18.04.1
Version table:
   *** 0.9.1ubuntu18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.9.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  4) dock is there
  5) dock is not there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+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 1801524] Re: package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 60 to 2

2018-11-03 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic
  link '/usr/share/help/ca/gnome-help/documents-previews.page' size has
  changed from 60 to 2

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  Got this error message while software updater was installing
  downloaded packages.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gnome-user-guide 3.8.2-1
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Sat Nov  3 14:08:16 2018
  DuplicateSignature: package:gnome-user-guide:3.8.2-1:symbolic link 
'/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 
60 to 2
  ErrorMessage: symbolic link 
'/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 
60 to 2
  InstallationDate: Installed on 2014-12-02 (1431 days ago)
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.18
  SourcePackage: gnome-user-docs
  Title: package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic 
link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed 
from 60 to 2
  UpgradeStatus: Upgraded to trusty on 2015-12-20 (1048 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1801524/+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 1778422] Re: evince responds to mouse location when it does not have focus. Scrolls wildly up or down.

2018-11-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  evince responds to mouse location when it does not have focus. Scrolls
  wildly up or down.

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Evince sometimes gets into a state when it scrolls all the way up or
  all the way down in a document, based on where the mouse cursor is,
  even though evince does not have the focus, and any of the other
  windows is actively receiving input / etc, ie obviously has focus.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 24 11:57:21 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (218 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1778422/+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 1801524] [NEW] package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 60 to 2

2018-11-03 Thread Jim McTavish
Public bug reported:

Got this error message while software updater was installing downloaded
packages.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gnome-user-guide 3.8.2-1
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
Date: Sat Nov  3 14:08:16 2018
DuplicateSignature: package:gnome-user-guide:3.8.2-1:symbolic link 
'/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 
60 to 2
ErrorMessage: symbolic link 
'/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 
60 to 2
InstallationDate: Installed on 2014-12-02 (1431 days ago)
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.8
 apt  1.0.1ubuntu2.18
SourcePackage: gnome-user-docs
Title: package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic 
link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed 
from 60 to 2
UpgradeStatus: Upgraded to trusty on 2015-12-20 (1048 days ago)

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


** Tags: apport-package i386 third-party-packages trusty

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

Title:
  package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic
  link '/usr/share/help/ca/gnome-help/documents-previews.page' size has
  changed from 60 to 2

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  Got this error message while software updater was installing
  downloaded packages.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gnome-user-guide 3.8.2-1
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  Date: Sat Nov  3 14:08:16 2018
  DuplicateSignature: package:gnome-user-guide:3.8.2-1:symbolic link 
'/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 
60 to 2
  ErrorMessage: symbolic link 
'/usr/share/help/ca/gnome-help/documents-previews.page' size has changed from 
60 to 2
  InstallationDate: Installed on 2014-12-02 (1431 days ago)
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.18
  SourcePackage: gnome-user-docs
  Title: package gnome-user-guide 3.8.2-1 failed to install/upgrade: symbolic 
link '/usr/share/help/ca/gnome-help/documents-previews.page' size has changed 
from 60 to 2
  UpgradeStatus: Upgraded to trusty on 2015-12-20 (1048 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1801524/+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 1574582] Re: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager

2018-11-03 Thread debb1046
In 18.04 I can get the modem working by:
sudo usb_modeswitch -v 0x03f0 -p 0x9d1d -u3

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

Title:
  HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-
  manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  USB modem not recognized by network-manager. Modem information in
  attached

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Apr 25 11:14:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.106.36.1 dev wlp2s0  proto static  metric 600 
   1.1.1.1 via 10.106.36.1 dev wlp2s0  proto dhcp  metric 600 
   10.106.36.0/22 dev wlp2s0  proto kernel  scope link  src 10.106.39.123  
metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH   
   CONNECTION  CON-UUID  CON-PATH   

   wlp2s0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/1  IQORAMS_REPAIR  
3b1e13ff-f9c9-4a49-a576-465bc2713e21  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enxb2e41f35ffe1  ethernet  disconnected  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   enp0s31f6ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   lo   loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+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 1801520] [NEW] On login screen, gdm3 behaves as if someone continually hit 'Enter'

2018-11-03 Thread Valentin Quequet
Public bug reported:

After logging in, using a session, zapping (locking) the session and
leaving the computer alone for some time, gdm3 sometimes behaves
erratically.

The strange behavior is the following :
  - Keys pressed don't show as dots in password text field ; they don't show at 
all
  - gdm3 tries validating empty password, in loop, without me even typing 
'Enter', continually

Please, look the folder at https://www.jinstallelinux.net/pub1/www/GDM3_Bugs/ .
The 3 pictures show what happen when someone type a wrong password (normal gdm3 
behavior).
The video shows the bad behavior of gdm3 under mysterious circumstances (yet to 
be defined).

Thanks for reading,
In hope this helps.

Val

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

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

Title:
  On login screen, gdm3 behaves as if someone continually hit 'Enter'

Status in gdm3 package in Ubuntu:
  New

Bug description:
  After logging in, using a session, zapping (locking) the session and
  leaving the computer alone for some time, gdm3 sometimes behaves
  erratically.

  The strange behavior is the following :
- Keys pressed don't show as dots in password text field ; they don't show 
at all
- gdm3 tries validating empty password, in loop, without me even typing 
'Enter', continually

  Please, look the folder at https://www.jinstallelinux.net/pub1/www/GDM3_Bugs/ 
.
  The 3 pictures show what happen when someone type a wrong password (normal 
gdm3 behavior).
  The video shows the bad behavior of gdm3 under mysterious circumstances (yet 
to be defined).

  Thanks for reading,
  In hope this helps.

  Val

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801520/+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 1801515] Re: package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-11-03 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
  failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned
  error exit status 2

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The crash notification window popped up after logging in.

  It appears chromium was running in background using ffmpeg codecs.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   chromium-codecs-ffmpeg-extra:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Oct 29 07:51:15 2018
  DpkgTerminalLog:
   Preparing to unpack 
.../chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb ...
   Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  DuplicateSignature:
   package:chromium-codecs-ffmpeg-extra:70.0.3538.77-0ubuntu0.18.04.1
   Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: chromium-browser
  Title: package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 
failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1801515/+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 1801517] Re: package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 5

2018-11-03 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 5

Status in cups-filters package in Ubuntu:
  New

Bug description:
  I dont know anything at all..

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-browsed 1.8.3-2ubuntu3.4
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Nov  3 14:39:39 2018
  DpkgHistoryLog:
   Start-Date: 2018-11-03  14:39:28
   Commandline: apt-get -f install
   Requested-By: ikaya (1000)
   Upgrade: mysql-server-5.7:amd64 (5.7.23-0ubuntu0.16.04.1, 
5.7.24-0ubuntu0.16.04.1), mysql-server-core-5.7:amd64 (5.7.23-0ubuntu0.16.04.1, 
5.7.24-0ubuntu0.16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 5
  InstallationDate: Installed on 2017-07-25 (465 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 5986:0710 Acer, Inc 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80V4
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=2474b0c3-ce5f-4820-a51b-0a55bd757ba6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: cups-filters
  Title: package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2XCN38WW(V2.12)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 710-14IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr2XCN38WW(V2.12):bd07/10/2018:svnLENOVO:pn80V4:pvrLenovoYOGA710-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct31:cvrLenovoYOGA710-14IKB:
  dmi.product.family: YOGA 710-14IKB
  dmi.product.name: 80V4
  dmi.product.version: Lenovo YOGA 710-14IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1801517/+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 1801515] [NEW] package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-11-03 Thread j.greg.bl...@gmail.com
Public bug reported:

The crash notification window popped up after logging in.

It appears chromium was running in background using ffmpeg codecs.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 chromium-codecs-ffmpeg-extra:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Oct 29 07:51:15 2018
DpkgTerminalLog:
 Preparing to unpack 
.../chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb ...
 Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
 dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
 dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2
DuplicateSignature:
 package:chromium-codecs-ffmpeg-extra:70.0.3538.77-0ubuntu0.18.04.1
 Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
 dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
 dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: chromium-browser
Title: package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 
failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: chromium-browser (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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1801515

Title:
  package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
  failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned
  error exit status 2

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The crash notification window popped up after logging in.

  It appears chromium was running in background using ffmpeg codecs.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   chromium-codecs-ffmpeg-extra:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Oct 29 07:51:15 2018
  DpkgTerminalLog:
   Preparing to unpack 
.../chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb ...
   Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  DuplicateSignature:
   package:chromium-codecs-ffmpeg-extra:70.0.3538.77-0ubuntu0.18.04.1
   Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: chromium-browser
  Title: package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 
failed to install/upgrade: 

[Desktop-packages] [Bug 1801516] [NEW] package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-11-03 Thread j.greg.bl...@gmail.com
*** This bug is a duplicate of bug 1801515 ***
https://bugs.launchpad.net/bugs/1801515

Public bug reported:

The crash notification window popped up after logging in.

It appears chromium was running in background using ffmpeg codecs.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 chromium-codecs-ffmpeg-extra:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Oct 29 07:51:15 2018
DpkgTerminalLog:
 Preparing to unpack 
.../chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb ...
 Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
 dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
 dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2
DuplicateSignature:
 package:chromium-codecs-ffmpeg-extra:70.0.3538.77-0ubuntu0.18.04.1
 Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
 dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
 dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: chromium-browser
Title: package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 
failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: chromium-browser (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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1801516

Title:
  package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
  failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned
  error exit status 2

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The crash notification window popped up after logging in.

  It appears chromium was running in background using ffmpeg codecs.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   chromium-codecs-ffmpeg-extra:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Oct 29 07:51:15 2018
  DpkgTerminalLog:
   Preparing to unpack 
.../chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb ...
   Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  DuplicateSignature:
   package:chromium-codecs-ffmpeg-extra:70.0.3538.77-0ubuntu0.18.04.1
   Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: chromium-browser
  Title: package 

[Desktop-packages] [Bug 1801516] Re: package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-11-03 Thread Apport retracing service
*** This bug is a duplicate of bug 1801515 ***
https://bugs.launchpad.net/bugs/1801515

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1801515, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1801515
   package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

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

Title:
  package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
  failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned
  error exit status 2

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The crash notification window popped up after logging in.

  It appears chromium was running in background using ffmpeg codecs.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   chromium-codecs-ffmpeg-extra:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Oct 29 07:51:15 2018
  DpkgTerminalLog:
   Preparing to unpack 
.../chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb ...
   Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  DuplicateSignature:
   package:chromium-codecs-ffmpeg-extra:70.0.3538.77-0ubuntu0.18.04.1
   Unpacking chromium-codecs-ffmpeg-extra (70.0.3538.67-0ubuntu0.18.04.1) over 
(69.0.3497.81-0ubuntu0.18.04.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb':
 No such file or directory
   dpkg: error processing archive 
/var/cache/apt/archives/chromium-codecs-ffmpeg-extra_70.0.3538.67-0ubuntu0.18.04.1_amd64.deb
 (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: chromium-browser
  Title: package chromium-codecs-ffmpeg-extra 70.0.3538.77-0ubuntu0.18.04.1 
failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1801516/+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 1801517] [NEW] package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 5

2018-11-03 Thread cenk
Public bug reported:

I dont know anything at all..

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-browsed 1.8.3-2ubuntu3.4
ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CupsErrorLog:
 
Date: Sat Nov  3 14:39:39 2018
DpkgHistoryLog:
 Start-Date: 2018-11-03  14:39:28
 Commandline: apt-get -f install
 Requested-By: ikaya (1000)
 Upgrade: mysql-server-5.7:amd64 (5.7.23-0ubuntu0.16.04.1, 
5.7.24-0ubuntu0.16.04.1), mysql-server-core-5.7:amd64 (5.7.23-0ubuntu0.16.04.1, 
5.7.24-0ubuntu0.16.04.1)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 5
InstallationDate: Installed on 2017-07-25 (465 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 003: ID 5986:0710 Acer, Inc 
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80V4
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=2474b0c3-ce5f-4820-a51b-0a55bd757ba6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
SourcePackage: cups-filters
Title: package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 5
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/10/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 2XCN38WW(V2.12)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40688 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 710-14IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr2XCN38WW(V2.12):bd07/10/2018:svnLENOVO:pn80V4:pvrLenovoYOGA710-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct31:cvrLenovoYOGA710-14IKB:
dmi.product.family: YOGA 710-14IKB
dmi.product.name: 80V4
dmi.product.version: Lenovo YOGA 710-14IKB
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package xenial

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

Title:
  package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 5

Status in cups-filters package in Ubuntu:
  New

Bug description:
  I dont know anything at all..

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-browsed 1.8.3-2ubuntu3.4
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Nov  3 14:39:39 2018
  DpkgHistoryLog:
   Start-Date: 2018-11-03  14:39:28
   Commandline: apt-get -f install
   Requested-By: ikaya (1000)
   Upgrade: mysql-server-5.7:amd64 (5.7.23-0ubuntu0.16.04.1, 
5.7.24-0ubuntu0.16.04.1), mysql-server-core-5.7:amd64 (5.7.23-0ubuntu0.16.04.1, 
5.7.24-0ubuntu0.16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 5
  InstallationDate: Installed on 2017-07-25 (465 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 5986:0710 Acer, Inc 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80V4
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=2474b0c3-ce5f-4820-a51b-0a55bd757ba6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: cups-filters
  Title: package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2XCN38WW(V2.12)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  

[Desktop-packages] [Bug 1318030] Re: Cannot login-without-password when home folder is encrypted

2018-11-03 Thread Jeroen
** Summary changed:

- Cannot login-without-password when home folder in encrypted
+ Cannot login-without-password when home folder is encrypted

** Description changed:

- Users of which the home folder is encrypted using the CLI (unfortunately
+ Users of whom the home folder is encrypted using the CLI (unfortunately
  there is no GUI option for this, see
  https://bugs.launchpad.net/ubuntu/+source/gnome-control-
  center/+bug/1279766), and for which the 'login without password' is set,
  cannot login.
  
  Steps to reproduce:
  1. Using an Administrator account, create a new user in System Settings > 
User Accounts and set a password.
  2. Open a shell and encrypt the newly created user folder by 'sudo 
ecryptfs-migrate-home -u '
  3. Login into the new account: successful
  4. Logout and login into the Administrator account and select 'Login without 
password' for the newly created user.
  5. Login into the new account: cannot login (the password field for this 
users now displays 'Log in' but trying to login results in a flickering screen 
and back to the login screen.
  
  Ubuntu 14.04 x64 (reproducable on two different machines)

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

Title:
  Cannot login-without-password when home folder is encrypted

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

Bug description:
  Users of whom the home folder is encrypted using the CLI
  (unfortunately there is no GUI option for this, see
  https://bugs.launchpad.net/ubuntu/+source/gnome-control-
  center/+bug/1279766), and for which the 'login without password' is
  set, cannot login.

  Steps to reproduce:
  1. Using an Administrator account, create a new user in System Settings > 
User Accounts and set a password.
  2. Open a shell and encrypt the newly created user folder by 'sudo 
ecryptfs-migrate-home -u '
  3. Login into the new account: successful
  4. Logout and login into the Administrator account and select 'Login without 
password' for the newly created user.
  5. Login into the new account: cannot login (the password field for this 
users now displays 'Log in' but trying to login results in a flickering screen 
and back to the login screen.

  Ubuntu 14.04 x64 (reproducable on two different machines)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1318030/+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 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic

2018-11-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Regression: cannot use impress remote over bluetooth with ubuntu
  bionic

Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

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


Re: [Desktop-packages] [Bug 1798053] Re: [SRU] Click on the back icon in gnome-software doesn't work

2018-11-03 Thread Timmmm
The easiest workaround I found is to close it, then right-click the icon
and select "view details". I have no idea what that is supposed to do but
for some reason it opens the software centre on the updates tab, or
something like that.

On Sat, 3 Nov 2018, 11:30 Denyer <1798...@bugs.launchpad.net wrote:

> Just for anyone like me finding the bug by search, the man page notes
> you can open gnome-software to a particular screen which works around
> being stuck on the last one accessed, eg:
>
> gnome-software overview &
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1800380).
> https://bugs.launchpad.net/bugs/1798053
>
> Title:
>   [SRU] Click on the back icon in gnome-software doesn't work
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798053/+subscriptions
>

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

Title:
  [SRU] Click on the back icon in gnome-software doesn't work

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Test Case]

  1. Open gnome-software
  2. Press Ctrl+F and type "firefox" or any string that will return results
  3. Click any result in the list (snap package or deb, already installed or 
not, it doesn't matter)
  4. Observe that a new page is open showing details about the application
  5. Close gnome-software
  6. Open gnome-software again
  7. Observe that the application is open on the last open page (details view 
about the application)
  8. Click the back button (top-left corner)

  Expected result: the application goes back to the list of search
  results (or perhaps to the home screen)

  Current result: nothing happens

  Please note that the upstream fix reverts a new behaviour and as a
  result, when opening again gnome-software at step 6, the application
  opens on the home screen instead of resuming the last open page. This
  is consistent with how gnome-software behaves in bionic. So after
  applying the patch, steps 7 and 8 can be folded into one single step:
  "Observe that the application is open on the home screen".

  
  [Regression Potential]

  Low. This is a cherry-pick of a self-contained trivial upstream commit that 
is already released in gnome-software 3.30.3 
(https://gitlab.gnome.org/GNOME/gnome-software/commit/ca5f8e74b6f9991ae228caa2c698131a54764774).
  As noted above, it does change the behaviour of re-opening the application 
after closing it, but it reverts it to the behaviour it had in bionic, so I 
don't think it should be considered a regression.

  Re-opening the application after closing it in a number of different
  situations should be thoroughly exercised to make sure that this
  doesn't introduce any functional regression.

  
  [Original Description]

  Searched for Chromium, installed Chromium (snap version), clicked Launched 
and used chromium.
  Went back to gnome-software and clicked the back button. Nothing happened. 
Restarted gnome-software and clicked the back button. Nothing happened.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu3 [modified: 
usr/share/gnome-shell/search-providers/org.gnome.Software-search-provider.ini]
  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
  CasperVersion: 1.399
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 11:22:16 2018
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu3
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181016)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798053/+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 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic

2018-11-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Regression: cannot use impress remote over bluetooth with ubuntu
  bionic

Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]

2018-11-03 Thread Konstantin Yegupov
Daniel, the audio card id string seems to be the same, so I suspect it
might be the same issue.

Anyway, I have found the culprit. Sound card was intercepted by another
process (timidity), so Pulseaudio was unable to use it.

I have discovered the offending process via the `sudo fuser /dev/snd/*`
command.

Uninstalling timidity has solved the issue.

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

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

Status in pulseaudio package in Ubuntu:
  Incomplete

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

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

  and have included some output of those diagnostic steps below:

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

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

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

  Sound settings still only list dummy output.

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

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

-- 
Mailing list: https://launchpad.net/~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 1801097] Re: gnome-software does not exit a search

2018-11-03 Thread Paul White
*** This bug is a duplicate of bug 1798053 ***
https://bugs.launchpad.net/bugs/1798053

Marking as a duplicate of bug 1798053
Bug already reported and fixed
Updated package gnome-software - 3.30.2-0ubuntu8 currently in -proposed


 

** This bug has been marked a duplicate of bug 1798053
   [SRU] Click on the back icon in gnome-software doesn't work

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

Title:
  gnome-software does not exit a search

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I (accidentally) started Rhythmbox for the firt time ever at this
  laptop. It started, and a pop-up came asking if I wanted to install
  additional needed codecs (title line says "Available software for
  MPEG-4 ACC decoder", so I guess this was the search argument.

  I accepted, and gnome-software opened with a search result for
  GSTreamer codecs. I installed two of them, life is good, closed
  (Alt-F4) gnome-software.

  Then I decided to install some other package via GS as well. Opened
  (again) it, and... I am shown a search result for GStreamer codecs. I
  cannot exit this search. (via the "<" at the left of the title line).
  I can only close the thing.

  End result: gnome-software is now, for all practical purposes,
  unavailable. Hence, the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu7
  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: Thu Nov  1 09:15:18 2018
  ExecutablePath: /usr/bin/gnome-software
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu7
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to cosmic on 2018-07-07 (116 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-03-07T18:07:32.794203

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1801097/+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 1801098] Re: gnome-software does not exit a search

2018-11-03 Thread Paul White
*** This bug is a duplicate of bug 1798053 ***
https://bugs.launchpad.net/bugs/1798053

** This bug is no longer a duplicate of bug 1801097
   gnome-software does not exit a search
** This bug has been marked a duplicate of bug 1798053
   [SRU] Click on the back icon in gnome-software doesn't work

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

Title:
  gnome-software does not exit a search

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I (accidentally) started Rhythmbox for the firt time ever at this
  laptop. It started, and a pop-up came asking if I wanted to install
  additional needed codecs (title line says "Available software for
  MPEG-4 ACC decoder", so I guess this was the search argument.

  I accepted, and gnome-software opened with a search result for
  GSTreamer codecs. I installed two of them, life is good, closed
  (Alt-F4) gnome-software.

  Then I decided to install some other package via GS as well. Opened
  (again) it, and... I am shown a search result for GStreamer codecs. I
  cannot exit this search. (via the "<" at the left of the title line).
  I can only close the thing.

  End result: gnome-software is now, for all practical purposes,
  unavailable. Hence, the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu7
  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: Thu Nov  1 09:15:18 2018
  ExecutablePath: /usr/bin/gnome-software
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu7
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to cosmic on 2018-07-07 (116 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-03-07T18:07:32.794203

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1801098/+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 1734095] Re: After upgrade to ubuntu 17.10 Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

2018-11-03 Thread Luis
I seem to have found a solution. Install polkit, in my case
sudo apt install lxpolkit

And then, it may be useful to check the Default applications in Menu ->
Preferences -> Default applications for LXSession , select Core
Applications , and make sure 'Polkit Agent' is set to lxpolkit.

Is it possible that in the default installation of ubuntu, the polkit
package is not being installed by default?

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

Title:
  After upgrade to ubuntu 17.10 Software & Updates not showing
  authorization popup [gnome-shell[N]: pushModal: invocation of
  begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1734095/+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 1798053] Re: [SRU] Click on the back icon in gnome-software doesn't work

2018-11-03 Thread Denyer
Just for anyone like me finding the bug by search, the man page notes
you can open gnome-software to a particular screen which works around
being stuck on the last one accessed, eg:

gnome-software overview &

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

Title:
  [SRU] Click on the back icon in gnome-software doesn't work

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  [Test Case]

  1. Open gnome-software
  2. Press Ctrl+F and type "firefox" or any string that will return results
  3. Click any result in the list (snap package or deb, already installed or 
not, it doesn't matter)
  4. Observe that a new page is open showing details about the application
  5. Close gnome-software
  6. Open gnome-software again
  7. Observe that the application is open on the last open page (details view 
about the application)
  8. Click the back button (top-left corner)

  Expected result: the application goes back to the list of search
  results (or perhaps to the home screen)

  Current result: nothing happens

  Please note that the upstream fix reverts a new behaviour and as a
  result, when opening again gnome-software at step 6, the application
  opens on the home screen instead of resuming the last open page. This
  is consistent with how gnome-software behaves in bionic. So after
  applying the patch, steps 7 and 8 can be folded into one single step:
  "Observe that the application is open on the home screen".

  
  [Regression Potential]

  Low. This is a cherry-pick of a self-contained trivial upstream commit that 
is already released in gnome-software 3.30.3 
(https://gitlab.gnome.org/GNOME/gnome-software/commit/ca5f8e74b6f9991ae228caa2c698131a54764774).
  As noted above, it does change the behaviour of re-opening the application 
after closing it, but it reverts it to the behaviour it had in bionic, so I 
don't think it should be considered a regression.

  Re-opening the application after closing it in a number of different
  situations should be thoroughly exercised to make sure that this
  doesn't introduce any functional regression.

  
  [Original Description]

  Searched for Chromium, installed Chromium (snap version), clicked Launched 
and used chromium.
  Went back to gnome-software and clicked the back button. Nothing happened. 
Restarted gnome-software and clicked the back button. Nothing happened.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu3 [modified: 
usr/share/gnome-shell/search-providers/org.gnome.Software-search-provider.ini]
  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
  CasperVersion: 1.399
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 11:22:16 2018
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu3
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181016)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798053/+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 1734095] Re: After upgrade to ubuntu 17.10 Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

2018-11-03 Thread Luis
I am having similar problem in Lubuntu 18.04 LTS. I found it originally
when I run 'Software and Updates' from the menu (software-properties-
gtk) and try to check/uncheck software sources. Checking/unchecking does
not work. I can only see the error message "ERROR:root:Authentication
canceled, changes have not been saved" if I run it from the command
line.

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

Title:
  After upgrade to ubuntu 17.10 Software & Updates not showing
  authorization popup [gnome-shell[N]: pushModal: invocation of
  begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1734095/+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 1797178] Re: gnome-shell activities / application icon touches not fully registering

2018-11-03 Thread Mario Vukelic
FWIW and FYI, I cannot repro this on Cosmic with Dell XPS 15 9575

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

Title:
  gnome-shell activities / application icon touches not fully
  registering

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On a dell xps 15 2-in-1 (model 9575), the touchscreen mostly works.
  However, in gnome-shell, touching the top-left 'Activities' menu
  results in a quick flash of the menu button, but not the launching of
  the overview.  Once in the overview (via mouse/keyboard/swipe-from-
  left), touching on an application icon (in either the left tray or the
  applications grid) results in the application icon flashing, but not
  activating.  A long-touch will bring up a menu in which touching on
  "new window" works properly.  Additionally, touching the "show
  applications" grid button works, as do other components of the top
  bar, its only the the "activities" menu button and app icon launchers
  that are "registering" a touch but not activating properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 10 09:13:40 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-26 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+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 579168] Re: VPNs to hosts resolving to multiple IPs often fail

2018-11-03 Thread Wladimir Mutel
well, the discussion has unfolded quickly with a negative response from James 
Cameron (probably the only remaining/active author of pptpclient).
from there, I would see these options of what to do next :
- send more responses voicing user concerns and interest in this feature to the 
started discussion;
- propose our own patch for get_ip_address function in pptp.c (not sure I am 
capable enough as a C programmer, but I would start from OpenSSH patch posted 
at https://groups.google.com/forum/#!topic/opensshunixdev/lErxlPk_MnA as a 
source for inspiration );
- create some external wrapper for quickly scanning a list of IPs and returning 
the fastest-responding one to be substituted into pptp command line. For a 
start, I would use nmap with arguments like these:
nmap --script resolveall --script-args newtargets -PS1723 -sn vpn.server.name # 
as described at 
https://serverfault.com/questions/843304/can-nmap-scan-test-all-answers-from-round-robin-dns
 or at 
https://security.stackexchange.com/questions/141480/nmap-to-scan-all-resolved-ip-addresses-for-a-given-domain-name
and then process its output in some automated way (I only used it manually and 
interpreted visually).
this substitution can be usable with pppd configs stored in /etc/ppp/peers but 
I am unsure if it could be easily integrated into Network Manager setup.

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

Title:
  VPNs to hosts resolving to multiple IPs often fail

Status in network-manager-pptp package in Ubuntu:
  Triaged
Status in pptp-linux package in Ubuntu:
  New

Bug description:
  Binary package hint: network-manager

  I tried to set up ipredator VPN via the network manager on ubuntu lucid lynx 
10.04 64 bit and like a few other users as I could see on several forum, if I 
store password in keyring, it just don't try to connect. 
  Knowing that I disabled the keyring, and then was prompter for password, then 
it tried to connect but failed with a connection timed out error...
  I had to put the IP adress of vpn.ipredator.se instead of the hostname for it 
to work... 
  I checked, it is not a problem with my ISP dns server:

  doki@doki-desktop:~$ nslookup vpn.ipredator.se
  Server:   93.182.182.85
  Address:  93.182.182.85#53

  Non-authoritative answer:
  Name: vpn.ipredator.se
  Address: 93.182.146.2
  Name: vpn.ipredator.se
  Address: 93.182.147.2
  Name: vpn.ipredator.se
  Address: 93.182.148.2
  Name: vpn.ipredator.se
  Address: 93.182.149.2
  Name: vpn.ipredator.se
  Address: 93.182.150.2
  Name: vpn.ipredator.se
  Address: 93.182.151.2
  Name: vpn.ipredator.se
  Address: 93.182.152.2
  Name: vpn.ipredator.se
  Address: 93.182.153.2
  Name: vpn.ipredator.se
  Address: 93.182.164.2
  Name: vpn.ipredator.se
  Address: 93.182.179.2
  Name: vpn.ipredator.se
  Address: 93.182.180.2
  Name: vpn.ipredator.se
  Address: 93.182.181.2
  Name: vpn.ipredator.se
  Address: 93.182.185.2
  Name: vpn.ipredator.se
  Address: 93.182.186.2
  Name: vpn.ipredator.se
  Address: 93.182.187.2
  Name: vpn.ipredator.se
  Address: 93.182.188.2
  Name: vpn.ipredator.se
  Address: 93.182.189.2
  Name: vpn.ipredator.se
  Address: 93.182.190.2
  Name: vpn.ipredator.se
  Address: 93.182.130.2
  Name: vpn.ipredator.se
  Address: 93.182.132.2
  Name: vpn.ipredator.se
  Address: 93.182.133.2

  So I don't know if it's a problem with network manager, or with pptp
  layer, but still, it doesn't seem to be able to resolve this
  hostname...

  If you want me to run some tests/command or if you need more details,
  just ask :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/579168/+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 1656790] Re: print-notifications: Don't show error for job in progress

2018-11-03 Thread Till Kamppeter
First, keep in mind that one source package (upstream project) can have
several binary packages in Ubuntu, each containing a certain component
of the project. To get the complete project installed you need to
install all binary packages, if you do not need all of the functionality
you can leave out one or another binary package.

Also take into account that you cannot combine binary packages of
different version. You need to install all of the binary packages.

So let us see which binary packages of system-config-printer you have
installed:

dpkg -l | grep 1.5.7+2016

You will see a list of some packages. You have to update all of them,
all at once, with a single "dpkg -i ..." command line.

So look at the binary packages of the desired newer version:

https://launchpad.net/ubuntu/+source/system-config-printer/1.5.9+20170825-0ubuntu1
https://launchpad.net/ubuntu/+source/system-config-printer/1.5.9+20170825-0ubuntu1/+build/13297396

See the section "Built files" under the last link.

Download all .deb files from here and install the ones form which you
have the old version installed with a single command line, like for
example:

dpkg -i python3-cupshelpers_1.5.9+20170825-0ubuntu1_all.deb system-
config-printer-common_1.5.9+20170825-0ubuntu1_all.deb system-config-
printer-gnome_1.5.9+20170825-0ubuntu1_all.deb system-config-printer-
udev_1.5.9+20170825-0ubuntu1_amd64.deb system-config-
printer_1.5.9+20170825-0ubuntu1_all.deb

This will most probably work. If not, we need to rebuild the source
package for your distribution version, but try this first and tell
whether this works. If not, I will show you how to do the rebuild.

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

Title:
  print-notifications: Don't show error for job in progress

Status in ubuntu-mate:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Running Ubuntu MATE 16.04.1 LTS

  Every single time I print something, I get an error notification.

  Unfortunly, I'm running a Norwegian desktop, so this will be a
  translation of what I suppose the notification says on an English
  desktop:

  Printer error
  Printer 'NAME':'cups-waiting-for-job-completed'

  
  It is a bit annoying, but it disappears after a couple of seconds, when the 
print job is done.

  
  After a bit of Googling, I found this is a known error from earlier, with 
gnome-settings-daemon. I guess the fix never have been included in 
mate-settings-daemon ?

  
  This is the bug in Red Hat for the same problem:
  https://bugzilla.redhat.com/show_bug.cgi?id=1207154

  This is the patch for gnome-settings-daemon from May 20 2015 :
  https://mail.gnome.org/archives/commits-list/2015-May/msg03447.html

  
  The 'cups-waiting-for-job-completed' is a notification in Cups, which should 
not be ignored by gnome-settings-daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1656790/+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 1801494] Re: dock missing

2018-11-03 Thread Paul White
** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu)

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

Title:
  dock missing

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 18.04.1 LTS
  Release:  18.04
  2) $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 0.9.1ubuntu18.04.1
Candidate: 0.9.1ubuntu18.04.1
Version table:
   *** 0.9.1ubuntu18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.9.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  4) dock is there
  5) dock is not there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+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 1801494] [NEW] dock missing

2018-11-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

1) Description: Ubuntu 18.04.1 LTS
Release:18.04
2) $ apt-cache policy gnome-shell-extension-ubuntu-dock
gnome-shell-extension-ubuntu-dock:
  Installed: 0.9.1ubuntu18.04.1
  Candidate: 0.9.1ubuntu18.04.1
  Version table:
 *** 0.9.1ubuntu18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
100 /var/lib/dpkg/status
 0.9.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
4) dock is there
5) dock is not there

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New

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

-- 
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 1656790] Re: print-notifications: Don't show error for job in progress

2018-11-03 Thread JerryFu
Dear Till,

Thank you very much for your fast reply.

We downloaded a deb package 
(system-config-printer_1.5.9+20170825-0ubuntu1_all.deb) from the following 
address:
https://ubuntu.pkgs.org/17.10/ubuntu-main-amd64/system-config-printer_1.5.9+20170825-0ubuntu1_all.deb.html

When we tried to install this deb package on Ubuntu 16.04, an error
occurred. Please refer to the attached picture for details.

In addition, we also tried to upgrade the system-config-printer
component with the [sudo apt-get upgrade] command, but the version is
still 1.5.7 after the upgrade.

Could you tell us how to install system-config-printer 1.5.9 on Ubuntu
16.04?

** Attachment added: "Error information when install system-config-printer 
1.5.9"
   
https://bugs.launchpad.net/ubuntu-mate/+bug/1656790/+attachment/5208725/+files/install_error.png

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

Title:
  print-notifications: Don't show error for job in progress

Status in ubuntu-mate:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Running Ubuntu MATE 16.04.1 LTS

  Every single time I print something, I get an error notification.

  Unfortunly, I'm running a Norwegian desktop, so this will be a
  translation of what I suppose the notification says on an English
  desktop:

  Printer error
  Printer 'NAME':'cups-waiting-for-job-completed'

  
  It is a bit annoying, but it disappears after a couple of seconds, when the 
print job is done.

  
  After a bit of Googling, I found this is a known error from earlier, with 
gnome-settings-daemon. I guess the fix never have been included in 
mate-settings-daemon ?

  
  This is the bug in Red Hat for the same problem:
  https://bugzilla.redhat.com/show_bug.cgi?id=1207154

  This is the patch for gnome-settings-daemon from May 20 2015 :
  https://mail.gnome.org/archives/commits-list/2015-May/msg03447.html

  
  The 'cups-waiting-for-job-completed' is a notification in Cups, which should 
not be ignored by gnome-settings-daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1656790/+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 1801496] [NEW] Printing job in 16.04 is slower than in 14.04

2018-11-03 Thread William.Yeung
Public bug reported:

Ubuntu 16.04LTS
OS Version: 16.04.5
CUPS Version:   2.1.3
Ghostscript Version:9.25 (2018-09-13)

Printing job in 16.04 is slower than in 14.04

We(RICOH printer driver developer) are report a problem from our printer users:
I print file Ubuntu 14.04.5, CUPS 2.1.3,Ghostscript 9.25 is fast(12 Seconds).

But, after I update to Ubuntu 16.04, CUPS 2.1.3, Ghostscript 9.25, I
print the same file with the same driver is slow(326 Seconds).

I figure out that all the print jobs is much slower on Ubuntu 16.04.

I view the "CUPS Error Log",   it shows that there are three points
which maybe the reasons that makes the print job slowly.


FIRST:

By counting the time from "Starting renderer" to "renderer exited with status 
0", we figure out that 16.04 spend more time than 14.04 on "renderer" process.
So we assuming that:"renderer" is one of the key process that makes the print 
job slowly.

"Starting renderer with command: \"printf \'\\033%%-12345X@PJL 
JOB\\012\';printf \'@PJL SET DATAMODE=TWIN\\  @PJL 
EOJ\\012\\033%%-12345X\'\""
.
renderer exited with status 0"



SECOND:

On 16.04, a print job outputs lots of logs as below:
"[Job xxx] Removing document files."

This step(“Removing document files”)does not exsit on 14.04.



The phenomenon that print jobs slower in 16.04 is more obvious when printing 
many jobs in the same time.

THIRD
We tried drivers form other company(HP,Brother…), the printings also slow down 
in Ubuntu 16.04 than 14.04.

Our question is:
1. Do you have any plan to improve the performance of printing on Ubuntu 16.04?
2. Do you have any workaround before this problems fixed?

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

** Attachment added: "Log time"
   https://bugs.launchpad.net/bugs/1801496/+attachment/5208724/+files/Log.zip

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

Title:
  Printing job in 16.04 is slower than in 14.04

Status in ghostscript package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04LTS
  OS Version:   16.04.5
  CUPS Version: 2.1.3
  Ghostscript Version:  9.25 (2018-09-13)

  Printing job in 16.04 is slower than in 14.04

  We(RICOH printer driver developer) are report a problem from our printer 
users:
  I print file Ubuntu 14.04.5, CUPS 2.1.3,Ghostscript 9.25 is fast(12 Seconds).

  But, after I update to Ubuntu 16.04, CUPS 2.1.3, Ghostscript 9.25, I
  print the same file with the same driver is slow(326 Seconds).

  I figure out that all the print jobs is much slower on Ubuntu 16.04.

  I view the "CUPS Error Log",   it shows that there are three points
  which maybe the reasons that makes the print job slowly.

  
  FIRST:
  
  By counting the time from "Starting renderer" to "renderer exited with status 
0", we figure out that 16.04 spend more time than 14.04 on "renderer" process.
  So we assuming that:"renderer" is one of the key process that makes the print 
job slowly.

  "Starting renderer with command: \"printf \'\\033%%-12345X@PJL 
JOB\\012\';printf \'@PJL SET DATAMODE=TWIN\\  @PJL 
EOJ\\012\\033%%-12345X\'\""
  .
  renderer exited with status 0"
  


  SECOND:
  
  On 16.04, a print job outputs lots of logs as below:
  "[Job xxx] Removing document files."

  This step(“Removing document files”)does not exsit on 14.04.
  

  
  The phenomenon that print jobs slower in 16.04 is more obvious when printing 
many jobs in the same time.

  THIRD
  We tried drivers form other company(HP,Brother…), the printings also slow 
down in Ubuntu 16.04 than 14.04.

  Our question is:
  1. Do you have any plan to improve the performance of printing on Ubuntu 
16.04?
  2. Do you have any workaround before this problems fixed?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1801496/+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 1306849] Re: Printing error

2018-11-03 Thread Howard Ryan
Noxious programming code, known as malware, had been brought into
Bangladesh Bank's frameworks in January without the learning of the
bank's data frameworks staff, as indicated by an official comfortable
with the Bangladesh Bank examination. The programmers struck the
frameworks on Feb. 4, said the official, who requested that not be named
in light of the fact that he's not approved to talk about the test.

Atiur Rahman surrendered as Bangladesh's national bank representative on 
Tuesday, saying he assumed good liability subsequent to neglecting to promptly 
advise the Finance Ministry of the burglary. He denied any bad behavior, and 
said he had told insight organizations of the wrongdoing. Two of his agents 
were likewise expelled. Bangladesh on Wednesday designated vocation 
administrator Fazle Kabir as his substitution.
https://technicalsupportforprinter.com/blog/fix-printer-error-code-messages/

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

Title:
  Printing error

Status in foomatic-db package in Ubuntu:
  Confirmed

Bug description:
  I get the message ERROR NAME; stackunderflow COMMAND; pop OPERAND
  STACK; when I try to print from Firefox or anything that has a picture
  as part of the file.  I am running saucy on an AMD64 system. so far I
  have tried deleting the printer and setting it up again. No change.
  Ubuntu 13.10

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


  1   2   >