[Touch-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing

2020-07-23 Thread Damir
Thank you Pierre for the solution. I had the same problem and tried
everything. Lost a lot of time on this stupid problem. I cannot believe
this is happening in Ubuntu in 2020. This kind of BS keeps me from
recommending Linux to regular computer users!

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed

  Additional information
  ==

  $ lspci -vv -s 01:00.0
  01:00.0 Network controller: Intel Corporation 

[Touch-packages] [Bug 1803503] [NEW] package vim-runtime 2:8.0.1453-1ubuntu1 failed to install/upgrade: installed vim-runtime package post-installation script subprocess returned error exit status 255

2018-11-15 Thread Damir
Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: vim-runtime 2:8.0.1453-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
 vim-runtime:amd64: Install
 vim:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Nov 15 11:09:28 2018
ErrorMessage: installed vim-runtime package post-installation script subprocess 
returned error exit status 255
InstallationDate: Installed on 2018-11-13 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: vim
Title: package vim-runtime 2:8.0.1453-1ubuntu1 failed to install/upgrade: 
installed vim-runtime package post-installation script subprocess returned 
error exit status 255
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package vim-runtime 2:8.0.1453-1ubuntu1 failed to install/upgrade:
  installed vim-runtime package post-installation script subprocess
  returned error exit status 255

Status in vim package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: vim-runtime 2:8.0.1453-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   vim-runtime:amd64: Install
   vim:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Nov 15 11:09:28 2018
  ErrorMessage: installed vim-runtime package post-installation script 
subprocess returned error exit status 255
  InstallationDate: Installed on 2018-11-13 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: vim
  Title: package vim-runtime 2:8.0.1453-1ubuntu1 failed to install/upgrade: 
installed vim-runtime package post-installation script subprocess returned 
error exit status 255
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1100049] Re: Evince does not recognize CUPS printer.

2015-02-21 Thread Damir Butmir
** Package changed: cups (Ubuntu) = evince (Ubuntu)

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

Title:
  Evince does not recognize CUPS printer.

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Hello, I am trying to print a PDF file via wireless lexmark printer,
  using Evince. The printer is properly configured as other apps such as
  Firefox can print to it, it's powered on, and set as the default.
  However, Evince does not seem to recognize CUPS printers as when I
  open the PDF, the Print button is completely disabled (greyed out).

  Closing Evince and re-opening does not resolve the issue. The print
  option should be enabled as Evince should be detecting the printer I
  already have configured but it is not for some reason

  OS: Ubuntu 12.04 LTS x64
  CUPS: 1.3.8
  Evince: 3.4.0

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

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