[Touch-packages] [Bug 2061292] [NEW] Reduce animation setting gets forgotten on every reboot

2024-04-14 Thread Alistair Cunningham
Public bug reported:

After upgrading to Ubuntu 24.04, every time I reboot, the Accessibility
-> Reduce animations setting gets forgotten, and I have to turn it back
on again manually.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-settings 24.04.3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 14 08:33:34 2024
InstallationDate: Installed on 2020-07-14 (1370 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: ubuntu-settings
UpgradeStatus: Upgraded to noble on 2024-04-11 (3 days ago)

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble wayland-session

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

Title:
  Reduce animation setting gets forgotten on every reboot

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 24.04, every time I reboot, the
  Accessibility -> Reduce animations setting gets forgotten, and I have
  to turn it back on again manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-settings 24.04.3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 14 08:33:34 2024
  InstallationDate: Installed on 2020-07-14 (1370 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-settings
  UpgradeStatus: Upgraded to noble on 2024-04-11 (3 days ago)

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


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


[Touch-packages] [Bug 2038925] Re: Many hangs during apt full-upgrade

2024-03-13 Thread Alistair Cunningham
Thank you; I'll check this next time it happens.

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

Title:
  Many hangs during apt full-upgrade

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Ubuntu 23.10, running "apt full-upgrade" has
  resulted in many hangs of up to a minute or so during the upgrade
  procedure. These seem to happen at random and unpredictable steps
  during the upgrade. Running it just now, it hung for around a minute
  on this line:

  Installing new version of config file /etc/lsb-release ...

  At around the same time, the following was logged to /var/log/syslog,
  which may or may not be related:

  2023-10-10T06:38:33.162713-07:00 albatross hud-service[3499]:
  #033[31mvoid
  DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m:
  "No such interface “com.canonical.dbusmenu” on object at path
  /org/ayatana/bamf/window/73400498"

  It then hung again for about a minute at:

  Setting up apport (2.27.0-0ubuntu5) ...

  but nothing was logged to syslog.

  These hangs did not happen on 23.04.

  I appreciate that this is all a bit vague, so am happy to do further
  debugging if someone can advise me what to do. I also appreciate that
  apt might not be the correct package to file this bug against - feel
  free to reassign it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apt 2.7.3
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Oct 10 06:41:34 2023
  InstallationDate: Installed on 2020-07-14 (1183 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: apt
  UpgradeStatus: Upgraded to mantic on 2023-09-16 (24 days ago)

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


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


[Touch-packages] [Bug 2038925] Re: Many hangs during apt full-upgrade

2024-03-12 Thread Alistair Cunningham
They sometimes happen when updating and installing packages. I haven't
seen them happen when reinstalling packages, but I rarely reinstall
packages.

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

Title:
  Many hangs during apt full-upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  Since upgrading to Ubuntu 23.10, running "apt full-upgrade" has
  resulted in many hangs of up to a minute or so during the upgrade
  procedure. These seem to happen at random and unpredictable steps
  during the upgrade. Running it just now, it hung for around a minute
  on this line:

  Installing new version of config file /etc/lsb-release ...

  At around the same time, the following was logged to /var/log/syslog,
  which may or may not be related:

  2023-10-10T06:38:33.162713-07:00 albatross hud-service[3499]:
  #033[31mvoid
  DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m:
  "No such interface “com.canonical.dbusmenu” on object at path
  /org/ayatana/bamf/window/73400498"

  It then hung again for about a minute at:

  Setting up apport (2.27.0-0ubuntu5) ...

  but nothing was logged to syslog.

  These hangs did not happen on 23.04.

  I appreciate that this is all a bit vague, so am happy to do further
  debugging if someone can advise me what to do. I also appreciate that
  apt might not be the correct package to file this bug against - feel
  free to reassign it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apt 2.7.3
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Oct 10 06:41:34 2023
  InstallationDate: Installed on 2020-07-14 (1183 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: apt
  UpgradeStatus: Upgraded to mantic on 2023-09-16 (24 days ago)

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


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


[Touch-packages] [Bug 2038925] [NEW] Many hangs during apt full-upgrade

2023-10-10 Thread Alistair Cunningham
Public bug reported:

Since upgrading to Ubuntu 23.10, running "apt full-upgrade" has resulted
in many hangs of up to a minute or so during the upgrade procedure.
These seem to happen at random and unpredictable steps during the
upgrade. Running it just now, it hung for around a minute on this line:

Installing new version of config file /etc/lsb-release ...

At around the same time, the following was logged to /var/log/syslog,
which may or may not be related:

2023-10-10T06:38:33.162713-07:00 albatross hud-service[3499]:
#033[31mvoid
DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m:
"No such interface “com.canonical.dbusmenu” on object at path
/org/ayatana/bamf/window/73400498"

It then hung again for about a minute at:

Setting up apport (2.27.0-0ubuntu5) ...

but nothing was logged to syslog.

These hangs did not happen on 23.04.

I appreciate that this is all a bit vague, so am happy to do further
debugging if someone can advise me what to do. I also appreciate that
apt might not be the correct package to file this bug against - feel
free to reassign it.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: apt 2.7.3
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Oct 10 06:41:34 2023
InstallationDate: Installed on 2020-07-14 (1183 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: apt
UpgradeStatus: Upgraded to mantic on 2023-09-16 (24 days ago)

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


** Tags: amd64 apport-bug mantic

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

Title:
  Many hangs during apt full-upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  Since upgrading to Ubuntu 23.10, running "apt full-upgrade" has
  resulted in many hangs of up to a minute or so during the upgrade
  procedure. These seem to happen at random and unpredictable steps
  during the upgrade. Running it just now, it hung for around a minute
  on this line:

  Installing new version of config file /etc/lsb-release ...

  At around the same time, the following was logged to /var/log/syslog,
  which may or may not be related:

  2023-10-10T06:38:33.162713-07:00 albatross hud-service[3499]:
  #033[31mvoid
  DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m:
  "No such interface “com.canonical.dbusmenu” on object at path
  /org/ayatana/bamf/window/73400498"

  It then hung again for about a minute at:

  Setting up apport (2.27.0-0ubuntu5) ...

  but nothing was logged to syslog.

  These hangs did not happen on 23.04.

  I appreciate that this is all a bit vague, so am happy to do further
  debugging if someone can advise me what to do. I also appreciate that
  apt might not be the correct package to file this bug against - feel
  free to reassign it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apt 2.7.3
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Oct 10 06:41:34 2023
  InstallationDate: Installed on 2020-07-14 (1183 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: apt
  UpgradeStatus: Upgraded to mantic on 2023-09-16 (24 days ago)

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


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


[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug

2023-09-19 Thread Alistair Cunningham
This is still happening after upgrading to 23.10.

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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


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


[Touch-packages] [Bug 2036580] [NEW] Bluetooth won't turn on after upgrade to 23.10

2023-09-19 Thread Alistair Cunningham
Public bug reported:

After upgrading from Ubuntu 23.04 to 23.10, Bluetooth won't turn on. I
click on the Unity gear wheel icon, then click on System Settings, then
on Bluetooth. The "Bluetooth" toggle is set to off, and the box on the
left says "Bluetooth is disabled". Clicking the toggle turns the toggle
on, but nothing else changes. The box on the left still says that
Bluetooth is disabled, and no Bluetooth icon shows on the menu bar
despite "Show Bluetooth status in the menu bar" being enabled.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluetooth 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Sep 19 11:20:23 2023
InstallationDate: Installed on 2020-07-14 (1162 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro loglevel=4 splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to mantic on 2023-09-16 (3 days ago)
dmi.bios.date: 08/30/2022
dmi.bios.release: 1.28
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET38W (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET38W(1.28):bd08/30/2022:br1.28:efr1.15:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:55 acl:0 sco:0 events:4 errors:0
TX bytes:15 acl:0 sco:0 commands:4 errors:0

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


** Tags: amd64 apport-bug mantic

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

Title:
  Bluetooth won't turn on after upgrade to 23.10

Status in bluez package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10, Bluetooth won't turn on. I
  click on the Unity gear wheel icon, then click on System Settings,
  then on Bluetooth. The "Bluetooth" toggle is set to off, and the box
  on the left says "Bluetooth is disabled". Clicking the toggle turns
  the toggle on, but nothing else changes. The box on the left still
  says that Bluetooth is disabled, and no Bluetooth icon shows on the
  menu bar despite "Show Bluetooth status in the menu bar" being
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: bluetooth 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Sep 19 11:20:23 2023
  InstallationDate: Installed on 2020-07-14 (1162 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro loglevel=4 splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to mantic on 2023-09-16 (3 days ago)
  dmi.bios.date: 08/30/2022
  dmi.bios.release: 1.28
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET38W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET38W(1.28):bd08/30/2022:br1.28:efr1.15:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0

[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-09-05 Thread Alistair Buxton
Since installing 23.04 I can no longer print at all. Attempting to print
anything from any application makes the printer display "Error 49 - Turn
off and turn on again" on the display, and then reboot itself. This was
a clean install.

Older versions of Ubuntu continue to print at the correct size as they
always have.

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 2016404] [NEW] NetworkManager Applet popups continue despite asking not to

2023-04-16 Thread Alistair Cunningham
Public bug reported:

After upgrading to Ubuntu 23.04, I keep receiving popup notifications
from "NetworkManager Applet" telling me that I am connected to a wifi
network or disconnected from a wifi network. I repeatedly click on
"Don't show this again", but they keep on being shown. My desktop
environment is Unity.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: network-manager 1.42.4-1ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Apr 16 10:33:10 2023
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 # Include files from /etc/network/interfaces.d:
 source-directory /etc/network/interfaces.d
InstallationDate: Installed on 2020-07-14 (1005 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 192.168.86.141 dev wlp0s20f3 proto dhcp src 192.168.86.33 metric 
600 
 10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
 192.168.86.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.86.33 metric 
600
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: network-manager
UpgradeStatus: Upgraded to lunar on 2023-03-31 (15 days ago)
modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
[modified]
mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-08-05T00:08:37.126151
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.42.4   connected  started  full  enabled enabled  
enabled  missing  enabled

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


** Tags: amd64 apport-bug lunar

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

Title:
  NetworkManager Applet popups continue despite asking not to

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 23.04, I keep receiving popup notifications
  from "NetworkManager Applet" telling me that I am connected to a wifi
  network or disconnected from a wifi network. I repeatedly click on
  "Don't show this again", but they keep on being shown. My desktop
  environment is Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: network-manager 1.42.4-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr 16 10:33:10 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2020-07-14 (1005 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.141 dev wlp0s20f3 proto dhcp src 192.168.86.33 metric 
600 
   10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.86.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.86.33 
metric 600
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to lunar on 2023-03-31 (15 days ago)
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
[modified]
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-08-05T00:08:37.126151
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.42.4   connected  started  full  enabled enabled  
enabled  missing  enabled

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-02-06 Thread Alistair Buxton
The printer has firmware 20111021. The newest available firmware is
20140618 but can only be installed through Windows.

This printer always reports low toner and I ignore it because it will
continue printing with no loss of quality for hundreds of pages, usually
several times what I already printed. It has also been telling me to
replace the imaging drum for about 4 years.

If you want me to try sending a mono Apple Raster you'll need to tell me
how.

How does any of this explain why 18.04 still prints at the correct size?

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-25 Thread Alistair Buxton
PPD file from 18.04. The MD5 does not match the other one so it is
definitely different somehow. Note that the name is nearly identical but
has an extra underscore at the end for some reason.

Also there are two print queues for this printer on the old machine. I
didn't try the other one. It's PPD file is 10x the size of this one.

** Attachment added: "HP_LaserJet_100_colorMFP_M175nw_61F41D_.ppd"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5643469/+files/HP_LaserJet_100_colorMFP_M175nw_61F41D_.ppd

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-25 Thread Alistair Buxton
Error log from 18.04.

The command I ran was:

lp -d HP_LaserJet_100_colorMFP_M175nw_61F41D_ -o print-scaling=none
170x230.pdf

I also previously tried it without the print-scaling option (not
logged), and result was the same. Very close to the correct size both
times.


** Attachment added: "error_log_18_04"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5643468/+files/error_log_18_04

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-25 Thread Alistair Buxton
Also I just tried printing the test document on another computer which
still has Ubuntu 18.04 installed. The output rectangle was undersized by
less than 1mm, which seems okay. I can attach the ppd file and error log
from there if it would help.

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-25 Thread Alistair Buxton
Note that both of the print commands failed to print anything at all,
but the testipp printer does know that my printer is low on toner. Also
I tried deleting the testipp printer and recreating it but still
nothing.

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-25 Thread Alistair Buxton
ppd file

** Attachment added: "testipp.ppd"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5643436/+files/testipp.ppd

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-25 Thread Alistair Buxton
error log

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

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-22 Thread Alistair Buxton
So attaching the PPD to my bug report about not being able to attach it
seems to have fixed the problem, and now I was able to attach it here.
:)

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-22 Thread Alistair Buxton
ppd

** Attachment added: "HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5642945/+files/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-22 Thread Alistair Buxton
Okay well it seems to be specific to the PPD file. I wonder why it won't
accept it. I tried adding ".txt" to the filename too but it still
wouldn't accept it. Must be due to the contents.

Anyway that's the PDF I used to test (same as previous one) and I used
the lp command line invocation.

I'll see about getting you the PPD some other way.

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-22 Thread Alistair Buxton
test

** Attachment added: "170x230.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5642941/+files/170x230.pdf

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-22 Thread Alistair Buxton
Launchpad throws an error whenever I try to attach the ppd.

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2023-01-22 Thread Alistair Buxton
error log

** Attachment added: "var_log_cups_error_log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5642940/+files/var_log_cups_error_log.txt

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2022-12-07 Thread Alistair Buxton
** Attachment added: "Test SVG"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5635061/+files/170x230.svg

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2022-12-07 Thread Alistair Buxton
I tested printing a PDF with `lp -o print-scaling=none 170x230.pdf`. The
PDF and source SVG are attached. The resulting rectangle is still 168mm
x 226mm.

** Attachment added: "Test PDF"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5635060/+files/170x230.pdf

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2022-12-07 Thread Alistair Buxton
Inkscape and Atril both have the same print dialog. It looks like the
attached screenshot. Notice "Scale" is set to 101.5%. This is the only
way I can get either of them to print at the correct size.

LibreOffice has a different print dialog with no scaling options at all,
hence why I had to print it to a PDF first, and then print the PDF using
Atril.

** Attachment added: "print dialog for most software except libreoffice"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5635059/+files/print-dialog.png

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2022-12-06 Thread Alistair Buxton
In order to work around this I first printed my labels to a PDF file in
LibreOffice, then printed that file with 101.5% scaling.

I had to do it this way because LibreOffice does not use the standard
printer dialog - the scaling option is not shown.

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
   W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
  CurrentDesktop: XFCE
  Date: Tue Dec  6 11:42:58 2022
  InstallationDate: Installed on 2018-05-07 (1673 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1998917] [NEW] Everything prints approximately 2% too small after upgrading to Ubuntu 22.04

2022-12-06 Thread Alistair Buxton
Public bug reported:

To reproduce:

1. Open Inkscape.
2. Draw a rectangle 170mm x 230mm.
3. Print it.

Expected result:

The printed rectangle on paper should measure 170mm x 230mm.

Actual result:

The rectangle measures 168mm x 226mm, a difference of approximately 2%.


I print a lot of labels. I make them in both LibreOffice (for mail
merge) and Inkscape (when I want them all the same).

I use standard downloaded templates in LibreOffice and in Inkscape I
have made my own manually.

I recently upgraded to 22.04 and now whenever I print any of my existing
documents they no longer line up with the labels. They line up in the
top left of the page but at the bottom right they are misaligned,
shifted up and left. This happens because the entire page is now printed
2% smaller.

Nothing else has changed about my setup: it is the same printer and the
same documents printing differently. The printer is a network printer.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4.1
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CupsErrorLog:
 W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists
 W [06/Dec/2022:00:00:06 +] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists
CurrentDesktop: XFCE
Date: Tue Dec  6 11:42:58 2022
InstallationDate: Installed on 2018-05-07 (1673 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/
MachineType: System manufacturer System Product Name
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: 
Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
Snap.Changes: no changes found
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago)
dmi.bios.date: 03/15/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3802
dmi.board.asset.tag: Default string
dmi.board.name: Z170-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug jammy

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

Title:
  Everything prints approximately 2% too small after upgrading to Ubuntu
  22.04

Status in cups package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open Inkscape.
  2. Draw a rectangle 170mm x 230mm.
  3. Print it.

  Expected result:

  The printed rectangle on paper should measure 170mm x 230mm.

  Actual result:

  The rectangle measures 168mm x 226mm, a difference of approximately
  2%.


  I print a lot of labels. I make them in both LibreOffice (for mail
  merge) and Inkscape (when I want them all the same).

  I use standard downloaded templates in LibreOffice and in Inkscape I
  have made my own manually.

  I recently upgraded to 22.04 and now whenever I print any of my
  existing documents they no longer line up with the labels. They line
  up in the top left of the page but at the bottom right they are
  misaligned, shifted up and left. This happens because the entire page
  is now printed 2% smaller.

  Nothing else has changed about my setup: it is the same printer and
  the same documents printing differently. The printer is a network
  printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [06

[Touch-packages] [Bug 1992254] Re: PCI/internal sound card not detected

2022-10-08 Thread Alistair Buxton
I rebooted and everything came back?

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just rebooted my computer and now my sound card, which has worked
  perfectly well for the past 5 or so years, apparently no longer
  exists.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sat Oct  8 19:52:11 2022
  InstallationDate: Installed on 2018-05-07 (1614 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (57 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1992254] Re: PCI/internal sound card not detected

2022-10-08 Thread Alistair Buxton
** Attachment added: "No sound cards"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1992254/+attachment/5622336/+files/no-sound-cards.png

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just rebooted my computer and now my sound card, which has worked
  perfectly well for the past 5 or so years, apparently no longer
  exists.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sat Oct  8 19:52:11 2022
  InstallationDate: Installed on 2018-05-07 (1614 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (57 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1992254] [NEW] PCI/internal sound card not detected

2022-10-08 Thread Alistair Buxton
Public bug reported:

I just rebooted my computer and now my sound card, which has worked
perfectly well for the past 5 or so years, apparently no longer exists.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sat Oct  8 19:52:11 2022
InstallationDate: Installed on 2018-05-07 (1614 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: Upgraded to jammy on 2022-08-12 (57 days ago)
dmi.bios.date: 03/15/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3802
dmi.board.asset.tag: Default string
dmi.board.name: Z170-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug jammy

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just rebooted my computer and now my sound card, which has worked
  perfectly well for the past 5 or so years, apparently no longer
  exists.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sat Oct  8 19:52:11 2022
  InstallationDate: Installed on 2018-05-07 (1614 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (57 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1986542] Re: Issue building the debian source archive

2022-08-22 Thread Alistair
** Tags added: jammy

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

Title:
  Issue building the debian source archive

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  I cannot build the ubuntu source package gst-plugins-
  good1.0_1.20.3-0ubuntu1.dsc. I am doing:

  > dget -q 
http://archive.ubuntu.com/ubuntu/pool/main/g/gst-plugins-good1.0/gst-plugins-good1.0_1.20.3-0ubuntu1.dsc
  > cd gst-plugins-good1.0-1.20.3/
  > DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -us -uc -d -nc -b

  and I receive the error:

  ../gst-libs/gst/basecamerabinsrc/meson.build:28:3: ERROR: Unknown
  variable "static_build".

  I am testing inside of an ubuntu:jammy-20220801 container.

  I have narrowed the issue down to a patch in the changelog on the 15th
  Mar which states "Import plugins from -bad that are needed for main
  applications". This patch imports some "bad" plugins into the source
  but the meson file isn't setup correctly for this to work. Manually
  removing the patches related to the bad plugins fixed the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1986542/+subscriptions


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


[Touch-packages] [Bug 1986542] [NEW] Issue building the debian source archive

2022-08-15 Thread Alistair
Public bug reported:

I cannot build the ubuntu source package gst-plugins-
good1.0_1.20.3-0ubuntu1.dsc. I am doing:

> dget -q 
> http://archive.ubuntu.com/ubuntu/pool/main/g/gst-plugins-good1.0/gst-plugins-good1.0_1.20.3-0ubuntu1.dsc
> cd gst-plugins-good1.0-1.20.3/
> DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -us -uc -d -nc -b

and I receive the error:

../gst-libs/gst/basecamerabinsrc/meson.build:28:3: ERROR: Unknown
variable "static_build".

I am testing inside of an ubuntu:jammy-20220801 container.

I have narrowed the issue down to a patch in the changelog on the 15th
Mar which states "Import plugins from -bad that are needed for main
applications". This patch imports some "bad" plugins into the source but
the meson file isn't setup correctly for this to work. Manually removing
the patches related to the bad plugins fixed the issue.

** Affects: gst-plugins-good1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Issue building the debian source archive

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  I cannot build the ubuntu source package gst-plugins-
  good1.0_1.20.3-0ubuntu1.dsc. I am doing:

  > dget -q 
http://archive.ubuntu.com/ubuntu/pool/main/g/gst-plugins-good1.0/gst-plugins-good1.0_1.20.3-0ubuntu1.dsc
  > cd gst-plugins-good1.0-1.20.3/
  > DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -us -uc -d -nc -b

  and I receive the error:

  ../gst-libs/gst/basecamerabinsrc/meson.build:28:3: ERROR: Unknown
  variable "static_build".

  I am testing inside of an ubuntu:jammy-20220801 container.

  I have narrowed the issue down to a patch in the changelog on the 15th
  Mar which states "Import plugins from -bad that are needed for main
  applications". This patch imports some "bad" plugins into the source
  but the meson file isn't setup correctly for this to work. Manually
  removing the patches related to the bad plugins fixed the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1986542/+subscriptions


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


[Touch-packages] [Bug 1985964] Re: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte

2022-08-14 Thread Alistair Buxton
The full upgrade logs are available on bug 1985966 which I have marked
as a duplicate of bug 1969786.

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

Title:
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position
  1: invalid start byte

Status in apport package in Ubuntu:
  New

Bug description:
  While attempting to do-release-upgrade from 20.04 to 22.04, the
  upgrader crashed, and then the problem report script also crashed,
  leaving behind a corrupted crash report in /var/crash. This bug is
  about the problem report crash. I will report the upgrader crash
  separately.

  Here are the last few lines of output:

  
  Running mktexlsr /var/lib/texmf ... done.
  Building format(s) --all.
  This may take some time... done.
  Processing triggers for dbus (1.12.20-2ubuntu4) ...
  Processing triggers for libvlc-bin:amd64 (3.0.16-1build7) ...
  Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.8+dfsg-1) ...
  Processing triggers for libgdk-pixbuf-2.0-0:i386 (2.42.8+dfsg-1) ...
  Processing triggers for rygel (0.40.3-1ubuntu2) ...
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done

  Calculating the changes

  Calculating the changes

  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-ksd7z8sv/jammy", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeMain.py", line 
241, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 2042, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 1991, in fullUpgrade
  if not self.calcDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 1100, in calcDistUpgrade
  if not self.cache.installTasks(self.tasks):
  AttributeError: 'DistUpgradeController' object has no attribute 'tasks'
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write
  block = f.read(1048576)
File "/usr/lib/python3.8/codecs.py", line 322, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-ksd7z8sv/jammy", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeMain.py", line 
241, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 2042, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 1991, in fullUpgrade
  if not self.calcDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 1100, in calcDistUpgrade
  if not self.cache.installTasks(self.tasks):
  AttributeError: 'DistUpgradeController' object has no attribute 'tasks'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.24
  ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195
  Uname: Linux 5.4.0-124-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   644:0:119:0:2022-08-12 11:36:12.283871223 +0100:2022-08-12 
11:36:12.283871223 +0100:/var/crash/_usr_bin_do-release-upgrade.0.upload
   640:0:119:15237203:2022-08-12 11:36:10.283871173 +0100:2022-08-12 
11:36:44.453251015 +0100:/var/crash/_usr_bin_do-release-upgrade.0.crash
   600:112:119:5:2022-08-12 11:36:12.355865391 +0100:2022-08-12 
11:36:12.355865391 +0100:/var/crash/_usr_bin_do-release-upgrade.0.uploaded
   640:1000:119:2093621:2022-08-12 11:33:46.059253454 +0100:2022-08-12 
11:33:47.059253454 
+0100:/var/crash/_usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.crash
  CurrentDesktop: XFCE
  Date: Fri Aug 12 11:37:21 2022
  InstallationDate: Installed on 2018-05-07 (1557 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2022-08-12 (0 days ago)

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


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

[Touch-packages] [Bug 1985964] [NEW] UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte

2022-08-12 Thread Alistair Buxton
Public bug reported:

While attempting to do-release-upgrade from 20.04 to 22.04, the upgrader
crashed, and then the problem report script also crashed, leaving behind
a corrupted crash report in /var/crash. This bug is about the problem
report crash. I will report the upgrader crash separately.

Here are the last few lines of output:


Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time... done.
Processing triggers for dbus (1.12.20-2ubuntu4) ...
Processing triggers for libvlc-bin:amd64 (3.0.16-1build7) ...
Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.8+dfsg-1) ...
Processing triggers for libgdk-pixbuf-2.0-0:i386 (2.42.8+dfsg-1) ...
Processing triggers for rygel (0.40.3-1ubuntu2) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done

Calculating the changes

Calculating the changes

Traceback (most recent call last):
  File "/tmp/ubuntu-release-upgrader-ksd7z8sv/jammy", line 8, in 
sys.exit(main())
  File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeMain.py", 
line 241, in main
if app.run():
  File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 2042, in run
return self.fullUpgrade()
  File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 1991, in fullUpgrade
if not self.calcDistUpgrade():
  File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 1100, in calcDistUpgrade
if not self.cache.installTasks(self.tasks):
AttributeError: 'DistUpgradeController' object has no attribute 'tasks'
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in 
add_to_existing
self.write(f)
  File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write
block = f.read(1048576)
  File "/usr/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid 
start byte

Original exception was:
Traceback (most recent call last):
  File "/tmp/ubuntu-release-upgrader-ksd7z8sv/jammy", line 8, in 
sys.exit(main())
  File "/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeMain.py", 
line 241, in main
if app.run():
  File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 2042, in run
return self.fullUpgrade()
  File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 1991, in fullUpgrade
if not self.calcDistUpgrade():
  File 
"/tmp/ubuntu-release-upgrader-ksd7z8sv/DistUpgrade/DistUpgradeController.py", 
line 1100, in calcDistUpgrade
if not self.cache.installTasks(self.tasks):
AttributeError: 'DistUpgradeController' object has no attribute 'tasks'

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apport 2.20.11-0ubuntu27.24
ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195
Uname: Linux 5.4.0-124-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
 644:0:119:0:2022-08-12 11:36:12.283871223 +0100:2022-08-12 11:36:12.283871223 
+0100:/var/crash/_usr_bin_do-release-upgrade.0.upload
 640:0:119:15237203:2022-08-12 11:36:10.283871173 +0100:2022-08-12 
11:36:44.453251015 +0100:/var/crash/_usr_bin_do-release-upgrade.0.crash
 600:112:119:5:2022-08-12 11:36:12.355865391 +0100:2022-08-12 
11:36:12.355865391 +0100:/var/crash/_usr_bin_do-release-upgrade.0.uploaded
 640:1000:119:2093621:2022-08-12 11:33:46.059253454 +0100:2022-08-12 
11:33:47.059253454 
+0100:/var/crash/_usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-2.0.1000.crash
CurrentDesktop: XFCE
Date: Fri Aug 12 11:37:21 2022
InstallationDate: Installed on 2018-05-07 (1557 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to focal on 2022-08-12 (0 days ago)

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position
  1: invalid start byte

Status in apport package in Ubuntu:
  New

Bug description:
  While attempting to do-release-upgrade from 20.04 to 22.04, the
  upgrader crashed, and then the problem report script also crashed,
  leaving behind a corrupted crash report in /var/crash. This bug is
  about the problem report crash. I will report the upgrader crash
  separately.

  Here are the last few lines of output:

  
  Running mktexlsr /var/lib/texmf ... done.
  Building format(s) -

[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug

2022-03-18 Thread Alistair Cunningham
Is there any news on this? The problem still happens after upgrading to
Ubuntu 22.04. There don't appear to have been updates since I last
reported this for 21.10.

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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


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


[Touch-packages] [Bug 1956835] Re: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2022-01-15 Thread Alistair
I have ZFS (ZSYS) installed and the snapshots on a laptop can fill up the 
space.  I was able to free up the disk space by loading the zsys config file 
(not installed by default) and reduce the number of "keep" snapshots.  ZSYS 
assumes that it is running on a machine that is up most of the time, but if it 
is not, then there can be large changes (kernel updates) within more than 
expected snapshots, hence space fills up faster than may have been expected.
The actual space available to /boot is 2G, but when the snapshots don't get 
garbage collected, the free space gets too small for updates to run.
zsys assumptions and garbage collection default rules need to be re-considered 
based on usage, even if it is just described in the man/info pages, rather than 
needing to look them up in didrocks blogs (again).
If the problem was caused by lack of /boot space, close this bug.

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

Title:
  package linux-firmware 1.187.24 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  After updating the system, rebooted and this error appeared.
  Fixed a problem related to /boot/grub/grubenv - "Error in environment" and 
grub-common.service
  by providing absolute path to grub-editenv.  /boot/grub/grubenv was full of 
0x0, rather than 0x2323 as it has now.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.24
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   3520 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 17:37:06 2022
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-11-12 (422 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x1by5v@/vmlinuz-5.11.0-44-generic 
root=ZFS=rpool/ROOT/ubuntu_x1by5v ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.24 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2018
  dmi.bios.release: 15.113
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.71
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.38
  dmi.chassis.asset.tag: CNU3109W10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 66.56
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.71:bd04/12/2018:br15.113:efr66.56:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:skuC3Q91UC#ABU:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8470p
  dmi.product.sku: C3Q91UC#ABU
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956835/+subscriptions


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


[Touch-packages] [Bug 1956835] [NEW] package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2022-01-08 Thread Alistair
Public bug reported:

After updating the system, rebooted and this error appeared.
Fixed a problem related to /boot/grub/grubenv - "Error in environment" and 
grub-common.service
by providing absolute path to grub-editenv.  /boot/grub/grubenv was full of 
0x0, rather than 0x2323 as it has now.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.24
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alistair   3520 F pulseaudio
CasperMD5CheckResult: skip
Date: Sat Jan  8 17:37:06 2022
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-11-12 (422 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Hewlett-Packard HP EliteBook 8470p
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x1by5v@/vmlinuz-5.11.0-44-generic 
root=ZFS=rpool/ROOT/ubuntu_x1by5v ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.24 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/12/2018
dmi.bios.release: 15.113
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68ICF Ver. F.71
dmi.board.name: 179B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 42.38
dmi.chassis.asset.tag: CNU3109W10
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.ec.firmware.release: 66.56
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.71:bd04/12/2018:br15.113:efr66.56:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:skuC3Q91UC#ABU:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 8470p
dmi.product.sku: C3Q91UC#ABU
dmi.product.version: A1029D1102
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package focal

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

Title:
  package linux-firmware 1.187.24 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After updating the system, rebooted and this error appeared.
  Fixed a problem related to /boot/grub/grubenv - "Error in environment" and 
grub-common.service
  by providing absolute path to grub-editenv.  /boot/grub/grubenv was full of 
0x0, rather than 0x2323 as it has now.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.24
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USER    PID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   3520 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 17:37:06 2022
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-11-12 (422 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x1by5v@/vmlinuz-5.11.0-44-generic 
root=ZFS=rpool/ROOT/ubuntu_x1by5v ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.24 failed to install/upgrade: inst

[Touch-packages] [Bug 1947871] Re: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2021-10-20 Thread Alistair
Identified that the command :

update-initramfs: Generating /boot/initrd.img-5.11.0-38-generic

required approx 88M of disk space on /boot, but I only had 73M:
df -h /boot
bpool/BOOT/ubuntu_l3g9y7  286M  213M   73M  75% /boot

Problem resolved by manually running zsys garbage collection (laptop, so
scheduled jobs are unable  to run when the laptop is off/hybernating.

To demonstrate, use "zsysctl machine show to list the ZFS snapshots that
are part of zsys.  Use with wc to show the number of snapshots before
garbage collection and after, hopefully with a reduction:

zsysctl machine show|wc
127 4687959
zsysctl service gc
zsysctl machine show|wc
105 3816350

Free space after this has run:
df -lh /boot
FilesystemSize  Used Avail Use% Mounted on
bpool/BOOT/ubuntu_l3g9y7  375M  202M  174M  54% /boot

Monitoring the Avail space for boot while re-running apt upgrade :
 df -h /boot
FilesystemSize  Used Avail Use% Mounted on
bpool/BOOT/ubuntu_l3g9y7  375M  289M   86M  78% /boot
before returning to 174M available.
zfs list -r bpool
NAME   USED  AVAIL REFER  MOUNTPOINT
bpool 1.58G   174M   96K  /boot
bpool/BOOT1.58G   174M   96K  none
bpool/BOOT/ubuntu_l3g9y7  1.58G   174M  201M  /boot

The used space in this case is in zfs snapshots, hence zsys garbage
collection resolved this.

Where zfs and zsys are installed, checking free space and "bloat"
required space, with the option/suggestion to run "zsysctl service gc".

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

Title:
  package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  System error reported - while reading webpage.  last login in last 10 
minutes, so possibly an auto update.
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  Codename: focal
  uname -a
  Linux alistair-HP-EliteBook-8470p 5.11.0-37-generic #41~20.04.2-Ubuntu SMP 
Fri Sep 24 09:06:38 UTC 2021 x86_64 x86_64 x86_64

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Oct 20 13:55:09 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2020-11-12 (342 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1947871/+subscriptions


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


[Touch-packages] [Bug 1947871] [NEW] package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2021-10-20 Thread Alistair
Public bug reported:

System error reported - while reading webpage.  last login in last 10 minutes, 
so possibly an auto update.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.3 LTS
Release:20.04
Codename:   focal
uname -a
Linux alistair-HP-EliteBook-8470p 5.11.0-37-generic #41~20.04.2-Ubuntu SMP Fri 
Sep 24 09:06:38 UTC 2021 x86_64 x86_64 x86_64

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Oct 20 13:55:09 2021
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2020-11-12 (342 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: initramfs-tools
Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check third-party-packages

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

Title:
  package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  System error reported - while reading webpage.  last login in last 10 
minutes, so possibly an auto update.
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  Codename: focal
  uname -a
  Linux alistair-HP-EliteBook-8470p 5.11.0-37-generic #41~20.04.2-Ubuntu SMP 
Fri Sep 24 09:06:38 UTC 2021 x86_64 x86_64 x86_64

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Oct 20 13:55:09 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2020-11-12 (342 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1947871/+subscriptions


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


[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug

2021-10-01 Thread Alistair Cunningham
This still happens after upgrading to Ubuntu 21.10. Is there any news on
fixing it?

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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


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


[Touch-packages] [Bug 1928789] [NEW] bpool free space low caused package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returne

2021-05-18 Thread Alistair
utozsys_wyysrc
Found initrd image: initrd.img-5.8.0-41-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_wyysrc
Found linux image: vmlinuz-5.8.0-40-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_wyysrc
Found initrd image: initrd.img-5.8.0-40-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_wyysrc
Found linux image: vmlinuz-5.8.0-43-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_88t86h
Found initrd image: initrd.img-5.8.0-43-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_88t86h
Found linux image: vmlinuz-5.8.0-41-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_88t86h
Found initrd image: initrd.img-5.8.0-41-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_88t86h
Found linux image: vmlinuz-5.8.0-40-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_88t86h
Found initrd image: initrd.img-5.8.0-40-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_88t86h
Found linux image: vmlinuz-5.8.0-44-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_bnx720
Found initrd image: initrd.img-5.8.0-44-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_bnx720
Found linux image: vmlinuz-5.8.0-43-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_bnx720
Found initrd image: initrd.img-5.8.0-43-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_bnx720
Found linux image: vmlinuz-5.8.0-41-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_bnx720
Found initrd image: initrd.img-5.8.0-41-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_bnx720
Found linux image: vmlinuz-5.8.0-40-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_bnx720
Found initrd image: initrd.img-5.8.0-40-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_bnx720
Found linux image: vmlinuz-5.8.0-44-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_8onazk
Found initrd image: initrd.img-5.8.0-44-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_8onazk
Found linux image: vmlinuz-5.8.0-43-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_8onazk
Found initrd image: initrd.img-5.8.0-43-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_8onazk
Found linux image: vmlinuz-5.8.0-41-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_8onazk
Found initrd image: initrd.img-5.8.0-41-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_8onazk
Found linux image: vmlinuz-5.8.0-40-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_8onazk
Found initrd image: initrd.img-5.8.0-40-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_8onazk
Found linux image: vmlinuz-5.8.0-44-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_2plbti
Found initrd image: initrd.img-5.8.0-44-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_2plbti
Found linux image: vmlinuz-5.8.0-43-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_2plbti
Found initrd image: initrd.img-5.8.0-43-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_2plbti
Found linux image: vmlinuz-5.8.0-44-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_dzjytk
Found initrd image: initrd.img-5.8.0-44-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_dzjytk
Found linux image: vmlinuz-5.8.0-43-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_dzjytk
Found initrd image: initrd.img-5.8.0-43-generic in 
rpool/ROOT/ubuntu_l3g9y7@autozsys_dzjytk
device-mapper: reload ioctl on osprober-linux-sda4  failed: Device or resource 
busy
Command failed.
Adding boot menu entry for UEFI Firmware Settings
done
Removing linux-modules-5.8.0-49-generic (5.8.0-49.55~20.04.1) ...
Removing python3-virtualenv (20.0.17-1ubuntu0.3) ...
Removing python3-appdirs (1.4.3-2.1) ...
Removing python3-distlib (0.3.0-1) ...
Removing python3-filelock (3.0.12-2) ...
Removing python3-importlib-metadata (1.5.0-1) ...
Removing python3-zipp (1.0.0-1) ...
Removing python3-more-itertools (4.2.0-1build1) ...
Setting up initramfs-tools (0.136ubuntu6.4) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-firmware (1.187.12) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-53-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=43e308d8-51f7-4134-8540-ad8d05371f96)
I: Set the RESUME variable to override this.
update-initramfs: Generating /boot/initrd.img-5.8.0-50-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=43e308d8-51f7-4134-8540-ad8d05371f96)
I: Set the RESUME variable to override this.
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for initramfs-tools (0.136ubuntu6.4) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-53-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=43e308d8-51f7-4134-8540-ad8d05371f96)
I: Set the RESUME variable to override this.
ZSys is adding automatic system snapshot to GRUB menu
alistair@alistair-HP-EliteBook-8470p:~$ df -h
FilesystemSize  Used Avail Use% Mounted 
on
udev  3.8G 0  3.8G   0% /dev
tmpfs 784M  2.0M  782M   1% /run
rpool/ROOT/ubuntu_l3g9y7  377G  4.4G  373G   2% /
tmpfs 3.9G 0  3.9G   0% /dev/shm
tmpfs  

[Touch-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

2020-12-09 Thread Alistair Cunningham
Unfortunately it's not fixed. It doesn't happen every time, but perhaps
half the time. I haven't been able to determine any pattern.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Touch-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

2020-12-09 Thread Alistair Cunningham
Unfortunately it's not fixed. It doesn't happen every time, but perhaps
half the time. I haven't been able to determine any pattern.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Touch-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

2020-12-04 Thread Alistair Cunningham
This *appears* to be fixed in the latest Ubuntu 20.10 updates.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Touch-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

2020-12-04 Thread Alistair Cunningham
This *appears* to be fixed in the latest Ubuntu 20.10 updates.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Touch-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

2020-10-12 Thread Alistair Cunningham
This is still happening after upgrading to Ubuntu 20.10.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug

2020-10-05 Thread Alistair Cunningham
This still happens after upgrading to Ubuntu 20.10:

grep: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
grep: /usr/share/apport/symptoms/installation.py: No such file or directory
grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory
qgrep: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
grep: /usr/share/apport/symptoms/installation.py: No such file or directory
grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

Note that that I have the following alias set for ls:

alias ls='ls -N --color=yes --time-style=long-iso'

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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

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


[Touch-packages] [Bug 1893655] Re: Headphones connect but don't appear in the audio devices list

2020-09-02 Thread Alistair Cunningham
I logged out, and logged in again using regular Ubuntu, and the same
happens. When I switch the headphones on, the Bluetooth settings show
the headphones connected for a second or so, then disconnected. They
don't appear in the sounds settings.

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

Title:
  Headphones connect but don't appear in the audio devices list

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Touch-packages] [Bug 1893655] Re: Headphones connect but don't appear as audio output

2020-09-01 Thread Alistair Cunningham
The workaround doesn't seem to help. I also notice that when the
headphones connect, the Bluetooth settings window shows them connected
for a second or so, then disconnected again.

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

Title:
  Headphones connect but don't appear as audio output

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Touch-packages] [Bug 1893655] Re: Headphones connect but don't appear as audio output

2020-09-01 Thread Alistair Cunningham
They don't appear in the audio device list at all. Thank you for the
workaround; I'll give it a try and let you know if it helps.

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

Title:
  Headphones connect but don't appear as audio output

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Touch-packages] [Bug 1893655] [NEW] Headphones connect but don't appear as audio output

2020-08-31 Thread Alistair Cunningham
Public bug reported:

When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
laptop at Bluetooth level, but don't appear as an audio device. I have
to remove them in the Ubuntu Bluetooth settings, and then re-pair them,
every time. This is rather inconvenient. This started happening after
upgrading to Ubuntu 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
Uname: Linux 5.6.0-1021-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Aug 31 14:48:53 2020
InstallationDate: Installed on 2020-07-14 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20U9CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET19W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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


** Tags: amd64 apport-bug focal

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

Title:
  Headphones connect but don't appear as audio output

Status in bluez package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Touch-packages] [Bug 1882610] [NEW] Lenovo E590 Graphics problems using standard Ubuntu/Budgie install

2020-06-08 Thread Alistair
Public bug reported:

Ive had major problems (seg errors and various) stopping several apps which 
were all working a couple of months ago, on my new Lenovo E590 Thinkpad 
notebook.
sudo lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey 
Lake) (rev 02)

What helped me sort it was the following command: sudo lshw -C display
which showed the driver was xserver-xorg-video-intel which is not recommended; 
its older and problematic. Aptitude recommends use system default which is 
driver=i915).

After removing this errant driver, its solved my applications crashing
problems and more.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
Date: Tue Jun  9 12:42:39 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:5072]
InstallationDate: Installed on 2020-01-23 (137 days ago)
InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200119)
LightdmDisplayLog:
 (EE) event4  - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and 
discarded.
 See 
https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html
 for details
 (EE) client bug: timer event4 keyboard: scheduled expiry is in the past 
(-1435ms), your system is too slow
 (EE) client bug: timer event4 keyboard: scheduled expiry is in the past 
(-821ms), your system is too slow
 (EE) client bug: timer event4 keyboard: scheduled expiry is in the past 
(-204ms), your system is too slow
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:2130 Acer, Inc Integrated Camera
 Bus 001 Device 002: ID 8087:0025 Intel Corp. 
 Bus 001 Device 008: ID 14cd:6600 Super Top M110E PATA bridge
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20NBCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=fab243f0-09ed-4b95-8ed6-995ffdde426c ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: R0YET42W (1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NBCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0YET42W(1.25):bd01/13/2020:svnLENOVO:pn20NBCTO1WW:pvrThinkPadE590:rvnLENOVO:rn20NBCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E590
dmi.product.name: 20NBCTO1WW
dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590
dmi.product.version: ThinkPad E590
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Lenovo E590 Graphics problems using standard Ubuntu/Budgie install

Status in xorg package in Ubuntu:
  New

Bug description:
  Ive had major problems (seg errors and various) stopping several apps which 
were all working a couple of months ago, on my new Lenovo E590 Thinkpad 
notebook.
  sudo lspci | grep -i vga
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 
(Whiskey Lake) (rev 02)

  What helped me sort it was the following command: sudo lshw -C display
  which showed the driver was xserver-xorg-video-intel which is not 
recommended; its older and problematic. Aptitude recommends use system default 
which is driver=i915).

  After removing this errant driver, its solved my applications crashing
  problems and more.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2

[Touch-packages] [Bug 1877829] [NEW] Won't reconnect to shared headphones

2020-05-09 Thread Alistair Cunningham
Public bug reported:

In Ubuntu 19.04, I could use my Sony WH-1000XM3 headphones with both my
laptop running Ubuntu, and my Android smartphone. The headphones would
pair with both, and I could simply re-enable the connection in Ubuntu or
Android to connect to the headphones if the other device had been using
the headphones last.

In Ubuntu 20.04, Ubuntu now refuses to reconnect to the headphones if my
Android phone was using the headphones last. I have to manually unpair
the headphones and re-pair them again. This is very inconvenient.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun May 10 15:44:22 2020
InstallationDate: Installed on 2017-08-16 (997 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HFCTO1WW
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to focal on 2020-04-12 (27 days ago)
dmi.bios.date: 11/29/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET57W (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET57W(1.36):bd11/29/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:20456 acl:96 sco:0 events:2692 errors:0
TX bytes:604938 acl:84 sco:0 commands:2573 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T23:41:27.085337

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


** Tags: amd64 apport-bug focal

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

Title:
  Won't reconnect to shared headphones

Status in bluez package in Ubuntu:
  New

Bug description:
  In Ubuntu 19.04, I could use my Sony WH-1000XM3 headphones with both
  my laptop running Ubuntu, and my Android smartphone. The headphones
  would pair with both, and I could simply re-enable the connection in
  Ubuntu or Android to connect to the headphones if the other device had
  been using the headphones last.

  In Ubuntu 20.04, Ubuntu now refuses to reconnect to the headphones if
  my Android phone was using the headphones last. I have to manually
  unpair the headphones and re-pair them again. This is very
  inconvenient.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 10 15:44:22 2020
  InstallationDate: Installed on 2017-08-16 (997 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HFCTO1WW
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to focal on 2020-04-12 (27 days ago)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WE

[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug

2020-05-04 Thread Alistair Cunningham
This also happens on 20.04. It now gives:

/usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
grep: /usr/share/apport/symptoms/installation.py: No such file or directory
grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  New

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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

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


[Touch-packages] [Bug 1867982] [NEW] unable to copy and paste login and password

2020-03-18 Thread Alistair
Public bug reported:

Select eg Google account when you have your user and password in clipboard.
In the new account interface, cant paste into fields.
Expected is paste.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-online-accounts 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Thu Mar 19 08:37:01 2020
InstallationDate: Installed on 2020-03-15 (2 days ago)
InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200312)
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  unable to copy and paste login and password

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

Bug description:
  Select eg Google account when you have your user and password in clipboard.
  In the new account interface, cant paste into fields.
  Expected is paste.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Thu Mar 19 08:37:01 2020
  InstallationDate: Installed on 2020-03-15 (2 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200312)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected

2019-12-31 Thread Alistair Cunningham
I can confirm that installing these packages onto Ubuntu 19.10 fixes the
problem for my Sony WH-1000XM3. Thank you very much Daniel!

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

Title:
  Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low
  quality headset mode and fails to switch to A2DP when selected

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

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

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


[Touch-packages] [Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected

2019-12-10 Thread Alistair Cunningham
Is anything happening with solving this?

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

Title:
  Bluetooth headphones/speaker default to low quality headset mode and
  fails to switch to A2DP when selected

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

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

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


[Touch-packages] [Bug 1854392] Re: Bluetooth headphones won't use A2DP on reconnect

2019-11-28 Thread Alistair Cunningham
** Attachment added: "headphones"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+attachment/5308568/+files/headphones

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

Title:
   Bluetooth headphones won't use A2DP on reconnect

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  *** This bug is the same as bug 1724919, but is NOT A DUPLICATE
  because that bug was closed because it was reported for Ubuntu 17.10,
  which is out of support. This bug is for newer versions, such as
  19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. ***

  On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones
  pair using Bluetooth with no problems, and use A2DP by default. If I
  then power off the headphones and power them back on, they reconnect
  but use HSP/HFP and sound terrible. If I manually go into the sound
  settings, A2DP is offered as an option, but selecting it doesn't take
  effect. The headphones remain stuck in HSP/HFP mode.

  Unpairing the headphones and re-pairing them again selects A2DP by
  default, until the next time I switch the headphones off. Then they're
  back to stuck in HSP/HFP until I unpair them once again. I therefore
  need to unpair and re-pair them every time I want to use them, which
  is a nuisance.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Nov 28 13:28:52 2019
  InstallationDate: Installed on 2017-08-16 (833 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0
TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337

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

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


[Touch-packages] [Bug 1854392] Re: Bluetooth headphones won't use A2DP on reconnect

2019-11-28 Thread Alistair Cunningham
The only other Bluetooth headphones I've had access to recently were a
pair of Bose QC35 (1st generation). They showed up in the list of
visible BT devices, but my laptop couldn't connect to them at all,
despite numerous attempts. As a result, I bought the Sonys and got rid
of the Bose.

If you take a look at bug 1724919, you'll see that other people have the
same problem with other models of headphones.

Attached is a copy of /var/log/syslog since last boot, with minor
cleaning. Note that just after booting I wanted to use the headphones
for real, so I manually ran the attached 'headphones' script to
disconnect the headphones, reconnect them, and force A2DP mode. Then at
18:09:17, I deliberately recreated the bug by connecting the headphones,
and unsuccessfully trying to set A2DP in the sound settings.

** Attachment added: "syslog_cleaned.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+attachment/5308567/+files/syslog_cleaned.txt

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

Title:
   Bluetooth headphones won't use A2DP on reconnect

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  *** This bug is the same as bug 1724919, but is NOT A DUPLICATE
  because that bug was closed because it was reported for Ubuntu 17.10,
  which is out of support. This bug is for newer versions, such as
  19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. ***

  On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones
  pair using Bluetooth with no problems, and use A2DP by default. If I
  then power off the headphones and power them back on, they reconnect
  but use HSP/HFP and sound terrible. If I manually go into the sound
  settings, A2DP is offered as an option, but selecting it doesn't take
  effect. The headphones remain stuck in HSP/HFP mode.

  Unpairing the headphones and re-pairing them again selects A2DP by
  default, until the next time I switch the headphones off. Then they're
  back to stuck in HSP/HFP until I unpair them once again. I therefore
  need to unpair and re-pair them every time I want to use them, which
  is a nuisance.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Nov 28 13:28:52 2019
  InstallationDate: Installed on 2017-08-16 (833 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0
TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337

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

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


[Touch-packages] [Bug 1854392] Re: Bluetooth headphones won't use A2DP on reconnect

2019-11-28 Thread Alistair Cunningham
How do I run blueman after installing it?

$ blueman

Command 'blueman' not found, did you mean:

  command 'bluemon' from deb bluemon (1.4-7)

Try: sudo apt install 

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

Title:
   Bluetooth headphones won't use A2DP on reconnect

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  *** This bug is the same as bug 1724919, but is NOT A DUPLICATE
  because that bug was closed because it was reported for Ubuntu 17.10,
  which is out of support. This bug is for newer versions, such as
  19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. ***

  On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones
  pair using Bluetooth with no problems, and use A2DP by default. If I
  then power off the headphones and power them back on, they reconnect
  but use HSP/HFP and sound terrible. If I manually go into the sound
  settings, A2DP is offered as an option, but selecting it doesn't take
  effect. The headphones remain stuck in HSP/HFP mode.

  Unpairing the headphones and re-pairing them again selects A2DP by
  default, until the next time I switch the headphones off. Then they're
  back to stuck in HSP/HFP until I unpair them once again. I therefore
  need to unpair and re-pair them every time I want to use them, which
  is a nuisance.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Nov 28 13:28:52 2019
  InstallationDate: Installed on 2017-08-16 (833 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0
TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337

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

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


[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

2019-11-28 Thread Alistair Cunningham
Because no-one is willing to re-open this bug, I have opened new bug
1854392 for this same problem on newer versions of Ubuntu such as 19.10.
Those who are affected by this problem, please add a note to bug 1854392
stating that you're affected.

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1854392] [NEW] Bluetooth headphones won't use A2DP on reconnect

2019-11-28 Thread Alistair Cunningham
Public bug reported:

*** This bug is the same as bug 1724919, but is NOT A DUPLICATE because
that bug was closed because it was reported for Ubuntu 17.10, which is
out of support. This bug is for newer versions, such as 19.10. PLEASE DO
NOT MARK THIS BUG AS A DUPLICATE. ***

On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair
using Bluetooth with no problems, and use A2DP by default. If I then
power off the headphones and power them back on, they reconnect but use
HSP/HFP and sound terrible. If I manually go into the sound settings,
A2DP is offered as an option, but selecting it doesn't take effect. The
headphones remain stuck in HSP/HFP mode.

Unpairing the headphones and re-pairing them again selects A2DP by
default, until the next time I switch the headphones off. Then they're
back to stuck in HSP/HFP until I unpair them once again. I therefore
need to unpair and re-pair them every time I want to use them, which is
a nuisance.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: bluez 5.50-0ubuntu4
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Nov 28 13:28:52 2019
InstallationDate: Installed on 2017-08-16 (833 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HFCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago)
dmi.bios.date: 08/30/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET56W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0
TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337

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


** Tags: amd64 apport-bug eoan

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

Title:
   Bluetooth headphones won't use A2DP on reconnect

Status in bluez package in Ubuntu:
  New

Bug description:
  *** This bug is the same as bug 1724919, but is NOT A DUPLICATE
  because that bug was closed because it was reported for Ubuntu 17.10,
  which is out of support. This bug is for newer versions, such as
  19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. ***

  On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones
  pair using Bluetooth with no problems, and use A2DP by default. If I
  then power off the headphones and power them back on, they reconnect
  but use HSP/HFP and sound terrible. If I manually go into the sound
  settings, A2DP is offered as an option, but selecting it doesn't take
  effect. The headphones remain stuck in HSP/HFP mode.

  Unpairing the headphones and re-pairing them again selects A2DP by
  default, until the next time I switch the headphones off. Then they're
  back to stuck in HSP/HFP until I unpair them once again. I therefore
  need to unpair and re-pair them every time I want to use them, which
  is a nuisance.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Nov 28 13:28:52 2019
  InstallationDate: Installed on 2017-08-16 (833 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluet

[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

2019-11-21 Thread Alistair Cunningham
For those with Sony headphones, and who are affected by this annoying
bug, the attached "headphones" Perl script is a partial workaround.
You'll need to edit it for the bluetooth address of your headphones. Run
it after switching your headphones on and they connect, and it sets
A2DP.

** Attachment added: "headphones"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+attachment/5306921/+files/headphones

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

2019-11-21 Thread Alistair Cunningham
Can this please be re-opened? Daniel van Vugt marked it as "won't fix"
in comment #14 due to Ubuntu 17.10 being end of life, but numerous
people are still encountering the problem with more recent versions. I'm
encountering it on Ubuntu 19.10 and a new Sony WH-1000XM3.

If this bug can't be re-opened, should we create a new bug for more
recent versions of Ubuntu?

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug

2019-11-11 Thread Alistair Cunningham
Still the same, unfortunately.

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  New

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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

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


[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug

2019-11-06 Thread Alistair Cunningham
# ls -l /usr/share/apport/symptoms/ubuntu-release-upgrader.py
-rw-r--r-- 1 root root 214 May 17 16:32 
/usr/share/apport/symptoms/ubuntu-release-upgrader.py

# dpkg -S /usr/share/apport/symptoms/ubuntu-release-upgrader.py
apport-symptoms: /usr/share/apport/symptoms/ubuntu-release-upgrader.py

# debsums apport-symptoms
/usr/share/apport/symptoms/_audio_checks.py   OK
/usr/share/apport/symptoms/_audio_data.py OK
/usr/share/apport/symptoms/_audio_mixercontrol.py OK
/usr/share/apport/symptoms/audio.py   OK
/usr/share/apport/symptoms/display.py OK
/usr/share/apport/symptoms/security.pyOK
/usr/share/apport/symptoms/storage.py OK
/usr/share/apport/symptoms/ubuntu-release-upgrader.py OK
/usr/share/doc/apport-symptoms/changelog.gz   OK
/usr/share/doc/apport-symptoms/copyright  OK

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  New

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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

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


[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug

2019-11-05 Thread Alistair Cunningham
# ls -l /usr/share/apport/symptoms/dist-upgrade.py
lrwxrwxrwx 1 root root 26 May 17 16:32 
/usr/share/apport/symptoms/dist-upgrade.py -> ubuntu-release-upgrader.py

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  New

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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

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


[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug

2019-11-05 Thread Alistair Cunningham
apport-symptoms is installed, but this keeps happening:

# dpkg -l apport-symptoms 
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture Description
+++-===---=
ii  apport-symptoms 0.22 all  symptom scripts for apport

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  New

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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

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


[Touch-packages] [Bug 1850804] [NEW] Tab completion warnings with ubuntu-bug

2019-10-31 Thread Alistair Cunningham
Public bug reported:

When running ubuntu-bug on the command line, and tab completing the
package name, the following warnings are printed:

/usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apport 2.20.11-0ubuntu8.1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog:
 
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Oct 31 10:54:43 2019
InstallationDate: Installed on 2017-08-16 (805 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  New

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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

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


[Touch-packages] [Bug 1850051] [NEW] Bluetooth headphones won't use A2DP on reconnect

2019-10-27 Thread Alistair Cunningham
Public bug reported:

On Ubuntu 19.04 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair
using Bluetooth with no problems, and use A2DP by default. If I then
power off the headphones and power them back on, they reconnect but use
HSP/HFP and sound terrible. If I manually go into the sound settings,
A2DP is offered as an option, but selecting it doesn't take effect. The
headphones remain stuck in HSP/HFP mode.

Unpairing the headphones and re-pairing them again selects A2DP by
default, until the next time I switch the headphones off. Then they're
back to stuck in HSP/HFP until I unpair them once again. I therefore
need to unpair and re-pair them every time I want to use them, which is
a nuisance.

I'm not sure which package is responsible for handling this, so am
reporting to for bluez since it provides /etc/bluetooth/main.conf. If
I'm wrong, please re-assign.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Oct 27 10:43:21 2019
InstallationDate: Installed on 2017-08-16 (801 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HFCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to eoan on 2019-10-04 (22 days ago)
dmi.bios.date: 08/30/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET56W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:730576 acl:159 sco:13734 events:3688 errors:0
TX bytes:2014957 acl:979 sco:13705 commands:2568 errors:0

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


** Tags: amd64 apport-bug eoan

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

Title:
  Bluetooth headphones won't use A2DP on reconnect

Status in bluez package in Ubuntu:
  New

Bug description:
  On Ubuntu 19.04 on my Thinkpad T470s, my Sony WH-1000XM3 headphones
  pair using Bluetooth with no problems, and use A2DP by default. If I
  then power off the headphones and power them back on, they reconnect
  but use HSP/HFP and sound terrible. If I manually go into the sound
  settings, A2DP is offered as an option, but selecting it doesn't take
  effect. The headphones remain stuck in HSP/HFP mode.

  Unpairing the headphones and re-pairing them again selects A2DP by
  default, until the next time I switch the headphones off. Then they're
  back to stuck in HSP/HFP until I unpair them once again. I therefore
  need to unpair and re-pair them every time I want to use them, which
  is a nuisance.

  I'm not sure which package is responsible for handling this, so am
  reporting to for bluez since it provides /etc/bluetooth/main.conf. If
  I'm wrong, please re-assign.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Oct 27 10:43:21 2019
  InstallationDate: Installed on 2017-08-16 (801 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
   Bus 001 Device 004: ID 

[Touch-packages] [Bug 1812948] [NEW] bug search

2019-01-22 Thread Alistair
Public bug reported:

just did a search and these bugs came up.I'm not sure haw they work

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Jan 22 19:38:51 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 18.03.00, 4.15.0-43-generic, x86_64: installed
 nvidia, 390.77, 4.15.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GF108 [GeForce GT 620] [3842:2625]
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
 Bus 002 Device 004: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
 Bus 002 Device 002: ID 062a: Creative Labs Optical mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=c599b74a-de09-473c-b0e9-39538d42a83d ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/31/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: N68C-GS FX
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:bd10/31/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.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.
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: Tue Jan 22 17:27:30 2019
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputHID 062a:MOUSE, id 8
 inputDELL DELL USB Keyboard KEYBOARD, id 9
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  bug search

Status in xorg package in Ubuntu:
  New

Bug description:
  just did a search and these bugs came up.I'm not sure haw they
  work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: No

[Touch-packages] [Bug 1811731] [NEW] compuer freeze

2019-01-14 Thread Alistair
Public bug reported:

computer system freeze

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jan 14 14:57:48 2019
DistUpgraded: 2018-09-05 17:29:52,691 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GF108 [GeForce GT 620] [3842:2625]
InstallationDate: Installed on 2015-01-24 (1451 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 062a: Creative Labs Optical mouse
 Bus 002 Device 002: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
 Bus 002 Device 004: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=c599b74a-de09-473c-b0e9-39538d42a83d ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-09-06 (130 days ago)
dmi.bios.date: 10/31/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: N68C-GS FX
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:bd10/31/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.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.
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.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: Wed Sep  5 09:58:08 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDELL DELL USB Keyboard KEYBOARD, id 8
 inputHID 062a:MOUSE, id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  compuer freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  computer system freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jan 14 14:57:48 2019
  DistUpgraded: 2018-09-05 17:29:52,691 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 620] [3842:2625]
  InstallationDate: Installed on 2015-01-24 (1451 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 062a: Creative Labs Optical mouse
   Bus 002 Device 002: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
   Bus 002 Device 004: ID 

[Touch-packages] [Bug 1332623] Re: Thunar behaves inconsistently with USB flash drive FAT32 partitions

2018-12-27 Thread Alistair Buxton
I have Bionic/18.04/glib 2.56 and this bug still happens.

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

Title:
  Thunar behaves inconsistently with USB flash drive FAT32 partitions

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Fix Released

Bug description:
  I installed Xubuntu 14.04 and performed no customizations or
  reconfigurations.

  Observation:  Thunar 1.6.3 ("File Manager" from menu) on Xubuntu 14.04 
handles write permission to inserted USB flash drives inconsistently:
  * I am able to create a nil file on the flash drive with Thunar and edit it.  
Clearly, the flash drive is not read-only.
  * Using Thunar, I cannot copy an existing file (E.g. ~/.profile) and paste it 
on the flash drive - "destination is read-only" (not true!).
  * However, in a terminal window, `cp` with the flash drive as a destination 
succeeds.

  I tried this on drives by different manufacturers and with differing
  capacities and on two different Xubuntu 14.04 installations.

  There might be a configuration change for Thunar to allow paste to
  flash drives.  If so, this should be enabled when Thunar is installed
  as this behaviour is what users expect.

  Note: I created the FAT32 partition with `gparted` on Linux.  I also
  got the same results after creating a FAT32 partition using an MACOSX
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: thunar 1.6.3-1ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jun 20 11:30:40 2014
  InstallationDate: Installed on 2014-06-19 (1 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: thunar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-04-09 Thread Alistair Buxton
*** This bug is a duplicate of bug 1749546 ***
https://bugs.launchpad.net/bugs/1749546

The Bluez timeout errors still show up in ~/.xsession-errors at least on
hardware without Bluetooth. However, it seems to be harmless.

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-04-03 Thread Alistair Buxton
One final thing: this does not affect Ubuntu desktop after install. But
it does affect the Ubuntu live image, which takes an extra minute or so
to boot. It seems that the Ubuntu desktop installer rebuilds the system
font cache during install.

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-04-03 Thread Alistair Buxton
Some more: touching the system cache files doesn't make it work.

Binary diff on the cache files before and after running fc-cache shows
this:

63 c7 c3 5a 00 00 00 00  47 72 ce 15 00 00 00 00
63 c7 c3 5a 00 00 00 00  00 00 00 00 00 00 00 00

Before, at offset 0x38, the "bad" cache files have a non-zero 32 bit
number. The number is different in every "bad" cache file. It is always
zero in the "good" files. This is the only difference. The rest of each
file is identical.

I don't know what this field represents. Need a fontconfig expert to
look at this.

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-04-03 Thread Alistair Buxton
Another piece of the puzzle: if you run:

sudo fc-cache -fv

this will rebuild the system font cache in /var/cache/fontconfig

If you then delete the user's cache in ~/.cache/fontconfig and re-log,
there is no delay... and the user's font cache will NOT be rebuilt.

After a delayed login, user's cache and the system cache appear to
contain the same files.

So it looks as if something thinks the system cache is out of date and
wants to rebuild it. Whatever it is only has user permissions, so
rebuilds the font cache in the user's .cache

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-04-03 Thread Alistair Buxton
As far as the original bug with delayed login goes... it seems that the
Bluetooth stuff is a red herring.

Since it only happens on first login, I deleted the contents of ~ and
relogged. The delay came back, so I bisected the files until I arrived
at the single file which needs to be deleted in order for the delay to
happen. And that file is:

   ~/.cache/fontconfig/9b89f8e3dae116d678bbf48e5f21f69b-le32d4.cache-7

This cache file is associated with the Noto CJK fonts at:

/usr/share/fonts/opentype/noto

(You can see this by running strings on it.)

Deleting this file while the user is not logged in causes the next login
to take 60 seconds.

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

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-04-03 Thread Alistair Buxton
seems related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845058

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-03-31 Thread Alistair Buxton
I tried to log in over ssh and run top so I could watch which processes
were running but this caused the delay to disappear.

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-03-31 Thread Alistair Buxton
Since this only happens on first login, I ran a diff on the full home
directory before/after login:

https://paste.ubuntu.com/p/SJ2nNx7WfP/

I don't see anything obvious in there. The pulse cookie and a blueman
settings file (empty) were created. The rest seems to be Thunar/desktop
defaults and example files.

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-03-31 Thread Alistair Buxton
On the current daily ISO this now hangs for 50 seconds instead of 75,
and the blueman/bluetooth messages are completely gone from xsession-
errors.

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-03-13 Thread Alistair Buxton
There is more stuff in syslog too. It looks like pulseaudio is trying
and failing to start blueman.

** Attachment added: "cat syslog | grep -E '(pulseaudio|blueman)'"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5077997/+files/syslog.txt

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Possibly also causing the long time to desktop from try/install
  livesession dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:
   
  rfkill:
   
  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]:   
[1520681416.8951] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

2018-03-13 Thread Alistair Buxton
** Attachment added: "log running blueman-applet manually"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5077985/+files/blueman-applet-manual.txt

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Possibly also causing the long time to desktop from try/install
  livesession dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:
   
  rfkill:
   
  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]:   
[1520681416.8951] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.blue

2018-03-13 Thread Alistair Buxton
** Summary changed:

- Xubuntu: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': 
timed out (service_start_timeout=25000ms)
+ ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)

** Summary changed:

- ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
+ Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Possibly also causing the long time to desktop from try/install
  livesession dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:
   
  rfkill:
   
  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]:   
[1520681416.8951] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Xubuntu: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_star

2018-03-13 Thread Alistair Buxton
No, we are talking about the errors in xsession-errors.txt:

ERROR:dbus.proxies:Introspect error on org.bluez:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
ERROR:dbus.proxies:Introspect error on org.bluez:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)

Note that each one of these errors is a separate time out, so the total
delay is 75 seconds. This delay blocks the desktop from starting during
boot and first login.

The delay can be reproduced any time on the live session by attempting
to start blueman-applet from the terminal - it will produce the same
errors and then give up after 75 seconds.

The computer under test has no bluetooth hardware and blueman is not
running. A patch was added to 16.04 because this situation led to
blueman outright crashing there. Now in 18.04 instead of crashing it
delays boot up by 75 seconds instead.

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

Title:
  ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Possibly also causing the long time to desktop from try/install
  livesession dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:
   
  rfkill:
   
  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]:   
[1520681416.8951] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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


[Touch-packages] [Bug 1754836] Re: Failed to activate service

2018-03-11 Thread Alistair Buxton
The same messages are logged on the live image boot.

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

Title:
  Failed to activate service

Status in bluez package in Ubuntu:
  New

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Possibly also causing the long time to desktop from try/install
  livesession dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:
   
  rfkill:
   
  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]:   
[1520681416.8951] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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


[Touch-packages] [Bug 1265418] Re: Gtk3 bookmark can't be removed if it points to a file

2017-08-18 Thread Alistair Buxton
Just because the upstream report was marked as a duplicate, does not
mean it is invalid.

** Bug watch added: GNOME Bug Tracker #762252
   https://bugzilla.gnome.org/show_bug.cgi?id=762252

** Changed in: gtk
   Importance: Medium => Unknown

** Changed in: gtk
   Status: Invalid => Unknown

** Changed in: gtk
 Remote watch: GNOME Bug Tracker #721321 => GNOME Bug Tracker #762252

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

Title:
  Gtk3 bookmark can't be removed if it points to a file

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  In the file requestor of Gtk3 you can drag files and directories to
  the sidebar to create bookmarks. If the user drags a file here the
  bookmark can never be deleted because the option is disabled.

  To reproduce:

  1. Open a Gtk3 application such as firefox, gedit etc.
  2. Open the File Open requester.
  3. Drag a file to the bookmarks.
  4. Right click on the file bookmark.

  Expected result: Should be able to click on "Remove" to remove the
  bookmark.

  Actual result: The remove option is always disabled.

  Workaround: Edit ~/.config/gtk-3.0/bookmarks and delete the bookmark
  line.

  Also affects trusty.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgtk-3-0 3.8.6-0ubuntu3.1
  Uname: Linux 3.11.0-031100-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Jan  2 02:49:04 2014
  InstallationDate: Installed on 2013-08-27 (127 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827)
  MarkForUpload: True
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 764414] Re: private master bugs are confusing and lead to more duplicate filings

2017-02-15 Thread Alistair Buxton
This bug happened to me today. I found an easily reproducible bug in a
package, so because I am a helpful person, I did a fresh install just to
repro it in +1, and submitted a core dump through apport. Because I knew
for a fact that there was no private information in the clean install I
set my bug to public. Apport then marked it as a duplicate of a private
bug which I cannot access.

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

Title:
  private master bugs are confusing and lead to more duplicate filings

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apport

  Apport currently tracks the master bug as a private bug visible only
  to Ubuntu developers (bugcontrol) and makes duplicate bugs public
  after stripping their data.

  This works well but has some downsides:
   - Launchpad cannot show the master bug to folk reporting bugs via apport (so 
they file new bugs always)
   - After users file a new bug apport detects its a duplicate and then they 
cannot see the master bug and get frustrated.

  It would be nice to have:
   - the master bug be public so that reporters of dups can see it in the dupe 
finder and can see if a dupe is detected post-filing.
   - Developers still have easy access to the raw crash data.
    - One way to do that that does not need much development would be to have a 
private bug exist, linked from the master bug (e.g. with a comment or in the 
description; something like 'Confidential crashdump for this bug is attached to 
bug 12345 - only visible to Ubuntu developers').

  One way to achieve this is to have apport file a new public bug to be
  the master. This would have the necessary metadata and would include
  the link to the private bug + gather all the duplicates to itself. One
  downside is that Apport would appear to be the bug reporter for all
  crashdump based bug reports. That's not necessarily a bad thing, but
  it may confuse people.

  Another way would be to have apport file a new private bug, move the
  attachments over from the original bug, add explanation and metadata
  in the description, subscribe bugcontrol and then sanitise the
  original bug report the same way it sanitises public bugs today. This
  would make the original bug be the public master, preserving the date
  of filing and the reporter. OTOH large files would need to be shuffled
  around and this might be unreliable.

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

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


[Touch-packages] [Bug 1572528] Re: Side stage close/ collapse gesture hard to discover

2016-10-05 Thread Alistair Buxton
Also the first time I encountered the side stage was after opening the
weather app and then rotating to landscape mode. The weather app
automatically puts itself into the side stage, obscuring the message
about three finger dragging.

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

Title:
  Side stage close/ collapse gesture hard to discover

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Once any app has been in the side stage there seems to be no way to close it 
anymore as long as the device is in landscape orientation. Moving all of the 
side staged apps back to the main stage or closing them will leave a black 
screen behind telling how to use 3 fingers to use the side stage.
  This is particularly inconvenient due to bug 1564348 and renders many apps 
difficult or impossible to use in landscape.

  This is on Frieza with OTA 10.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1572528/+subscriptions

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


[Touch-packages] [Bug 1572528] Re: Side stage close/ collapse gesture hard to discover

2016-10-05 Thread Alistair Buxton
+1 the area you need to hit is so small that it takes several attempts
even if you know exactly what you are aiming for. If you just guess that
maybe you can swipe away the side stage then your chances of actually
hitting the absolutely tiny region where it works are virtually nil.

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

Title:
  Side stage close/ collapse gesture hard to discover

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Once any app has been in the side stage there seems to be no way to close it 
anymore as long as the device is in landscape orientation. Moving all of the 
side staged apps back to the main stage or closing them will leave a black 
screen behind telling how to use 3 fingers to use the side stage.
  This is particularly inconvenient due to bug 1564348 and renders many apps 
difficult or impossible to use in landscape.

  This is on Frieza with OTA 10.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1572528/+subscriptions

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


[Touch-packages] [Bug 1630724] [NEW] Application remains on unity launcher after uninstallation

2016-10-05 Thread Alistair Buxton
Public bug reported:

I'm not sure if this is reproducible but this is what I did:

1. Enter Ubuntu One account details through system settings -> online accounts.
2. Open the app store from the main app scope.
3. Install Popey's Youtube app and then "open" it from the app store page.
4. Play around in Youtube app for a bit.
5. Go to the main app scope and long press the Youtube icon to open the store 
page.
6. Uninstall the app.
7. Search the store for another Youtube app and install it. (This time I 
installed the top rated one.)
8. Again, open it by pressing "open" on the store page.
9. Swipe the left edge to open the app switcher.

At this point I have two Youtube icons on the switcher. One corresponds
to the first youtube app, now uninstalled. If I press it, I see a low
resolution screenshot of that app. I can't interact with it though, and
if I tap the screen it flickers between the screenshot and another app.

Next I plugged in a keyboard and mouse, activating desktop mode. The
ghost youtube app now brings up a black window with "youtube" in the
middle in white text. The close button on the window has no effect.

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

** Summary changed:

- Ghost application remains on unity launcher after uninstallation
+ Application remains on unity launcher after uninstallation

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

Title:
  Application remains on unity launcher after uninstallation

Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm not sure if this is reproducible but this is what I did:

  1. Enter Ubuntu One account details through system settings -> online 
accounts.
  2. Open the app store from the main app scope.
  3. Install Popey's Youtube app and then "open" it from the app store page.
  4. Play around in Youtube app for a bit.
  5. Go to the main app scope and long press the Youtube icon to open the store 
page.
  6. Uninstall the app.
  7. Search the store for another Youtube app and install it. (This time I 
installed the top rated one.)
  8. Again, open it by pressing "open" on the store page.
  9. Swipe the left edge to open the app switcher.

  At this point I have two Youtube icons on the switcher. One
  corresponds to the first youtube app, now uninstalled. If I press it,
  I see a low resolution screenshot of that app. I can't interact with
  it though, and if I tap the screen it flickers between the screenshot
  and another app.

  Next I plugged in a keyboard and mouse, activating desktop mode. The
  ghost youtube app now brings up a black window with "youtube" in the
  middle in white text. The close button on the window has no effect.

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

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


[Touch-packages] [Bug 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

2016-04-21 Thread Alistair Buxton
I have an Atom N455 convertible with Pineview graphics. Unity8 session
just displays a black screen forever. Unity 7 works fine.

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

Title:
  Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT:
  "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtdeclarative package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

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

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


[Touch-packages] [Bug 1573292] Re: Black screen after greeter.

2016-04-21 Thread Alistair Buxton
*** This bug is a duplicate of bug 1549455 ***
https://bugs.launchpad.net/bugs/1549455

** This bug has been marked a duplicate of bug 1549455
   Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: 
"eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

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

Title:
  Black screen after greeter.

Status in unity8 package in Ubuntu:
  New

Bug description:
  1. Install ubuntu-desktop-16.04-amd64
  2. sudo apt-get update && sudo apt-get install unity8-desktop-session-mir
  3. Reboot.
  4. Log in to unity8 session.

  Result: black screen, no mouse pointer. The screen backlight dims
  after a while.

  Reporting yet another new bug to try to get apport to attach useful
  logs.

  Workarounds which don't help:

  * Moving the mouse for 20 seconds to generate entropy before logging in.
  * Deleting ~/.cache
  * Switching to/from ttys.

  On checking ps waxf I can see that a large number of unity related
  programs are running, including unity8 and unity8-dash (see
  attachment) but nothing is rendered.

  My system is an N455 Atom with Pineview graphics, which should use the
  intel driver. Unity 7 works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160401-0ubuntu1
  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
  Date: Thu Apr 21 23:48:28 2016
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1573292] Re: Black screen after greeter.

2016-04-21 Thread Alistair Buxton
** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1573292/+attachment/4642061/+files/unity8.log

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

Title:
  Black screen after greeter.

Status in unity8 package in Ubuntu:
  New

Bug description:
  1. Install ubuntu-desktop-16.04-amd64
  2. sudo apt-get update && sudo apt-get install unity8-desktop-session-mir
  3. Reboot.
  4. Log in to unity8 session.

  Result: black screen, no mouse pointer. The screen backlight dims
  after a while.

  Reporting yet another new bug to try to get apport to attach useful
  logs.

  Workarounds which don't help:

  * Moving the mouse for 20 seconds to generate entropy before logging in.
  * Deleting ~/.cache
  * Switching to/from ttys.

  On checking ps waxf I can see that a large number of unity related
  programs are running, including unity8 and unity8-dash (see
  attachment) but nothing is rendered.

  My system is an N455 Atom with Pineview graphics, which should use the
  intel driver. Unity 7 works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160401-0ubuntu1
  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
  Date: Thu Apr 21 23:48:28 2016
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1573292] [NEW] Black screen after greeter.

2016-04-21 Thread Alistair Buxton
Public bug reported:

1. Install ubuntu-desktop-16.04-amd64
2. sudo apt-get update && sudo apt-get install unity8-desktop-session-mir
3. Reboot.
4. Log in to unity8 session.

Result: black screen, no mouse pointer. The screen backlight dims after
a while.

Reporting yet another new bug to try to get apport to attach useful
logs.

Workarounds which don't help:

* Moving the mouse for 20 seconds to generate entropy before logging in.
* Deleting ~/.cache
* Switching to/from ttys.

On checking ps waxf I can see that a large number of unity related
programs are running, including unity8 and unity8-dash (see attachment)
but nothing is rendered.

My system is an N455 Atom with Pineview graphics, which should use the
intel driver. Unity 7 works fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity8 8.12+16.04.20160401-0ubuntu1
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
Date: Thu Apr 21 23:48:28 2016
InstallationDate: Installed on 2016-04-21 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "running processes"
   https://bugs.launchpad.net/bugs/1573292/+attachment/4642057/+files/pswaxf.txt

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

Title:
  Black screen after greeter.

Status in unity8 package in Ubuntu:
  New

Bug description:
  1. Install ubuntu-desktop-16.04-amd64
  2. sudo apt-get update && sudo apt-get install unity8-desktop-session-mir
  3. Reboot.
  4. Log in to unity8 session.

  Result: black screen, no mouse pointer. The screen backlight dims
  after a while.

  Reporting yet another new bug to try to get apport to attach useful
  logs.

  Workarounds which don't help:

  * Moving the mouse for 20 seconds to generate entropy before logging in.
  * Deleting ~/.cache
  * Switching to/from ttys.

  On checking ps waxf I can see that a large number of unity related
  programs are running, including unity8 and unity8-dash (see
  attachment) but nothing is rendered.

  My system is an N455 Atom with Pineview graphics, which should use the
  intel driver. Unity 7 works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160401-0ubuntu1
  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
  Date: Thu Apr 21 23:48:28 2016
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1181423] Re: Cannot print at all with USB to parallel adapter and HP 4L

2015-08-02 Thread Alistair Buxton
** Attachment added: "cups error log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1181423/+attachment/4437636/+files/error_log.gz

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

Title:
  Cannot print at all with USB to parallel adapter and HP 4L

Status in cups package in Ubuntu:
  New

Bug description:
  Since upgrading to raring I am unable to print anything at all using
  Prolific 2303 USB to parallel adapter and a HP LaserJet 4L. cups error
  log attached. This is the output when adding the printer and trying to
  print a test page.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: cups 1.6.2-1ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri May 17 23:29:30 2013
  InstallationDate: Installed on 2013-04-26 (20 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  KernLog:
   
  Lpstat:
   device for HP-LaserJet-4L: usb://Unknown/Printer
   device for M175nw: hp:/net/HP_LaserJet_100_colorMFP_M175nw?ip=192.168.0.175
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Papersize: a4
  PpdFiles:
   HP-LaserJet-4L: HP LaserJet 4L Foomatic/ljet4 (recommended)
   M175nw: HP LaserJet 100 color MFP M175 Postscript (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=52fbfaf1-aa35-45f8-9a1c-b867ce923edd ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0704
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A79XTD EVO
  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.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO: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/cups/+bug/1181423/+subscriptions

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


[Touch-packages] [Bug 1181423] Re: Cannot print at all with USB to parallel adapter and HP 4L

2015-08-02 Thread Alistair Buxton
Still broken in 15.04.

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

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

Title:
  Cannot print at all with USB to parallel adapter and HP 4L

Status in cups package in Ubuntu:
  New

Bug description:
  Since upgrading to raring I am unable to print anything at all using
  Prolific 2303 USB to parallel adapter and a HP LaserJet 4L. cups error
  log attached. This is the output when adding the printer and trying to
  print a test page.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: cups 1.6.2-1ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri May 17 23:29:30 2013
  InstallationDate: Installed on 2013-04-26 (20 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  KernLog:
   
  Lpstat:
   device for HP-LaserJet-4L: usb://Unknown/Printer
   device for M175nw: hp:/net/HP_LaserJet_100_colorMFP_M175nw?ip=192.168.0.175
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Papersize: a4
  PpdFiles:
   HP-LaserJet-4L: HP LaserJet 4L Foomatic/ljet4 (recommended)
   M175nw: HP LaserJet 100 color MFP M175 Postscript (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=52fbfaf1-aa35-45f8-9a1c-b867ce923edd ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0704
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A79XTD EVO
  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.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO: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/cups/+bug/1181423/+subscriptions

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


[Touch-packages] [Bug 1311344] Re: [sticky keys] shift key is stuck down after suspending/resuming

2015-05-01 Thread Alistair Miles
Currently in Ubuntu 14.10 (up to date packages) it seems that sometimes
two shift key presses are required before entering login password,
sometimes one shift key press, with no predictability. Hence for every
login I have to guess and typically have to try entering the password
two to four times before I get it right. As I regularly close and open
the lid of my laptop this behaviour is spectacularly annoying. Please
please please can you give this some priority.

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

Title:
  [sticky keys] shift key is stuck down after suspending/resuming

Status in unity package in Ubuntu:
  Invalid
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  With stick keys enabled, the shift key is stuck down after
  suspending/resuming.

  To reproduce:
  1) Enables stick keys
  2) Suspend the screen closing the lid
  3) Open the lid

  This breaks both unity lockscreen and lightdm

  [Workaround]
  Press shift key before entering the passowrd.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:27:14 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-02 (475 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (0 days ago)

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

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


[Touch-packages] [Bug 1270486] Re: indicator-application doesn't use the menu item's label if it has a stock icon

2015-02-05 Thread Alistair Buxton
The bug still appears in vivid/xfce from about 3 days ago.

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

Title:
  indicator-application doesn't use the menu item's label if it has a
  stock icon

Status in libdbusmenu package in Ubuntu:
  Triaged

Bug description:
  To reproduce, run the attached testcase1.py. You will see a new
  indicator, inside it will be one menu item with label "Pause" and a
  pause button icon. The menu item should have the label "Hello".

  Also note that this bug has been fixed once before:
  https://bugs.launchpad.net/indicator-application/+bug/520048

  For trusty, see comment 3. Glade is used by deluge to set the
  indicator menu, this is where the problem was first observed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-application 12.10.1+13.10.20131107-0ubuntu1
  Uname: Linux 3.11.0-031100-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Jan 18 20:40:29 2014
  InstallationDate: Installed on 2013-08-27 (143 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827)
  MarkForUpload: True
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1270486] Re: indicator-application doesn't use the menu item's label if it has a stock icon

2015-02-04 Thread Alistair Buxton
See screenshot.

"Open" should be "Open a torrent"
"Open" should be "Open URL"
"Pause" should be "Pause all torrents"
"Play" should be "Start all torrents".

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

Title:
  indicator-application doesn't use the menu item's label if it has a
  stock icon

Status in libdbusmenu package in Ubuntu:
  Triaged

Bug description:
  To reproduce, run the attached testcase1.py. You will see a new
  indicator, inside it will be one menu item with label "Pause" and a
  pause button icon. The menu item should have the label "Hello".

  Also note that this bug has been fixed once before:
  https://bugs.launchpad.net/indicator-application/+bug/520048

  For trusty, see comment 3. Glade is used by deluge to set the
  indicator menu, this is where the problem was first observed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-application 12.10.1+13.10.20131107-0ubuntu1
  Uname: Linux 3.11.0-031100-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Jan 18 20:40:29 2014
  InstallationDate: Installed on 2013-08-27 (143 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827)
  MarkForUpload: True
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


  1   2   >