[Touch-packages] [Bug 1974040] Re: Cannot connect to PEAP wifi (eduroam)

2022-05-18 Thread Alfredo Buttari
*** This bug is a duplicate of bug 1958267 ***
https://bugs.launchpad.net/bugs/1958267

thanks for your quick answer Sebastien. I tried to do as suggested in
#22 and then #36 but still not working. Can I provide and further
information to help track this problem down?

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

Title:
  Cannot connect to PEAP wifi (eduroam)

Status in wpa package in Ubuntu:
  New

Bug description:
  Connection to wifi fails with

  May 18 15:08:55 attila wpa_supplicant[9698]: OpenSSL:
  openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal
  error

  
  Description:Ubuntu 22.04 LTS
  Release:22.04


  wpasupplicant:
Installed: 2:2.10-6ubuntu1
Candidate: 2:2.10-6ubuntu1
Version table:
   *** 2:2.10-6ubuntu1 1 (phased 40%)
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:2.10-6 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May 18 15:13:41 2022
  InstallationDate: Installed on 2019-10-22 (938 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1974040/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

2022-05-18 Thread Alfredo Buttari
Same as @melser-anton
I installed 2:2.10-6ubuntu1 from ubuntu-updates but still no luck. I followed 
the instructions in #35 and submitted a new bug  #1974040

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Fix Released

Bug description:
  * Impact

  Connecting to some PEAP wifi doesn't work anymore since the openssl3
  transition

  Details on the issue can be found on
  http://lists.infradead.org/pipermail/hostap/2022-May/040511.html

  * Test case

  Try using a PEAP wifi not implementing RFC5746, it should be able to
  connect

  * Regression potential

  The change allows to connect to less secure WiFis the same way that
  wpa allowed before openssl3, lower security enforcement isn't ideal
  but still better than non working hardware.

  

  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2022-02-27T21:07:16.553410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1974040] Re: Cannot connect to PEAP wifi (eduroam)

2022-05-18 Thread Alfredo Buttari
This looks like the same as bug #1962541
Followed the instructions in comment #35 therein.


** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1974040/+attachment/5590933/+files/journalctl.log

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

Title:
  Cannot connect to PEAP wifi (eduroam)

Status in wpa package in Ubuntu:
  New

Bug description:
  Connection to wifi fails with

  May 18 15:08:55 attila wpa_supplicant[9698]: OpenSSL:
  openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal
  error

  
  Description:Ubuntu 22.04 LTS
  Release:22.04


  wpasupplicant:
Installed: 2:2.10-6ubuntu1
Candidate: 2:2.10-6ubuntu1
Version table:
   *** 2:2.10-6ubuntu1 1 (phased 40%)
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:2.10-6 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May 18 15:13:41 2022
  InstallationDate: Installed on 2019-10-22 (938 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1974040/+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 1974040] [NEW] Cannot connect to PEAP wifi (eduroam)

2022-05-18 Thread Alfredo Buttari
Public bug reported:

Connection to wifi fails with

May 18 15:08:55 attila wpa_supplicant[9698]: OpenSSL: openssl_handshake
- SSL_connect error:0A0C0103:SSL routines::internal error


Description:Ubuntu 22.04 LTS
Release:22.04


wpasupplicant:
  Installed: 2:2.10-6ubuntu1
  Candidate: 2:2.10-6ubuntu1
  Version table:
 *** 2:2.10-6ubuntu1 1 (phased 40%)
500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2:2.10-6 500
500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: wpasupplicant 2:2.10-6ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed May 18 15:13:41 2022
InstallationDate: Installed on 2019-10-22 (938 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: wpa
UpgradeStatus: Upgraded to jammy on 2022-04-22 (26 days ago)

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

Title:
  Cannot connect to PEAP wifi (eduroam)

Status in wpa package in Ubuntu:
  New

Bug description:
  Connection to wifi fails with

  May 18 15:08:55 attila wpa_supplicant[9698]: OpenSSL:
  openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal
  error

  
  Description:Ubuntu 22.04 LTS
  Release:22.04


  wpasupplicant:
Installed: 2:2.10-6ubuntu1
Candidate: 2:2.10-6ubuntu1
Version table:
   *** 2:2.10-6ubuntu1 1 (phased 40%)
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:2.10-6 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May 18 15:13:41 2022
  InstallationDate: Installed on 2019-10-22 (938 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1974040/+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 1888101] Re: 'unsupported protocol' error when using PyMySQL

2020-08-18 Thread Luis Alfredo Contreras
Hi, I had the same issue but I found a solution.

I was creating a docker container based on ubuntu 20.04 and Python3.8.2.
It installed openssl by default. The version from 2020-Mar-31 12:41:55
openssl-1.1.1f.tar.gz was giving me an this error: ssl.SSLError: [SSL:
UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:1108). After looking
for solutions, I found this link: https://cloudwafer.com/blog
/installing-openssl-on-ubuntu-16-04-18-04/. In that link, you can find
how to install openssl from the source. It shows you how to install the
version from 2019-May-28 13:26:28 openssl-1.1.1c.tar.gz. First I built
my container as originally and logged in and I followed the steps in the
link. It solved my problem. The latest version from March 2020 was
causing the issue.

I added the lines of code below when building the docker container to
automate the steps. See:

RUN apt install build-essential checkinstall zlib1g-dev -y
WORKDIR /usr/local/src/
RUN wget https://www.openssl.org/source/openssl-1.1.1c.tar.gz && tar -xf 
openssl-1.1.1c.tar.gz
WORKDIR openssl-1.1.1c
RUN ./config --prefix=/usr/local/ssl --openssldir=/usr/local/ssl shared zlib && 
make && make install
COPY ./openssl-1.1.1c.conf /etc/ld.so.conf.d/
RUN ldconfig -v && mv /usr/bin/c_rehash /usr/bin/c_rehash.backup && mv 
/usr/bin/openssl /usr/bin/openssl.backup
ENV 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/ssl/bin"


* Note that I created the openssl-1.1.1c.conf file before building the 
container. The file is copied from the same directory where the dockerfile is 
saved. Create the file with that name and paste this inside: /usr/local/ssl/lib

I hope this helps.

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

Title:
  'unsupported protocol' error when using PyMySQL

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  1)
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2)
  openssl:
Installiert:   1.1.1f-1ubuntu2
Installationskandidat: 1.1.1f-1ubuntu2
Versionstabelle:
   *** 1.1.1f-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) + 4)
  I am trying to connect to my MariaDB with python package "PyMySQL" and SSL 
enabled. On my old installation (Kubuntu 19.10) this worked. With the new 
installation (also new PC: Xubuntu 20.04) I get this error message:

  ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol
  (_ssl.c:1108)

  Here are my installation details:
  Old installation: python 3.7.5, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1c 
28 May 2019
  New installation: python 3.8.2, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1f 
31 Mar 2020

  When I use python with a different SSL version...:
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.0m-dev xx XXX 
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 
  this works: python 3.8.2, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 

  
  It seems, like the one specific version of openSSL (1.1.1f 31 Mar 2020) does 
not work together with PyMySQL.

  Some more details I have posted here:
  
https://stackoverflow.com/questions/62964998/unsupported-protocol-error-when-using-pymysql

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1f-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Jul 18 15:42:27 2020
  InstallationDate: Installed on 2020-07-13 (4 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1888101/+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 1791196] Re: [USB-Audio - US122 MKII, recording] Recording problem

2019-01-13 Thread Alfredo Anderson
Hi guys, I managed to have this working (on lubuntu) following
https://linuxmusicians.com/viewtopic.php?t=16711

In short, blacklist snd_usb_audio (and get the board listed as US-122L
instead of US-122mkII)

lfredo@alfredo-pc:~$ cat /proc/asound/cards 
 0 [NVidia ]: HDA-Intel - HDA NVidia
  HDA NVidia at 0xdbff8000 irq 23
 1 [US122L ]: USB US-122L - TASCAM US-122L
  TASCAM US-122L (644:8021 if 0 at 001/002)

Then create .asoundrc file.

And finally run jackd with the following presets

jackd -RP60 -dalsa -dusb_stream:1  -r48000 -p256 -n2

Hope someone find this useful.

Regards, Alfredo

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

Title:
  [USB-Audio - US122 MKII, recording] Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Can't get the US122 MKII listed as an input device.

  Not in pavucontrol, nor in sound settings nor in jackd.

  May be this helps,

  alfredo@alfredo-ubuntu:~$ jackd -d alsa -d hw:MKII
  jackdmp 1.9.12
  ...
  Acquire audio card Audio1
  creating alsa driver ... 
hw:MKII|hw:MKII|1024|2|48000|0|0|nomon|swmeter|-|32bit
  ALSA: Cannot open PCM device alsa_pcm for capture. Falling back to 
playback-only mode
  ...

  Please let me know if you need further information.

  Regards, Alfredo

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfredo7890 F pulseaudio
   /dev/snd/controlC1:  alfredo7890 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  6 22:02:55 2018
  InstallationDate: Installed on 2018-03-03 (187 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) :   N o   s u c h   f i l e  
 o r   d i r e c t o r y
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:MKII failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   m a i n : 7 8 8 :   a u d 
i o   o p e n   e r r o r :   N o   s u c h   f i l e   o r   d i r e c t o r y
  Symptom_Card: TASCAM US-122mkII - US122 MKII
  Symptom_Type: None of the above
  Title: [USB-Audio - US122 MKII, recording] Recording problem
  UpgradeStatus: Upgraded to bionic on 2018-09-02 (4 days ago)
  dmi.bios.date: 03/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd03/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1791196/+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 1795894] [NEW] package software-properties-common 0.96.24.32.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2018-10-03 Thread Alfredo EW
Public bug reported:

I can not install chrome

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: software-properties-common 0.96.24.32.5
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 google-chrome-stable:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Oct  3 08:27:14 2018
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2018-10-03 (0 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
 apt  1.6.3ubuntu0.1
SourcePackage: software-properties
Title: package software-properties-common 0.96.24.32.5 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795894

Title:
  package software-properties-common 0.96.24.32.5 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in software-properties package in Ubuntu:
  New

Bug description:
  I can not install chrome

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: software-properties-common 0.96.24.32.5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   google-chrome-stable:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Oct  3 08:27:14 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2018-10-03 (0 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
   apt  1.6.3ubuntu0.1
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.24.32.5 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795894/+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 1791196] [NEW] [USB-Audio - US122 MKII, recording] Recording problem

2018-09-06 Thread Alfredo Anderson
Public bug reported:

Can't get the US122 MKII listed as an input device.

Not in pavucontrol, nor in sound settings nor in jackd.

May be this helps,

alfredo@alfredo-ubuntu:~$ jackd -d alsa -d hw:MKII
jackdmp 1.9.12
...
Acquire audio card Audio1
creating alsa driver ... hw:MKII|hw:MKII|1024|2|48000|0|0|nomon|swmeter|-|32bit
ALSA: Cannot open PCM device alsa_pcm for capture. Falling back to 
playback-only mode
...

Please let me know if you need further information.

Regards, Alfredo

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alfredo7890 F pulseaudio
 /dev/snd/controlC1:  alfredo7890 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep  6 22:02:55 2018
InstallationDate: Installed on 2018-03-03 (187 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) :   N o   s u c h   f i l e   
o r   d i r e c t o r y
Symptom_AlsaRecordingTest: ALSA recording test through plughw:MKII failed
Symptom_AlsaRecordingTestStderr: a r e c o r d :   m a i n : 7 8 8 :   a u d i 
o   o p e n   e r r o r :   N o   s u c h   f i l e   o r   d i r e c t o r y
Symptom_Card: TASCAM US-122mkII - US122 MKII
Symptom_Type: None of the above
Title: [USB-Audio - US122 MKII, recording] Recording problem
UpgradeStatus: Upgraded to bionic on 2018-09-02 (4 days ago)
dmi.bios.date: 03/26/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0503
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M2N-MX SE Plus
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd03/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug bionic

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

Title:
  [USB-Audio - US122 MKII, recording] Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Can't get the US122 MKII listed as an input device.

  Not in pavucontrol, nor in sound settings nor in jackd.

  May be this helps,

  alfredo@alfredo-ubuntu:~$ jackd -d alsa -d hw:MKII
  jackdmp 1.9.12
  ...
  Acquire audio card Audio1
  creating alsa driver ... 
hw:MKII|hw:MKII|1024|2|48000|0|0|nomon|swmeter|-|32bit
  ALSA: Cannot open PCM device alsa_pcm for capture. Falling back to 
playback-only mode
  ...

  Please let me know if you need further information.

  Regards, Alfredo

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfredo7890 F pulseaudio
   /dev/snd/controlC1:  alfredo7890 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  6 22:02:55 2018
  InstallationDate: Installed on 2018-03-03 (187 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) :   N o   s u c h   f i l e  
 o r   d i r e c t o r y
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:MKII failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   m a i n : 7 8 8 :   a u d 
i o   o p e n   e r r o r :   N o   s u c h   f i l e   o r   d i r e c t o r y
  Symptom_Card: TASCAM US-122mkII - US122 MKII
  Symptom_Type: None of the above
  Title: [USB-Audio - US122 MKII, recording] Recording problem
  UpgradeStatus: Upgraded to bionic on 2018-09-02 (4 days ago)
  dmi.bios.date: 03/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.ch

[Touch-packages] [Bug 1787757] [NEW] pinning doesn't recognizes releases names

2018-08-18 Thread Alfredo Rezinovsky
Public bug reported:

Because pinning doesn't recongnizes releases names and treats them
alphabetically it fails knowing which package is newest.

This failed because the alphabet has ended and release names started
again with A, B...

Eg: 13.2.1-1bionic seems as a downgrade for 13.2.1-1xenial when it's
really an upgrade.

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

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

Title:
  pinning doesn't recognizes releases names

Status in apt package in Ubuntu:
  New

Bug description:
  Because pinning doesn't recongnizes releases names and treats them
  alphabetically it fails knowing which package is newest.

  This failed because the alphabet has ended and release names started
  again with A, B...

  Eg: 13.2.1-1bionic seems as a downgrade for 13.2.1-1xenial when it's
  really an upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787757/+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 1686211] [NEW] package libpython2.7 2.7.11-7ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to '/usr/lib/i386-lin

2017-04-25 Thread Alfredo Bateman
Public bug reported:

i dont know details thinked was automatic

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpython2.7 2.7.11-7ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
Date: Tue Apr 25 15:47:34 2017
ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to 
'/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected end of file 
or stream
InstallationDate: Installed on 2017-04-23 (2 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: python2.7
Title: package libpython2.7 2.7.11-7ubuntu1 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to 
'/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected end of file 
or stream
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libpython2.7 2.7.11-7ubuntu1 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/i386-linux-gnu/libpython2.7.so.1.0'
  to '/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected
  end of file or stream

Status in python2.7 package in Ubuntu:
  New

Bug description:
  i dont know details thinked was automatic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpython2.7 2.7.11-7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Tue Apr 25 15:47:34 2017
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to 
'/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2017-04-23 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python2.7
  Title: package libpython2.7 2.7.11-7ubuntu1 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to 
'/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1686211/+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 1685473] [NEW] package gir1.2-accounts-1.0:amd64 1.23+17.04.20161104-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

2017-04-22 Thread Alfredo Rangel
Public bug reported:

This error occurs without nothing done by me. It occurs all the time...

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gir1.2-accounts-1.0:amd64 1.23+17.04.20161104-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Fri Apr 21 12:23:57 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-11-22 (151 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: libaccounts-glib
Title: package gir1.2-accounts-1.0:amd64 1.23+17.04.20161104-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to zesty on 2017-04-21 (0 days ago)

** Affects: libaccounts-glib (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check zesty

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

Title:
  package gir1.2-accounts-1.0:amd64 1.23+17.04.20161104-0ubuntu1 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in libaccounts-glib package in Ubuntu:
  New

Bug description:
  This error occurs without nothing done by me. It occurs all the
  time...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gir1.2-accounts-1.0:amd64 1.23+17.04.20161104-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 21 12:23:57 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-22 (151 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libaccounts-glib
  Title: package gir1.2-accounts-1.0:amd64 1.23+17.04.20161104-0ubuntu1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-04-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libaccounts-glib/+bug/1685473/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

2017-02-13 Thread alfredo
I have a Toshiba Satellite Pro, and it has same problem: white noise for
internal microphone.

> uname -a
Linux DarkEnergy 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

> lspci|grep -i aud
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1638348] [NEW] package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubun

2016-11-01 Thread Jose Alfredo Gomes Areas
Public bug reported:

No details available

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libjpeg-progs 8c-2ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic i686
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
Date: Tue Nov  1 15:05:03 2016
ErrorMessage: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no 
pacote libjpeg-turbo-progs 1.3.0-0ubuntu2
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: libjpeg8-empty
Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar 
sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote 
libjpeg-turbo-progs 1.3.0-0ubuntu2
UpgradeStatus: Upgraded to xenial on 2016-09-21 (41 days ago)

** Affects: libjpeg8-empty (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar
  sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-
  turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  No details available

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Tue Nov  1 15:05:03 2016
  ErrorMessage: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no 
pacote libjpeg-turbo-progs 1.3.0-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar 
sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  UpgradeStatus: Upgraded to xenial on 2016-09-21 (41 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1638348/+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 1577599] Re: [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted / Audio Notification unstable (Popping in/out)

2016-05-22 Thread Alfredo Mendez
After looking through other distros, this is a widespread bug. I've
tested Ubuntu Mate 16.04 and the same issue persists, instead of
notification, the audio cuts off at times.

Another distro i've tested is ChaletOS, the notification is constant in
this one and same audio issues persist. I would recommend switching this
to critical.

http://i.imgur.com/FXPqPs8.png

I did not screenshot the Mate distro since I dont have a lot of time in
my hands, but you can technically see that in ChaletOS, its also
affected. Which leads that my current setup is incompatible with any new
current linux distros.

Lastly, there is some sort of Bluetooth bug as well. This computer does
not have any sort of WIFI/Bluetooth capabilities that I'm aware of in
Windows. So, the issue is bigger than I thought it would be. I will
continue to analyze further. Thanks everyone for the fast notice.

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

Title:
  [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted /
  Audio Notification unstable (Popping in/out)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  For a better explanation, here is a video I've made.
  https://youtu.be/8q092XpLT-Y

  For further diagnostics, here is a ubuntu forum post I've made.
  http://ubuntuforums.org/showthread.php?t=2322708

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0c:   deviantxs   1672 F...m pulseaudio
   /dev/snd/controlC2:  deviantxs   1672 F pulseaudio
   /dev/snd/controlC0:  deviantxs   1672 F pulseaudio
   /dev/snd/controlC1:  deviantxs   1672 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May  2 16:35:54 2016
  InstallationDate: Installed on 2016-04-30 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM1855
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr1501:bd08/20/2013:svnASUSTeKCOMPUTERINC.:pnCM1855:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCM1855:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: CM1855
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1577599/+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 1577599] [NEW] [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted / Audio Notification unstable (Popping in/out)

2016-05-02 Thread Alfredo De La Mora Mendez
Public bug reported:

For a better explanation, here is a video I've made.
https://youtu.be/8q092XpLT-Y

For further diagnostics, here is a ubuntu forum post I've made.
http://ubuntuforums.org/showthread.php?t=2322708

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC2D0c:   deviantxs   1672 F...m pulseaudio
 /dev/snd/controlC2:  deviantxs   1672 F pulseaudio
 /dev/snd/controlC0:  deviantxs   1672 F pulseaudio
 /dev/snd/controlC1:  deviantxs   1672 F pulseaudio
CurrentDesktop: Unity
Date: Mon May  2 16:35:54 2016
InstallationDate: Installed on 2016-04-30 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
Symptom_Card: Built-in Audio - HDA ATI SB
Symptom_Jack: Green Line Out, Rear
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: CM1855
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
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.:bvr1501:bd08/20/2013:svnASUSTeKCOMPUTERINC.:pnCM1855:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCM1855:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: CM1855
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug xenial

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

Title:
  [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted /
  Audio Notification unstable (Popping in/out)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  For a better explanation, here is a video I've made.
  https://youtu.be/8q092XpLT-Y

  For further diagnostics, here is a ubuntu forum post I've made.
  http://ubuntuforums.org/showthread.php?t=2322708

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0c:   deviantxs   1672 F...m pulseaudio
   /dev/snd/controlC2:  deviantxs   1672 F pulseaudio
   /dev/snd/controlC0:  deviantxs   1672 F pulseaudio
   /dev/snd/controlC1:  deviantxs   1672 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May  2 16:35:54 2016
  InstallationDate: Installed on 2016-04-30 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM1855
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr1501:bd08/20/2013:svnASUSTeKCOMPUTERINC.:pnCM1855:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCM1855:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: CM1855
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1577599/+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 1313546] Re: keyboard shortcuts not working

2016-02-29 Thread Alfredo Marchini
Hi,
I'm really sorry but laptop's motherboard has gone some weeks ago. 
Now I have a zbook 15 g2 with xenial amd64 installed... it works very well.
Thank you very much
Bye

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

Title:
  keyboard shortcuts not working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi all,
  since the release upgrade to 14.04 amd64 I have some problems with keyboard, 
I think the problem is xorg or gnome-shell related, I'll try to explain it. The 
laptop is a Asus N56VZ, if I press any of the fn keys (except the laptop screen 
on-off) they don't work anymore, no response from the os.
  But If I go in settings -> keyboard -> shortcuts, I find the fn buttons 
properly configured and, If I try to reconfigure the keyboard backlight fn 
button, for example, the system recognize it, as any other fn button.  
  So the system recognize the fn buttons, but they don't work inside 
gnome-shell session.
  Another strange think is the CTRL+ALT+T button, that doesn't work anymore, 
but in keyboard shortcuts is correctly recognized and configured.
  Thank you very much
  Bye

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  334.21  Thu Feb 27 15:55:45 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr 28 09:23:03 2014
  DistUpgraded: 2014-04-18 10:22:58,581 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-334, 334.21, 3.13.0-24-generic, x86_64: installed
   vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103]
   NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103]
  InstallationDate: Installed on 2013-05-11 (351 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MachineType: ASUSTeK COMPUTER INC. N56VZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a960f078-a3fd-4a99-9d65-8f0ed45a85f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (9 days ago)
  dmi.bios.date: 05/22/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.217
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.217:bd05/22/2013:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.53+git20140420.d4083dc7-0ubuntu0ricotz
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.2.0~git20140424.fd92346c-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.2.0~git20140424.fd92346c-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.3.99+git20140420.48d3dbc8-0ubuntu0ricotz
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.911+git20140420.08e71e18-0ubuntu0ricotz
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt
  xserver.bootTime: Mon Apr 28 09:13:05 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] KMS not enabled
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12620 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2

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

[Touch-packages] [Bug 1470730] Re: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work

2015-12-23 Thread Alfredo
Just the same situation reported by Vytautas Lukenskas (lukevyta)

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

Title:
  [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line
  in/Line out on docking station doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When I plug in external speakers to line in/line out combo on the
  laptop the internal speakers are turned off but when I plug the
  speakers into the docking station (HP UltraSlim Dock 2013 EURO,
  D9Y32AA) music keeps playing in the internal speakers. Similar
  behaviour (nothing happens) is experienced with microphone connected
  to line in on docking station.

  ### Expected behaviour
  Plugging in external speakers to docking station should turn off sound from 
laptop internal speakers.

  Plugging in microphone to line in on docking station should switch
  from "internal microphone" to "microphone" in Ubuntu sound settings.

  ### Current behaviour
  Sound keeps playing in internal speakers when plugging in external speakers 
to docking station.

  Plugging in microphone to line in on docking station, nothing happens.

  ### Hardware
  Laptop: HP EliteBook 840 G2
  Product number: H9W19EA#AK8

  Docking station: HP UltraSlim Dock 2013 EURO
  Product number: D9Y32AA

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chol   2001 F pulseaudio
   /dev/snd/controlC0:  chol   2001 F pulseaudio
   /dev/snd/controlC1:  chol   2001 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  2 08:16:15 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-06-05 (26 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M71 Ver. 01.04
  dmi.board.name: 2216
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.54
  dmi.chassis.asset.tag: 5CG5093YZ7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:svnHewlett-Packard:pnHPEliteBook840G2:pvrA3009D410303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G2
  dmi.product.version: A3009D410303
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1470730/+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 1500252] [NEW] package libqt4-declarative (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6' to '/usr/

2015-09-27 Thread Alfredo
Public bug reported:

aa

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: libqt4-declarative (not installed)
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic i686
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
Date: Sun Sep 27 21:19:26 2015
DuplicateSignature: package:libqt4-declarative:(not installed):cannot copy 
extracted data for './usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6' to 
'/usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6.dpkg-new': unexpected end of 
file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6' to 
'/usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6.dpkg-new': unexpected end of 
file or stream
InstallationDate: Installed on 2015-09-27 (0 days ago)
InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4
SourcePackage: qt4-x11
Title: package libqt4-declarative (not installed) failed to install/upgrade: 
cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6' to 
'/usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6.dpkg-new': unexpected end of 
file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 vivid

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

Title:
  package libqt4-declarative (not installed) failed to install/upgrade:
  cannot copy extracted data for './usr/lib/i386-linux-
  gnu/libQtDeclarative.so.4.8.6' to '/usr/lib/i386-linux-
  gnu/libQtDeclarative.so.4.8.6.dpkg-new': unexpected end of file or
  stream

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  aa

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: libqt4-declarative (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  Date: Sun Sep 27 21:19:26 2015
  DuplicateSignature: package:libqt4-declarative:(not installed):cannot copy 
extracted data for './usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6' to 
'/usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6.dpkg-new': unexpected end of 
file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6' to 
'/usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6.dpkg-new': unexpected end of 
file or stream
  InstallationDate: Installed on 2015-09-27 (0 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: qt4-x11
  Title: package libqt4-declarative (not installed) failed to install/upgrade: 
cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6' to 
'/usr/lib/i386-linux-gnu/libQtDeclarative.so.4.8.6.dpkg-new': unexpected end of 
file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1500252/+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 1488813] [NEW] package python3 failed to install/upgrade

2015-08-26 Thread Alfredo Pacheco Jr
Public bug reported:

package python3-problem-report 2.14.1-0ubuntu3.11 failed to
install/upgrade: unable to securely remove '/usr/share/doc/python3
-problem-report/copyright.dpkg-new': Read-only file system

Multiple packages failed to install, including this one. Occured when
attempting to run software updater.


-Version-
Kernel  : Linux 3.13.0-62-generic (i686)
Compiled: #102-Ubuntu SMP Tue Aug 11 14:28:35 UTC 2015
C Library   : Unknown
Default C Compiler  : Unknown
Distribution: Ubuntu 14.04.3 LTS
-Current Session-
Computer Name   : 
User Name   
Home Directory  : 
Desktop Environment : LXDE (Lubuntu)
-Misc-
Uptime  : 1 day, 5 hours and 8 minutes
Load Average: 0.50, 0.84, 1.59

Python: 2.7.6

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python3-problem-report 2.14.1-0ubuntu3.11
ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
Uname: Linux 3.13.0-62-generic i686
ApportLog:
 
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: i386
Date: Wed Aug 26 00:50:36 2015
Dependencies:
 
DuplicateSignature: package:python3-problem-report:2.14.1-0ubuntu3.11:unable to 
securely remove '/usr/share/doc/python3-problem-report/copyright.dpkg-new': 
Read-only file system
ErrorMessage: unable to securely remove 
'/usr/share/doc/python3-problem-report/copyright.dpkg-new': Read-only file 
system
InstallationDate: Installed on 2014-11-08 (290 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
PackageArchitecture: all
SourcePackage: apport
Title: package python3-problem-report 2.14.1-0ubuntu3.11 failed to 
install/upgrade: unable to securely remove 
'/usr/share/doc/python3-problem-report/copyright.dpkg-new': Read-only file 
system
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 trusty

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

Title:
  package python3 failed to install/upgrade

Status in apport package in Ubuntu:
  New

Bug description:
  package python3-problem-report 2.14.1-0ubuntu3.11 failed to
  install/upgrade: unable to securely remove '/usr/share/doc/python3
  -problem-report/copyright.dpkg-new': Read-only file system

  Multiple packages failed to install, including this one. Occured when
  attempting to run software updater.


  -Version-
  Kernel: Linux 3.13.0-62-generic (i686)
  Compiled  : #102-Ubuntu SMP Tue Aug 11 14:28:35 UTC 2015
  C Library : Unknown
  Default C Compiler: Unknown
  Distribution  : Ubuntu 14.04.3 LTS
  -Current Session-
  Computer Name : 
  User Name 
  Home Directory: 
  Desktop Environment   : LXDE (Lubuntu)
  -Misc-
  Uptime: 1 day, 5 hours and 8 minutes
  Load Average  : 0.50, 0.84, 1.59

  Python: 2.7.6

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python3-problem-report 2.14.1-0ubuntu3.11
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic i686
  ApportLog:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  Date: Wed Aug 26 00:50:36 2015
  Dependencies:
   
  DuplicateSignature: package:python3-problem-report:2.14.1-0ubuntu3.11:unable 
to securely remove '/usr/share/doc/python3-problem-report/copyright.dpkg-new': 
Read-only file system
  ErrorMessage: unable to securely remove 
'/usr/share/doc/python3-problem-report/copyright.dpkg-new': Read-only file 
system
  InstallationDate: Installed on 2014-11-08 (290 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: apport
  Title: package python3-problem-report 2.14.1-0ubuntu3.11 failed to 
install/upgrade: unable to securely remove 
'/usr/share/doc/python3-problem-report/copyright.dpkg-new': Read-only file 
system
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1488813/+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 1074778] Re: Upgrading to 12.10 created a "~/fontconfig" folder but did not delete it

2015-04-18 Thread Alfredo Hernández
Three years and this bug is still marked just as "Confirmed"? Oh, boy...

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

Title:
  Upgrading to 12.10 created a "~/fontconfig" folder but did not delete
  it

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from Ubuntu 12.04 to 12.10. In the process, a folder called
  "~/fontconfig" was created and not deleted. This happened on my two
  machines.

  More information here: http://askubuntu.com/questions/202796/what-is-
  the-fontconfig-folder-in-my-home-may-i-delete-it

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: fontconfig 2.10.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sat Nov  3 18:57:29 2012
  InstallationDate: Installed on 2012-04-29 (188 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1074778/+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 1402195] Re: Newer versions available

2014-12-26 Thread Alfredo Hernández
The workaround  worked just fine to install  nakasi LRX22G from LRX21P
(Ubuntu GNOME 14.10 x64).

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

Title:
  Newer versions available

Status in android-tools package in Ubuntu:
  Triaged
Status in android-tools source package in Vivid:
  Triaged

Bug description:
  When adb sideloading 5.0.0 -> 5.0.1, the recovery on a nexus 5
  requires at least adb 1.0.32

  $ adb version
  Android Debug Bridge version 1.0.31

  :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: android-tools-adb 4.2.2+git20130218-3ubuntu36
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 13 14:47:38 2014
  InstallationDate: Installed on 2014-02-07 (308 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: android-tools
  UpgradeStatus: Upgraded to utopic on 2014-11-08 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1402195/+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 1384615] [NEW] package tzdata-java 2014e-0ubuntu0.14.04 failed to install/upgrade: unable to securely remove '/usr/share/javazi/Atlantic/Canary.dpkg-new': Read-only file system

2014-10-23 Thread Alfredo Pacheco Jr
Public bug reported:

Error occurred while attempting to update Java 7.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: tzdata-java 2014e-0ubuntu0.14.04
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic i686
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: i386
Date: Thu Oct 23 01:28:19 2014
DuplicateSignature: package:tzdata-java:2014e-0ubuntu0.14.04:unable to securely 
remove '/usr/share/javazi/Atlantic/Canary.dpkg-new': Read-only file system
ErrorMessage: unable to securely remove 
'/usr/share/javazi/Atlantic/Canary.dpkg-new': Read-only file system
InstallationDate: Installed on 2014-10-19 (3 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
PackageArchitecture: all
SourcePackage: tzdata
Title: package tzdata-java 2014e-0ubuntu0.14.04 failed to install/upgrade: 
unable to securely remove '/usr/share/javazi/Atlantic/Canary.dpkg-new': 
Read-only file system
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 trusty

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

Title:
  package tzdata-java 2014e-0ubuntu0.14.04 failed to install/upgrade:
  unable to securely remove '/usr/share/javazi/Atlantic/Canary.dpkg-
  new': Read-only file system

Status in “tzdata” package in Ubuntu:
  New

Bug description:
  Error occurred while attempting to update Java 7.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tzdata-java 2014e-0ubuntu0.14.04
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  Date: Thu Oct 23 01:28:19 2014
  DuplicateSignature: package:tzdata-java:2014e-0ubuntu0.14.04:unable to 
securely remove '/usr/share/javazi/Atlantic/Canary.dpkg-new': Read-only file 
system
  ErrorMessage: unable to securely remove 
'/usr/share/javazi/Atlantic/Canary.dpkg-new': Read-only file system
  InstallationDate: Installed on 2014-10-19 (3 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: tzdata
  Title: package tzdata-java 2014e-0ubuntu0.14.04 failed to install/upgrade: 
unable to securely remove '/usr/share/javazi/Atlantic/Canary.dpkg-new': 
Read-only file system
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1384615/+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 1384612] [NEW] package tzdata 2014e-0ubuntu0.14.04 failed to install/upgrade: unable to securely remove '/usr/sbin/tzconfig.dpkg-new': Read-only file system

2014-10-23 Thread Alfredo Pacheco Jr
Public bug reported:

package tzdata 2014e-0ubuntu0.14.04 failed to install/upgrade: unable to
securely remove '/usr/sbin/tzconfig.dpkg-new': Read-only file system

Error occured while attempting to install Java 7 update on 23 OCT 2014.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: tzdata 2014e-0ubuntu0.14.04
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic i686
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: i386
Date: Thu Oct 23 01:28:19 2014
DuplicateSignature: package:tzdata:2014e-0ubuntu0.14.04:unable to securely 
remove '/usr/sbin/tzconfig.dpkg-new': Read-only file system
ErrorMessage: unable to securely remove '/usr/sbin/tzconfig.dpkg-new': 
Read-only file system
InstallationDate: Installed on 2014-10-19 (3 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
PackageArchitecture: all
SourcePackage: tzdata
Title: package tzdata 2014e-0ubuntu0.14.04 failed to install/upgrade: unable to 
securely remove '/usr/sbin/tzconfig.dpkg-new': Read-only file system
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 trusty

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

Title:
  package tzdata 2014e-0ubuntu0.14.04 failed to install/upgrade: unable
  to securely remove '/usr/sbin/tzconfig.dpkg-new': Read-only file
  system

Status in “tzdata” package in Ubuntu:
  New

Bug description:
  package tzdata 2014e-0ubuntu0.14.04 failed to install/upgrade: unable
  to securely remove '/usr/sbin/tzconfig.dpkg-new': Read-only file
  system

  Error occured while attempting to install Java 7 update on 23 OCT
  2014.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tzdata 2014e-0ubuntu0.14.04
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  Date: Thu Oct 23 01:28:19 2014
  DuplicateSignature: package:tzdata:2014e-0ubuntu0.14.04:unable to securely 
remove '/usr/sbin/tzconfig.dpkg-new': Read-only file system
  ErrorMessage: unable to securely remove '/usr/sbin/tzconfig.dpkg-new': 
Read-only file system
  InstallationDate: Installed on 2014-10-19 (3 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: tzdata
  Title: package tzdata 2014e-0ubuntu0.14.04 failed to install/upgrade: unable 
to securely remove '/usr/sbin/tzconfig.dpkg-new': Read-only file system
  UpgradeStatus: No upgrade log present (probably fresh install)

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