[Touch-packages] [Bug 1861911] [NEW] initramfs-tools 0.133ubuntu13 post-installation

2020-02-04 Thread granjerox
*** This bug is a duplicate of bug 1861890 ***
https://bugs.launchpad.net/bugs/1861890

Public bug reported:

package initramfs-tools 0.133ubuntu13 failed to install/upgrade:
installed initramfs-tools package post-installation script subprocess
returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.133ubuntu13
ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16
Uname: Linux 5.4.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Tue Feb  4 18:44:23 2020
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2019-12-13 (52 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191213)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.1, python3-minimal, 3.8.0-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.8
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.133ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal package-from-proposed

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

Title:
  initramfs-tools 0.133ubuntu13 post-installation

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  package initramfs-tools 0.133ubuntu13 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.133ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16
  Uname: Linux 5.4.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 18:44:23 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2019-12-13 (52 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191213)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.1, python3-minimal, 3.8.0-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.8
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.133ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861911/+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 520546] Re: Alt-f2 switches to virtual terminal 2

2018-04-11 Thread granjerox
Hello I've notice this strange behabiour a few days ago.

Here my setup:
- Dell XPS 13 first gen
- Ubuntu Gnome 16.04 up to date

Every alt+Fx changes to virtual terminals, win+left or right also. But
its not like control is pressed.

By the way alt+f2 brings back to GUI. And alt+f4 changes to virtual 4
and same time closes active window ... a real nightmare.

I havent narrow down the trigger but if I restart it gets solved and
returns from time to time.

I, like most linux users, love keyboard shortcut and there ara a few
with alt+fx.

Is this bug being tracked somewhere else?

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+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 1525628] Re: tracker needs to be killed on every boot

2017-07-01 Thread granjerox
Had to kill tracker after boot

MyUser@portaildell:~$ apt-cache policy tracker
tracker:
  Installed: 1.6.2-0ubuntu1.1
  Candidate: 1.6.2-0ubuntu1.1
  Version table:
 *** 1.6.2-0ubuntu1.1 500
500 http://es.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 1.6.2-0ubuntu1 500
500 http://es.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

MyUser@portaildell:~$ apt-cache madison tracker
   tracker | 1.6.2-0ubuntu1.1 | http://es.archive.ubuntu.com/ubuntu 
xenial-updates/universe amd64 Packages
   tracker | 1.6.2-0ubuntu1.1 | http://security.ubuntu.com/ubuntu 
xenial-security/universe amd64 Packages
   tracker | 1.6.2-0ubuntu1 | http://es.archive.ubuntu.com/ubuntu 
xenial/universe amd64 Packages


MyUser@portaildell:~$ apt-cache policy tracker
tracker:
  Installed: 1.6.2-0ubuntu1.1
  Candidate: 1.6.2-0ubuntu1.1
  Version table:
 *** 1.6.2-0ubuntu1.1 500
500 http://es.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 1.6.2-0ubuntu1 500
500 http://es.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
pagraher@portaildell:~$ apt-cache madison tracker
   tracker | 1.6.2-0ubuntu1.1 | http://es.archive.ubuntu.com/ubuntu 
xenial-updates/universe amd64 Packages
   tracker | 1.6.2-0ubuntu1.1 | http://security.ubuntu.com/ubuntu 
xenial-security/universe amd64 Packages
   tracker | 1.6.2-0ubuntu1 | http://es.archive.ubuntu.com/ubuntu 
xenial/universe amd64 Packages

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

Title:
  tracker needs to be killed on every boot

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  At every boot, tacker-miner-fs and tracker-extract uses all of the
  processor and needs to be killed manually for computer to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tracker 1.6.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec 13 13:02:58 2015
  InstallationDate: Installed on 2015-04-24 (232 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1525628/+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 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

2017-06-11 Thread granjerox
Hello,

I've just upgraded pluseaudio with ppa from #66 and now my Q12 Bluetooth
headset always connect fine as with A2DP Sink. I'm on Ubuntu 16.04 by
the way.

Before the upgrade, I had to ensure to change profile back to HSP/HFP
before disconnecting, otherwise I had to do it, disconnect, connect
again and then set A2DP... really annoying.

Thanks for the fix, whatever it was.

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

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  ZapaƂowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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