[Touch-packages] [Bug 1753509] Re: avahi-daemon adds/installs every printer on network

2024-02-20 Thread Carlos Renê
I'm testing Ubuntu 24.04 and have same problem. All print duplication in
GTK applications like Firefox, Libreoffice :-/

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

Title:
  avahi-daemon adds/installs every printer on network

Status in cups package in Ubuntu:
  Triaged

Bug description:
  When connected to a network, avahi-daemon adds & installs all printer
  on a network without being prompted.  This is not desired behaviour.
  Discovery of the printers is good, but not automatic installation &
  addition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  5 09:29:05 2018
  InstallationDate: Installed on 2017-09-29 (157 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1753509/+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 2045931] [NEW] ps3 sixasis controller request pin to connect to bt

2023-12-07 Thread Carlos
Public bug reported:

Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
to connect my PS3 Sixasis controller via bluetooth. It is aking to enter
a PIN in the device (not possible to enter a pin in the gamepad).

Source pacakge (from "apt list -a bluez"):

bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64

Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again
without asking for a connection PIN.

Ubuntu release:
Description:Ubuntu 22.04.3 LTS
Release:22.04

Package version:
bluez:
  Installed: 5.64-0ubuntu1.1

Expected to happen:
Connect PS3 Controller by Bluetooth without asking for a PIN code

Happened instead:
PS3 Controller cannot connect because PIN code is requested

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

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

Title:
  ps3 sixasis controller request pin to connect to bt

Status in bluez package in Ubuntu:
  New

Bug description:
  Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
  to connect my PS3 Sixasis controller via bluetooth. It is aking to
  enter a PIN in the device (not possible to enter a pin in the
  gamepad).

  Source pacakge (from "apt list -a bluez"):

  bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64

  Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again
  without asking for a connection PIN.

  Ubuntu release:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Package version:
  bluez:
Installed: 5.64-0ubuntu1.1

  Expected to happen:
  Connect PS3 Controller by Bluetooth without asking for a PIN code

  Happened instead:
  PS3 Controller cannot connect because PIN code is requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2030505] Re: on ubuntu 22.04 systemd fails with per interface dns configurations

2023-11-17 Thread Carlos Martinez
Any update on when this will be addressed in Ubuntu 22.04? This is
impacting several of our users.

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

Title:
  on ubuntu 22.04 systemd fails with per interface dns configurations

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi There,

  Systemd seems to work awesome, except when dns proxy is running on
  localhost ipaddress.  The below fix seems to takescare of such cases.
  Unfortunately this is not included in the latest systemd versions on
  ubuntu22.04 LTS.  Is it possible to consider our humble request and
  add this to the systemd versions supported on ubuntu22.04, it is
  creating lots of issues for our users.

  https://github.com/systemd/systemd/pull/25438

  I am raising this ticket as requested below

  -snippet

  actionparsnip 
  Aug 5, 2023, 6:26 PM (2 days ago)
  to me

  Your question #707538 on systemd in Ubuntu changed:
  https://answers.launchpad.net/ubuntu/+source/systemd/+question/707538

  Status: Open => Answered

  actionparsnip proposed the following answer:
  I suggest you report a bug. Add your URL to the bug for visibility. You
  can start the process by running:

  ubuntu-bug systemd
  

  Thanks in advance

  Regards,
  Dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2030505/+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 2018656] Re: login process frozen in between username and password

2023-09-19 Thread Luis Carlos Nogueira Mijias
Still with the same error, I have already uninstalled Ubuntu and it
continues to freeze when logging in.

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

Title:
  login process frozen in between username and password

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

Bug description:
   MY SYSTEM 
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

  gnome-online-accounts:
Installed: 3.48.0-1
Candidate: 3.48.0-1
Version table:
   *** 3.48.0-1 500
  500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I have tested this on my desktop running 23.04 on Intel I-9, and the second 
desktop running the same (23.04) but on Intel I-7, and both of them show the 
same problem.

  -PROBLEM---

  When I entered my email address in my Google account, I could provide
  my email address, and after I clicked on the following form to enter
  my password.  The form was able to pick up my email address and moved
  to the following form for password entry; it just froze in between.
  Sometimes, the password form could pick up the first keyboard
  character but never go past 2nd character.  Sometimes, it just froze
  without being able to pick up the first keyboard character.

  Then a bit later, the whole box of gnome-online-accounts blacks out.
  Closing with X didn't work, so I had to xkill the app.

  -TYPICAL BEHAVIOR---

  Usually, on 22.04, I never had a problem adding online accounts,
  particularly for Google accounts.   The first form asked for my email
  address, and quickly moved on to the following form asking for a
  password.  Once the password is accepted, it will move on to the next
  form requesting my authorization for GNOME to connect to my account on
  Google before adding it to my Ubuntu system (I'd see the drive folder
  on the bar on Nautilus).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-online-accounts 3.48.0-1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  6 13:51:07 2023
  InstallationDate: Installed on 2023-05-04 (2 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2018656/+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 2017224] Re: [asus-bluetooth] Cannot enable bluetooth in gnome-shell on ASUS ZenBook UX435EG

2023-05-05 Thread Carlos Ernani da Veiga
I followed the instructions on this post and it didn't work, but this
other post (https://www.techtudo.com.br/dicas-e-
tutoriais/2017/07/aprenda-como-configurar-o-bluetooth-no-linux.ghtml)
made it work properly, and I had to remove the registered devices.

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

Title:
  [asus-bluetooth] Cannot enable bluetooth in gnome-shell on ASUS
  ZenBook UX435EG

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 23.04, Bluetooth service is started but can't enable
  it in gnome-shell.

  Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth 
service...
  Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already 
exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 
555)
  Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66
  Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server
  Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus 
experimental not enabled
  Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to 
init vcp plugin
  Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus 
experimental not enabled
  Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to 
init mcp plugin
  Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus 
experimental not enabled
  Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to 
init bap plugin
  Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service.
  Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 
initialized


  
  I installed the latest linux-firmware from the repo but it didn't help.

  # dmesg | grep -i bluetooth
  [ 18.861759] Bluetooth: Core ver 2.22
  [ 18.863617] NET: Registered PF_BLUETOOTH protocol family
  [ 18.863621] Bluetooth: HCI device and connection manager initialized
  [ 18.863628] Bluetooth: HCI socket layer initialized
  [ 18.863631] Bluetooth: L2CAP socket layer initialized
  [ 18.863638] Bluetooth: SCO socket layer initialized
  [ 19.146683] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
  [ 19.147702] Bluetooth: hci0: Device revision is 2
  [ 19.147707] Bluetooth: hci0: Secure boot is enabled
  [ 19.147709] Bluetooth: hci0: OTP lock is enabled
  [ 19.147712] Bluetooth: hci0: API lock is enabled
  [ 19.147714] Bluetooth: hci0: Debug lock is disabled
  [ 19.147716] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [ 19.150729] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
  [ 19.150841] Bluetooth: hci0: Boot Address: 0x24800
  [ 19.150843] Bluetooth: hci0: Firmware Version: 15-45.22
  [ 19.998952] Bluetooth: hci0: urb 8cd2a5b0 failed to resubmit (2)
  [ 20.015315] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [ 20.015321] Bluetooth: BNEP filters: protocol multicast
  [ 20.015329] Bluetooth: BNEP socket layer initialized
  [ 22.005627] Bluetooth: hci0: command 0xfc09 tx timeout
  [ 30.037760] Bluetooth: hci0: Failed to send firmware data (-110)
  [ 30.037855] Bluetooth: hci0: Intel reset sent to retry FW download
  [ 32.213626] Bluetooth: hci0: Failed to read MSFT supported features (-110)


  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: bluez 5.66-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 21 11:44:40 2023
  InstallationDate: Installed on 2023-01-04 (106 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  InterestingModules: bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago)
  dmi.bios.date: 04/22/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX435EG.315
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX435EG
  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:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX435EG_UX435EG
  dmi.product.version: 1.0
  

[Touch-packages] [Bug 1990684] Re: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed

2022-09-23 Thread Carlos F.
Set APT::Get::Never-Include-Phased-Updates "1"; and try again. Packages
will be kept-back.

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

Title:
  grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but
  2.06-2ubuntu10 is to be installed

Status in apt package in Ubuntu:
  Confirmed
Status in grub2-signed package in Ubuntu:
  Fix Released

Bug description:
  # apt clean

  # apt update
  Hit:1 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy InRelease
  Hit:2 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates 
InRelease
  Hit:3 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-backports 
InRelease
  Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  24 packages can be upgraded. Run 'apt list --upgradable' to see them.

  # apt upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  The following packages have unmet dependencies:
   grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 
2.06-2ubuntu10 is to be installed
  E: Broken packages

  # apt show -a grub-efi-arm64 2>/dev/null | grep -P "Version:|APT-Sources:"
  Version: 2.06-2ubuntu10
  APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports 
jammy-updates/main arm64 Packages
  Version: 2.06-2ubuntu7
  APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy/main 
arm64 Packages

  # curl -s 
"http://ports.ubuntu.com/ubuntu-ports/dists/jammy/main/binary-arm64/Packages.gz;
 | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:"
  Package: grub-efi-arm64-dbg
  Depends: grub-efi-arm64-bin (= 2.06-2ubuntu7)
  Package: grub-efi-arm64-signed
  Depends: grub-efi-arm64 (= 2.06-2ubuntu7)

  # curl -s 
"http://ports.ubuntu.com/ubuntu-ports/dists/jammy-updates/main/binary-arm64/Packages.gz;
 | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:"
  Package: grub-efi-arm64-dbg
  Depends: grub-efi-arm64-bin (= 2.06-2ubuntu10)
  Package: grub-efi-arm64-signed
  Depends: grub-efi-arm64 (= 2.06-2ubuntu10)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: grub-efi-arm64-signed 1.180+2.06-2ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri Sep 23 13:12:07 2022
  Ec2AMI: ami-092d30890417a55e5
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ca-central-1d
  Ec2InstanceType: t4g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: grub2-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1990684/+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 1990526] Re: [FFe] UDI snap no longer strictly needed for WSL OOBE

2022-09-22 Thread Carlos Nihelton
** Patch removed: "ubuntu wsl seed diff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+attachment/5618055/+files/ubuntu-seeds.diff

** Patch added: "ubuntu wsl seed diff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+attachment/5618064/+files/0001-WSL-Replaces-UDI-by-Subiquity-snap-LP-1990526.patch

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

Title:
  [FFe] UDI snap no longer strictly needed for WSL OOBE

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop Installer (UDI, for short) package implementing the WSL
  OOBE has been ported to Windows and the WSL application is able to
  launch the OOBE running as a native Win32 application, instead of
  relying on WSLg to display the OOBE.

  That implies in the possibility of replacing UDI by Subiquity snap,
  which results in a smaller rootfs image (besides an enhanced
  experience due native rendering on graphics - instead of depending on
  RDP as it is currently with the OOBE running inside Ubuntu).

  Fixing this would require:

  - replace UDI by Subiquity snaps in the WSL seed;
  - updating the wsl-setup package to the latest upstream (which is able to 
mount and launch Subiquity from its snap) LP: #1990426 .

  Following the approach above won't have effects outside of WSL.

  Kinetic being not an LTS is a good release to receive the fix for this
  first, as it affects a small audience of Ubuntu WSL community, giving
  us time to learn from them before backporting this to Jammy early next
  cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+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 1990526] Re: [FFe] UDI snap no longer strictly needed for WSL OOBE

2022-09-22 Thread Carlos Nihelton
** Patch added: "ubuntu wsl seed diff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+attachment/5618055/+files/ubuntu-seeds.diff

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

Title:
  [FFe] UDI snap no longer strictly needed for WSL OOBE

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop Installer (UDI, for short) package implementing the WSL
  OOBE has been ported to Windows and the WSL application is able to
  launch the OOBE running as a native Win32 application, instead of
  relying on WSLg to display the OOBE.

  That implies in the possibility of replacing UDI by Subiquity snap,
  which results in a smaller rootfs image (besides an enhanced
  experience due native rendering on graphics - instead of depending on
  RDP as it is currently with the OOBE running inside Ubuntu).

  Fixing this would require:

  - replace UDI by Subiquity snaps in the WSL seed;
  - updating the wsl-setup package to the latest upstream (which is able to 
mount and launch Subiquity from its snap) LP: #1990426 .

  Following the approach above won't have effects outside of WSL.

  Kinetic being not an LTS is a good release to receive the fix for this
  first, as it affects a small audience of Ubuntu WSL community, giving
  us time to learn from them before backporting this to Jammy early next
  cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+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 1990526] Re: [FFe] UDI snap no longer strictly needed for WSL OOBE

2022-09-22 Thread Carlos Nihelton
-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1990526

Title:
  [FFe] UDI snap no longer strictly needed for WSL OOBE

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop Installer (UDI, for short) package implementing the WSL
  OOBE has been ported to Windows and the WSL application is able to
  launch the OOBE running as a native Win32 application, instead of
  relying on WSLg to display the OOBE.

  That implies in the possibility of replacing UDI by Subiquity snap,
  which results in a smaller rootfs image (besides an enhanced
  experience due native rendering on graphics - instead of depending on
  RDP as it is currently with the OOBE running inside Ubuntu).

  Fixing this would require:

  - replace UDI by Subiquity snaps in the WSL seed;
  - updating the wsl-setup package to the latest upstream (which is able to 
mount and launch Subiquity from its snap) LP: #1990426 .

  Following the approach above won't have effects outside of WSL.

  Kinetic being not an LTS is a good release to receive the fix for this
  first, as it affects a small audience of Ubuntu WSL community, giving
  us time to learn from them before backporting this to Jammy early next
  cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+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 1990526] [NEW] [FFe] UDI snap no longer strictly needed for WSL OOBE

2022-09-22 Thread Carlos Nihelton
Public bug reported:

Ubuntu Desktop Installer (UDI, for short) package implementing the WSL
OOBE has been ported to Windows and the WSL application is able to
launch the OOBE running as a native Win32 application, instead of
relying on WSLg to display the OOBE.

That implies in the possibility of replacing UDI by Subiquity snap,
which results in a smaller rootfs image (besides an enhanced experience
due native rendering on graphics - instead of depending on RDP as it is
currently with the OOBE running inside Ubuntu).

Fixing this would require:

- replace UDI by Subiquity snaps in the WSL seed;
- updating the wsl-setup package to the latest upstream (which is able to mount 
and launch Subiquity from its snap) LP: #1990426 .

Following the approach above won't have effects outside of WSL.

Kinetic being not an LTS is a good release to receive the fix for this
first, as it affects a small audience of Ubuntu WSL community, giving us
time to learn from them before backporting this to Jammy early next
cycle.

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

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

Title:
  [FFe] UDI snap no longer strictly needed for WSL OOBE

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop Installer (UDI, for short) package implementing the WSL
  OOBE has been ported to Windows and the WSL application is able to
  launch the OOBE running as a native Win32 application, instead of
  relying on WSLg to display the OOBE.

  That implies in the possibility of replacing UDI by Subiquity snap,
  which results in a smaller rootfs image (besides an enhanced
  experience due native rendering on graphics - instead of depending on
  RDP as it is currently with the OOBE running inside Ubuntu).

  Fixing this would require:

  - replace UDI by Subiquity snaps in the WSL seed;
  - updating the wsl-setup package to the latest upstream (which is able to 
mount and launch Subiquity from its snap) LP: #1990426 .

  Following the approach above won't have effects outside of WSL.

  Kinetic being not an LTS is a good release to receive the fix for this
  first, as it affects a small audience of Ubuntu WSL community, giving
  us time to learn from them before backporting this to Jammy early next
  cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+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 1989352] Re: [WSL] Prepare kinetic for common snap use cases

2022-09-13 Thread Carlos Nihelton
Upgrading a Jammy instance with `do-release-upgrade -d` worked as
expected.

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

Title:
  [WSL] Prepare kinetic for common snap use cases

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Users of Ubuntu WSL might be surprised by unexpected dependencies when
  dealing with snaps. The Ubuntu WSL development team is looking for
  ways to let early adopters to experiment some snapd support in
  Kinetic, while still providing the most seamless experience for them.
  Tests done in WSL instances showed surprises that we should mitigate
  soon.

  Some examples are:

  * Sublime Text and Sublime Merge apps silently depend on libgl1. This
  seems a bug which we didn't yet figure out how to fix in the snaps
  themselves. Being such hidden dependencies, we'd expect to soon find
  similar cases as those.

  * Flutter snap provides all dependencies and runs without issues, but
  apps compiled by Flutter requires libgl1, libegl1 and libgtk-3-0
  present in the system during development. Attempting to just run any
  app compiled with Flutter during development will result in crash due
  those libs not being found. Most likely, once package as snaps, those
  apps will behave as expected, if the packager lists dependencies
  properly. The issue reported here affects the app developer
  experience.

  One solution for those problems is seeding for Ubuntu WSL
  specifically:

  - libgl1
  - libegl1
  - libgtk-3-0

  Experienced Ubuntu users would figure out how to overcome those issues
  very quickly, but we should expect that most of Ubuntu WSL userbase
  won't fit in that persona.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989352/+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 1989352] Re: [WSL] Prepare kinetic for common snap use cases

2022-09-12 Thread Carlos Nihelton
** Description changed:

  Users of Ubuntu WSL might be surprised by unexpected dependencies when
  dealing with snaps. The Ubuntu WSL development team is looking for ways
  to let early adopters to experiment some snapd support in Kinetic, while
  still providing the most seamless experience for them. Tests done in WSL
  instances showed surprises that we should mitigate soon.
  
  Some examples are:
  
  * Sublime Text and Sublime Merge apps silently depend on libgl1. This
  seems a bug which we didn't yet figure out how to fix in the snaps
  themselves. Being such hidden dependencies, we'd expect to soon find
  similar cases as those.
  
  * Flutter snap provides all dependencies and runs without issues, but
  apps compiled by Flutter requires libgl1, libegl1 and libgtk-3-0 present
  in the system during development. Attempting to just run any app
  compiled with Flutter during development will result in crash due those
  libs not being found. Most likely, once package as snaps, those apps
  will behave as expected, if the packager lists dependencies properly.
  The issue reported here affects the app developer experience.
  
  One solution for those problems is seeding for Ubuntu WSL specifically:
  
  - libgl1
  - libegl1
  - libgtk-3-0
  
  Experienced Ubuntu users would figure out how to overcome those issues
- very quickly, but we should expect that most of our userbase doesn't fit
- in that persona.
+ very quickly, but we should expect that most of Ubuntu WSL userbase
+ won't fit in that persona.

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

Title:
  [WSL] Prepare kinetic for common snap use cases

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Users of Ubuntu WSL might be surprised by unexpected dependencies when
  dealing with snaps. The Ubuntu WSL development team is looking for
  ways to let early adopters to experiment some snapd support in
  Kinetic, while still providing the most seamless experience for them.
  Tests done in WSL instances showed surprises that we should mitigate
  soon.

  Some examples are:

  * Sublime Text and Sublime Merge apps silently depend on libgl1. This
  seems a bug which we didn't yet figure out how to fix in the snaps
  themselves. Being such hidden dependencies, we'd expect to soon find
  similar cases as those.

  * Flutter snap provides all dependencies and runs without issues, but
  apps compiled by Flutter requires libgl1, libegl1 and libgtk-3-0
  present in the system during development. Attempting to just run any
  app compiled with Flutter during development will result in crash due
  those libs not being found. Most likely, once package as snaps, those
  apps will behave as expected, if the packager lists dependencies
  properly. The issue reported here affects the app developer
  experience.

  One solution for those problems is seeding for Ubuntu WSL
  specifically:

  - libgl1
  - libegl1
  - libgtk-3-0

  Experienced Ubuntu users would figure out how to overcome those issues
  very quickly, but we should expect that most of Ubuntu WSL userbase
  won't fit in that persona.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989352/+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 1989352] Re: [WSL] Prepare kinetic for common snap use cases

2022-09-12 Thread Carlos Nihelton
** Description changed:

  Users of Ubuntu WSL might be surprised by unexpected dependencies when
- dealing with snaps. The development team is looking for ways to let
- early adopters to experiment some snapd support in Kinetic, while still
- providing the most seamless experience for them. Tests done in WSL
- instances showed surprises that we should mitigate soon. Some examples
- are:
+ dealing with snaps. The Ubuntu WSL development team is looking for ways
+ to let early adopters to experiment some snapd support in Kinetic, while
+ still providing the most seamless experience for them. Tests done in WSL
+ instances showed surprises that we should mitigate soon.
  
- Sublime Text and Sublime Merge apps silently depend on libgl1.
- Flutter snap provides all dependencies, but apps compiled by Flutter requires 
libgl1, libegl1 and libgtk-3-0 present in the system.
+ Some examples are:
  
- Besides those, LXD, missing on Kinetic, is a good support for cloud
- related use cases, which are a large share of our user base, and also
- can be a good source of telemetry usage information, alongside with
- snapd.
+ * Sublime Text and Sublime Merge apps silently depend on libgl1. This
+ seems a bug which we didn't yet figure out how to fix in the snaps
+ themselves. Being such hidden dependencies, we'd expect to soon find
+ similar cases as those.
  
- One solution for this problem is seeding for Ubuntu WSL specifically:
+ * Flutter snap provides all dependencies and runs without issues, but
+ apps compiled by Flutter requires libgl1, libegl1 and libgtk-3-0 present
+ in the system during development. Attempting to just run any app
+ compiled with Flutter during development will result in crash due those
+ libs not being found. Most likely, once package as snaps, those apps
+ will behave as expected, if the packager lists dependencies properly.
+ The issue reported here affects the app developer experience.
+ 
+ One solution for those problems is seeding for Ubuntu WSL specifically:
  
  - libgl1
  - libegl1
  - libgtk-3-0
- - lxd
+ 
+ Experienced Ubuntu users would figure out how to overcome those issues
+ very quickly, but we should expect that most of our userbase doesn't fit
+ in that persona.

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

Title:
  [WSL] Prepare kinetic for common snap use cases

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Users of Ubuntu WSL might be surprised by unexpected dependencies when
  dealing with snaps. The Ubuntu WSL development team is looking for
  ways to let early adopters to experiment some snapd support in
  Kinetic, while still providing the most seamless experience for them.
  Tests done in WSL instances showed surprises that we should mitigate
  soon.

  Some examples are:

  * Sublime Text and Sublime Merge apps silently depend on libgl1. This
  seems a bug which we didn't yet figure out how to fix in the snaps
  themselves. Being such hidden dependencies, we'd expect to soon find
  similar cases as those.

  * Flutter snap provides all dependencies and runs without issues, but
  apps compiled by Flutter requires libgl1, libegl1 and libgtk-3-0
  present in the system during development. Attempting to just run any
  app compiled with Flutter during development will result in crash due
  those libs not being found. Most likely, once package as snaps, those
  apps will behave as expected, if the packager lists dependencies
  properly. The issue reported here affects the app developer
  experience.

  One solution for those problems is seeding for Ubuntu WSL
  specifically:

  - libgl1
  - libegl1
  - libgtk-3-0

  Experienced Ubuntu users would figure out how to overcome those issues
  very quickly, but we should expect that most of our userbase doesn't
  fit in that persona.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989352/+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 1989352] [NEW] [WSL] Prepare kinetic for common snap use cases

2022-09-12 Thread Carlos Nihelton
Public bug reported:

Users of Ubuntu WSL might be surprised by unexpected dependencies when
dealing with snaps. The development team is looking for ways to let
early adopters to experiment some snapd support in Kinetic, while still
providing the most seamless experience for them. Tests done in WSL
instances showed surprises that we should mitigate soon. Some examples
are:

Sublime Text and Sublime Merge apps silently depend on libgl1.
Flutter snap provides all dependencies, but apps compiled by Flutter requires 
libgl1, libegl1 and libgtk-3-0 present in the system.

Besides those, LXD, missing on Kinetic, is a good support for cloud
related use cases, which are a large share of our user base, and also
can be a good source of telemetry usage information, alongside with
snapd.

One solution for this problem is seeding for Ubuntu WSL specifically:

- libgl1
- libegl1
- libgtk-3-0
- lxd

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

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

Title:
  [WSL] Prepare kinetic for common snap use cases

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Users of Ubuntu WSL might be surprised by unexpected dependencies when
  dealing with snaps. The development team is looking for ways to let
  early adopters to experiment some snapd support in Kinetic, while
  still providing the most seamless experience for them. Tests done in
  WSL instances showed surprises that we should mitigate soon. Some
  examples are:

  Sublime Text and Sublime Merge apps silently depend on libgl1.
  Flutter snap provides all dependencies, but apps compiled by Flutter requires 
libgl1, libegl1 and libgtk-3-0 present in the system.

  Besides those, LXD, missing on Kinetic, is a good support for cloud
  related use cases, which are a large share of our user base, and also
  can be a good source of telemetry usage information, alongside with
  snapd.

  One solution for this problem is seeding for Ubuntu WSL specifically:

  - libgl1
  - libegl1
  - libgtk-3-0
  - lxd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989352/+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 1968764] Re: Google Login Window not rendering when adding Google Account

2022-04-12 Thread Carlos Peralta
*** This bug is a duplicate of bug 1966418 ***
https://bugs.launchpad.net/bugs/1966418

Same problem here, can not login into Google account in Ubuntu 22.04.

Login screen just blanks, no prompt.

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

Title:
  Google Login Window not rendering when adding Google Account

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

Bug description:
  When attempting to add a Google account through settings, the login
  window doesn't render correctly.

  It appears to load but only shows a stock background color.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 11:08:57 2022
  InstallationDate: Installed on 2020-12-18 (480 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1968764/+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 1968720] [NEW] Missing font on the Flutter installer UI in WSL

2022-04-12 Thread Carlos Nihelton
Public bug reported:

Since in WSL we don't have a real complete snap setup and the Flutter UI
sets the window title by using GTK+ API, it's necessary to make the
fonts-ubuntu package available in the system to avoid the bad user
experience of not being able to display the window title.

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

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

Title:
  Missing font on the Flutter installer UI in WSL

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Since in WSL we don't have a real complete snap setup and the Flutter
  UI sets the window title by using GTK+ API, it's necessary to make the
  fonts-ubuntu package available in the system to avoid the bad user
  experience of not being able to display the window title.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1968720/+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 1932579] Re: snap pt_BR locale shows warning every time

2021-09-17 Thread Carlos Eduardo Alves
@iogui, every system I've tried works well with that workaround (4
installations with Ubuntu 20.04). Please reinstall language-pack-pt-base
an try again.

Yes, it is a binary file, a gettext .po compiled into a .mo. The sed is a quick 
workaround that works fine for me even with the binary. If you continue having 
problems, another way is retranslating with these commands:
```
sudo cp /usr/share/locale-langpack/pt/LC_MESSAGES/snappy.mo 
/usr/share/locale-langpack/pt/LC_MESSAGES/snappy.mo~
msgunfmt /usr/share/locale-langpack/pt/LC_MESSAGES/snappy.mo > /tmp/snappy.po
sed -i 's/o directório de destino/O directório de destino/' /tmp/snappy.po # or 
edit with PoEditor
sudo msgfmt /tmp/snappy.po -o 
/usr/share/locale-langpack/pt/LC_MESSAGES/snappy.mo
```

I can't find the origin of these translations to contribute to 
language-pack-pt-base.
Do you know about these translations and how to contribute?
I only find some git hooks in the sources manipulating translation contents, 
but don't understood clearly how it is done. Some help is welcome.

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

Title:
  snap pt_BR locale shows warning every time

Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1932579/+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 1932579] Re: snap pt_BR locale shows warning every time

2021-08-26 Thread Carlos Eduardo Alves
** Changed in: language-pack-pt-base (Ubuntu)
   Status: New => Confirmed

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

Title:
  snap pt_BR locale shows warning every time

Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1932579/+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 1932579] Re: snap pt_BR locale shows warning every time

2021-08-26 Thread Carlos Eduardo Alves
** Also affects: language-pack-pt-base (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  snap pt_BR locale shows warning every time

Status in language-pack-pt-base package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1932579/+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 1918643] [NEW] package libjpeg-progs 8c-2ubuntu7 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-turbo-progs 1.1.90+svn733-

2021-03-11 Thread Carlos de Sá
Public bug reported:


This warning appears when I call some apps, Terminal included (yes, I'm working 
in a desktop environment)

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: libjpeg-progs 8c-2ubuntu7
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
AptOrdering:
 libjpeg9:amd64: Install
 libjpeg-progs:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Mar 11 06:50:08 2021
ErrorMessage: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no 
pacote libjpeg-turbo-progs 1.1.90+svn733-0ubuntu4.1
InstallationDate: Installed on 2021-03-09 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10ubuntu0.2
SourcePackage: libjpeg8-empty
Title: package libjpeg-progs 8c-2ubuntu7 failed to install/upgrade: a tentar 
sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-turbo-progs 
1.1.90+svn733-0ubuntu4.1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package groovy

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

Title:
  package libjpeg-progs 8c-2ubuntu7 failed to install/upgrade: a tentar
  sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-
  turbo-progs 1.1.90+svn733-0ubuntu4.1

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  
  This warning appears when I call some apps, Terminal included (yes, I'm 
working in a desktop environment)

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: libjpeg-progs 8c-2ubuntu7
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  AptOrdering:
   libjpeg9:amd64: Install
   libjpeg-progs:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Mar 11 06:50:08 2021
  ErrorMessage: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no 
pacote libjpeg-turbo-progs 1.1.90+svn733-0ubuntu4.1
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.2
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu7 failed to install/upgrade: a tentar 
sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-turbo-progs 
1.1.90+svn733-0ubuntu4.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1918643/+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 1685542] Re: xserver libinput and synaptics conflict on mouse/touchpad settings

2021-03-03 Thread Luiz Carlos Maciel Franco
why MatchIsTouchpad "on" for both???

synaptics and libinput xorg config at /usr/share/X11/xorg.conf.d/

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

Title:
  xserver libinput and synaptics conflict on mouse/touchpad settings

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  xserver-xorg-input-all was installed. As a result, both xserver-xorg-
  input synaptics and xserver-xorg-input-libinput got installed.

  This breaks usage for both natural scrolling *and* moving the primary
  button of the mouse/touchpad to the right (a.k.a. typing while being
  left-handed).

  Purging xserver-xorg-input-synaptics resolves it, with both natural
  scrolling and left-handedness now working.

  This bug only affects Gnome; KDE and Unity work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-input-all (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Apr 22 14:44:44 2017
  DistUpgraded: 2016-12-02 17:02:11,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:0655]
  InstallationDate: Installed on 2016-02-08 (439 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  MachineType: System76, Inc. Gazelle Professional
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2016-12-02 (140 days ago)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.00.05RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00.05RS76:bd08/15/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sat Apr 22 14:35:09 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1685542/+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 1913780] [NEW] [ROG Strix G512LW_G512LW, Realtek ALC294, Speaker, Internal] Playback problem

2021-01-29 Thread carlos ..... .....
Public bug reported:

Speakers dont work, although headphones do work. Using Ubuntu 20.04.1 LTS
Release:20.04
Package version 3.38.1


Meanwhile, the whole sound system is fine under Ubuntu 20.04 Live Usb.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  car1528 F pulseaudio
  car3528 F alsamixer
 /dev/snd/pcmC0D0p:   car1528 F...m pulseaudio
 /dev/snd/controlC1:  car1528 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 29 18:14:35 2021
InstallationDate: Installed on 2021-01-27 (2 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Audio Interno - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: Only some of outputs are working
Title: [ROG Strix G512LW_G512LW, Realtek ALC294, Speaker, Internal] Playback 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G512LW.310
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G512LW
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.ec.firmware.release: 3.8
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG512LW.310:bd07/13/2020:br5.17:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGStrixG512LW_G512LW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG512LW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G512LW_G512LW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug focal

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

Title:
  [ROG Strix G512LW_G512LW, Realtek ALC294, Speaker, Internal] Playback
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Speakers dont work, although headphones do work. Using Ubuntu 20.04.1 LTS
  Release:  20.04
  Package version 3.38.1

  
  Meanwhile, the whole sound system is fine under Ubuntu 20.04 Live Usb.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  car1528 F pulseaudio
car3528 F alsamixer
   /dev/snd/pcmC0D0p:   car1528 F...m pulseaudio
   /dev/snd/controlC1:  car1528 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 29 18:14:35 2021
  InstallationDate: Installed on 2021-01-27 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Audio Interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [ROG Strix G512LW_G512LW, Realtek ALC294, Speaker, Internal] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G512LW.310
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G512LW
  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.ec.firmware.release: 3.8
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG512LW.310:bd07/13/2020:br5.17:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGStrixG512LW_G512LW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG512LW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G512LW_G512LW
  dmi.product.version: 1.0
  

[Touch-packages] [Bug 1912091] Re: Memory Leak GNU Tar 1.33

2021-01-18 Thread Carlos Andres Ramirez
Update:

CVE-2021-20193 has been assigned to this vulnerability by Red Hat
Security team.

---
Carlos

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-20193

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

Title:
  Memory Leak GNU Tar 1.33

Status in tar package in Ubuntu:
  New

Bug description:
  
  An issue was discovered in GNU Tar 1.33 and earlier. There is a memory leak 
in read_header() in list.c in the tar application. Occastionally, ASAN detects 
an out of bounds memory read. Valgrind confirms the memory leak in the standard 
tar tool installed by default. This degrades the availability of the tar tool, 
and could potentially result in other memory-related issues.

  Common Weakness Enumeration IDs for reference:
  CWE-401: Missing Release of Memory after Effective Lifetime
  CWE-125: Out-of-bounds Read

  Attached to this report is a PoC malcrafted file "1311745-out-
  bounds.tar"

  VALGRIND OUTPUT:
  valgrind tar -xf 1311745-out-bounds.tar 
  ==3776== Memcheck, a memory error detector
  ==3776== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==3776== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
  ==3776== Command: tar -xf output/1311745-out-bounds.tar
  ==3776== 
  tar: Unexpected EOF in archive
  tar: Exiting with failure status due to previous errors
  ==3776== 
  ==3776== HEAP SUMMARY:
  ==3776== in use at exit: 1,311,761 bytes in 2 blocks
  ==3776==   total heap usage: 52 allocs, 50 frees, 1,349,212 bytes allocated
  ==3776== 
  ==3776== LEAK SUMMARY:
  ==3776==definitely lost: 1,311,745 bytes in 1 blocks
  ...

  NOTE: Version 1.30, 1.32, 1.33 were tested and confirmed to be
  vulnerable.

  lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  apt-cache policy tar
  tar:
Installed: 1.30+dfsg-7ubuntu0.20.04.1
Candidate: 1.30+dfsg-7ubuntu0.20.04.1

  ---
  Carlos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1912091/+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 1912091] Re: Memory Leak GNU Tar 1.33

2021-01-17 Thread Carlos Andres Ramirez
Update
This vulnerability has been discussed with the developer.
Developer has released a public fix.

Original Post in GNU TAR Project:
https://savannah.gnu.org/bugs/?59897

Commit with fix:
https://git.savannah.gnu.org/cgit/tar.git/commit/?id=d9d4435692150fa8ff68e1b1a473d187cc3fd777

This thread can go public now.

** Bug watch added: GNU Savannah Bug Tracker #59897
   http://savannah.gnu.org/bugs/?59897

** Information type changed from Private Security to Public Security

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

Title:
  Memory Leak GNU Tar 1.33

Status in tar package in Ubuntu:
  New

Bug description:
  
  An issue was discovered in GNU Tar 1.33 and earlier. There is a memory leak 
in read_header() in list.c in the tar application. Occastionally, ASAN detects 
an out of bounds memory read. Valgrind confirms the memory leak in the standard 
tar tool installed by default. This degrades the availability of the tar tool, 
and could potentially result in other memory-related issues.

  Common Weakness Enumeration IDs for reference:
  CWE-401: Missing Release of Memory after Effective Lifetime
  CWE-125: Out-of-bounds Read

  Attached to this report is a PoC malcrafted file "1311745-out-
  bounds.tar"

  VALGRIND OUTPUT:
  valgrind tar -xf 1311745-out-bounds.tar 
  ==3776== Memcheck, a memory error detector
  ==3776== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==3776== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
  ==3776== Command: tar -xf output/1311745-out-bounds.tar
  ==3776== 
  tar: Unexpected EOF in archive
  tar: Exiting with failure status due to previous errors
  ==3776== 
  ==3776== HEAP SUMMARY:
  ==3776== in use at exit: 1,311,761 bytes in 2 blocks
  ==3776==   total heap usage: 52 allocs, 50 frees, 1,349,212 bytes allocated
  ==3776== 
  ==3776== LEAK SUMMARY:
  ==3776==definitely lost: 1,311,745 bytes in 1 blocks
  ...

  NOTE: Version 1.30, 1.32, 1.33 were tested and confirmed to be
  vulnerable.

  lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  apt-cache policy tar
  tar:
Installed: 1.30+dfsg-7ubuntu0.20.04.1
Candidate: 1.30+dfsg-7ubuntu0.20.04.1

  ---
  Carlos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1912091/+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 1597708] Re: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex mac/headphone port does not produce sound.

2020-11-18 Thread Carlos Renê
All HP G1 Series won't have front combo jack!

http://h10032.www1.hp.com/ctg/Manual/c03803181

http://h10032.www1.hp.com/ctg/Manual/c04570601

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex
  mac/headphone port does not produce sound.

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  The duplex mic/headphone port does not produce any sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuomov 6588 F pulseaudio
   /dev/snd/pcmC1D0p:   tuomov 6588 F...m pulseaudio
   /dev/snd/controlC1:  tuomov 6588 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 30 11:50:45 2016
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuomov 6588 F pulseaudio
   /dev/snd/pcmC1D0p:   tuomov 6588 F...m pulseaudio
   /dev/snd/controlC1:  tuomov 6588 F pulseaudio
  Symptom_Jack: Black Mic, Front
  Symptom_Type: No sound at all
  Title: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L04 v02.22
  dmi.board.asset.tag: 1019155
  dmi.board.name: 1825
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 1019155
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL04v02.22:bd07/16/2015:svnHewlett-Packard:pnHPEliteDesk800G1DM:pvr:rvnHewlett-Packard:rn1825:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP EliteDesk 800 G1 DM
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-28T14:28:35.250807

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597708/+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 1597708] Re: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex mac/headphone port does not produce sound.

2020-11-18 Thread Carlos Renê
Check HP hardware manual says

"When a device is plugged into the Microphone/Headphone Connector, a
dialog box will pop up asking if you want to use the connector for a
microphone Line-In device or a headphone. You can reconfigure the
connector at any time by double-clicking the Audio Manager icon in the
Windows taskbar."

So, i think this jack is not combinated.

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

Title:
  [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex
  mac/headphone port does not produce sound.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The duplex mic/headphone port does not produce any sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuomov 6588 F pulseaudio
   /dev/snd/pcmC1D0p:   tuomov 6588 F...m pulseaudio
   /dev/snd/controlC1:  tuomov 6588 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 30 11:50:45 2016
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuomov 6588 F pulseaudio
   /dev/snd/pcmC1D0p:   tuomov 6588 F...m pulseaudio
   /dev/snd/controlC1:  tuomov 6588 F pulseaudio
  Symptom_Jack: Black Mic, Front
  Symptom_Type: No sound at all
  Title: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L04 v02.22
  dmi.board.asset.tag: 1019155
  dmi.board.name: 1825
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 1019155
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL04v02.22:bd07/16/2015:svnHewlett-Packard:pnHPEliteDesk800G1DM:pvr:rvnHewlett-Packard:rn1825:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP EliteDesk 800 G1 DM
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-28T14:28:35.250807

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597708/+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 1597708] Re: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex mac/headphone port does not produce sound.

2020-11-17 Thread Carlos Renê
I had try too in ubuntu 20.10 and doesn`t work

** Attachment added: "alsa-info-2010.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597708/+attachment/5435181/+files/alsa-info-2010.txt

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

Title:
  [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex
  mac/headphone port does not produce sound.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The duplex mic/headphone port does not produce any sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuomov 6588 F pulseaudio
   /dev/snd/pcmC1D0p:   tuomov 6588 F...m pulseaudio
   /dev/snd/controlC1:  tuomov 6588 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 30 11:50:45 2016
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuomov 6588 F pulseaudio
   /dev/snd/pcmC1D0p:   tuomov 6588 F...m pulseaudio
   /dev/snd/controlC1:  tuomov 6588 F pulseaudio
  Symptom_Jack: Black Mic, Front
  Symptom_Type: No sound at all
  Title: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L04 v02.22
  dmi.board.asset.tag: 1019155
  dmi.board.name: 1825
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 1019155
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL04v02.22:bd07/16/2015:svnHewlett-Packard:pnHPEliteDesk800G1DM:pvr:rvnHewlett-Packard:rn1825:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP EliteDesk 800 G1 DM
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-28T14:28:35.250807

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597708/+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 1597708] Re: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex mac/headphone port does not produce sound.

2020-11-17 Thread Carlos Renê
I had try too in ubuntu 20.04.1 and doesn't work

** Attachment added: "alsa-info-20.04.1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597708/+attachment/5435138/+files/alsa-info-20.04.1.txt

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

Title:
  [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex
  mac/headphone port does not produce sound.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The duplex mic/headphone port does not produce any sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuomov 6588 F pulseaudio
   /dev/snd/pcmC1D0p:   tuomov 6588 F...m pulseaudio
   /dev/snd/controlC1:  tuomov 6588 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 30 11:50:45 2016
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuomov 6588 F pulseaudio
   /dev/snd/pcmC1D0p:   tuomov 6588 F...m pulseaudio
   /dev/snd/controlC1:  tuomov 6588 F pulseaudio
  Symptom_Jack: Black Mic, Front
  Symptom_Type: No sound at all
  Title: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L04 v02.22
  dmi.board.asset.tag: 1019155
  dmi.board.name: 1825
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 1019155
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL04v02.22:bd07/16/2015:svnHewlett-Packard:pnHPEliteDesk800G1DM:pvr:rvnHewlett-Packard:rn1825:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP EliteDesk 800 G1 DM
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-28T14:28:35.250807

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597708/+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 1597708] Re: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex mac/headphone port does not produce sound.

2020-11-17 Thread Carlos Renê
The Ubuntu 16.04.7 combo jack no sound and detect mic in pavucontrol but
doesnt work!

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597708/+attachment/5435137/+files/alsa-info.txt

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

Title:
  [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex
  mac/headphone port does not produce sound.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The duplex mic/headphone port does not produce any sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuomov 6588 F pulseaudio
   /dev/snd/pcmC1D0p:   tuomov 6588 F...m pulseaudio
   /dev/snd/controlC1:  tuomov 6588 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 30 11:50:45 2016
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuomov 6588 F pulseaudio
   /dev/snd/pcmC1D0p:   tuomov 6588 F...m pulseaudio
   /dev/snd/controlC1:  tuomov 6588 F pulseaudio
  Symptom_Jack: Black Mic, Front
  Symptom_Type: No sound at all
  Title: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L04 v02.22
  dmi.board.asset.tag: 1019155
  dmi.board.name: 1825
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 1019155
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL04v02.22:bd07/16/2015:svnHewlett-Packard:pnHPEliteDesk800G1DM:pvr:rvnHewlett-Packard:rn1825:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP EliteDesk 800 G1 DM
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-28T14:28:35.250807

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

2020-10-28 Thread Carlos Pita
For future reference:

Upstream report: https://gitlab.gnome.org/GNOME/evolution-data-
server/-/issues/262

Workarounds:
 - Disable autostart as described above, but this will cancel both Gnome Shell 
and e-a-n notifications.
 - Alternatively, set 
/org/gnome/evolution-data-server/calendar/notify-with-tray which keeps Gnome 
Shell notifications but hides the standalone e-a-n popup window.

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

Title:
  Getting notifications twice

Status in evolution-data-server package in Ubuntu:
  Invalid

Bug description:
  I would like to revisit https://bugs.launchpad.net/ubuntu/+source
  /evolution-data-server/+bug/1805666

  For years, I've been closing both the "modern" notification popup and
  the "classic" popup window at the same time, many times a day.
  Sometimes even the "e-a-n is ready" notification. This is really
  annoying.

  The only way of disabling this is to remove or modify a desktop file
  that will be overwritten with the next package update.

  Isn't it time to remove /etc/xdg/autostart/org.gnome.Evolution-alarm-
  notify.desktop ? Or is this an upstream issue ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1901236/+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 1901236] Re: Getting notifications twice

2020-10-28 Thread Carlos Pita
I'm closing this since according to upstream they are the ones who
should fix this (but it's blocked on a Gnome Shell issue).

** Changed in: evolution-data-server (Ubuntu)
   Status: Incomplete => Invalid

** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #262
   https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/262

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

Title:
  Getting notifications twice

Status in evolution-data-server package in Ubuntu:
  Invalid

Bug description:
  I would like to revisit https://bugs.launchpad.net/ubuntu/+source
  /evolution-data-server/+bug/1805666

  For years, I've been closing both the "modern" notification popup and
  the "classic" popup window at the same time, many times a day.
  Sometimes even the "e-a-n is ready" notification. This is really
  annoying.

  The only way of disabling this is to remove or modify a desktop file
  that will be overwritten with the next package update.

  Isn't it time to remove /etc/xdg/autostart/org.gnome.Evolution-alarm-
  notify.desktop ? Or is this an upstream issue ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1901236/+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 1901236] Re: Getting notifications twice

2020-10-23 Thread Carlos Pita
** Description changed:

  I would like to revisit https://bugs.launchpad.net/ubuntu/+source
  /evolution-data-server/+bug/1805666
  
  For years, I've been closing both the "modern" notification popup and
- the "classic" popup window at the same time, many times a day. This is
- really annoying.
+ the "classic" popup window at the same time, many times a day. Sometimes
+ even the "e-a-n is ready notification". This is really annoying.
  
  The only way of disabling this is to remove or modify a desktop file
  that will be overwritten with the next package update.
  
  Isn't it time to remove /etc/xdg/autostart/org.gnome.Evolution-alarm-
  notify.desktop ? Or is this an upstream issue ?

** Description changed:

  I would like to revisit https://bugs.launchpad.net/ubuntu/+source
  /evolution-data-server/+bug/1805666
  
  For years, I've been closing both the "modern" notification popup and
  the "classic" popup window at the same time, many times a day. Sometimes
- even the "e-a-n is ready notification". This is really annoying.
+ even the "e-a-n is ready" notification. This is really annoying.
  
  The only way of disabling this is to remove or modify a desktop file
  that will be overwritten with the next package update.
  
  Isn't it time to remove /etc/xdg/autostart/org.gnome.Evolution-alarm-
  notify.desktop ? Or is this an upstream issue ?

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

Title:
  Getting notifications twice

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I would like to revisit https://bugs.launchpad.net/ubuntu/+source
  /evolution-data-server/+bug/1805666

  For years, I've been closing both the "modern" notification popup and
  the "classic" popup window at the same time, many times a day.
  Sometimes even the "e-a-n is ready" notification. This is really
  annoying.

  The only way of disabling this is to remove or modify a desktop file
  that will be overwritten with the next package update.

  Isn't it time to remove /etc/xdg/autostart/org.gnome.Evolution-alarm-
  notify.desktop ? Or is this an upstream issue ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1901236/+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 1901236] Re: Getting notifications twice

2020-10-23 Thread Carlos Pita
Well, according to the XDG spec you can disable autostarting at the user
level in a way that won't be overwritten by future updated:

> If an application autostarts by having a .desktop file installed in
the system wide autostart directory, an individual user can disable the
autotomatic start of this application by placing a .desktop file of the
same name in its personal autostart directory which contains the key
Hidden=true.

I believe my point still stands, though, since this require manual
intervention to revert an arguably incoherent default configuration.

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

Title:
  Getting notifications twice

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I would like to revisit https://bugs.launchpad.net/ubuntu/+source
  /evolution-data-server/+bug/1805666

  For years, I've been closing both the "modern" notification popup and
  the "classic" popup window at the same time, many times a day. This is
  really annoying.

  The only way of disabling this is to remove or modify a desktop file
  that will be overwritten with the next package update.

  Isn't it time to remove /etc/xdg/autostart/org.gnome.Evolution-alarm-
  notify.desktop ? Or is this an upstream issue ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1901236/+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 1901236] [NEW] Getting notifications twice

2020-10-23 Thread Carlos Pita
Public bug reported:

I would like to revisit https://bugs.launchpad.net/ubuntu/+source
/evolution-data-server/+bug/1805666

For years, I've been closing both the "modern" notification popup and
the "classic" popup window at the same time, many times a day. This is
really annoying.

The only way of disabling this is to remove or modify a desktop file
that will be overwritten with the next package update.

Isn't it time to remove /etc/xdg/autostart/org.gnome.Evolution-alarm-
notify.desktop ? Or is this an upstream issue ?

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Getting notifications twice

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I would like to revisit https://bugs.launchpad.net/ubuntu/+source
  /evolution-data-server/+bug/1805666

  For years, I've been closing both the "modern" notification popup and
  the "classic" popup window at the same time, many times a day. This is
  really annoying.

  The only way of disabling this is to remove or modify a desktop file
  that will be overwritten with the next package update.

  Isn't it time to remove /etc/xdg/autostart/org.gnome.Evolution-alarm-
  notify.desktop ? Or is this an upstream issue ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1901236/+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 1893909] [NEW] Xorg crash

2020-09-02 Thread Carlos Barriuso
Public bug reported:

Despues de un bloqueo de pantalla, me atentique y el equipo se
desbloqueo, pero aparecio una ventana que pedia atenticarse para algo
relacionado con un demonio. En esa ventana no podía introducir la
contraseña, ni cerrar la ventana. Despues de apagar el equipo, se quedo
en bucle de inicio de sesión, la contraseña es correcta pero no inicia.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep  2 09:30:16 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 620 [1028:0794]
InstallationDate: Installed on 2020-04-26 (129 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 15-3568
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=9fb1e369-7f7f-446b-b384-a83cbaf54f9d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.07.00
dmi.board.name: 0571HJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0571HJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 15-3568
dmi.product.sku: 0794
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug crash focal ubuntu

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Despues de un bloqueo de pantalla, me atentique y el equipo se
  desbloqueo, pero aparecio una ventana que pedia atenticarse para algo
  relacionado con un demonio. En esa ventana no podía introducir la
  contraseña, ni cerrar la ventana. Despues de apagar el equipo, se
  quedo en bucle de inicio de sesión, la contraseña es correcta pero no
  inicia.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  2 09:30:16 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0794]
  InstallationDate: Installed on 2020-04-26 (129 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 15-3568
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

[Touch-packages] [Bug 1893907] [NEW] Xorg crash

2020-09-02 Thread Carlos Barriuso
Public bug reported:

Me aparecio una ventana pidiendome que me atenticara para algo
relacionado con un demonio. No me dejaba introducir la contraseña. Al
final reinicie e equipo y entro en bucle de inicio de sesión.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
Uname: Linux 4.15.0-115-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep  2 09:20:43 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04f5]
InstallationDate: Installed on 2020-02-19 (195 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. OptiPlex 390
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-115-generic 
root=UUID=5420fc93-5321-4f87-9fa0-bdc6fc629763 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0M5DCD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnOptiPlex390:pvr01:rvnDellInc.:rn0M5DCD:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 390
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic crash ubuntu

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Me aparecio una ventana pidiendome que me atenticara para algo
  relacionado con un demonio. No me dejaba introducir la contraseña. Al
  final reinicie e equipo y entro en bucle de inicio de sesión.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  2 09:20:43 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04f5]
  InstallationDate: Installed on 2020-02-19 (195 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. OptiPlex 390
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-115-generic 
root=UUID=5420fc93-5321-4f87-9fa0-bdc6fc629763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0M5DCD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnOptiPlex390:pvr01:rvnDellInc.:rn0M5DCD:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 390
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: 

[Touch-packages] [Bug 1882871] [NEW] it' doesn't star

2020-06-09 Thread carlos
Public bug reported:

No arranca, solo en modo a prueba de fallos, cuando cierro mi laptop
para entrar en modo de hibernación la maquina ya no regresa a su estado
donde se quedó.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18
Uname: Linux 5.3.0-55-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.9
Architecture: amd64
CompositorRunning: None
Date: Tue Jun  9 22:59:37 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company GT218M [NVS 3100M] [103c:172b]
InstallationDate: Installed on 2018-06-22 (718 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-Packard HP EliteBook 8440p
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-55-generic 
root=UUID=babc465c-5b7e-4eee-bf3a-9445727b4bb5 ro recovery nomodeset
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CCU Ver. F.22
dmi.board.name: 172B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 30.33
dmi.chassis.asset.tag: 2039774
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.22:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.33:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP EliteBook 8440p
dmi.product.sku: SJ653UC#ABM
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Tue Jun  9 22:49:31 2020
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.5+git20191008-0ubuntu1

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


** Tags: amd64 apport-bug eoan ubuntu

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

Title:
  it' doesn't star

Status in xorg package in Ubuntu:
  New

Bug description:
  No arranca, solo en modo a prueba de fallos, cuando cierro mi laptop
  para entrar en modo de hibernación la maquina ya no regresa a su
  estado donde se quedó.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18
  Uname: Linux 5.3.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jun  9 22:59:37 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company GT218M [NVS 3100M] [103c:172b]
  InstallationDate: Installed on 2018-06-22 (718 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP EliteBook 8440p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-55-generic 
root=UUID=babc465c-5b7e-4eee-bf3a-9445727b4bb5 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.22
  dmi.board.name: 172B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.33
  dmi.chassis.asset.tag: 2039774
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.22:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.33:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8440p
  dmi.product.sku: SJ653UC#ABM
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
  

[Touch-packages] [Bug 1878261] [NEW] package libcanberra0 0.30-7ubuntu1 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libcanberra0/changelog.Debian.gz', que es dist

2020-05-12 Thread Carlos de Luna Saenz
Public bug reported:

I need to install Lotus Notes 9 for Linux and seems like some libraries
are being depracated because of the 32 bits  nature. I need this and i
am trying to install the software

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libcanberra0 0.30-7ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue May 12 13:14:08 2020
DpkgTerminalLog:
 Preparando para desempaquetar .../0-libcanberra0_0.30-7ubuntu1_i386.deb ...
 Desempaquetando libcanberra0:i386 (0.30-7ubuntu1) sobre (0.30-2.1ubuntu1) ...
 dpkg: error al procesar el archivo 
/tmp/apt-dpkg-install-X1trMo/0-libcanberra0_0.30-7ubuntu1_i386.deb (--unpack):
  intentando sobreescribir el compartido 
`/usr/share/doc/libcanberra0/changelog.Debian.gz', que es distinto de otras 
instancias del paquetes libcanberra0:i386
ErrorMessage: intentando sobreescribir el compartido 
`/usr/share/doc/libcanberra0/changelog.Debian.gz', que es distinto de otras 
instancias del paquetes libcanberra0:i386
InstallationDate: Installed on 2018-10-25 (564 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: libcanberra
Title: package libcanberra0 0.30-7ubuntu1 failed to install/upgrade: intentando 
sobreescribir el compartido `/usr/share/doc/libcanberra0/changelog.Debian.gz', 
que es distinto de otras instancias del paquetes libcanberra0:i386
UpgradeStatus: Upgraded to focal on 2020-05-08 (3 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package libcanberra0 0.30-7ubuntu1 failed to install/upgrade:
  intentando sobreescribir el compartido
  `/usr/share/doc/libcanberra0/changelog.Debian.gz', que es distinto de
  otras instancias del paquetes libcanberra0:i386

Status in libcanberra package in Ubuntu:
  New

Bug description:
  I need to install Lotus Notes 9 for Linux and seems like some
  libraries are being depracated because of the 32 bits  nature. I need
  this and i am trying to install the software

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libcanberra0 0.30-7ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue May 12 13:14:08 2020
  DpkgTerminalLog:
   Preparando para desempaquetar .../0-libcanberra0_0.30-7ubuntu1_i386.deb ...
   Desempaquetando libcanberra0:i386 (0.30-7ubuntu1) sobre (0.30-2.1ubuntu1) ...
   dpkg: error al procesar el archivo 
/tmp/apt-dpkg-install-X1trMo/0-libcanberra0_0.30-7ubuntu1_i386.deb (--unpack):
intentando sobreescribir el compartido 
`/usr/share/doc/libcanberra0/changelog.Debian.gz', que es distinto de otras 
instancias del paquetes libcanberra0:i386
  ErrorMessage: intentando sobreescribir el compartido 
`/usr/share/doc/libcanberra0/changelog.Debian.gz', que es distinto de otras 
instancias del paquetes libcanberra0:i386
  InstallationDate: Installed on 2018-10-25 (564 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: libcanberra
  Title: package libcanberra0 0.30-7ubuntu1 failed to install/upgrade: 
intentando sobreescribir el compartido 
`/usr/share/doc/libcanberra0/changelog.Debian.gz', que es distinto de otras 
instancias del paquetes libcanberra0:i386
  UpgradeStatus: Upgraded to focal on 2020-05-08 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1878261/+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 1877502] [NEW] package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado

2020-05-07 Thread Carlos Silva
Public bug reported:

I don't know to tell you about the fail.

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: cups-core-drivers 2.2.12-2ubuntu1.1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
Date: Fri May  8 01:15:08 2020
ErrorMessage: problemas de dependência - deixando desconfigurado
InstallationDate: Installed on 2019-11-19 (170 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Dell Inc. Inspiron 5437
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: cups
Title: package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: 
problemas de dependência - deixando desconfigurado
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/09/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 01PN4H
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/09/2019:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn01PN4H:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 5437
dmi.product.sku: Inspiron 5437
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package eoan

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

Title:
  package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade:
  problemas de dependência - deixando desconfigurado

Status in cups package in Ubuntu:
  New

Bug description:
  I don't know to tell you about the fail.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: cups-core-drivers 2.2.12-2ubuntu1.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Fri May  8 01:15:08 2020
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2019-11-19 (170 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Inspiron 5437
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: cups
  Title: package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: 
problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 01PN4H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/09/2019:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn01PN4H:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5437
  dmi.product.sku: Inspiron 5437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1877502/+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 1672822] Re: sound only coming from left speaker on acer predator (fresh install)

2020-01-10 Thread Carlos Velasco
Hi, I have the same problem I think (2.1 speakers and sounds only the
left, if i remove the two little ones (L & R), the subwoofer can sound)

I run "sudo lshw" so the text is long:

descripción: Equipo de escritorio
producto: System Product Name (ASUS_MB_CNL)
fabricante: System manufacturer
versión: System Version
serie: System Serial Number
anchura: 64 bits
capacidades: smbios-3.2.1 dmi-3.2.1 smp vsyscall32
configuración: boot=normal chassis=desktop family=To be filled by O.E.M. 
sku=ASUS_MB_CNL uuid=369FBB1D-1BB1-EC38-97E5-04D9F582D7F3
  *-core
   descripción: Placa base
   producto: PRIME Z390-A
   fabricante: ASUSTeK COMPUTER INC.
   id físico: 0
   versión: Rev 1.xx
   serie: 190755509801753
   ranura: Default string
 *-firmware
  descripción: BIOS
  fabricante: American Megatrends Inc.
  id físico: 0
  versión: 1401
  date: 11/26/2019
  tamaño: 64KiB
  capacidad: 16MiB
  capacidades: pci apm upgrade shadowing cdboot bootselect socketedrom 
edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard 
int14serial int17printer acpi usb biosbootspecification uefi
 *-memory
  descripción: Memoria de sistema
  id físico: 4b
  ranura: Placa de sistema o placa base
  tamaño: 16GiB
*-bank:0
 descripción: Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL 
NAME PO-Revision-Date: 2012-03-14 06:38+Last-Translator: 
Paco Molinero Language-Team: Spanish MIME-Version: 
1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 
8bitX-Launchpad-Export-Date: 2019-10-10 15:05+X-Generator: Launchpad (build 
af2eefe214bd95389a09b7c956720881bab16807)Project-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME PO-Revision-Date: 2012-03-14 
06:38+Last-Translator: Paco Molinero Language-Team: Spanish 
MIME-Version: 1.0Content-Type: text/plain; 
charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2019-10-10 
15:05+X-Generator: Launchpad (build 
af2eefe214bd95389a09b7c956720881bab16807) [vacío]
 id físico: 0
 ranura: ChannelA-DIMM1
*-bank:1
 descripción: DIMM DDR4 Síncrono 3200 MHz (0,3 ns)
 producto: CMW16GX4M2C3200C16
 fabricante: Corsair
 id físico: 1
 serie: 
 ranura: ChannelA-DIMM2
 tamaño: 8GiB
 anchura: 64 bits
 reloj: 3200MHz (0.3ns)
*-bank:2
 descripción: Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL 
NAME PO-Revision-Date: 2012-03-14 06:38+Last-Translator: 
Paco Molinero Language-Team: Spanish MIME-Version: 
1.0Content-Type: text/plain; charset=UTF-8Content-Transfer-Encoding: 
8bitX-Launchpad-Export-Date: 2019-10-10 15:05+X-Generator: Launchpad (build 
af2eefe214bd95389a09b7c956720881bab16807)Project-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME PO-Revision-Date: 2012-03-14 
06:38+Last-Translator: Paco Molinero Language-Team: Spanish 
MIME-Version: 1.0Content-Type: text/plain; 
charset=UTF-8Content-Transfer-Encoding: 8bitX-Launchpad-Export-Date: 2019-10-10 
15:05+X-Generator: Launchpad (build 
af2eefe214bd95389a09b7c956720881bab16807) [vacío]
 id físico: 2
 ranura: ChannelB-DIMM1
*-bank:3
 descripción: DIMM DDR4 Síncrono 3200 MHz (0,3 ns)
 producto: CMW16GX4M2C3200C16
 fabricante: Corsair
 id físico: 3
 serie: 
 ranura: ChannelB-DIMM2
 tamaño: 8GiB
 anchura: 64 bits
 reloj: 3200MHz (0.3ns)
 *-cache:0
  descripción: L1 caché
  id físico: 56
  ranura: L1 Cache
  tamaño: 256KiB
  capacidad: 256KiB
  capacidades: synchronous internal write-back unified
  configuración: level=1
 *-cache:1
  descripción: L2 caché
  id físico: 57
  ranura: L2 Cache
  tamaño: 1MiB
  capacidad: 1MiB
  capacidades: synchronous internal write-back unified
  configuración: level=2
 *-cache:2
  descripción: L3 caché
  id físico: 58
  ranura: L3 Cache
  tamaño: 6MiB
  capacidad: 6MiB
  capacidades: synchronous internal write-back unified
  configuración: level=3
 *-cpu
  descripción: CPU
  producto: Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz
  fabricante: Intel Corp.
  id físico: 59
  información del bus: cpu@0
  versión: Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz
  serie: To Be Filled By O.E.M.
  ranura: LGA1151
  tamaño: 3203MHz
  capacidad: 4200MHz
  anchura: 64 bits
  reloj: 100MHz
  capacidades: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 

[Touch-packages] [Bug 1847077] [NEW] Xorg crash

2019-10-07 Thread Carlos Zegarra
Public bug reported:

oct 07 06:10:22 linux systemd[14697]: Listening on D-Bus User Message Bus Socket
oct 07 06:10:22 linux systemd[14697]: Reached target Sockets.
oct 07 06:10:22 linux systemd[14697]: Reached target Basic System.
oct 07 06:10:22 linux systemd[14697]: Reached target Default.
oct 07 06:10:22 linux systemd[14697]: Startup finished in 52ms.
oct 07 06:10:22 linux systemd[1]: Started User Manager for UID 121.
oct 07 06:10:22 linux systemd[14697]: Started D-Bus User Message Bus.
oct 07 06:10:22 linux dbus-daemon[14711]: [session uid=121 pid=14711] AppArmor D
oct 07 06:10:22 linux gnome-shell[14719]: Failed to apply DRM plane transform 0:
oct 07 06:10:22 linux gnome-shell[14719]: WL: error in client communication (pid
oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: (EE)
oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: Fatal server error:
oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: (EE) wl_drm@4: error 0: au
oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: (EE)
oct 07 06:10:22 linux gnome-shell[14719]: X Wayland crashed; exiting
oct 07 06:10:22 linux gnome-session[14713]: gnome-session-binary[14713]: WARNING
oct 07 06:10:22 linux gnome-session-binary[14713]: WARNING: App 'org.gnome.Shell
oct 07 06:10:22 linux gnome-session-binary[14713]: Unrecoverable failure in requ
oct 07 06:10:22 linux gdm-launch-environment][14693]: pam_unix(gdm-launch-enviro
oct 07 06:10:22 linux gdm3[1178]: GdmDisplay: display lasted 0,643077 seconds
oct 07 06:10:22 linux gdm3[1178]: Child process -14709 was already dead.
oct 07 06:10:22 linux gdm3[1178]: Child process 14693 was already dead.
oct 07 06:10:22 linux gdm3[1178]: Unable to kill session worker process
oct 07 06:10:23 linux gdm-launch-environment][14732]: pam_unix(gdm-launch-enviro
oct 07 06:10:23 linux systemd-logind[738]: New session c503 of user gdm.
oct 07 06:10:23 linux systemd[1]: Started Session c503 of user gdm.
oct 07 06:10:23 linux systemd-logind[738]: Removed session c502.
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: (--) Log file renamed 
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: X.Org X Server 1.20.4
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: X Protocol Version 11,
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Build Operating System
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Current Operating Syst
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Kernel command line: B
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Build Date: 02 May 201
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: xorg-server-hwe-18.04 
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Current version of pix
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Before reporti
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: to make sure t
oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Markers: (--) probed,

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  7 06:30:25 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.0.0-27-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.0.0-29-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.0.0-31-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
InstallationDate: Installed on 2019-08-22 (45 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Dell Inc. Inspiron 3442
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=08ab3346-65ab-48e9-862e-5d9bc103907e ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 021VNN
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn021VNN:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3442
dmi.product.sku: 0651
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: 

[Touch-packages] [Bug 1839024] [NEW] display flickering in perpetual loop while starting ubuntu 18.04.2

2019-08-05 Thread Carlos Suarez
Public bug reported:

gnome 3.28.2

Laptop needs to be re-started

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Aug  5 14:04:47 2019
DistUpgraded: 2019-03-08 20:01:34,757 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3649]
   Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3649]
InstallationDate: Installed on 2018-02-07 (544 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Hewlett-Packard HP Pavilion dm3 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=74d5e8df-abd0-45c0-a0c6-ca60e2f84b67 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-03-09 (149 days ago)
dmi.bios.date: 08/12/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.01
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3649
dmi.board.vendor: Flextronics
dmi.board.version: 41.3A
dmi.chassis.type: 10
dmi.chassis.vendor: Flextronics
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.01:bd08/12/2009:svnHewlett-Packard:pnHPPaviliondm3NotebookPC:pvr03A01024001011012:rvnFlextronics:rn3649:rvr41.3A:cvnFlextronics:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dm3 Notebook PC
dmi.product.version: 03A01024001011012
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Fri Mar  8 17:47:08 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  display flickering in perpetual loop while starting ubuntu 18.04.2

Status in xorg package in Ubuntu:
  New

Bug description:
  gnome 3.28.2

  Laptop needs to be re-started

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug  5 14:04:47 2019
  DistUpgraded: 2019-03-08 20:01:34,757 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3649]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3649]
  InstallationDate: Installed on 2018-02-07 (544 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP Pavilion dm3 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=74d5e8df-abd0-45c0-a0c6-ca60e2f84b67 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-09 (149 days ago)
  dmi.bios.date: 08/12/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.01
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3649
  dmi.board.vendor: Flextronics
  dmi.board.version: 41.3A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Flextronics
  

[Touch-packages] [Bug 1838976] [NEW] package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libpng12-0/ANNOUNCE', que es distinto de otras

2019-08-05 Thread Carlos Lopez
Public bug reported:

No dejo de tener el mismo error siempre que inicio Ubuntu

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpng12-0 1.2.50-2+deb8u3
ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Fri Aug  2 15:17:29 2019
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu11
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu11
 zlib1g 1:1.2.8.dfsg-2ubuntu4.1
DpkgHistoryLog:
 Start-Date: 2019-08-02  15:17:28
 Commandline: apt-get -f install
 Requested-By: clopez (1000)
 Upgrade: libpng12-0:amd64 (1.2.50-2+deb8u3, 1.2.54-1ubuntu1.1)
DpkgTerminalLog:
 Preparando para desempaquetar .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ...
 Desempaquetando libpng12-0:amd64 (1.2.54-1ubuntu1.1) sobre (1.2.50-2+deb8u3) 
...
 dpkg: error al procesar el archivo 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
  intentando sobreescribir el compartido `/usr/share/doc/libpng12-0/ANNOUNCE', 
que es distinto de otras instancias del paquetes libpng12-0:amd64
ErrorMessage: intentando sobreescribir el compartido 
`/usr/share/doc/libpng12-0/ANNOUNCE', que es distinto de otras instancias del 
paquetes libpng12-0:amd64
InstallationDate: Installed on 2018-05-09 (452 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.32
SourcePackage: libpng
Title: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: intentando 
sobreescribir el compartido `/usr/share/doc/libpng12-0/ANNOUNCE', que es 
distinto de otras instancias del paquetes libpng12-0:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade:
  intentando sobreescribir el compartido
  `/usr/share/doc/libpng12-0/ANNOUNCE', que es distinto de otras
  instancias del paquetes libpng12-0:amd64

Status in libpng package in Ubuntu:
  New

Bug description:
  No dejo de tener el mismo error siempre que inicio Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpng12-0 1.2.50-2+deb8u3
  ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Fri Aug  2 15:17:29 2019
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu11
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu11
   zlib1g 1:1.2.8.dfsg-2ubuntu4.1
  DpkgHistoryLog:
   Start-Date: 2019-08-02  15:17:28
   Commandline: apt-get -f install
   Requested-By: clopez (1000)
   Upgrade: libpng12-0:amd64 (1.2.50-2+deb8u3, 1.2.54-1ubuntu1.1)
  DpkgTerminalLog:
   Preparando para desempaquetar .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ...
   Desempaquetando libpng12-0:amd64 (1.2.54-1ubuntu1.1) sobre (1.2.50-2+deb8u3) 
...
   dpkg: error al procesar el archivo 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
intentando sobreescribir el compartido 
`/usr/share/doc/libpng12-0/ANNOUNCE', que es distinto de otras instancias del 
paquetes libpng12-0:amd64
  ErrorMessage: intentando sobreescribir el compartido 
`/usr/share/doc/libpng12-0/ANNOUNCE', que es distinto de otras instancias del 
paquetes libpng12-0:amd64
  InstallationDate: Installed on 2018-05-09 (452 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: libpng
  Title: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: 
intentando sobreescribir el compartido `/usr/share/doc/libpng12-0/ANNOUNCE', 
que es distinto de otras instancias del paquetes libpng12-0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1838976/+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 1832798] [NEW] Better qt experience out of the box (suggestion)

2019-06-13 Thread Carlos Pita
Public bug reported:

(I'm unsure about the right package to report this to)

The qt experience out of the box is currently a mess. Short of proper
Yaru integration, why not install qt5ct with consistent Ubuntu fonts and
icons and Breeze by default? Every qt app will work just fine with
Breeze. Currently we’re exposing a newcomer that barely knows that gtk
and qt are things, let alone different things, to a difficult manual
configuration process that’s not even well documented. That’s much worse
than theme integration issues. A new user wanting to launch lyx or
qbittorrent should just launch lyx or qbittorrent and have a pleasant
experience. That’s not so hard:

* Preinstall kde-style-breeze and qt5ct
* Set ubuntu fonts, dialogs and icons in qt5ct
* Add
export QT_QPA_PLATFORMTHEME=qt5ct
export QT_AUTO_SCREEN_SCALE_FACTOR=1
  to the default profile.

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

** Description changed:

  (I'm unsure about the right package to report this to)
  
  The qt experience out of the box is currently a mess. Short of proper
  Yaru integration, why not install qt5ct with consistent Ubuntu fonts and
  icons and Breeze by default? Every qt app will work just fine with
  Breeze. Currently we’re exposing a newcomer that barely knows gtk and qt
  are things, let alone different things, to a difficult manual
  configuration process that’s not even well documented. That’s much worse
  than theme integration issues. A new user wanting to launch lyx or
  qbittorrent should just launch lyx or qbittorrent and have a pleasant
  experience. That’s not so hard:
  
- Preinstall kde-style-breeze and qt5ct
- Set ubuntu fonts, dialogs and icons in qt5ct
- Add
- export QT_QPA_PLATFORMTHEME=qt5ct
- export QT_AUTO_SCREEN_SCALE_FACTOR=1
- 
- to the default profile.
+ * Preinstall kde-style-breeze and qt5ct
+ * Set ubuntu fonts, dialogs and icons in qt5ct
+ * Add
+ export QT_QPA_PLATFORMTHEME=qt5ct
+ export QT_AUTO_SCREEN_SCALE_FACTOR=1
+   to the default profile.

** Description changed:

  (I'm unsure about the right package to report this to)
  
  The qt experience out of the box is currently a mess. Short of proper
  Yaru integration, why not install qt5ct with consistent Ubuntu fonts and
  icons and Breeze by default? Every qt app will work just fine with
- Breeze. Currently we’re exposing a newcomer that barely knows gtk and qt
- are things, let alone different things, to a difficult manual
+ Breeze. Currently we’re exposing a newcomer that barely knows that gtk
+ and qt are things, let alone different things, to a difficult manual
  configuration process that’s not even well documented. That’s much worse
  than theme integration issues. A new user wanting to launch lyx or
  qbittorrent should just launch lyx or qbittorrent and have a pleasant
  experience. That’s not so hard:
  
  * Preinstall kde-style-breeze and qt5ct
  * Set ubuntu fonts, dialogs and icons in qt5ct
  * Add
- export QT_QPA_PLATFORMTHEME=qt5ct
- export QT_AUTO_SCREEN_SCALE_FACTOR=1
-   to the default profile.
+ export QT_QPA_PLATFORMTHEME=qt5ct
+ export QT_AUTO_SCREEN_SCALE_FACTOR=1
+   to the default profile.

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

Title:
  Better qt experience out of the box (suggestion)

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  (I'm unsure about the right package to report this to)

  The qt experience out of the box is currently a mess. Short of proper
  Yaru integration, why not install qt5ct with consistent Ubuntu fonts
  and icons and Breeze by default? Every qt app will work just fine with
  Breeze. Currently we’re exposing a newcomer that barely knows that gtk
  and qt are things, let alone different things, to a difficult manual
  configuration process that’s not even well documented. That’s much
  worse than theme integration issues. A new user wanting to launch lyx
  or qbittorrent should just launch lyx or qbittorrent and have a
  pleasant experience. That’s not so hard:

  * Preinstall kde-style-breeze and qt5ct
  * Set ubuntu fonts, dialogs and icons in qt5ct
  * Add
  export QT_QPA_PLATFORMTHEME=qt5ct
  export QT_AUTO_SCREEN_SCALE_FACTOR=1
    to the default profile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1832798/+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 1813759] [NEW] Scale display doesn't work with an external monitor attached

2019-01-29 Thread Carlos Perelló Marín
Public bug reported:

I have a Dell XPS 13" (2018) connected to an LG 4K 32" display thru
USB-C cable. both screens are supposed to have the same resolution, but
the laptop one uses 200% of scale setting due to small size.

When the laptop is connected to the external display, the scale setting
does nothing and almost everything looks pretty small and hard to read,
only gnome-terminal content seems to follow the scaling setting but
windows decorators and app menus are pretty small.

If I disconnect the external display everything works as expected (at
least with the usual apps like GNOME apps, Firefox, Chrome, etc...).

I'm using Ubuntu 18.10 with latest updates installed.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 29 13:08:45 2019
DistUpgraded: 2019-01-05 13:19:27,114 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py': './xorg_fix_proprietary.py')
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:07e6]
InstallationDate: Installed on 2019-01-05 (24 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. XPS 13 9370
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=UUID=0331a22b-f276-4072-83bb-95f04eb8ba77 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to cosmic on 2019-01-05 (23 days ago)
dmi.bios.date: 11/04/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.3
dmi.board.name: 0F6P3V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic resolution ubuntu wayland-session

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

Title:
  Scale display doesn't work with an external monitor attached

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell XPS 13" (2018) connected to an LG 4K 32" display thru
  USB-C cable. both screens are supposed to have the same resolution,
  but the laptop one uses 200% of scale setting due to small size.

  When the laptop is connected to the external display, the scale
  setting does nothing and almost everything looks pretty small and hard
  to read, only gnome-terminal content seems to follow the scaling
  setting but windows decorators and app menus are pretty small.

  If I disconnect the external display everything works as expected (at
  least with the usual apps like GNOME apps, Firefox, Chrome, etc...).

  I'm using Ubuntu 18.10 with latest updates installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 13:08:45 2019
  DistUpgraded: 2019-01-05 13:19:27,114 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py': './xorg_fix_proprietary.py')
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:07e6]
  InstallationDate: Installed on 

[Touch-packages] [Bug 1452239] Re: root escalation with fs.suid_dumpable=2

2019-01-22 Thread Carlos D. Gonzalez
In Bionic, when apport is enabled fs.suid_dumpable will be set to 2, no
matters what you try to set it up using sysctl. Is this the same issue?

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

Title:
  root escalation with fs.suid_dumpable=2

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Utopic:
  Fix Released
Status in apport source package in Vivid:
  Fix Released
Status in apport source package in Wily:
  Fix Released

Bug description:
  Sander Bos discovered that Apport enabled a user to perform a root
  escalation since it now configures fs.suid_dumpable=2.

  Here's a brief description of the issue:
  1- A regular user can trigger a coredump with /proc/$PID/stat as root:root 
simply by doing chmod u-r
  2- The root-owned coredump will then be written in the CWD, which in the PoC 
is /etc/logrotate.d
  3- logrotate will gladly skip parts of the coredump it doesn't understand and 
will successfully run the parts it does

  I've set a CRD of 2015-05-21 (original proposal: 2015-05-12) for the
  publication of this issue.

  I have assigned CVE-2015-1324 to this issue.

  We can either:

  1- Disable fs.suid_dumpable=2
  2- Stop creating core dump files when they are to be created as root
  3- Create root-owned core dump files in a well-known location

  

  Here is the original report from Sander Bos (now with the CVE number
  included):

  OVERVIEW
  

  Date: 2015-05-05
  Bug name: SCORE: Simple Coredump-Oriented Root Exploit
  CVE: CVE-2015-1324
  Author: Sander Bos
  Author's e-mail address: sbos _at_ sbosnet _dot_ nl

  SUMMARY
  ---

  I found a combination of vulnerabilities to lead to privilege escalation
  (root exploitation) by local users in Ubuntu releases 12.04 up to and
  including 15.04.  Depending on configuration, remote exploitation might
  be possible as well.  Local exploitation can even be done as the local,
  passwordless LightDM "Guest" account user on systems supporting it --
  indeed: from anonymous guest user to root.

  DESCRIPTION
  ---

  The Apport package creates user core dumps in the crashed process'
  CWD, and does so since Bazaar revision number 602 [1] / release 0.59.
  This is okay, but not always: there is a flaw in the fact that Apport
  also does this, as root, for tainted/protected binaries (setuid() and
  friends, capabilities(7) enabled binaries, non-readable binaries) when
  the sysctl(8)'s fs.suid_dumpable variable is set to 2 (see core(5)).
  This means that users can create core dumps as root, in arbitrary
  directories which are otherwise write-protected for those users.

  In short: Apport should _not_ create user core dumps in the CWD in dump
  mode 2 for such tainted binaries; it should either not make user core
  dumps at all then, or if possible use a designated and safe directory
  for that.

  All Ubuntu releases starting with 12.04 have the Apport service enabled by
  default [2] (and Ubuntu has Apport installed by default for much longer).

  All Ubuntu releases starting with 12.04 (or patched that way after
  their release) have sysctl(8)'s fs.suid_dumpable set to 2 by default,
  through the Apport package; see bug #1194541, "Create core dumps for
  setuid binaries", 2013-06-25 [3].

  Along with solving that bug (that is, adding the "missing feature" of
  setuid core dumps), the patch to that bug report actually created a root
  exploit hole in the upcoming release 13.10, as well as being backported
  into the at that time supported Ubuntu releases 12.04, 12.10 and 13.04.

  The exact Apport package versions (with their Ubuntu releases) that were
  "patched" to have fs.suid_dumpable set to "2"  are:

  2.0.1-0ubuntu17.4 (Ubuntu 12.04)
  2.6.1-0ubuntu12   (Ubuntu 12.10)
  2.9.2-0ubuntu8.3  (Ubuntu 13.04)

  The value fs.suid_dumpable=2 remained in Ubuntu ever since.  The exception
  to this is the systemd Apport script in Ubuntu 15.04: the option setting
  fs.suid_dumpable to "2" was forgotten to be enabled here, although in the
  Upstart script in Ubuntu 15.04 the option is still enabled.  I recently
  contacted the Apport package maintainer to make sure the systemd script
  will not enable the option, as that would enable the root hole in 15.04
  with systemd (which is the default init system) as well.  Please note:
  15.04 with systemd being safe regarding this vulnerabilty has nothing
  to do with systemd itself.

  Please note that even though Ubuntu has the value of fs.suid_dumpable set
  to 2 in releases 12.04 and later, Apport itself has been creating user
  coredumps (to CWD, and also with fs.suid_dumpable=2) since Ubuntu 7.04,
  which has Apport package release 0.76/0.76.1.  Any system 

[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

2019-01-11 Thread Carlos Garcia
Just updated 229-4ubuntu21.15 today and this issue is back.

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
    i->uid_set ? i->uid : UID_INVALID,
    i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  Any help fixing this problem would be highly appreciated.
  Many thanks,
  Rafael

  === Notes ===
  fchownat() was added to Linux in kernel 2.6.16;
  library support was added to glibc in version 2.4.
  checkinf if it is blocked/filtered/sandboxed, rarther than unavailable.
  glibc in bionic requires minimum linux 3.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847/+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 1808239] [NEW] package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado

2018-12-12 Thread CARLOS ALBERTO PEREIRA NASCIMENTO
Public bug reported:

Está aparecendo mensagem de erro!

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python2.7 2.7.15~rc1-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Dec 12 13:58:54 2018
ErrorMessage: problemas de dependência - deixando desconfigurado
InstallationDate: Installed on 2018-12-12 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: python2.7
Title: package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: 
problemas de dependência - deixando desconfigurado
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade:
  problemas de dependência - deixando desconfigurado

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Está aparecendo mensagem de erro!

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python2.7 2.7.15~rc1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Dec 12 13:58:54 2018
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2018-12-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: python2.7
  Title: package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: 
problemas de dependência - deixando desconfigurado
  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/1808239/+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 1805056] [NEW] cant minimize cant close cant move windows keyboard layout changes like shift key is pressed mouse selection is wrong like the shift key is pressed but i have chan

2018-11-25 Thread Carlos Estr
Public bug reported:

cant minimize cant close cant move windows keyboard layout changes like
shift key is pressed mouse selection is wrong like the shift key is
pressed but i have changed keyboard and there is no issues with
hardware: cant type numbers only symbols above numbers have to kill
lxsession or systemd process to get out of the situation

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.9
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
Architecture: amd64
CurrentDesktop: LXDE
Date: Sun Nov 25 18:07:26 2018
InstallationDate: Installed on 2018-05-20 (189 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05e3:0723 Genesys Logic, Inc. GL827L SD/MMC/MS Flash 
Card Reader
 Bus 001 Device 002: ID 0458:0186 KYE Systems Corp. (Mouse Systems) 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=e0f65cc4-ba09-40af-b0ef-4519ac61a8a2 ro quiet splash vt.handoff=1
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /etc/systemd/system/clamav-daemon.service → 
/etc/systemd/system/clamav-daemon.service.d/extend.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 3 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3805
dmi.board.asset.tag: Default string
dmi.board.name: H110M-R
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-R:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

Title:
  cant minimize cant close cant move windows keyboard layout changes
  like shift key is pressed mouse selection is wrong like the shift key
  is pressed but i have changed keyboard and there is no issues with
  hardware: cant type numbers only symbols above numbers have to kill
  lxsession or systemd process to get out of the situation

Status in systemd package in Ubuntu:
  New

Bug description:
  cant minimize cant close cant move windows keyboard layout changes
  like shift key is pressed mouse selection is wrong like the shift key
  is pressed but i have changed keyboard and there is no issues with
  hardware: cant type numbers only symbols above numbers have to kill
  lxsession or systemd process to get out of the situation

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.9
  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
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sun Nov 25 18:07:26 2018
  InstallationDate: Installed on 2018-05-20 (189 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05e3:0723 Genesys Logic, Inc. GL827L SD/MMC/MS Flash 
Card Reader
   Bus 001 Device 002: ID 0458:0186 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=e0f65cc4-ba09-40af-b0ef-4519ac61a8a2 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/clamav-daemon.service → 
/etc/systemd/system/clamav-daemon.service.d/extend.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3805
  

[Touch-packages] [Bug 1803879] [NEW] package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

2018-11-18 Thread Carlos Pulido
Public bug reported:

Application failed while I was updating the system with SW Actualization
app

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.5
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
Architecture: amd64
Date: Sun Nov 18 16:05:46 2018
Df:
 
Dmesg:
 
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 2
InstallationDate: Installed on 2018-11-18 (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.1
 apt  1.6.6
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Application failed while I was updating the system with SW
  Actualization app

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.5
  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
  Architecture: amd64
  Date: Sun Nov 18 16:05:46 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2018-11-18 (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.1
   apt  1.6.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1803879/+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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

2018-11-17 Thread Carlos Suárez
There is a error into the /usr/share/polkit-1/actions/com.ubuntu.pkexec
.gdebi-gtk.policy file:

Change "" with "".

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in vte2.91 source package in Bionic:
  Fix Released

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

2018-10-24 Thread Carlos Eduardo Moreira dos Santos
This started happening after installing lubuntu-desktop. Even after
removing it, it is still failing to mount. After running "keyctl link @u
@s", it works.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

2018-10-24 Thread Carlos Eduardo Moreira dos Santos
Note: I'm using 18.04

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1796702] [NEW] Actualmente el arranque normal de ubuntu 18.04 se detiene en la posición indicada. Arranca normal en modo protegido. Muchas gracias.

2018-10-08 Thread Carlos Pastorino
Public bug reported:

Normal start stops at:"Started user manager for vud 122"

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Oct  8 12:14:35 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation 82945G/GZ Integrated Graphics Controller 
[1849:2772]
InstallationDate: Installed on 2018-06-11 (118 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=es_UY:es
 PATH=(custom, no user)
 LANG=es_UY.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=dceb6db0-13a5-4b39-932e-ffde095bd981 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.20
dmi.board.name: 945GCM-S
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd02/05/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn945GCM-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct  8 07:18:12 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Actualmente el arranque normal de ubuntu 18.04 se detiene en la
  posición indicada. Arranca normal en modo protegido. Muchas gracias.

Status in xorg package in Ubuntu:
  New

Bug description:
  Normal start stops at:"Started user manager for vud 122"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct  8 12:14:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 82945G/GZ Integrated Graphics Controller 
[1849:2772]
  InstallationDate: Installed on 2018-06-11 (118 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=es_UY:es
   PATH=(custom, no user)
   LANG=es_UY.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=dceb6db0-13a5-4b39-932e-ffde095bd981 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: 945GCM-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Touch-packages] [Bug 1786812] [NEW] package python-pkg-resources 39.0.1-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat

2018-08-13 Thread Carlos Fernandes
Public bug reported:

This erros happening in my update

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python-pkg-resources 39.0.1-2
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 libarchive13:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Aug 13 12:33:41 2018
Dependencies:
 
DuplicateSignature:
 package:python-pkg-resources:39.0.1-2
 Setting up libarchive13:amd64 (3.2.2-3.1ubuntu0.1) ...
 dpkg: error processing package python-pkg-resources (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-08-09 (3 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: python-setuptools
Title: package python-pkg-resources 39.0.1-2 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package python-pkg-resources 39.0.1-2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in python-setuptools package in Ubuntu:
  New

Bug description:
  This erros happening in my update

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python-pkg-resources 39.0.1-2
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   libarchive13:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Aug 13 12:33:41 2018
  Dependencies:
   
  DuplicateSignature:
   package:python-pkg-resources:39.0.1-2
   Setting up libarchive13:amd64 (3.2.2-3.1ubuntu0.1) ...
   dpkg: error processing package python-pkg-resources (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-08-09 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: python-setuptools
  Title: package python-pkg-resources 39.0.1-2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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


Re: [Touch-packages] [Bug 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2018-07-14 Thread Carlos Lujan Maldonado Ramirez
Thanks all for they help i AM very new in linux..

Obtener Outlook para Android<https://aka.ms/ghei36>


From: boun...@canonical.com  on behalf of Carlos Sotto 
Maior <1779...@bugs.launchpad.net>
Sent: Saturday, July 14, 2018 6:29:40 PM
To: cmaldonado7...@hotmail.com
Subject: Re: [Bug 1779237] Re: package python3 3.6.5-3ubuntu1 failed to 
install/upgrade: installed python3 package post-installation script subprocess 
returned error exit status 4

Hey Youssef Amin.

Thanks for the fix. It worked great for me.

Carlos

Em sáb, 14 de jul de 2018 às 16:55, Youssef Amin <1779...@bugs.launchpad.net>
escreveu:

> Hey Johann
> Do this
>
> cd /usr/share/hplip
> sudo python3 uninstall.py
>
> Worked like a charm. then upgrade python.   All worked fine!!
>
> Cheers!!
>
> On Sat, Jul 14, 2018 at 5:00 AM Johann Tuffe <1779...@bugs.launchpad.net>
> wrote:
>
> > Any idea how to workaround it?
> > I have tried to uninstall hplip but it is not enough.
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1779237
> >
> > Title:
> >   package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
> >   python3 package post-installation script subprocess returned error
> >   exit status 4
> >
> > Status in python3-defaults package in Ubuntu:
> >   Confirmed
> >
> > Bug description:
> >   Only Ubuntu Update
> >
> >   ProblemType: Package
> >   DistroRelease: Ubuntu 18.04
> >   Package: python3 3.6.5-3ubuntu1
> >   ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
> >   Uname: Linux 4.15.0-22-generic x86_64
> >   ApportVersion: 2.20.9-0ubuntu7.2
> >   Architecture: amd64
> >   Date: Thu Jun 28 22:51:28 2018
> >   ErrorMessage: installed python3 package post-installation script
> > subprocess returned error exit status 4
> >   InstallationDate: Installed on 2018-04-13 (76 days ago)
> >   InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64
> > (20180228)
> >   Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
> > 3.6.5-3ubuntu1
> >   PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
> > 2.7.15~rc1-1
> >   RelatedPackageVersions:
> >dpkg 1.19.0.5ubuntu2
> >apt  1.6.2
> >   SourcePackage: python3-defaults
> >   Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade:
> > installed python3 package post-installation script subprocess returned
> > error exit status 4
> >   UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago)
> >
> > To manage notifications about this bug go to:
> >
> >
> https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1781497).
> https://bugs.launchpad.net/bugs/1779237
>
> Title:
>   package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
>   python3 package post-installation script subprocess returned error
>   exit status 4
>
> Status in python3-defaults package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Only Ubuntu Update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 18.04
>   Package: python3 3.6.5-3ubuntu1
>   ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
>   Uname: Linux 4.15.0-22-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   Date: Thu Jun 28 22:51:28 2018
>   ErrorMessage: installed python3 package post-installation script
> subprocess returned error exit status 4
>   InstallationDate: Installed on 2018-04-13 (76 days ago)
>   InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64
> (20180228)
>   Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
> 3.6.5-3ubuntu1
>   PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
> 2.7.15~rc1-1
>   RelatedPackageVersions:
>dpkg 1.19.0.5ubuntu2
>apt  1.6.2
>   SourcePackage: python3-defaults
>   Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade:
> installed python3 package post-installation script subprocess returned
> error exit status 4
>   UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+subscriptions
>


--
Carlos Sotto Maior
carlossotto.ma...@gmail.com

--
You received this bug notification because you are subscribed to a

Re: [Touch-packages] [Bug 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2018-07-14 Thread Carlos Sotto Maior
Hey Youssef Amin.

Thanks for the fix. It worked great for me.

Carlos

Em sáb, 14 de jul de 2018 às 16:55, Youssef Amin <1779...@bugs.launchpad.net>
escreveu:

> Hey Johann
> Do this
>
> cd /usr/share/hplip
> sudo python3 uninstall.py
>
> Worked like a charm. then upgrade python.   All worked fine!!
>
> Cheers!!
>
> On Sat, Jul 14, 2018 at 5:00 AM Johann Tuffe <1779...@bugs.launchpad.net>
> wrote:
>
> > Any idea how to workaround it?
> > I have tried to uninstall hplip but it is not enough.
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1779237
> >
> > Title:
> >   package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
> >   python3 package post-installation script subprocess returned error
> >   exit status 4
> >
> > Status in python3-defaults package in Ubuntu:
> >   Confirmed
> >
> > Bug description:
> >   Only Ubuntu Update
> >
> >   ProblemType: Package
> >   DistroRelease: Ubuntu 18.04
> >   Package: python3 3.6.5-3ubuntu1
> >   ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
> >   Uname: Linux 4.15.0-22-generic x86_64
> >   ApportVersion: 2.20.9-0ubuntu7.2
> >   Architecture: amd64
> >   Date: Thu Jun 28 22:51:28 2018
> >   ErrorMessage: installed python3 package post-installation script
> > subprocess returned error exit status 4
> >   InstallationDate: Installed on 2018-04-13 (76 days ago)
> >   InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64
> > (20180228)
> >   Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
> > 3.6.5-3ubuntu1
> >   PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
> > 2.7.15~rc1-1
> >   RelatedPackageVersions:
> >dpkg 1.19.0.5ubuntu2
> >apt  1.6.2
> >   SourcePackage: python3-defaults
> >   Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade:
> > installed python3 package post-installation script subprocess returned
> > error exit status 4
> >   UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago)
> >
> > To manage notifications about this bug go to:
> >
> >
> https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1781497).
> https://bugs.launchpad.net/bugs/1779237
>
> Title:
>   package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
>   python3 package post-installation script subprocess returned error
>   exit status 4
>
> Status in python3-defaults package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Only Ubuntu Update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 18.04
>   Package: python3 3.6.5-3ubuntu1
>   ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
>   Uname: Linux 4.15.0-22-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   Date: Thu Jun 28 22:51:28 2018
>   ErrorMessage: installed python3 package post-installation script
> subprocess returned error exit status 4
>   InstallationDate: Installed on 2018-04-13 (76 days ago)
>   InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64
> (20180228)
>   Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
> 3.6.5-3ubuntu1
>   PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
> 2.7.15~rc1-1
>   RelatedPackageVersions:
>dpkg 1.19.0.5ubuntu2
>apt  1.6.2
>   SourcePackage: python3-defaults
>   Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade:
> installed python3 package post-installation script subprocess returned
> error exit status 4
>   UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+subscriptions
>


-- 
Carlos Sotto Maior
carlossotto.ma...@gmail.com

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

Title:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Only Ubuntu Update

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22

[Touch-packages] [Bug 1781583] [NEW] package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2018-07-13 Thread Carlos Lujan Maldonado Ramirez
*** This bug is a duplicate of bug 1779237 ***
https://bugs.launchpad.net/bugs/1779237

Public bug reported:

a message always appear informing this error and i cant find how to
eliminate or fix the error

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3 3.6.5-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Fri Jul 13 08:35:46 2018
ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
InstallationDate: Installed on 2018-06-28 (15 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.2
SourcePackage: python3-defaults
Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  a message always appear informing this error and i cant find how to
  eliminate or fix the error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Jul 13 08:35:46 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-06-28 (15 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1781583/+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 1781497] [NEW] package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2018-07-12 Thread Carlos Sotto Maior
*** This bug is a duplicate of bug 1779237 ***
https://bugs.launchpad.net/bugs/1779237

Public bug reported:

E: py3compile:183: cannot create directory
/usr/share/hplip/ui5/__pycache__: FileNotFoundError(2, 'No such file or
directory')

The above erro line was the first error in the Synaptic update process.

There are subsequent erros 2 and error 4 messages but I am assuming that
they are consequences of this first error.

I have first updated all available SOFTWaRE UPDATES and then started
Synaptic >> Mark all updates >> Install.

Thanks for your attention in analysing this message.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3 3.6.5-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Jul 12 19:01:01 2018
ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
InstallationDate: Installed on 2018-05-13 (60 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.2
SourcePackage: python3-defaults
Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  E: py3compile:183: cannot create directory
  /usr/share/hplip/ui5/__pycache__: FileNotFoundError(2, 'No such file
  or directory')

  The above erro line was the first error in the Synaptic update
  process.

  There are subsequent erros 2 and error 4 messages but I am assuming
  that they are consequences of this first error.

  I have first updated all available SOFTWaRE UPDATES and then started
  Synaptic >> Mark all updates >> Install.

  Thanks for your attention in analysing this message.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jul 12 19:01:01 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-05-13 (60 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1781497/+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 1774342] Re: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable

2018-05-31 Thread JOSE CARLOS MARTIN IGLESIAS
package isc-dhcp-server version 4.3.5-3ubuntu7

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

Title:
  /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  package: isc-dhcp-server

  /etc/default/isc-dhcp-server define the variables INTERFACESv4 and
  INTERFACESv6 for define listening network interface, but
  /lib/systemd/system/isc-dhcp-server.service and /lib/systemd/system
  /isc-dhcp-server6.service use the variable INTERFACES (exec dhcpd
  -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf
  $CONFIG_FILE $INTERFACES'). This causes the service to listen on all
  interfaces.

  The correct way would be for /lib/systemd/system/isc-dhcp-server.service:
  ..
   exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf 
$CONFIG_FILE $INTERFACESv4'
  ..

  for /lib/systemd/system/isc-dhcp-server.service:
  ..
  exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf 
$CONFIG_FILE $INTERFACESv6'
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1774342/+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 1774342] [NEW] /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable

2018-05-31 Thread JOSE CARLOS MARTIN IGLESIAS
Public bug reported:

package: isc-dhcp-server

/etc/default/isc-dhcp-server define the variables INTERFACESv4 and
INTERFACESv6 for define listening network interface, but
/lib/systemd/system/isc-dhcp-server.service and /lib/systemd/system/isc-
dhcp-server6.service use the variable INTERFACES (exec dhcpd -user dhcpd
-group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE
$INTERFACES'). This causes the service to listen on all interfaces.

The correct way would be for /lib/systemd/system/isc-dhcp-server.service:
..
 exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf 
$CONFIG_FILE $INTERFACESv4'
..

for /lib/systemd/system/isc-dhcp-server.service:
..
exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf 
$CONFIG_FILE $INTERFACESv6'
.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  package: isc-dhcp-server

  /etc/default/isc-dhcp-server define the variables INTERFACESv4 and
  INTERFACESv6 for define listening network interface, but
  /lib/systemd/system/isc-dhcp-server.service and /lib/systemd/system
  /isc-dhcp-server6.service use the variable INTERFACES (exec dhcpd
  -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf
  $CONFIG_FILE $INTERFACES'). This causes the service to listen on all
  interfaces.

  The correct way would be for /lib/systemd/system/isc-dhcp-server.service:
  ..
   exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf 
$CONFIG_FILE $INTERFACESv4'
  ..

  for /lib/systemd/system/isc-dhcp-server.service:
  ..
  exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf 
$CONFIG_FILE $INTERFACESv6'
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1774342/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

2018-05-13 Thread Carlos Gomes
Most important information: I'm using ubuntu 18.04, fresh install

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  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
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

2018-05-13 Thread Carlos Gomes
My Thinkpad P51 is also affected by this bug. 
Gnome tweak tools is set to suspend on lid close, but nothing happens.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  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
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1770429] [NEW] Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3

2018-05-10 Thread Carlos Roque
Public bug reported:

I updated my Surface Pro 3 From Ubuntu 17.10 to Ubuntu 18.04 (did a clean 
install) and the only  audio working was from the headphone jack.
I tried all these:
[troubleshooting 
guide](https://help.ubuntu.com/community/SoundTroubleshootingProcedure)
[this 
answer](https://askubuntu.com/questions/117842/no-sound-from-speakers-but-headphones-work)
[another 
answer](https://askubuntu.com/questions/829520/ubuntu-16-04-no-sound-from-speakers-only-headphones-working)

I went back and tested the live CD and even the live cd has no audio
through the speakers. so this must be related to 18.04. I never had
sound issues before and under windows audio still works correctly.

here is my alsa iformation http://www.alsa-
project.org/db/?f=8bf135db52610a603014779ef24041a491c8a32d

and here is how I fixed it:

renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa-base.bk
, then rebooting the computer fixed the my speaker sound issue.

I then restored line by line in to /etc/modprobe.d/alsa-base.conf, rebooting 
between restored lines, until all lines were back and ... it still worked!
so I restored the original /etc/modprobe.d/alsa-base.conf and rebooted the 
computer and everything was still working
so I am not sure what the problem was but is now fixed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.16.7-041607-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  carlosr2267 F pulseaudio
 /dev/snd/controlC0:  carlosr2267 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu May 10 10:15:29 2018
InstallationDate: Installed on 2018-04-27 (13 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/23/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.11.2350
dmi.board.asset.tag: 0
dmi.board.name: Surface Pro 3
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: 0
dmi.chassis.type: 9
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11.2350:bd01/23/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
dmi.product.family: Surface
dmi.product.name: Surface Pro 3
dmi.product.version: 1
dmi.sys.vendor: Microsoft Corporation
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-09T14:04:13.313882

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


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

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

Title:
  Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I updated my Surface Pro 3 From Ubuntu 17.10 to Ubuntu 18.04 (did a clean 
install) and the only  audio working was from the headphone jack.
  I tried all these:
  [troubleshooting 
guide](https://help.ubuntu.com/community/SoundTroubleshootingProcedure)
  [this 
answer](https://askubuntu.com/questions/117842/no-sound-from-speakers-but-headphones-work)
  [another 
answer](https://askubuntu.com/questions/829520/ubuntu-16-04-no-sound-from-speakers-only-headphones-working)

  I went back and tested the live CD and even the live cd has no audio
  through the speakers. so this must be related to 18.04. I never had
  sound issues before and under windows audio still works correctly.

  here is my alsa iformation http://www.alsa-
  project.org/db/?f=8bf135db52610a603014779ef24041a491c8a32d

  and here is how I fixed it:

  renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa-
  base.bk , then rebooting the computer fixed the my speaker sound
  issue.

  I then restored line by line in to /etc/modprobe.d/alsa-base.conf, rebooting 
between restored lines, until all lines were back and ... it still worked!
  so I restored the original /etc/modprobe.d/alsa-base.conf and rebooted the 
computer and everything was still working
  so I am not sure what the problem was but is now fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carlosr2267 F pulseaudio
   /dev/snd/controlC0:  carlosr2267 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 10 10:15:29 2018
  InstallationDate: Installed on 2018-04-27 (13 days 

[Touch-packages] [Bug 1767336] [NEW] package ca-certificates 20180409 failed to install/upgrade: gatilhos em "loop", abandonado

2018-04-27 Thread Carlos Alberto Neri
Public bug reported:

i dont know

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri Apr 27 08:02:11 2018
ErrorMessage: gatilhos em "loop", abandonado
InstallationDate: Installed on 2018-03-15 (43 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: gatilhos em 
"loop", abandonado
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: gatilhos
  em "loop", abandonado

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 08:02:11 2018
  ErrorMessage: gatilhos em "loop", abandonado
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: gatilhos 
em "loop", abandonado
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767336/+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 1767331] [NEW] package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

2018-04-27 Thread Carlos Alberto Neri
Public bug reported:

i dont know

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: uuid-runtime 2.31.1-0.4ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Fri Apr 27 07:46:33 2018
ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
InstallationDate: Installed on 2018-03-15 (43 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: util-linux
Title: package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O
  pacote está num mau estado de inconsistência; deve  reinstala-lo antes
  de tentar configura-lo.

Status in util-linux package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: uuid-runtime 2.31.1-0.4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 27 07:46:33 2018
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: util-linux
  Title: package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1767331/+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 1563945] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2018-04-10 Thread carlos
I had this issue before with ubuntu 16.04lts. The weird part is that it worked 
fine until one update that failed, i believe it was by end of 2017. 
unfortunately and go figure ;),had same issue with  the previous version of 
elementaryOS, mint and now ubuntu mate. 
Weirdly enough for me, with solusOS as well. i'm not a tec./linux savvy but i 
was always able to install  different linux distros by myself but lately ... or 
its me that arrived at the end of my linux learning curve or i will need to 
replace soon my 11 year old x61s.

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess installed pre-removal script returned
  error exit status 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  interesting issues while updating packages this morning...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Wed Mar 30 09:33:28 2016
  DpkgTerminalLog:
   Removing avahi-discover (0.6.32~rc+dfsg-1ubuntu2) ...
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--remove):
subprocess installed pre-removal script returned error exit status 1
  DuplicateSignature:
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--remove):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-01-06 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess installed pre-removal script 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/avahi/+bug/1563945/+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 1762725] [NEW] Ubuntu Budgie selects USB mic as default audio output after every reboot.

2018-04-10 Thread Carlos Echenique
Public bug reported:

Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic
as the default output device. I have to manually select the analog
output every time. Also, the Default effect sound does not make any
noise.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  guru   2355 F pulseaudio
 /dev/snd/controlC1:  guru   2355 F pulseaudio
 /dev/snd/controlC0:  guru   2355 F pulseaudio
CurrentDesktop: Budgie:GNOME
Date: Tue Apr 10 08:54:30 2018
InstallationDate: Installed on 2018-04-07 (2 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.52
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 4
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A37
dmi.product.version: 2.0
dmi.sys.vendor: MSI

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

Title:
  Ubuntu Budgie selects USB mic as default audio output after every
  reboot.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Whenever I reboot my system, pulseaudio selects my Samson Meteor USB
  mic as the default output device. I have to manually select the analog
  output every time. Also, the Default effect sound does not make any
  noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2355 F pulseaudio
   /dev/snd/controlC1:  guru   2355 F pulseaudio
   /dev/snd/controlC0:  guru   2355 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Apr 10 08:54:30 2018
  InstallationDate: Installed on 2018-04-07 (2 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.52
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1762725/+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 1759921] Re: SOLVED - Problem with Lexmark Optra E310: printing system doesn't work

2018-04-05 Thread Carlos Rodriguez
** Summary changed:

- Problem with Lexmark Optra E310: printing system doesn't work
+ SOLVED - Problem with Lexmark Optra E310: printing system doesn't work

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

Title:
  SOLVED - Problem with Lexmark Optra E310: printing system doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  My printer, Lexmark Optra E310, is configured automatically by the
  system and it worked perfectly in Linux until now. The Printer is OK,
  it works perfectly in Windows, but now in Linux everytime I try to
  print something, whatever it is, it prints the next messages on paper:

  ERROR:
  configurationerror
  OFFENDING COMMAND:
  setpagedevice
  STACK:
  --nostringval--
  false
  842
  595
  0
  0
  842
  595
  --nostringval--
  5

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar 29 19:38:02 2018
  Lpstat: device for Lexmark-Optra-E310: 
usb://Lexmark/Optra%20E310?serial=5163293
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: Lexmark-Optra-E310: Lexmark Optra E310 Foomatic/Postscript 
(recommended)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=6a60c9b5-8fd9-472c-95f2-6fb8dcdd7e1d ro splash quiet vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68-GS3 UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1759921/+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 1759921] Re: Problem with Lexmark Optra E310: printing system doesn't work

2018-04-04 Thread Carlos Rodriguez
I have solved this.

The problem was that Lexmark Optra E310 printer is not supported by
Gutenprint project, so the CUPS/Gutenprint system automatically installs
a driver for the Lexmark Optra E321, that is a very different printer
and it works, or not, depending on document or other circumstances.

The solution was install the original PPD file made for the Optra E310
printer by Lexmark. I attach the file with this message in case it can
be helpful for someone with the same problem.

Greetings.


** Attachment added: "Original Lekmark Optra E310 PPD file"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1759921/+attachment/5101051/+files/lope310.ppd

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

Title:
  Problem with Lexmark Optra E310: printing system doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  My printer, Lexmark Optra E310, is configured automatically by the
  system and it worked perfectly in Linux until now. The Printer is OK,
  it works perfectly in Windows, but now in Linux everytime I try to
  print something, whatever it is, it prints the next messages on paper:

  ERROR:
  configurationerror
  OFFENDING COMMAND:
  setpagedevice
  STACK:
  --nostringval--
  false
  842
  595
  0
  0
  842
  595
  --nostringval--
  5

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar 29 19:38:02 2018
  Lpstat: device for Lexmark-Optra-E310: 
usb://Lexmark/Optra%20E310?serial=5163293
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: Lexmark-Optra-E310: Lexmark Optra E310 Foomatic/Postscript 
(recommended)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=6a60c9b5-8fd9-472c-95f2-6fb8dcdd7e1d ro splash quiet vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68-GS3 UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1759921/+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 1759921] Re: Problem with Lexmark Optra E310: printing system doesn't work

2018-04-02 Thread Carlos Rodriguez
** Summary changed:

- printing system doesn't work
+ Problem with Lexmark Optra E310: printing system doesn't work

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

Title:
  Problem with Lexmark Optra E310: printing system doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  My printer, Lexmark Optra E310, is configured automatically by the
  system and it worked perfectly in Linux until now. The Printer is OK,
  it works perfectly in Windows, but now in Linux everytime I try to
  print something, whatever it is, it prints the next messages on paper:

  ERROR:
  configurationerror
  OFFENDING COMMAND:
  setpagedevice
  STACK:
  --nostringval--
  false
  842
  595
  0
  0
  842
  595
  --nostringval--
  5

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar 29 19:38:02 2018
  Lpstat: device for Lexmark-Optra-E310: 
usb://Lexmark/Optra%20E310?serial=5163293
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: Lexmark-Optra-E310: Lexmark Optra E310 Foomatic/Postscript 
(recommended)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=6a60c9b5-8fd9-472c-95f2-6fb8dcdd7e1d ro splash quiet vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68-GS3 UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1759921/+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 1759921] Re: printing system doesn't work

2018-03-30 Thread Carlos Rodriguez
I've installed Debian 9.4.0 with Gnome desktop and CUPS print server to
test, and it works OK, so the problem is in Ubuntu.

Thank again.

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

Title:
  printing system doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  My printer, Lexmark Optra E310, is configured automatically by the
  system and it worked perfectly in Linux until now. The Printer is OK,
  it works perfectly in Windows, but now in Linux everytime I try to
  print something, whatever it is, it prints the next messages on paper:

  ERROR:
  configurationerror
  OFFENDING COMMAND:
  setpagedevice
  STACK:
  --nostringval--
  false
  842
  595
  0
  0
  842
  595
  --nostringval--
  5

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar 29 19:38:02 2018
  Lpstat: device for Lexmark-Optra-E310: 
usb://Lexmark/Optra%20E310?serial=5163293
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: Lexmark-Optra-E310: Lexmark Optra E310 Foomatic/Postscript 
(recommended)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=6a60c9b5-8fd9-472c-95f2-6fb8dcdd7e1d ro splash quiet vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68-GS3 UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1759921/+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 1759921] Re: printing system doesn't work

2018-03-29 Thread Carlos Rodriguez
I forgot to say that the system is fresh installed in oder to do the
printing test for this bug report.

Thanks.

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

Title:
  printing system doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  My printer, Lexmark Optra E310, is configured automatically by the
  system and it worked perfectly in Linux until now. The Printer is OK,
  it works perfectly in Windows, but now in Linux everytime I try to
  print something, whatever it is, it prints the next messages on paper:

  ERROR:
  configurationerror
  OFFENDING COMMAND:
  setpagedevice
  STACK:
  --nostringval--
  false
  842
  595
  0
  0
  842
  595
  --nostringval--
  5

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar 29 19:38:02 2018
  Lpstat: device for Lexmark-Optra-E310: 
usb://Lexmark/Optra%20E310?serial=5163293
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: Lexmark-Optra-E310: Lexmark Optra E310 Foomatic/Postscript 
(recommended)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=6a60c9b5-8fd9-472c-95f2-6fb8dcdd7e1d ro splash quiet vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68-GS3 UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1759921/+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 1759921] [NEW] printing system doesn't work

2018-03-29 Thread Carlos Rodriguez
Public bug reported:

My printer, Lexmark Optra E310, is configured automatically by the
system and it worked perfectly in Linux until now. The Printer is OK, it
works perfectly in Windows, but now in Linux everytime I try to print
something, whatever it is, it prints the next messages on paper:

ERROR:
configurationerror
OFFENDING COMMAND:
setpagedevice
STACK:
--nostringval--
false
842
595
0
0
842
595
--nostringval--
5

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4ubuntu0.4
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Mar 29 19:38:02 2018
Lpstat: device for Lexmark-Optra-E310: usb://Lexmark/Optra%20E310?serial=5163293
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Papersize: a4
PpdFiles: Lexmark-Optra-E310: Lexmark Optra E310 Foomatic/Postscript 
(recommended)
ProcEnviron:
 LANGUAGE=es_ES
 TERM=xterm
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=6a60c9b5-8fd9-472c-95f2-6fb8dcdd7e1d ro splash quiet vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: N68-GS3 UCC
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug xenial

** Attachment added: "cups error log file after try to print a printer test 
page"
   https://bugs.launchpad.net/bugs/1759921/+attachment/5095231/+files/error_log

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

Title:
  printing system doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  My printer, Lexmark Optra E310, is configured automatically by the
  system and it worked perfectly in Linux until now. The Printer is OK,
  it works perfectly in Windows, but now in Linux everytime I try to
  print something, whatever it is, it prints the next messages on paper:

  ERROR:
  configurationerror
  OFFENDING COMMAND:
  setpagedevice
  STACK:
  --nostringval--
  false
  842
  595
  0
  0
  842
  595
  --nostringval--
  5

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar 29 19:38:02 2018
  Lpstat: device for Lexmark-Optra-E310: 
usb://Lexmark/Optra%20E310?serial=5163293
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: Lexmark-Optra-E310: Lexmark Optra E310 Foomatic/Postscript 
(recommended)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=6a60c9b5-8fd9-472c-95f2-6fb8dcdd7e1d ro splash quiet vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68-GS3 UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1759921/+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 1756117] [NEW] Intel graphics driver does not work on Ubuntu 17.10

2018-03-15 Thread Carlos Lemos
Public bug reported:

hardware: mini pc using intel z8300 cherry trail, 2gb, 32 gb
Win10 works fine, all services work well, audio and video playplack fine, the 
only problem with w10 is the 2gb ram memory.
errors using ubuntu 17.10:
1. unclaimed intel multimedia and power drivers
2. audio and bluetooth do not work
3. wifi is working poorly at 24mbps (after a lot of work to make it). Win10 
gives me more than 100mbps with the same hardware
regards,
carlos

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 15 10:01:33 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
PCI Configuration Registers [8086:22b0] (rev 22) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [8086:7270]
InstallationDate: Installed on 2018-03-04 (11 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: N/A CherryTrail
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=36e07aa2-b2b1-4713-a077-c8813ab395a2 ro quiet splash 
i915.alpha_support=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/06/2016
dmi.bios.vendor: N/A.
dmi.bios.version: YT8.2x64.001
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name
dmi.board.vendor: N/A
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnN/A.:bvrYT8.2x64.001:bd01/06/2016:svnN/A:pnCherryTrail:pvrType1-TBDbyOEM:rvnN/A:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Type1 - Family
dmi.product.name: CherryTrail
dmi.product.version: Type1 - TBD by OEM
dmi.sys.vendor: N/A
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  Intel graphics driver does not work on Ubuntu 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  hardware: mini pc using intel z8300 cherry trail, 2gb, 32 gb
  Win10 works fine, all services work well, audio and video playplack fine, the 
only problem with w10 is the 2gb ram memory.
  errors using ubuntu 17.10:
  1. unclaimed intel multimedia and power drivers
  2. audio and bluetooth do not work
  3. wifi is working poorly at 24mbps (after a lot of work to make it). Win10 
gives me more than 100mbps with the same hardware
  regards,
  carlos

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 15 10:01:33 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
PCI Configuration Registers [8086:22b0] (rev 22) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [8086:7270]
  InstallationDate: Installed on 2018-03-04 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: N/A CherryTrail
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=36e07aa2-b2b1-4713-a077-c8813ab395a2 ro quiet splash 
i915.alpha_support=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.b

Re: [Touch-packages] [Bug 1739346] Re: Freeze up

2018-02-08 Thread Carlos Hamer
Reply answers below:

On 02/06/2018 10:45 PM, Christopher M. Penalver wrote:
> Carlos Hamer, thank you for reporting this and helping make Ubuntu
> better.
>
> 1) To clarify, is this something that started happening after an 
> update?_*Correct*_
>
> 2) When the OS freezes up, do you notice any resources pegged at 100% in
> System Monitor?*_No_*
>
> 3) Is the computer completely locking up and unresponsive or does it
> become responsive after a while?_*Completely locking up and unresponsive*_
>
>
> 4) Is there something you do specifically that is correlated to the OS
> freezing up?_*Opening and using Chrome Beta*_
>
> ** Tags added: bios-outdated-2.21
>
> ** Changed in: xorg (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Freeze up

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  OS freezes up all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec 19 23:16:31 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0649]
  MachineType: Gateway NE56R
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=056e1ca6-0c77-4e90-afee-879313071881 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.13
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.13:bd01/17/2013:svnGateway:pnNE56R:pvrV2.13:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.13:
  dmi.product.family: Type1Family
  dmi.product.name: NE56R
  dmi.product.version: V2.13
  dmi.sys.vendor: Gateway
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Nov 12 16:56:54 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

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


Re: [Touch-packages] [Bug 1739346] Re: Freeze up

2018-02-07 Thread Carlos Hamer
Sent from my Verizon, Samsung Galaxy smartphone
 Original message From: "Christopher M. Penalver" 
<christopher.m.penal...@gmail.com> Date: 2/7/18  11:27 AM  (GMT-05:00) To: 
carlosha...@comcast.net Subject: [Bug 1739346] Re: Freeze up 
Carlos Hamer:

1) To clarify, is this something that started happening after an update?
Yes

2) How often does the freeze happen, multiple times per day, daily,
weekly, etc.? Yes, multiple times a day.

3) Could you please provide the missing information from
https://help.ubuntu.com/community/DebuggingSystemCrash ? Will do, thanks. 

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1739346

Title:
  Freeze up

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  OS freezes up all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec 19 23:16:31 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0649]
  MachineType: Gateway NE56R
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=056e1ca6-0c77-4e90-afee-879313071881 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.13
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.13:bd01/17/2013:svnGateway:pnNE56R:pvrV2.13:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.13:
  dmi.product.family: Type1Family
  dmi.product.name: NE56R
  dmi.product.version: V2.13
  dmi.sys.vendor: Gateway
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Nov 12 16:56:54 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

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

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

Title:
  Freeze up

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  OS freezes up all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec 19 23:16:31 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0649]
  MachineType: Gateway NE56R
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=056e1ca6-0c77-4e90-afee-879313071881 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

Re: [Touch-packages] [Bug 1739346] Re: Freeze up

2018-02-07 Thread Carlos Hamer
Computer completely locking up and unresponsive. I have to do reboot. 
#2. No
#4. I don't know.

Sent from my Verizon, Samsung Galaxy smartphone
 Original message From: "Christopher M. Penalver" 
<christopher.m.penal...@gmail.com> Date: 2/6/18  10:45 PM  (GMT-05:00) To: 
carlosha...@comcast.net Subject: [Bug 1739346] Re: Freeze up 
Carlos Hamer, thank you for reporting this and helping make Ubuntu
better.

1) To clarify, is this something that started happening after an update?

2) When the OS freezes up, do you notice any resources pegged at 100% in
System Monitor?

3) Is the computer completely locking up and unresponsive or does it
become responsive after a while?

4) Is there something you do specifically that is correlated to the OS
freezing up?

** Tags added: bios-outdated-2.21

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1739346

Title:
  Freeze up

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  OS freezes up all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec 19 23:16:31 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0649]
  MachineType: Gateway NE56R
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=056e1ca6-0c77-4e90-afee-879313071881 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.13
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.13:bd01/17/2013:svnGateway:pnNE56R:pvrV2.13:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.13:
  dmi.product.family: Type1Family
  dmi.product.name: NE56R
  dmi.product.version: V2.13
  dmi.sys.vendor: Gateway
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Nov 12 16:56:54 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

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

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

Title:
  Freeze up

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  OS freezes up all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec 19 23:16:31 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0649]

[Touch-packages] [Bug 1739346] [NEW] Freeze up

2017-12-19 Thread Carlos Hamer
Public bug reported:

OS freezes up all the time.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Dec 19 23:16:31 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0649]
MachineType: Gateway NE56R
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=056e1ca6-0c77-4e90-afee-879313071881 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/17/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EG50_HC_HR
dmi.board.vendor: Gateway
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.13
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.13:bd01/17/2013:svnGateway:pnNE56R:pvrV2.13:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.13:
dmi.product.family: Type1Family
dmi.product.name: NE56R
dmi.product.version: V2.13
dmi.sys.vendor: Gateway
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sun Nov 12 16:56:54 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2

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


** Tags: amd64 apport-bug artful ubuntu

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

Title:
  Freeze up

Status in xorg package in Ubuntu:
  New

Bug description:
  OS freezes up all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec 19 23:16:31 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0649]
  MachineType: Gateway NE56R
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=056e1ca6-0c77-4e90-afee-879313071881 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.13
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.13:bd01/17/2013:svnGateway:pnNE56R:pvrV2.13:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.13:
  dmi.product.family: Type1Family
  dmi.product.name: NE56R
  dmi.product.version: V2.13
  dmi.sys.vendor: Gateway
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  

Re: [Touch-packages] [Bug 1738404] Re: Bluetooth sound extreme low quality

2017-12-18 Thread Carlos Blanquer Bogacz
Hi Daniel,


- Cambridge Silicon Radio dongles are historically unreliable. I found
my Bluetooth devices were excessively buggy with them. And other people
found the same. Try a different brand if you can.

I have reverted back to Ubuntu 17.04 some minutes ago and the 3x bluetooth
audio devices work again correctly, as they did before and as they do with
my android devices.
So I do not think, this is related to any hardware issue.
I have then installed all the updates and that is stilll working.


- Can you please check what audio profile you're using in sound settings
for Bluetooth? Make sure it is A2DP for the best quality. Not HSP/HFP.
Is the problem just the wrong profile defaulting?

The only available profile was A2DP in 17.10, which I already used.
HSP/FSP did not appear in the list.

---
I also tested form an USB with 17.10 for installation, same issues.


I think I am not doing any other actions, as my immediate incident is
solved by reverting to the former version.
I hope the actual problem get fixed until next Ubuntu stable release.

Best regards,

Carlos Blanquer Bogacz
___

水に流す mizu ni nagasu : let us flow in the water


On 18 December 2017 at 11:45, Daniel van Vugt <daniel.van.v...@canonical.com
> wrote:

> A few ideas come to mind:
>
> - Cambridge Silicon Radio dongles are historically unreliable. I found
> my Bluetooth devices were excessively buggy with them. And other people
> found the same. Try a different brand if you can.
>
> - Can you please check what audio profile you're using in sound settings
> for Bluetooth? Make sure it is A2DP for the best quality. Not HSP/HFP.
> Is the problem just the wrong profile defaulting?
>
> - Bug 405294
>
> - Kernel regressions... Please try an older kernel more in line with
> what 17.04 had (kernel version 4.10 or older): http://kernel.ubuntu.com
> /~kernel-ppa/mainline/?C=N;O=D
>
>
> Probably less relevant:
>
> - A regression in bluetooth in 17.10; sounds like it is Intel specific
> though: bug 1729389
>
> ** Changed in: bluez (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1738404
>
> Title:
>   Bluetooth sound extreme low quality
>
> Status in bluez package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I upgraded today from ubuntu 17.04 to ubuntu 17.10.
>
>   I use 3 different bluetooth audio devices ( BT earphones, BT speaker,
>   BT BOSE Soundlink speaker) , all of them worked properly on 17.04.
>
>   Since the upgrade, the sound gets continuous interruptions/cracking.
>   These sound interruptions and cracking are so annoying that I cannot
> keep on listening to music.
>   I could relate this to the fact that a new BT stack has replaced the
> former in Ubuntu.
>
>   If I use wired devices (hdmi connected screen+audio, the sound quality
> is good and as before) so the issue is related to the use of the new
> Bluetooth stack.
>   I have not found a way to parameterise it neither.
>
>   I have not found any similar report. "apport" seems not ot exist in
>   thise version, I cannot find and execute it.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/
> 1738404/+subscriptions
>

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

Title:
  Bluetooth sound extreme low quality

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I upgraded today from ubuntu 17.04 to ubuntu 17.10.

  I use 3 different bluetooth audio devices ( BT earphones, BT speaker,
  BT BOSE Soundlink speaker) , all of them worked properly on 17.04.

  Since the upgrade, the sound gets continuous interruptions/cracking. 
  These sound interruptions and cracking are so annoying that I cannot keep on 
listening to music.
  I could relate this to the fact that a new BT stack has replaced the former 
in Ubuntu.

  If I use wired devices (hdmi connected screen+audio, the sound quality is 
good and as before) so the issue is related to the use of the new Bluetooth 
stack.
  I have not found a way to parameterise it neither.

  I have not found any similar report. "apport" seems not ot exist in
  thise version, I cannot find and execute it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738404/+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 1738404] Re: Bluetooth sound extreme low quality

2017-12-15 Thread Carlos Blanquer Bogacz
As I could not get data about the package, here is the hardware I am running on.
Apparently bluetooth is enabled without problem but audio streaming is still 
working with :

carlos@XS35V4:~$ lspci
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC 
Transaction Register (rev 0e)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA 
AHCI Controller (rev 0e)
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron 
N2000 Series USB xHCI (rev 0e)
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Trusted Execution Engine (rev 0e)
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
High Definition Audio Controller (rev 0e)
00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 1 (rev 0e)
00:1c.1 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 2 (rev 0e)
00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 3 (rev 0e)
00:1c.3 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 4 (rev 0e)
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power 
Control Unit (rev 0e)
00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller 
(rev 0e)
01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless 
Network Adapter (rev 01)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI 
Express Card Reader (rev 01)
02:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 0a)

carlos@XS35V4:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle 
(HCI mode)
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
Bus 001 Device 005: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D / 
OP-620D
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

carlos@XS35V4:~$ dmesg | grep Bluetooth 
[6.503447] Bluetooth: Core ver 2.22
[6.503478] Bluetooth: HCI device and connection manager initialized
[6.503483] Bluetooth: HCI socket layer initialized
[6.503486] Bluetooth: L2CAP socket layer initialized
[6.503495] Bluetooth: SCO socket layer initialized
[7.087867] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[7.087871] Bluetooth: BNEP filters: protocol multicast
[7.087877] Bluetooth: BNEP socket layer initialized
[   25.200643] Bluetooth: RFCOMM TTY layer initialized
[   25.200659] Bluetooth: RFCOMM socket layer initialized
[   25.200670] Bluetooth: RFCOMM ver 1.11

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

Title:
  Bluetooth sound extreme low quality

Status in bluez package in Ubuntu:
  New

Bug description:
  I upgraded today from ubuntu 17.04 to ubuntu 17.10.

  I use 3 different bluetooth audio devices ( BT earphones, BT speaker,
  BT BOSE Soundlink speaker) , all of them worked properly on 17.04.

  Since the upgrade, the sound gets continuous interruptions/cracking. 
  These sound interruptions and cracking are so annoying that I cannot keep on 
listening to music.
  I could relate this to the fact that a new BT stack has replaced the former 
in Ubuntu.

  If I use wired devices (hdmi connected screen+audio, the sound quality is 
good and as before) so the issue is related to the use of the new Bluetooth 
stack.
  I have not found a way to parameterise it neither.

  I have not found any similar report. "apport" seems not ot exist in
  thise version, I cannot find and execute it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738404/+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 1711087] Re: ad2p sink profile mic not available

2017-11-02 Thread Carlos Navas
I'm having the exact same problem. I have to switch manually between A2DP and 
HFP/HSP everytime I'm listening to music and I have a meeting in Bluejeans, 
Hangouts, etc. Please notice that the main problem is the sound quality when 
you have a call.
Android, MacOSX, Windows and other operative systems have implemented a way to 
automatically switch from HFP/HSP and A2DP depending if you're talking or not, 
so you can get meetings and calls with great sound quality.  

Is there any trick/feature to get this working on Linux? (last thing in
the world will be leaving Linux :D) I'm sure you can get this working
guys! :)

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 1721138] Re: APT update fail when using HTTPS

2017-10-17 Thread Carlos D. Gonzalez
Thanks Julian, I work for a company with thousands so the process of
migration all the servers is a little slow but based on or security team
we need to move all our HTTP traffic to HTTPS. That's the reason why I
filed the bug.

Also why trusty cant also handle modern HTTPS connections? Its end of
line is until 2019

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

Title:
  APT update fail when using HTTPS

Status in gnutls26 package in Ubuntu:
  New

Bug description:
  ### Ubuntu Release
  root@:~# lsb_release -rd 
  Description:    Ubuntu 14.04.5 LTS
  Release:        14.04
  root@:~#

  ### Expected Behaviors

  Trusty’s version of apt should be able to pull updates from an
  internal mirror using the HTTPS protocol and a SHA256 certificate
  (please check the 2nd link at the end of this description)

  Note: Using the same configuration on Ubuntu Xenial works.

  ### Actual Behavior

  Apt error out with the error: gnutls_handshake() failed: The signature
  algorithm is not supported.

  ### Package Information
  Im not sure if the problem is actually with apt of with a library (I’m 
including libgnutls26 info as well)
  root@:~# apt-cache policy apt
  apt:
    Installed: 1.0.1ubuntu2.17
    Candidate: 1.0.1ubuntu2.17
    Version table:
   *** 1.0.1ubuntu2.17 0
          100 /var/lib/dpkg/status
  root@:~# 

  root@:~# apt-cache policy libgnutls26
  libgnutls26:
    Installed: 2.12.23-12ubuntu2.8
    Candidate: 2.12.23-12ubuntu2.8
    Version table:
   *** 2.12.23-12ubuntu2.8 0
          100 /var/lib/dpkg/status
  root@:~#

  ### Active sources
  root@:~# egrep -R -v '^#|^$' --include=\*.list /etc/apt/
  /etc/apt/sources.list:deb https:///ubuntu/test trusty main 
restricted universe multiverse
  root@:~# 

  ### Apt Update output

  root@:~# apt update -qq
  W: Failed to fetch https:///ubuntu/test/dists/trusty/main/binary-amd64/Packages  gnutls_handshake() 
failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/restricted/binary-amd64/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/universe/binary-amd64/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/multiverse/binary-amd64/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/main/binary-i386/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/restricted/binary-i386/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/universe/binary-i386/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  W: Failed to fetch https:///ubuntu/test/dists/trusty/multiverse/binary-i386/Packages
  gnutls_handshake() failed: The signature algorithm is not supported.

  E: Some index files failed to download. They have been ignored, or old ones 
used instead.
  root@:~#

  # NMAP output of the current allowed ciphers
  root@:~# nmap --script ssl-enum-ciphers -p 443

   

  Starting Nmap 6.40 ( http://nmap.org ) at 2017-10-03 21:07 GMT
  Nmap scan report for  ()
  Host is up (0.0039s latency).
  PORTSTATE SERVICE
  443/tcp open  https
  | ssl-enum-ciphers: 
  |   SSLv3: No supported ciphers found
  |   TLSv1.0: 
  | ciphers: 
  |   TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_AES_128_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_AES_256_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_SEED_CBC_SHA - strong
  |   TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA - strong
  |   TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA - strong
  |   TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA - strong
  |   TLS_ECDHE_RSA_WITH_RC4_128_SHA - strong
  |   TLS_RSA_WITH_3DES_EDE_CBC_SHA - strong
  |   TLS_RSA_WITH_AES_128_CBC_SHA - strong
  |   TLS_RSA_WITH_AES_256_CBC_SHA - strong
  |   TLS_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
  |   TLS_RSA_WITH_CAMELLIA_256_CBC_SHA - strong
  |   TLS_RSA_WITH_RC4_128_MD5 - strong
  |   TLS_RSA_WITH_RC4_128_SHA - strong
  |   TLS_RSA_WITH_SEED_CBC_SHA - strong
  | compressors: 
  |   NULL
  |   TLSv1.1: 
  | ciphers: 
  |   TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_AES_128_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_AES_256_CBC_SHA - strong
  |   TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
  |   

[Touch-packages] [Bug 1722835] [NEW] I was working and everything freeze.

2017-10-11 Thread Carlos Matons Cesco
Public bug reported:

Running Netbeans, Firefox, Audacious, Filemanager...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Oct 11 11:28:40 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF116 [GeForce GTX 550 Ti] [1043:83be]
InstallationDate: Installed on 2017-10-10 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
MachineType: Gigabyte Technology Co., Ltd. B85M-DS3H
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=ab28a80a-2036-46f7-af84-696df85b60bf ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-DS3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: B85M-DS3H
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  I was working and everything freeze.

Status in xorg package in Ubuntu:
  New

Bug description:
  Running Netbeans, Firefox, Audacious, Filemanager...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Oct 11 11:28:40 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF116 [GeForce GTX 550 Ti] [1043:83be]
  InstallationDate: Installed on 2017-10-10 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Gigabyte Technology Co., Ltd. B85M-DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=ab28a80a-2036-46f7-af84-696df85b60bf ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-DS3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: B85M-DS3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 

[Touch-packages] [Bug 1721138] [NEW] APT update fail when using HTTPS

2017-10-03 Thread Carlos D. Gonzalez
Public bug reported:

### Ubuntu Release
root@:~# lsb_release -rd 
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
root@:~#

### Expected Behaviors

Trusty’s version of apt should be able to pull updates from an internal
mirror using the HTTPS protocol and a SHA256 certificate (please check
the 2nd link at the end of this description)

Note: Using the same configuration on Ubuntu Xenial works.

### Actual Behavior

Apt error out with the error: gnutls_handshake() failed: The signature
algorithm is not supported.

### Package Information
Im not sure if the problem is actually with apt of with a library (I’m 
including libgnutls26 info as well)
root@:~# apt-cache policy apt
apt:
  Installed: 1.0.1ubuntu2.17
  Candidate: 1.0.1ubuntu2.17
  Version table:
 *** 1.0.1ubuntu2.17 0
        100 /var/lib/dpkg/status
root@:~# 

root@:~# apt-cache policy libgnutls26
libgnutls26:
  Installed: 2.12.23-12ubuntu2.8
  Candidate: 2.12.23-12ubuntu2.8
  Version table:
 *** 2.12.23-12ubuntu2.8 0
        100 /var/lib/dpkg/status
root@:~#

### Active sources
root@:~# egrep -R -v '^#|^$' --include=\*.list /etc/apt/
/etc/apt/sources.list:deb https:///ubuntu/test trusty main 
restricted universe multiverse
root@:~# 

### Apt Update output

root@:~# apt update -qq
W: Failed to fetch https:///ubuntu/test/dists/trusty/main/binary-amd64/Packages  gnutls_handshake() 
failed: The signature algorithm is not supported.

W: Failed to fetch https:///ubuntu/test/dists/trusty/restricted/binary-amd64/Packages
gnutls_handshake() failed: The signature algorithm is not supported.

W: Failed to fetch https:///ubuntu/test/dists/trusty/universe/binary-amd64/Packages
gnutls_handshake() failed: The signature algorithm is not supported.

W: Failed to fetch https:///ubuntu/test/dists/trusty/multiverse/binary-amd64/Packages
gnutls_handshake() failed: The signature algorithm is not supported.

W: Failed to fetch https:///ubuntu/test/dists/trusty/main/binary-i386/Packages
gnutls_handshake() failed: The signature algorithm is not supported.

W: Failed to fetch https:///ubuntu/test/dists/trusty/restricted/binary-i386/Packages
gnutls_handshake() failed: The signature algorithm is not supported.

W: Failed to fetch https:///ubuntu/test/dists/trusty/universe/binary-i386/Packages
gnutls_handshake() failed: The signature algorithm is not supported.

W: Failed to fetch https:///ubuntu/test/dists/trusty/multiverse/binary-i386/Packages
gnutls_handshake() failed: The signature algorithm is not supported.

E: Some index files failed to download. They have been ignored, or old ones 
used instead.
root@:~#

# NMAP output of the current allowed ciphers
root@:~# nmap --script ssl-enum-ciphers -p 443  

 

Starting Nmap 6.40 ( http://nmap.org ) at 2017-10-03 21:07 GMT
Nmap scan report for  ()
Host is up (0.0039s latency).
PORTSTATE SERVICE
443/tcp open  https
| ssl-enum-ciphers: 
|   SSLv3: No supported ciphers found
|   TLSv1.0: 
| ciphers: 
|   TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA - strong
|   TLS_DHE_RSA_WITH_AES_128_CBC_SHA - strong
|   TLS_DHE_RSA_WITH_AES_256_CBC_SHA - strong
|   TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
|   TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA - strong
|   TLS_DHE_RSA_WITH_SEED_CBC_SHA - strong
|   TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA - strong
|   TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA - strong
|   TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA - strong
|   TLS_ECDHE_RSA_WITH_RC4_128_SHA - strong
|   TLS_RSA_WITH_3DES_EDE_CBC_SHA - strong
|   TLS_RSA_WITH_AES_128_CBC_SHA - strong
|   TLS_RSA_WITH_AES_256_CBC_SHA - strong
|   TLS_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
|   TLS_RSA_WITH_CAMELLIA_256_CBC_SHA - strong
|   TLS_RSA_WITH_RC4_128_MD5 - strong
|   TLS_RSA_WITH_RC4_128_SHA - strong
|   TLS_RSA_WITH_SEED_CBC_SHA - strong
| compressors: 
|   NULL
|   TLSv1.1: 
| ciphers: 
|   TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA - strong
|   TLS_DHE_RSA_WITH_AES_128_CBC_SHA - strong
|   TLS_DHE_RSA_WITH_AES_256_CBC_SHA - strong
|   TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
|   TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA - strong
|   TLS_DHE_RSA_WITH_SEED_CBC_SHA - strong
|   TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA - strong
|   TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA - strong
|   TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA - strong
|   TLS_ECDHE_RSA_WITH_RC4_128_SHA - strong
|   TLS_RSA_WITH_3DES_EDE_CBC_SHA - strong
|   TLS_RSA_WITH_AES_128_CBC_SHA - strong
|   TLS_RSA_WITH_AES_256_CBC_SHA - strong
|   TLS_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
|   TLS_RSA_WITH_CAMELLIA_256_CBC_SHA - strong
|   TLS_RSA_WITH_RC4_128_MD5 - strong
|   TLS_RSA_WITH_RC4_128_SHA - strong
|   TLS_RSA_WITH_SEED_CBC_SHA - strong
| compressors: 
|   NULL
|   TLSv1.2: 
| ciphers: 
|   

[Touch-packages] [Bug 1717992] Re: Sound silently plays to "Dummy Output"

2017-09-20 Thread Carlos Eduardo Moreira dos Santos
Reboot in 4.10-0-33 and youtube is muted on Dummy Output. Tried VLC with
same results. The weird thing is that I could hear audio in 4.10.0-35 in
some occasions, with my device being correctly displayed in pavucontrol.
Suddenly, it had a Dummy Output again...

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

Title:
  Sound silently plays to "Dummy Output"

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0bcd17dc-d971-4048-8c1f-d2bb48e8a157
  InstallationDate: Installed on 2017-08-18 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 7460
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not 

[Touch-packages] [Bug 1717992] Re: Sound silently plays to "Dummy Output"

2017-09-18 Thread Carlos Eduardo Moreira dos Santos
The previous kernel I see in /boot is 4.10.0-33. Tomorrow or in the day
after, I'll boot in the older kernel to check whether it's working.

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

Title:
  Sound silently plays to "Dummy Output"

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0bcd17dc-d971-4048-8c1f-d2bb48e8a157
  InstallationDate: Installed on 2017-08-18 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 7460
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic.efi.signed 

[Touch-packages] [Bug 1717992] [NEW] Sound silently plays to "Dummy Output"

2017-09-18 Thread Carlos Eduardo Moreira dos Santos
Public bug reported:

Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
detected, but pavucontrol has only "Dummy Output". Bar animation shows
audio is playing, but no sound is heard. alsamixer is working fine, but
audio still can't be heard. Configuration tab says "No cards available
for configuration".

$ lspci -v
0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

# aplay -L
default
Playback/recording through the PulseAudio sound server
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
sysdefault:CARD=PCH
HDA Intel PCH, ALC3246 Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
Front speakers
surround21:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
hdmi:CARD=PCH,DEV=0
HDA Intel PCH, HDMI 0
HDMI Audio Output
hdmi:CARD=PCH,DEV=1
HDA Intel PCH, HDMI 1
HDMI Audio Output
hdmi:CARD=PCH,DEV=2
HDA Intel PCH, HDMI 2
HDMI Audio Output
dmix:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
Direct sample mixing device
dmix:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample mixing device
dmix:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct sample mixing device
dmix:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct sample mixing device
dsnoop:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
Direct sample snooping device
dsnoop:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample snooping device
dsnoop:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct sample snooping device
dsnoop:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct sample snooping device
hw:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
Direct hardware device without any conversions
hw:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct hardware device without any conversions
hw:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct hardware device without any conversions
hw:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct hardware device without any conversions
plughw:CARD=PCH,DEV=0
HDA Intel PCH, ALC3246 Analog
Hardware device with all software conversions
plughw:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Hardware device with all software conversions
plughw:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Hardware device with all software conversions
plughw:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Hardware device with all software conversions

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

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

Title:
  Sound silently plays to "Dummy Output"

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 

[Touch-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

2017-09-15 Thread Carlos Renê
Lubuntu 16.04.3 have same problem! :/

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

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Triaged
Status in Light Display Manager 1.18 series:
  Triaged
Status in lightdm package in Ubuntu:
  Confirmed
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Confirmed
Status in lxsession source package in Xenial:
  Confirmed

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+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 1716104] [NEW] can't get nvidia to work

2017-09-09 Thread Juan Carlos Carvajal Bermúdez
Public bug reported:

I can't get the nvidia driver to work.

When I type "prime-select intel" the system works.

When I type "prime-select nvidia" glxinfo breaks.


lsmod | grep nvidia
nvidia_uvm688128  0
nvidia_drm 49152  0
nvidia_modeset843776  1 nvidia_drm
nvidia  12984320  2 nvidia_modeset,nvidia_uvm
drm_kms_helper155648  2 i915,nvidia_drm
drm   364544  4 i915,drm_kms_helper,nvidia_drm


> BUT: Xorg.0.log has the following errors:

[   478.562] (EE) Failed to load module "nvidia" (module does not exist, 0)
[   478.562] (EE) Failed to load module "nouveau" (module does not exist, 0)
[   478.563] (EE) Failed to load module "nvidia" (module does not exist, 0)
[   478.563] (EE) Failed to load module "nouveau" (module does not exist, 0)
[   478.572] (EE) open /dev/fb0: No such file or directory
[   478.572] (EE) open /dev/fb0: No such file or directory
[   478.572] (EE) open /dev/fb0: No such file or directory
[   478.572] (EE) open /dev/fb0: No such file or directory
[   478.572] (EE) Screen 0 deleted because of no matching config section.
[   478.572] (EE) Screen 0 deleted because of no matching config section.
[   478.572] (EE) Screen 0 deleted because of no matching config section.
[   478.572] (EE) Screen 0 deleted because of no matching config section.
[   478.699] (EE) AIGLX: reverting to software rendering


> I think I need to generate a valid xorg.conf file


> BUT: when I execute sudo X -configure I get the following error at the 
end:


List of video drivers:
amdgpu
ati
cirrus
intel
mach64
mga
neomagic
openchrome
qxl
r128
radeon
savage
siliconmotion
sisusb
trident
vmware
vesa
modesetting
fbdev
tdfx
(++) Using config file: "/home/jccb/xorg.conf.new"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Number of created screens does not match number of detected devices.
  Configuration failed.
(EE) Server terminated with error (2). Closing log file.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.69  Wed Aug 16 19:34:54 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Sep  9 11:25:06 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
 nvidia-384, 384.69, 4.4.0-93-generic, x86_64: installed
 webcamstudio, 0.73, 3.13.0-101-generic, x86_64: installed
 webcamstudio, 0.73, 4.4.0-92-generic, x86_64: installed
 webcamstudio, 0.73, 4.4.0-93-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1113]
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM108M [GeForce 840M] 
[1462:1113]
InstallationDate: Installed on 2015-01-23 (960 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Micro-Star International Co., Ltd. GP60 2PE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=da904324-ef1b-4408-8fe7-543a661e7464 ro nomodeset=1 splash quiet
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16GHIMS.10B
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16GH
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
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.:bvrE16GHIMS.10B:bd10/23/2014:svnMicro-StarInternationalCo.,Ltd.:pnGP602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GH:rvrREV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: GP60 2PE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
nvidia-settings:
 ERROR: Error querying enabled displays on GPU 0 (Missing Extension).
 
 
 ERROR: Error querying connected 

[Touch-packages] [Bug 1715633] [NEW] nvidia drivers...

2017-09-07 Thread Juan Carlos Carvajal Bermúdez
Public bug reported:

I'm trying to install the nvidia driver since days. I'm afraid that one
of the "displays" (the intel VGA one) is not working anymore. At least
it appears unclaimed with or without the nvidia driver.


*** ANY HELP IS HIGHLY APPREACIATED, THANK YOU ***


ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.26.13  Wed Aug 16 04:02:47 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME-Flashback:Unity
Date: Thu Sep  7 14:54:16 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
 nvidia-381, 381.26.13, 4.4.0-93-generic, x86_64: installed
 webcamstudio, 0.73, 3.13.0-101-generic, x86_64: installed
 webcamstudio, 0.73, 4.4.0-92-generic, x86_64: installed
 webcamstudio, 0.73, 4.4.0-93-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GconfCompiz:
 /apps/compiz-1/plugins:
   /apps/compiz-1/plugins/unityshell:
/apps/compiz-1/plugins/unityshell/screen0:
 /apps/compiz-1/plugins/unityshell/screen0/options:
  devices_option = 0
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1113]
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM108M [GeForce 840M] 
[1462:1113]
InstallationDate: Installed on 2015-01-23 (958 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Micro-Star International Co., Ltd. GP60 2PE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=da904324-ef1b-4408-8fe7-543a661e7464 ro nomodeset=1 splash quiet
SourcePackage: xorg
UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 5: Error: GLX is not available on the system
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16GHIMS.10B
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16GH
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
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.:bvrE16GHIMS.10B:bd10/23/2014:svnMicro-StarInternationalCo.,Ltd.:pnGP602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GH:rvrREV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: GP60 2PE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Sep  7 14:46:28 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.3

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


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

** Description changed:

  I'm trying to install the nvidia driver since days. I'm afraid that one
  of the "displays" (the intel VGA one) is not working anymore. At least
  it appears unclaimed with or without the nvidia driver.
+ 
+ 
+ *** ANY HELP IS HIGHLY APPREACIATED, THANK YOU ***
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  

[Touch-packages] [Bug 1705122] Re: Installed snaps do not appear among other apps in menus when using Wayland

2017-08-20 Thread Carlos Gomes
One should also add, that happens to all snap apps, not only telegram.
In my case, with atom, and libreoffice packaged by snapcrafters

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

Title:
  Installed snaps do not appear among other apps in menus when using
  Wayland

Status in snapd package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  I installed the snap telegram-sergiusens but it doesn't appear among
  the other applications in the menu and I can't search for it from the
  Activities menu (GNOME Shell).

  I'm trying this from a Wayland session, I don't know if this can be
  related in any way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: snapd 2.26.10+17.10
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 22:39:57 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1705122/+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 1705122] Re: Installed snaps do not appear among other apps in menus when using Wayland

2017-08-20 Thread Carlos Gomes
This is also happening with Ubuntu Gnome 17.04. Only in wayland session,
in x11 its okay

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

Title:
  Installed snaps do not appear among other apps in menus when using
  Wayland

Status in snapd package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  I installed the snap telegram-sergiusens but it doesn't appear among
  the other applications in the menu and I can't search for it from the
  Activities menu (GNOME Shell).

  I'm trying this from a Wayland session, I don't know if this can be
  related in any way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: snapd 2.26.10+17.10
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 22:39:57 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1705122/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

2017-08-14 Thread Carlos Alirio Rico Acevedo
Hello I have a problem, my latop is an Asus450U has HDA Intel PCH, Chip:
Realtek ALC256. I had a problem with the microphone and line No. 8 gave
the solution to this, but I've found that does not recognize the two
internal speakers, only works the right speaker. And in the same way
does not recognize the two headphones, only recognizes the left. I have
played with Alsamixer but no configuration has helped, nor the
pavucontrol.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  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/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+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 1702393] [NEW] information!!

2017-07-04 Thread Carlos Ochoa
Public bug reported:

these are the bugs in my system, I am new in ubuntu for that i need
help. thanks!!

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Jul  4 21:15:41 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
InstallationDate: Installed on 2017-06-26 (8 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80GA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=2b7d12b4-a5b9-4bff-82a5-e1baa1ae40fe ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ACN26WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50515STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G40-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN26WW:bd07/31/2014:svnLENOVO:pn80GA:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrSDK0E50515STD:cvnLENOVO:ct10:cvrLenovoG40-70:
dmi.product.name: 80GA
dmi.product.version: Lenovo G40-70
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.81+git1706301830.3095cc~gd~z
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2~git1707031930.6158c0~gd~z
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2~git1707031930.6158c0~gd~z
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Tue Jul  4 20:44:22 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu zesty

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

Title:
  information!!

Status in xorg package in Ubuntu:
  New

Bug description:
  these are the bugs in my system, I am new in ubuntu for that i need
  help. thanks!!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jul  4 21:15:41 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
  InstallationDate: Installed on 2017-06-26 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80GA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=2b7d12b4-a5b9-4bff-82a5-e1baa1ae40fe ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN26WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50515STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G40-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN26WW:bd07/31/2014:svnLENOVO:pn80GA:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrSDK0E50515STD:cvnLENOVO:ct10:cvrLenovoG40-70:
  dmi.product.name: 80GA
  dmi.product.version: Lenovo G40-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81+git1706301830.3095cc~gd~z
  

[Touch-packages] [Bug 1701447] [NEW] package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-06-30 Thread Carlos Zargoza
*** This bug is a duplicate of bug 1632415 ***
https://bugs.launchpad.net/bugs/1632415

Public bug reported:

The bugs being reported were generated automatically (without any of my
input) when I allowed the system to upgrade itself from 16.04 to 16.10.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: gconf2 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.3
Architecture: amd64
Date: Thu Jun 29 21:58:13 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2016-11-27 (214 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.3.5
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to yakkety on 2017-06-30 (0 days ago)
mtime.conffile..etc.xdg.autostart.gsettings-data-convert.desktop: 
2017-01-03T13:15:58.771330

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


** Tags: amd64 apport-package yakkety

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  The bugs being reported were generated automatically (without any of
  my input) when I allowed the system to upgrade itself from 16.04 to
  16.10.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Thu Jun 29 21:58:13 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-11-27 (214 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-06-30 (0 days ago)
  mtime.conffile..etc.xdg.autostart.gsettings-data-convert.desktop: 
2017-01-03T13:15:58.771330

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1701447/+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 1701257] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-29 Thread carlos roberto alves benevides
*** This bug is a duplicate of bug 1688721 ***
https://bugs.launchpad.net/bugs/1688721

Public bug reported:

I just tried to install this app and it become frozen.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic i686
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: i386
Date: Thu Jun 29 09:30:14 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-23 (6 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  I just tried to install this app and it become frozen.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  Date: Thu Jun 29 09:30:14 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-23 (6 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1701257/+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 1698670] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 usr/lib/i386-linux-gnu/openssl-1.0.0

2017-06-18 Thread Carlos Moreno
Public bug reported:

please

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: 
lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sun Jun 18 11:19:46 2017
ErrorMessage: el paquete libssl1.0.0:i386 no está listo para configurarse  no 
se puede configurar (estado actual `half-installed')
InstallationDate: Installed on 2017-05-05 (44 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: lib/i386-linux-
  gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 usr/lib/i386
  -linux-gnu/openssl-1.0.0/engines/lib4758cca.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libaep.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libatalla.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libcapi.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libchil.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libcswift.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libgmp.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libgost.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libnuron.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libpadlock.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libsureware.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: el paquete libssl1.0.0:i386 no está listo para
  configurarse  no se puede configurar (estado actual `half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  please

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: 
lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jun 18 11:19:46 2017
  ErrorMessage: el paquete libssl1.0.0:i386 no está listo para configurarse  no 
se puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2017-05-05 (44 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  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/1698670/+subscriptions

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

[Touch-packages] [Bug 1697765] [NEW] package make 4.1-6 failed to install/upgrade: el paquete make no está listo para configurarse no se puede configurar (estado actual `half-installed')

2017-06-13 Thread Juan Carlos Prieto
Public bug reported:

I can't install or update any package.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: make 4.1-6
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
Date: Tue Jun 13 21:34:56 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu7
 libgcc1 1:6.0.1-0ubuntu1
ErrorMessage: el paquete make no está listo para configurarse  no se puede 
configurar (estado actual `half-installed')
InstallationDate: Installed on 2017-05-18 (26 days ago)
InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170216)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: make-dfsg
Title: package make 4.1-6 failed to install/upgrade: el paquete make no está 
listo para configurarse  no se puede configurar (estado actual `half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package make 4.1-6 failed to install/upgrade: el paquete make no está
  listo para configurarse  no se puede configurar (estado actual `half-
  installed')

Status in make-dfsg package in Ubuntu:
  New

Bug description:
  I can't install or update any package.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: make 4.1-6
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Tue Jun 13 21:34:56 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  ErrorMessage: el paquete make no está listo para configurarse  no se puede 
configurar (estado actual `half-installed')
  InstallationDate: Installed on 2017-05-18 (26 days ago)
  InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170216)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: make-dfsg
  Title: package make 4.1-6 failed to install/upgrade: el paquete make no está 
listo para configurarse  no se puede configurar (estado actual `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1697765/+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 1694214] [NEW] wget http://beta.unity3d.com/download/e348e673a4c6/unity-editor_amd64-5.6.0xf1Linux.deb -O unity-editor.deb

2017-05-29 Thread Joao Carlos Linhares
Public bug reported:

dpkg: erro ao processar o arquivo unity-editor.deb (--install):
 impossível acessar arquivo: Arquivo ou diretório não encontrado
Erros foram encontrados durante o processamento de:
 unity-editor.deb

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd-sysv 225-1ubuntu9.1
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sun May 28 18:00:52 2017
ErrorMessage: pre-dependency problem - not installing systemd-sysv
InstallationDate: Installed on 2015-12-06 (539 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: systemd
Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  wget http://beta.unity3d.com/download/e348e673a4c6/unity-
  editor_amd64-5.6.0xf1Linux.deb -O unity-editor.deb

Status in systemd package in Ubuntu:
  New

Bug description:
  dpkg: erro ao processar o arquivo unity-editor.deb (--install):
   impossível acessar arquivo: Arquivo ou diretório não encontrado
  Erros foram encontrados durante o processamento de:
   unity-editor.deb

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun May 28 18:00:52 2017
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-12-06 (539 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: systemd
  Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


  1   2   >