[Touch-packages] [Bug 1993806] [NEW] bluetooth not turning on and not connectting to my device

[André Luiz Gava]

Public bug reported:

Yesterday I connect my bluettoh phone in my new computer with Ubuntu
22.04, then today I wasnt able to reconect my phone, I tryes to
disconect it in ubuntu interface, but this doesnt disconect, but no
sound come from my earphone, then I tryed to turn bluetooth off, and it
doesnt turn in again now.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluetooth (not installed)
Uname: Linux 5.19.2-051902-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 21 08:37:09 2022
InstallationDate: Installed on 2022-08-18 (63 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Positivo Bahia - VAIO VJFE44F11X-B2111H
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.2-051902-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2022
dmi.bios.release: 5.24
dmi.bios.version: V1.19.X
dmi.board.asset.tag: Default string
dmi.board.name: VJFE-ADLBAT55
dmi.board.vendor: Positivo Tecnologia SA
dmi.board.version: 11179464
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Positivo Tecnologia SA
dmi.chassis.version: Default string
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvn:bvrV1.19.X:bd06/17/2022:br5.24:efr1.14:svnPositivoBahia-VAIO:pnVJFE44F11X-B2111H:pvrV1.19.X:rvnPositivoTecnologiaSA:rnVJFE-ADLBAT55:rvr11179464:cvnPositivoTecnologiaSA:ct10:cvrDefaultstring:sku3343073:
dmi.product.family: VJFE44
dmi.product.name: VJFE44F11X-B2111H
dmi.product.sku: 3343073
dmi.product.version: V1.19.X
dmi.sys.vendor: Positivo Bahia - VAIO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 70:32:17:8B:A0:FF  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:2874357 acl:298 sco:0 events:409778 errors:0
TX bytes:251252400 acl:406246 sco:0 commands:3297 errors:0
syslog:

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


** Tags: amd64 apport-bug jammy

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

Title:
  bluetooth not turning on and not connectting to my device

Status in bluez package in Ubuntu:
  New

Bug description:
  Yesterday I connect my bluettoh phone in my new computer with Ubuntu
  22.04, then today I wasnt able to reconect my phone, I tryes to
  disconect it in ubuntu interface, but this doesnt disconect, but no
  sound come from my earphone, then I tryed to turn bluetooth off, and
  it doesnt turn in again now.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluetooth (not installed)
  Uname: Linux 5.19.2-051902-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 21 08:37:09 2022
  InstallationDate: Installed on 2022-08-18 (63 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Positivo Bahia - VAIO VJFE44F11X-B2111H
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.2-051902-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2022
  dmi.bios.release: 5.24
  dmi.bios.version: V1.19.X
  dmi.board.asset.tag: Default string
  dmi.board.name: VJFE-ADLBAT55
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11179464
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvn:bvrV1.19.X:bd06/17/2022:br5.24:efr1.14:svnPositivoBahia-VAIO:pnVJFE44F11X-B2111H:pvrV1.19.X:rvnPositivoTecnologiaSA:rnVJFE-ADLBAT55:rvr11179464:cvnPositivoTecnologiaSA:ct10:cvrDefaultstring:sku3343073:
  dmi.product.family: VJFE44
  dmi.product.name: VJFE44F11X-B2111H
  dmi.product.sku: 3343073
  dmi.product.version: V1.19.X
  dmi.sys.vendor: Positivo Bahia - VAIO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 70:32:17:8B:A0:FF  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:2874357 acl:298 sco:0 events:409778 errors:0
TX bytes:251252400 acl:406246 sco:0 commands:3297 errors:0
  syslog:

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


-- 
Mailing list: 

[Touch-packages] [Bug 1002952] Re: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

[André Gomes]

The workaround is still valid. I just tested with my "Plantronics
Blackwire 5220 Seri"

http://alsa-project.org/db/?f=461556fb1a5f3a0f5de01e66274d71a59dfb27d9

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

Title:
  [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

Status in alsa-lib package in Ubuntu:
  Confirmed

Bug description:
  === Read me first ===

  = Symptom =

  If you have a USB headset, or other USB device that does not have any
  S/PDIF output, but yet sometimes there is an extra device called
  "Digital Output (S/PDIF)" for that device, you're suffering from this
  bug.

  This bug is only for USB devices - if you have an invalid digital
  output for some other type of device, please file a separate bug
  instead.

  = Workaround =

  If you're affected, please try this workaround:

  first check the output of "aplay -l" (lowercase L), or "arecord -l" if
  it's an input device, and grab the first of two name in brackets:

  Example:
  card 3: Headset [Sennheiser USB Headset], device 0: USB Audio [USB Audio]
  here grab the name "Sennheiser USB Headset". Now edit the file 
/usr/share/alsa/cards/USB-Audio.conf (requires root permissions)
  Around line 40, you will find a line saying "Logitech USB Headset" 999
  Add a new line after this line, so that there is now a new line called
  "Sennheiser USB Headset" 999
  (including quotes, and replace "Sennheiser USB Headset" with whatever your 
particular card was named.)

  Save the file and reboot your computer for the changes to take effect.

  = Already known devices =

  These card names are already in 12.04:

  "Blue Snowball"
  "Logitech USB Headset"
  "Logitech Web Camera"

  These card names are on their way into 12.04:

  "Logitech Speaker Lapdesk N700"
  "Logitech Wireless Headset"
  "Plantronics USB Headset"
  "Sennheiser USB headset"

  If you have one of the above four, please help out by testing the
  proposed repository and report back in bug 987163.

  If your name is not listed above, please add a comment to this bug,
  including your alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo -
  they will be collected for a SRU later on, or at least make it into
  the next release of Ubuntu.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1002952/+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 1938065] Re: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)

[André]

This was a byproduct of a incomplete usrmerge

Calling the binary below and solving the problems fixed the issue

/usr/lib/usrmerge/convert-usrmerge

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This happened when trying to upgrade from 21.04 to 21.10.

  Setting up systemd (248.3-1ubuntu2) ...
  systemd-machine-id-setup: error while loading shared libraries: 
libsystemd-shared-247.so: cannot open shared object file: No such file or 
directory
  dpkg: error processing package systemd (--configure):
   installed systemd package post-installation script subprocess returned error 
exit status 127
  Processing triggers for initramfs-tools (0.140ubuntu6) ...
  update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
  Processing triggers for libc-bin (2.33-0ubuntu7) ...
  Processing triggers for man-db (2.9.4-2) ...
  Processing triggers for dbus (1.12.20-2ubuntu1) ...
  Errors were encountered while processing:
   systemd

  I reverted to old version by manualing installing the hirsute's debs
  (from 21.04: libsystemd0_247.3-3ubuntu3.4_i386.deb
  systemd_247.3-3ubuntu3.4_amd64.deb libnss-
  systemd_247.3-3ubuntu3.4_amd64.deb libsystemd-
  dev_247.3-3ubuntu3.4_amd64.deb systemd-sysv_247.3-3ubuntu3.4_amd64.deb
  libpam-systemd_247.3-3ubuntu3.4_amd64.deb
  libudev1_247.3-3ubuntu3.4_amd64.deb udev_247.3-3ubuntu3.4_amd64.deb
  libsystemd0_247.3-3ubuntu3.4_amd64.deb libudev-
  dev_247.3-3ubuntu3.4_amd64.deb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938065/+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 1938065] Re: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)

[André]

Problem persists while trying to upgrade to newer version of package
(248.3-1ubuntu3)


(Reading database ... 769323 files and directories currently installed.)
Preparing to unpack .../libsystemd-dev_248.3-1ubuntu3_amd64.deb ...
Unpacking libsystemd-dev:amd64 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../libnss-systemd_248.3-1ubuntu3_amd64.deb ...
Unpacking libnss-systemd:amd64 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../libudev-dev_248.3-1ubuntu3_amd64.deb ...
Unpacking libudev-dev:amd64 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../libudev1_248.3-1ubuntu3_amd64.deb ...
Unpacking libudev1:amd64 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Setting up libudev1:amd64 (248.3-1ubuntu3) ...
(Reading database ... 769328 files and directories currently installed.)
Preparing to unpack .../systemd_248.3-1ubuntu3_amd64.deb ...
Unpacking systemd (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../udev_248.3-1ubuntu3_amd64.deb ...
Unpacking udev (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../libsystemd0_248.3-1ubuntu3_i386.deb ...
De-configuring libsystemd0:amd64 (247.3-3ubuntu3.4) ...
Unpacking libsystemd0:i386 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Preparing to unpack .../libsystemd0_248.3-1ubuntu3_amd64.deb ...
Unpacking libsystemd0:amd64 (248.3-1ubuntu3) over (247.3-3ubuntu3.4) ...
Setting up libsystemd0:amd64 (248.3-1ubuntu3) ...
Setting up systemd (248.3-1ubuntu3) ...
Installing new version of config file /etc/systemd/logind.conf ...
Installing new version of config file /etc/systemd/networkd.conf ...
Installing new version of config file /etc/systemd/pstore.conf ...
Installing new version of config file /etc/systemd/resolved.conf ...
Installing new version of config file /etc/systemd/sleep.conf ...
Installing new version of config file /etc/systemd/system.conf ...
Installing new version of config file /etc/systemd/user.conf ...
systemd-machine-id-setup: error while loading shared libraries: 
libsystemd-shared-247.so: cannot ope
n shared object file: No such file or directory
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error 
exit status 127
Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)

Status in systemd package in Ubuntu:
  New

Bug description:
  This happened when trying to upgrade from 21.04 to 21.10.

  Setting up systemd (248.3-1ubuntu2) ...
  systemd-machine-id-setup: error while loading shared libraries: 
libsystemd-shared-247.so: cannot open shared object file: No such file or 
directory
  dpkg: error processing package systemd (--configure):
   installed systemd package post-installation script subprocess returned error 
exit status 127
  Processing triggers for initramfs-tools (0.140ubuntu6) ...
  update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
  Processing triggers for libc-bin (2.33-0ubuntu7) ...
  Processing triggers for man-db (2.9.4-2) ...
  Processing triggers for dbus (1.12.20-2ubuntu1) ...
  Errors were encountered while processing:
   systemd

  I reverted to old version by manualing installing the hirsute's debs
  (from 21.04: libsystemd0_247.3-3ubuntu3.4_i386.deb
  systemd_247.3-3ubuntu3.4_amd64.deb libnss-
  systemd_247.3-3ubuntu3.4_amd64.deb libsystemd-
  dev_247.3-3ubuntu3.4_amd64.deb systemd-sysv_247.3-3ubuntu3.4_amd64.deb
  libpam-systemd_247.3-3ubuntu3.4_amd64.deb
  libudev1_247.3-3ubuntu3.4_amd64.deb udev_247.3-3ubuntu3.4_amd64.deb
  libsystemd0_247.3-3ubuntu3.4_amd64.deb libudev-
  dev_247.3-3ubuntu3.4_amd64.deb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938065/+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 1938065] [NEW] systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)

[André]

Public bug reported:

This happened when trying to upgrade from 21.04 to 21.10.

Setting up systemd (248.3-1ubuntu2) ...
systemd-machine-id-setup: error while loading shared libraries: 
libsystemd-shared-247.so: cannot open shared object file: No such file or 
directory
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error 
exit status 127
Processing triggers for initramfs-tools (0.140ubuntu6) ...
update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
Processing triggers for libc-bin (2.33-0ubuntu7) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for dbus (1.12.20-2ubuntu1) ...
Errors were encountered while processing:
 systemd

I reverted to old version by manualing installing the hirsute's debs
(from 21.04: libsystemd0_247.3-3ubuntu3.4_i386.deb
systemd_247.3-3ubuntu3.4_amd64.deb libnss-
systemd_247.3-3ubuntu3.4_amd64.deb libsystemd-
dev_247.3-3ubuntu3.4_amd64.deb systemd-sysv_247.3-3ubuntu3.4_amd64.deb
libpam-systemd_247.3-3ubuntu3.4_amd64.deb
libudev1_247.3-3ubuntu3.4_amd64.deb udev_247.3-3ubuntu3.4_amd64.deb
libsystemd0_247.3-3ubuntu3.4_amd64.deb libudev-
dev_247.3-3ubuntu3.4_amd64.deb)

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

** Package changed: calamares (Ubuntu) => systemd (Ubuntu)

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

Title:
  systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)

Status in systemd package in Ubuntu:
  New

Bug description:
  This happened when trying to upgrade from 21.04 to 21.10.

  Setting up systemd (248.3-1ubuntu2) ...
  systemd-machine-id-setup: error while loading shared libraries: 
libsystemd-shared-247.so: cannot open shared object file: No such file or 
directory
  dpkg: error processing package systemd (--configure):
   installed systemd package post-installation script subprocess returned error 
exit status 127
  Processing triggers for initramfs-tools (0.140ubuntu6) ...
  update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
  Processing triggers for libc-bin (2.33-0ubuntu7) ...
  Processing triggers for man-db (2.9.4-2) ...
  Processing triggers for dbus (1.12.20-2ubuntu1) ...
  Errors were encountered while processing:
   systemd

  I reverted to old version by manualing installing the hirsute's debs
  (from 21.04: libsystemd0_247.3-3ubuntu3.4_i386.deb
  systemd_247.3-3ubuntu3.4_amd64.deb libnss-
  systemd_247.3-3ubuntu3.4_amd64.deb libsystemd-
  dev_247.3-3ubuntu3.4_amd64.deb systemd-sysv_247.3-3ubuntu3.4_amd64.deb
  libpam-systemd_247.3-3ubuntu3.4_amd64.deb
  libudev1_247.3-3ubuntu3.4_amd64.deb udev_247.3-3ubuntu3.4_amd64.deb
  libsystemd0_247.3-3ubuntu3.4_amd64.deb libudev-
  dev_247.3-3ubuntu3.4_amd64.deb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938065/+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 1815045] Re: Failed unmounting /var when it is a separate filesystem

[André Burkhardt]

** Changed in: systemd (Ubuntu)
   Status: Invalid => New

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

Title:
  Failed unmounting /var when it is a separate filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  In a fresh install of Ubuntu Server 18.04.1 LTS with the /var-
  Filesystem on a separate partition (LVM), there are Errors on
  shutdown/reboot (Failed unmounting /var).

  1) The release
  Release: Ubuntu 18.04.1 LTS

  2) The version
  Version:apt-cache policy systemd
  systemd:  Installed: 237-3ubuntu10.12
Candidate: 237-3ubuntu10.12

  3) What you expected to happen
  Clean unmount of /var Filesystem without Failure

  4) What happened instead
  Console output on shutdown/reboot
  [...]
  [  OK  ] Stopped Flush Journal to Persistent Storage.
  [  OK  ] Stopped target Local File Systems.
   Unmounting /boot...
   Unmounting /var...
   Unmounting /run/user/1000...
  [FAILED] Failed unmounting /var.
  [  OK  ] Stopped File System Check on /dev/mapper/vg_system-lv_var.
  [  OK  ] Unmounted /run/user/1000
  [...]

  Extract from journalctl
  [...]
  Feb 07 13:13:31 x systemd[1]: Stopped Flush Journal to Persistent Storage.
  Feb 07 13:13:31 x systemd[1]: Stopped target Local File Systems.
  Feb 07 13:13:31 x systemd[1]: Unmounting /boot...
  Feb 07 13:13:31 x systemd[1]: Unmounting /var...
  Feb 07 13:13:31 x systemd[1]: Unmounting /run/user/1000...
  Feb 07 13:13:31 x umount[1775]: umount: /var: target is busy.
  Feb 07 13:13:31 x systemd[1]: var.mount: Mount process exited, 
code=exited status=32
  Feb 07 13:13:31 x systemd[1]: Failed unmounting /var.
  Feb 07 13:13:31 x systemd[1]: Stopped File System Check on 
/dev/mapper/vg_system-lv_var.
  Feb 07 13:13:31 x systemd[1]: Unmounted /run/user/1000.
  [...]

  Applying the changes described here:

  https://github.com/systemd/systemd/issues/867#issuecomment-250202183

  let the Error-Messages go away. But are there any side-effects?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815045/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"

[André Hänsel]

FWIW, I tried reproducing this artificially by running 200 Kubernetes
Pods on a freshly installed Focal and the issue did not occur.

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

Title:
  Many interfaces lead to "kernel receive buffer overrun"

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

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

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Diogo André Cardoso Pereira]

How do you guys modify the files ? Im new to linux so i dont have no idea what 
to do, i just install sudo apt get install hdajackretask,so what to do next?
Also i dont find the files mentioned anywhere, im probably making this all 
wrong XD

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"

[André Hänsel]

** Attachment added: "1912331-config-files.zip"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912331/+attachment/5466762/+files/1912331-config-files.zip

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

Title:
  Many interfaces lead to "kernel receive buffer overrun"

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Won't Fix
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

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

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"

[André Hänsel]

Where would I find those files? systemd-networkd is not something I have
consciously installed or configured, it just came with Ubuntu.

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

Title:
  Many interfaces lead to "kernel receive buffer overrun"

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Won't Fix
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

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

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"

[André Hänsel]

I don't completely understand it myself.

I have a Focal system with k3s installed and about 70 pods (about 150
containers) and about 70 veth devices.

In /lib/systemd/system/systemd-networkd.socket under "[Socket]" I have
set "ReceiveBuffer=128M".

Maybe that "128M" isn't enough but I can't add any more pods without
getting "Could not enumerate addresses: No buffer space available"
errors, so I *assumed* there's more to that patch than just the
ReceiveBuffer setting.

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

Title:
  Many interfaces lead to "kernel receive buffer overrun"

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Won't Fix
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

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

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+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 1914288] Re: Xorg freeze

[André Lucas Moisés Lacerda]

** Information type changed from Private Security to Private

** Information type changed from Private to Public Security

** Information type changed from Public Security to Public

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Freezes randomly during usage and always after recovering from suspend
  mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  2 16:51:10 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08ca]
 Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] 
[1028:08ca]
  InstallationDate: Installed on 2020-09-10 (144 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron 3583
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=7f3ab5d0-2b6b-4064-81ec-9a66d46303f4 ro quiet splash radeon.modeset=0 
amdgpu.dc=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2020
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0NN4D6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:br1.8:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0NN4D6:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1914288/+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 1914288] [NEW] Xorg freeze

[André Lucas Moisés Lacerda]

Public bug reported:

Freezes randomly during usage and always after recovering from suspend
mode.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  2 16:51:10 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08ca]
   Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] 
[1028:08ca]
InstallationDate: Installed on 2020-09-10 (144 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Inspiron 3583
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=7f3ab5d0-2b6b-4064-81ec-9a66d46303f4 ro quiet splash radeon.modeset=0 
amdgpu.dc=0 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2020
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 0NN4D6
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:br1.8:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0NN4D6:rvrA02:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3583
dmi.product.sku: 08CA
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
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 false-gpu-hang focal freeze ubuntu

** Information type changed from Public to Private Security

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Freezes randomly during usage and always after recovering from suspend
  mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  2 16:51:10 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08ca]
 Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] 
[1028:08ca]
  InstallationDate: Installed on 2020-09-10 (144 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron 3583
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=7f3ab5d0-2b6b-4064-81ec-9a66d46303f4 ro quiet splash radeon.modeset=0 
amdgpu.dc=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2020
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0NN4D6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:br1.8:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0NN4D6:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1912331] [NEW] Many interfaces lead to "kernel receive buffer overrun"

[André Hänsel]

Public bug reported:

This is about a systemd-networkd bug, described here:

https://github.com/systemd/systemd/issues/14417

There's a patch available:

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

Can this be backported to Focal?

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

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

Title:
  Many interfaces lead to "kernel receive buffer overrun"

Status in systemd package in Ubuntu:
  New

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

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

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912331/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Diogo André Cardoso Pereira]

I really would like to use pop os for my main os and i cant because of
this bug :( There is any update so far on this ? or any temporary fix
that anyone can help?

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1890854] Re: Conflict with python2

[André]

Seems like it's fixed with 4.20200804ubuntu3

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

Title:
  Conflict with python2

Status in dh-python package in Ubuntu:
  Confirmed
Status in dh-python package in Debian:
  Unknown

Bug description:
  During a package update in groovy I got this error message:

  Unpacking dh-python (4.20200804ubuntu1) over (4.20200315ubuntu1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb (--unpack):
   trying to overwrite '/usr/share/debhelper/autoscripts/postinst-pycompile', 
which is also in package python2 2.7.17-2ubuntu4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  +++

  Errors were encountered while processing:
   /tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1890854/+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 1862500] Re: Desktop icons are placed off-screen when using multiple monitors

[André Hoek]

Resolution Settings

** Attachment added: "MonitorSettings.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+attachment/5326639/+files/MonitorSettings.png

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

Title:
  Desktop icons are placed off-screen when using multiple monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  I have 2 monitors connected in "Join Display Mode".
  Monitor 1 (secondary) 1366x798, Landscape, 100%
  Monitor 2 (primary) 1920x1080, Landscape, 100%

  I can see files on the Desktop inside the File Browser, but on the
  Desktop icons are either not visible or limited text from one of the
  icons can be seen in the top left corner of the secondary monitor.

  Screenshots attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  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: Sun Feb  9 10:16:18 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] 
[1002:677b] (prog-if 00 [VGA controller])
 Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO 
[Radeon HD 7450] [1642:3a76]
  InstallationDate: Installed on 2019-12-20 (50 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 3212AP3
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT63AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  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:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3212AP3
  dmi.product.sku: LENOVO_MT_3212
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+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 1862500] Re: Desktop icons are placed off-screen when using multiple monitors

[André Hoek]

Image showing the perceived location of missing icons on Desktop

** Attachment added: "FullDesktop.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+attachment/5326638/+files/FullDesktop.jpg

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

Title:
  Desktop icons are placed off-screen when using multiple monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  I have 2 monitors connected in "Join Display Mode".
  Monitor 1 (secondary) 1366x798, Landscape, 100%
  Monitor 2 (primary) 1920x1080, Landscape, 100%

  I can see files on the Desktop inside the File Browser, but on the
  Desktop icons are either not visible or limited text from one of the
  icons can be seen in the top left corner of the secondary monitor.

  Screenshots attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  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: Sun Feb  9 10:16:18 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] 
[1002:677b] (prog-if 00 [VGA controller])
 Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO 
[Radeon HD 7450] [1642:3a76]
  InstallationDate: Installed on 2019-12-20 (50 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 3212AP3
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT63AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  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:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3212AP3
  dmi.product.sku: LENOVO_MT_3212
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+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 1862500] [NEW] Desktop icons are placed off-screen when using multiple monitors

[André Hoek]

Public bug reported:

I have 2 monitors connected in "Join Display Mode".
Monitor 1 (secondary) 1366x798, Landscape, 100%
Monitor 2 (primary) 1920x1080, Landscape, 100%

I can see files on the Desktop inside the File Browser, but on the
Desktop icons are either not visible or limited text from one of the
icons can be seen in the top left corner of the secondary monitor.

Screenshots attached.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
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: Sun Feb  9 10:16:18 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[17aa:3083]
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] 
(prog-if 00 [VGA controller])
   Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO 
[Radeon HD 7450] [1642:3a76]
InstallationDate: Installed on 2019-12-20 (50 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 3212AP3
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 9SKT63AUS
dmi.board.name: MAHOBAY
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
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:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: 3212AP3
dmi.product.sku: LENOVO_MT_3212
dmi.product.version: ThinkCentre M92p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.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 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/1862500

Title:
  Desktop icons are placed off-screen when using multiple monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  I have 2 monitors connected in "Join Display Mode".
  Monitor 1 (secondary) 1366x798, Landscape, 100%
  Monitor 2 (primary) 1920x1080, Landscape, 100%

  I can see files on the Desktop inside the File Browser, but on the
  Desktop icons are either not visible or limited text from one of the
  icons can be seen in the top left corner of the secondary monitor.

  Screenshots attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  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: Sun Feb  9 10:16:18 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] 
[1002:677b] (prog-if 00 [VGA controller])
 Subsystem: Bitland(ShenZhen) Information 

[Touch-packages] [Bug 1815045] [NEW] Failed unmounting /var when it is a separate filesystem

[André Burkhardt]

Public bug reported:

In a fresh install of Ubuntu Server 18.04.1 LTS with the /var-Filesystem
on a separate partition (LVM), there are Errors on shutdown/reboot
(Failed unmounting /var).

1) The release
Release: Ubuntu 18.04.1 LTS

2) The version
Version:apt-cache policy systemd
systemd:  Installed: 237-3ubuntu10.12
  Candidate: 237-3ubuntu10.12

3) What you expected to happen
Clean unmount of /var Filesystem without Failure

4) What happened instead
Console output on shutdown/reboot
[...]
[  OK  ] Stopped Flush Journal to Persistent Storage.
[  OK  ] Stopped target Local File Systems.
 Unmounting /boot...
 Unmounting /var...
 Unmounting /run/user/1000...
[FAILED] Failed unmounting /var.
[  OK  ] Stopped File System Check on /dev/mapper/vg_system-lv_var.
[  OK  ] Unmounted /run/user/1000
[...]

Extract from journalctl
[...]
Feb 07 13:13:31 x systemd[1]: Stopped Flush Journal to Persistent Storage.
Feb 07 13:13:31 x systemd[1]: Stopped target Local File Systems.
Feb 07 13:13:31 x systemd[1]: Unmounting /boot...
Feb 07 13:13:31 x systemd[1]: Unmounting /var...
Feb 07 13:13:31 x systemd[1]: Unmounting /run/user/1000...
Feb 07 13:13:31 x umount[1775]: umount: /var: target is busy.
Feb 07 13:13:31 x systemd[1]: var.mount: Mount process exited, code=exited 
status=32
Feb 07 13:13:31 x systemd[1]: Failed unmounting /var.
Feb 07 13:13:31 x systemd[1]: Stopped File System Check on 
/dev/mapper/vg_system-lv_var.
Feb 07 13:13:31 x systemd[1]: Unmounted /run/user/1000.
[...]

Applying the changes described here:

https://github.com/systemd/systemd/issues/867#issuecomment-250202183

let the Error-Messages go away. But are there any side-effects?

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

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

Title:
  Failed unmounting /var when it is a separate filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  In a fresh install of Ubuntu Server 18.04.1 LTS with the /var-
  Filesystem on a separate partition (LVM), there are Errors on
  shutdown/reboot (Failed unmounting /var).

  1) The release
  Release: Ubuntu 18.04.1 LTS

  2) The version
  Version:apt-cache policy systemd
  systemd:  Installed: 237-3ubuntu10.12
Candidate: 237-3ubuntu10.12

  3) What you expected to happen
  Clean unmount of /var Filesystem without Failure

  4) What happened instead
  Console output on shutdown/reboot
  [...]
  [  OK  ] Stopped Flush Journal to Persistent Storage.
  [  OK  ] Stopped target Local File Systems.
   Unmounting /boot...
   Unmounting /var...
   Unmounting /run/user/1000...
  [FAILED] Failed unmounting /var.
  [  OK  ] Stopped File System Check on /dev/mapper/vg_system-lv_var.
  [  OK  ] Unmounted /run/user/1000
  [...]

  Extract from journalctl
  [...]
  Feb 07 13:13:31 x systemd[1]: Stopped Flush Journal to Persistent Storage.
  Feb 07 13:13:31 x systemd[1]: Stopped target Local File Systems.
  Feb 07 13:13:31 x systemd[1]: Unmounting /boot...
  Feb 07 13:13:31 x systemd[1]: Unmounting /var...
  Feb 07 13:13:31 x systemd[1]: Unmounting /run/user/1000...
  Feb 07 13:13:31 x umount[1775]: umount: /var: target is busy.
  Feb 07 13:13:31 x systemd[1]: var.mount: Mount process exited, 
code=exited status=32
  Feb 07 13:13:31 x systemd[1]: Failed unmounting /var.
  Feb 07 13:13:31 x systemd[1]: Stopped File System Check on 
/dev/mapper/vg_system-lv_var.
  Feb 07 13:13:31 x systemd[1]: Unmounted /run/user/1000.
  [...]

  Applying the changes described here:

  https://github.com/systemd/systemd/issues/867#issuecomment-250202183

  let the Error-Messages go away. But are there any side-effects?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815045/+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 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state

[André Jutisz]

I am still affected by this bug (Bionic server installation with the latest 
updates - 24.01.2019)
Attached: unattended-upgrades.log

** Attachment added: "unattended-upgrades.log"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778219/+attachment/5232300/+files/unattended-upgrades.log

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in init-system-helpers package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in init-system-helpers source package in Bionic:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades hangs and gets killed when installing upgrades
  that stat/stop services on shutdown, leaving the system in a broken
  state

  [Test Case]

   * Install an updated bionic system:
     $ lxc launch ubuntu:18.04 uu-shutdown-test
     # apt update
     ...

   * When testing the fixed version, install upgrade u-u at this point checking 
that u-u.service is set up before and is wanted by shutdown.target:
  # systemd-analyze dot | grep unatt
   "unattended-upgrades.service"->"-.mount" [color="green"];
   "unattended-upgrades.service"->"system.slice" [color="green"];
   "unattended-upgrades.service"->"network.target" [color="green"];
   "unattended-upgrades.service"->"systemd-journald.socket" [color="green"];
   "unattended-upgrades.service"->"local-fs.target" [color="green"];
   "unattended-upgrades.service"->"-.mount" [color="black"];
   "unattended-upgrades.service"->"system.slice" [color="black"];
   "shutdown.target"->"unattended-upgrades.service" [color="green"];
   "shutdown.target"->"unattended-upgrades.service" [color="grey66"];
     Color legend: black = Requires
   dark blue = Requisite
   dark grey = Wants
   red   = Conflicts
   green = After

   * Configure u-u to run on shutdown and install -updates:
     # echo 'Unattended-Upgrade::InstallOnShutdown "true";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
     # echo 'Unattended-Upgrade::Allowed-Origins:: 
"${distro_id}:${distro_codename}-updates";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too

   * Downgrade snapd:
     # apt install snapd=2.32.5+18.04
   * Dowload packages for u-u:
     # unattended-upgrade --download-only
   * Reboot using logind to let inhibitors hold up shutdown:
     # dbus-send --system --print-reply --dest=org.freedesktop.login1 
/org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false

   * With not fixed u-u observe the upgrade process being stuck:
    # pstree| grep unatt
  
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
  `-{unattended-upgr}

   * With fixed u-u observe snapd update taking place and system
  rebooting after a few seconds with all updates installed

   * Since this fix is partially reverting the fix for LP: #1654600
  please test LP: #1654600 as well to avoid regressions.

  [Regression Potential]

   * As part of the fix manual changes were made to postinst to properly 
transition from coupling u-u.service with multi-user.target to coupling it with 
shutdown.target again which can make u-u started during normal boot when there 
is a bug in the implementation.
  on-testing the SRU.
   * Due to relationship changes between u-u.service, other services and 
targets u-u may fail to run on shutdown in case of an unexpected regression.
  * There is a rarely occurring new crash caused by the (second) fix tracked in 
LP: #1806487.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries 

[Touch-packages] [Bug 1773844] [NEW] [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all

[Fernando André]

Public bug reported:

This issue happens on xubuntu 17.10 and also ubuntu.
It may be related to this bug 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/802998
802998 , but since I'm using a new version I reported it again.

1)
lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

2)
apt-cache policy alsa-base
alsa-base:
  Instalado: 1.0.25+dfsg-0ubuntu5
  Candidato: 1.0.25+dfsg-0ubuntu5
  Tabela de versão:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://br.archive.ubuntu.com/ubuntu artful/main i386 Packages
100 /var/lib/dpkg/status

5)
uname -a
Linux patricia-NH4CU03 4.16.12 #1 SMP Sun May 27 16:56:57 -03 2018 x86_64 
x86_64 x86_64 GNU/Linux
Also happens on normal kernel version of 17.10 xubuntu and ubuntu
3)
I would expect it to play sound.

4)
It doesn't play any sound.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.16.12 x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andref 1587 F pulseaudio
CurrentDesktop: XFCE
Date: Mon May 28 16:05:23 2018
InstallationDate: Installed on 2018-01-25 (123 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Áudio interno - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andref 1587 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/16/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.00W
dmi.board.name: NH4CU03
dmi.board.vendor: Digiboard
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: Digibras
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00W:bd04/16/2013:svnDigibras:pnNH4CU03:pvr1.0:rvnDigiboard:rnNH4CU03:rvr1.0:cvnDigibras:ct10:cvr1.0:
dmi.product.name: NH4CU03
dmi.product.version: 1.0
dmi.sys.vendor: Digibras
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-26T21:36:27.395468

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


** Tags: amd64 apport-bug artful

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

Title:
  [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This issue happens on xubuntu 17.10 and also ubuntu.
  It may be related to this bug 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/802998
  802998 , but since I'm using a new version I reported it again.

  1)
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2)
  apt-cache policy alsa-base
  alsa-base:
Instalado: 1.0.25+dfsg-0ubuntu5
Candidato: 1.0.25+dfsg-0ubuntu5
Tabela de versão:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://br.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  5)
  uname -a
  Linux patricia-NH4CU03 4.16.12 #1 SMP Sun May 27 16:56:57 -03 2018 x86_64 
x86_64 x86_64 GNU/Linux
  Also happens on normal kernel version of 17.10 xubuntu and ubuntu
  3)
  I would expect it to play sound.

  4)
  It doesn't play any sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.16.12 x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andref 1587 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May 28 16:05:23 2018
  InstallationDate: Installed on 2018-01-25 (123 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andref 1587 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Touch-packages] [Bug 1438014] Re: gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts

[André Cruz]

Altered keyboard shortcuts for opening new terminals and copy/paste.

[11742.029806] gnome-terminal-[4755]: segfault at 7001e ip 7f82140be77e 
sp 7ffce1ff6fe8 error 4 in libgobject-2.0.so.0.5400.1[7f8214089000+52000]
[11785.274354] gnome-terminal-[27857]: segfault at 7001e ip 
7fdbbe5da77e sp 7ffee0b8a418 error 4 in 
libgobject-2.0.so.0.5400.1[7fdbbe5a5000+52000]
[12226.667034] gnome-terminal-[27916]: segfault at 7001e ip 
7fe13759c77e sp 7ffd2f2b76b8 error 4 in 
libgobject-2.0.so.0.5400.1[7fe137567000+52000]

17.10 (Artful Aardvark)

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

Title:
  gnome-terminal-server and mate-terminal crash when setting keyboard
  shortcuts

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I put my laptop to sleep for an hour or so; when I restored it, gnome-
  terminal had crashed. It did not do this the previous time I suspended
  my laptop today, so I doubt that's immediately related.

  This crash can be reproduced by setting a shortcut in preferences.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-terminal 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 30 00:19:43 2015
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2014-02-03 (419 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f98e2afbf1f :
testb  $0x4,0x16(%rax)
   PC (0x7f98e2afbf1f) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0xbcae) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel (widget=0x2580c30) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382
   window_group_cleanup_grabs (group=, 
window=window@entry=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110
   gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169
   gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134
  Title: gnome-terminal-server crashed with SIGSEGV in 
g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare 
sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1438014/+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 1759796] Re: Ubuntu images fail to build due to broken dh-python package

[Martin André]

@dino99: Thanks, good to know the package has been fixed upstream.

This has not yet been propagated to ubuntu-cloud-archive, though.

http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/xenial-
updates/queens/main/binary-amd64/Packages

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

Title:
  Ubuntu images fail to build due to broken dh-python package

Status in kolla:
  New
Status in dh-python package in Ubuntu:
  New

Bug description:
  Some ubuntu images fails to build and block the gate.

  2018-03-28 15:07:13.498244 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-controller' to succeed!
  2018-03-28 15:07:13.498650 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-northd' to succeed!
  2018-03-28 15:07:13.498957 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'bifrost-base' to succeed!
  2018-03-28 15:07:13.499241 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovsdpdk' to succeed!
  2018-03-28 15:07:13.499559 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-sb-db-server' to succeed!
  2018-03-28 15:07:13.499867 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-nb-db-server' to succeed!

  http://logs.openstack.org/33/555733/1/check/kolla-build-ubuntu-
  source/72f9085/job-output.txt.gz#_2018-03-28_15_07_13_498244

  Looking more closely, it appears they fail to install lsb-release that
  depends on python3. Going up the dependency chain, the issue seems to
  be in dh-python that added a dependency on python3-distuils. However
  python3-distuils doesn't exist and should probably be
  python3-distutils.

  ()[root@f8bc5d1d504e bifrost-5.0.1.dev43]# apt-cache show dh-python
  Package: dh-python
  Priority: optional
  Section: python
  Installed-Size: 429
  Maintainer: Piotr Ożarowski 
  Architecture: all
  Version: 3.20180325ubuntu1~cloud0
  Replaces: python3 (<< 3.3.2-4~)
  Suggests: libdpkg-perl, dpkg-dev
  Depends: python3:any (>= 3.3.2-2~), python3-distuils
  Breaks: python3 (<< 3.3.2-4~)
  Supported: 60m
  Filename: pool/main/d/dh-python/dh-python_3.20180325ubuntu1~cloud0_all.deb
  Size: 89382
  SHA256: 5d31a348f141d7ca366eeb21b58633bed96a0b27417ce8759e1cb785cb1db8bc
  SHA1: a817acac0042ab6e22dd686376717a20e449ae03
  MD5sum: d89b5e505bbb93b57efe4bfb85fc353d
  Description: Debian helper tools for packaging Python libraries and 
applications
  Description-md5: b21cd6f99d6093fdc7e0ba30c8dd949f
  Multi-Arch: foreign
  Original-Maintainer: Piotr Ożarowski 

To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla/+bug/1759796/+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 1714301] Re: systemd-networkd hangs my boot (wireless)

[André]

what does 'unconditional enablement' mean? just enable the 'systemd-
networkd' service?

bug #1697730 could be a duplicate of this (or the other way around)

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

Title:
  systemd-networkd hangs my boot (wireless)

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  Since that systemd-networkd is enabled, my laptop doesn't boot (hangs)
  until I plug in an ethernet cable.

  Here is the journal from this boot, note the hang up until I connect my cable 
at 17:51:35:
  août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  août 31 17:50:08 tidus systemd[1]: emergency-tmp.service: Cannot add 
dependency job, ignoring: Unit emergency-tmp.service is not loaded properly: 
Inva
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3836]: no servers can be used, exiting
  août 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Start request repeated too quickly.
  août 31 17:50:08 tidus systemd[1]: Failed to start 
systemd-resolved-update-resolvconf.service.
  août 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Failed with result 
'start-limit-hit'.
  août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:3 'up' [virbr0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/Ne
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0]: start 
running ordered scripts...
  août 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6148] 
dispatcher: (6) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  août 31 17:50:08 tidus ntpdate[3908]: no servers can be used, exiting
  août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/N
  août 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6612] 
dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 

[Touch-packages] [Bug 1441296] Re: Nautilus invisible focused item when selecting files with Ctrl and arrow keys

[André Xuereb]

The behaviour on 17.04 is still unchanged. Any clues for how to fix, or
at least what to look for?

** Changed in: ubuntu-themes
   Status: Incomplete => Confirmed

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

Title:
  Nautilus invisible focused item when selecting files with Ctrl and
  arrow keys

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Expired

Bug description:
  After upgrading to 15.04 beta2 I noticed that selecting files with
  Ctrl and the arrow keys in Nautilus became more difficult since the
  active item had no decorations. I'm sure before there was some sort of
  dashed line around the active item's name, so this may be a
  regression.

  I have searched for any other bug report on this, or any other person
  complaining about it, without success. I tried using the guest account
  to confirm it wasn't a previous configuration on my regular account,
  and the issue is also present. Maybe it is uncommon for people to
  select items in nautilus with the keyboard arrows?

  I fixed it on my system for Ambiance by adding a dashed line
  decoration to

  /usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css

  NautilusWindow * {
  -GtkPaned-handle-size: 1;
  outline-color: @selected_bg_color;
  outline-style: dashed;
  outline-width: 1px;
  outline-radius: 4px;
  outline-offset: -1px;
  }

  This may need to go in other selector properties, but it worked like
  this and I couldn't make it to work on any other selector.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1441296/+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 1441296] Re: Nautilus invisible focused item when selecting files with Ctrl and arrow keys

[André Xuereb]

I can confirm this bug in Ubuntu 17.04.

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

Title:
  Nautilus invisible focused item when selecting files with Ctrl and
  arrow keys

Status in Ubuntu theme:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 15.04 beta2 I noticed that selecting files with
  Ctrl and the arrow keys in Nautilus became more difficult since the
  active item had no decorations. I'm sure before there was some sort of
  dashed line around the active item's name, so this may be a
  regression.

  I have searched for any other bug report on this, or any other person
  complaining about it, without success. I tried using the guest account
  to confirm it wasn't a previous configuration on my regular account,
  and the issue is also present. Maybe it is uncommon for people to
  select items in nautilus with the keyboard arrows?

  I fixed it on my system for Ambiance by adding a dashed line
  decoration to

  /usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css

  NautilusWindow * {
  -GtkPaned-handle-size: 1;
  outline-color: @selected_bg_color;
  outline-style: dashed;
  outline-width: 1px;
  outline-radius: 4px;
  outline-offset: -1px;
  }

  This may need to go in other selector properties, but it worked like
  this and I couldn't make it to work on any other selector.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1441296/+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 1595695] Re: Bluetooth indicator disappears every time bluetooth is being turned off

[André Xuereb]

Also affects 17.04 on Thinkpad Carbon X1 (2014 model).

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

Title:
  Bluetooth indicator disappears every time bluetooth is being turned
  off

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04, every time I turn off bluetooth, the indicator icon 
disappears from the top panel.
  Each time I have to re-enable it by system setting or via dash.

  I expect it to behave in a same way as network indicator instead of
  disappearing.

  Here is the link with some info which could be helpful 
  https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1595695/+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 1668485] Re: Xorg intel blank screen

[André Claudino]

** Also affects: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Xorg intel blank screen

Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have an Hybrid graphics card, my lspci output for then is:

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
  02:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)

  Once installed nvidia drivre, things work fine (instead they don't
  with noveau). But my problem is using intel driver. This is parte of
  my xorg.conf for nvidia (complete file is attached).

  Section "ServerLayout"
  Identifier "layout"
  Screen 0 "nvidia"
  Inactive "intel"
  EndSection

  
  I have installed xserver-xorg-video-intel and just change xorg.conf

  
  Section "ServerLayout"
  Identifier "layout"
  Screen 0 "intel"
  Inactive "nvidia"
  EndSection

  
  this way, when restarting, I get frozen blank screen while booting, and can't 
do anything other than pressing the power button and and reboot.

  So, I have to start in recovery mode, only way I can work in terminal,
  and change xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 28 00:33:16 2017
  InstallationDate: Installed on 2017-02-15 (12 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170125.3)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1668485/+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 1668485] [NEW] Xorg intel blank screen

[André Claudino]

Public bug reported:

I have an Hybrid graphics card, my lspci output for then is:

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
02:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)

Once installed nvidia drivre, things work fine (instead they don't with
noveau). But my problem is using intel driver. This is parte of my
xorg.conf for nvidia (complete file is attached).

Section "ServerLayout"
Identifier "layout"
Screen 0 "nvidia"
Inactive "intel"
EndSection


I have installed xserver-xorg-video-intel and just change xorg.conf


Section "ServerLayout"
Identifier "layout"
Screen 0 "intel"
Inactive "nvidia"
EndSection


this way, when restarting, I get frozen blank screen while booting, and can't 
do anything other than pressing the power button and and reboot.

So, I have to start in recovery mode, only way I can work in terminal,
and change xorg.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Feb 28 00:33:16 2017
InstallationDate: Installed on 2017-02-15 (12 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170125.3)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

** Attachment added: "xorg.conf"
   https://bugs.launchpad.net/bugs/1668485/+attachment/4827989/+files/xorg.conf

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

Title:
  Xorg intel blank screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I have an Hybrid graphics card, my lspci output for then is:

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
  02:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)

  Once installed nvidia drivre, things work fine (instead they don't
  with noveau). But my problem is using intel driver. This is parte of
  my xorg.conf for nvidia (complete file is attached).

  Section "ServerLayout"
  Identifier "layout"
  Screen 0 "nvidia"
  Inactive "intel"
  EndSection

  
  I have installed xserver-xorg-video-intel and just change xorg.conf

  
  Section "ServerLayout"
  Identifier "layout"
  Screen 0 "intel"
  Inactive "nvidia"
  EndSection

  
  this way, when restarting, I get frozen blank screen while booting, and can't 
do anything other than pressing the power button and and reboot.

  So, I have to start in recovery mode, only way I can work in terminal,
  and change xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 28 00:33:16 2017
  InstallationDate: Installed on 2017-02-15 (12 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170125.3)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1668485/+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 1667972] [NEW] package udev 231-9ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[André]

Public bug reported:

The issue ocours in a system upgrade, it's al I can say right now,
sorry.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: udev 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Sat Feb 25 17:27:33 2017
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
MachineType: Dell Inc. Vostro 3500
ProcKernelCmdLine: 
file=/cdrom/multiboot/lubuntu-16.10-desktop-amd64/preseed/lubuntu.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/lubuntu-16.10-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/lubuntu-16.10-desktop-amd64/casper/ 
initrd=/multiboot/lubuntu-16.10-desktop-amd64/casper/initrd.lz quiet splash --- 
locale=pt_BR keyboard-configuration/layoutcode?=br 
keyboard-configuration/modelcode?=abnt2
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: systemd
Title: package udev 231-9ubuntu3 failed to install/upgrade: sub-processo script 
post-installation instalado retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 056TK2
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3500:pvrA12:rvnDellInc.:rn056TK2:rvrA12:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Vostro 3500
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.

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

Title:
  package udev 231-9ubuntu3 failed to install/upgrade: sub-processo
  script post-installation instalado retornou estado de saída de erro 1

Status in systemd package in Ubuntu:
  New

Bug description:
  The issue ocours in a system upgrade, it's al I can say right now,
  sorry.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: udev 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Sat Feb 25 17:27:33 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  MachineType: Dell Inc. Vostro 3500
  ProcKernelCmdLine: 
file=/cdrom/multiboot/lubuntu-16.10-desktop-amd64/preseed/lubuntu.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/lubuntu-16.10-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/lubuntu-16.10-desktop-amd64/casper/ 
initrd=/multiboot/lubuntu-16.10-desktop-amd64/casper/initrd.lz quiet splash --- 
locale=pt_BR keyboard-configuration/layoutcode?=br 
keyboard-configuration/modelcode?=abnt2
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: systemd
  Title: package udev 231-9ubuntu3 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 056TK2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3500:pvrA12:rvnDellInc.:rn056TK2:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Vostro 3500
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1667972/+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 1667971] [NEW] package initramfs-tools 0.125ubuntu6.3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[André]

Public bug reported:

The issue ocours in a system upgrade, it's al I can say right now,
sorry.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: initramfs-tools 0.125ubuntu6.3
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Thu Feb 23 10:50:41 2017
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.125ubuntu6.3 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package initramfs-tools 0.125ubuntu6.3 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The issue ocours in a system upgrade, it's al I can say right now,
  sorry.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: initramfs-tools 0.125ubuntu6.3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Feb 23 10:50:41 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu6.3 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1667971/+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 1667973] [NEW] package udev 231-9ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[André]

Public bug reported:

The issue ocours in a system upgrade, it's al I can say right now,
sorry.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: udev 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Sat Feb 25 17:27:33 2017
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
MachineType: Dell Inc. Vostro 3500
ProcKernelCmdLine: 
file=/cdrom/multiboot/lubuntu-16.10-desktop-amd64/preseed/lubuntu.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/lubuntu-16.10-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/lubuntu-16.10-desktop-amd64/casper/ 
initrd=/multiboot/lubuntu-16.10-desktop-amd64/casper/initrd.lz quiet splash --- 
locale=pt_BR keyboard-configuration/layoutcode?=br 
keyboard-configuration/modelcode?=abnt2
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: systemd
Title: package udev 231-9ubuntu3 failed to install/upgrade: sub-processo script 
post-installation instalado retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 056TK2
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3500:pvrA12:rvnDellInc.:rn056TK2:rvrA12:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Vostro 3500
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.

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

Title:
  package udev 231-9ubuntu3 failed to install/upgrade: sub-processo
  script post-installation instalado retornou estado de saída de erro 1

Status in systemd package in Ubuntu:
  New

Bug description:
  The issue ocours in a system upgrade, it's al I can say right now,
  sorry.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: udev 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Sat Feb 25 17:27:33 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  MachineType: Dell Inc. Vostro 3500
  ProcKernelCmdLine: 
file=/cdrom/multiboot/lubuntu-16.10-desktop-amd64/preseed/lubuntu.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/lubuntu-16.10-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/lubuntu-16.10-desktop-amd64/casper/ 
initrd=/multiboot/lubuntu-16.10-desktop-amd64/casper/initrd.lz quiet splash --- 
locale=pt_BR keyboard-configuration/layoutcode?=br 
keyboard-configuration/modelcode?=abnt2
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: systemd
  Title: package udev 231-9ubuntu3 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 056TK2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3500:pvrA12:rvnDellInc.:rn056TK2:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Vostro 3500
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1667973/+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 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[André]

version 1.4.4-1ubuntu2 (from pre-release and from Barry's ppa) is not
working correctly for me

Can only ping any host by ip and never by hostname (google.com /
sapo.pt)


** Attachment added: "Selection_00553.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647031/+attachment/4821011/+files/Selection_00553.png

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+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 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[André]

output of

$ systemd-resolve --status

** Attachment added: "Selection_00554.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647031/+attachment/4821012/+files/Selection_00554.png

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+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 1607169] Re: Youtube Videos in Video Scope are not working

[André Fettouhi]

Yes, if you log out of youtube and try again then the preview shows up
and can tap it and the browser opens up.


Den 31-01-2017 kl. 13:11 skrev Olivier Tilloy:
> Looks like an HTTP request issued to youtube to get the subscribe id for a 
> video times out.
> I’m not familiar with that code, just had a quick look at it. This is the 
> authenticated code path. When not logged in to youtube, a different code path 
> is used. Can you try logging out from the scope, and see if that improves 
> things?
>

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

Title:
  Youtube Videos in Video Scope are not working

Status in YouTube Scope:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  I have a Meizu MX4 running the OTA-12 update as of this morning and
  since OTA-9 I think clicking on a youtube in the video, music or
  youtube scope doesn't do anything. Normally one would get a preview of
  the youtube video along with a discription below and then you could
  click the video again and the web browser would start up and play the
  video. This still works for videos on Vimeo but not on Youtube. This
  has been broken for months now. It also happens as mention in the
  Music scope and Youtube scope. I was hopng that this would have been
  fixed with the OTA-12 update since this update focused on bugs and
  that you now could play videos directly from the Video scope. But
  sadly no... Has there been an API change with Youtube that caused this
  breakage maybe?

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scope-youtube/+bug/1607169/+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 1607169] Re: Youtube Videos in Video Scope are not working

[André Fettouhi]

Yes, I noticed those. Do they give a hint to what is causing this?

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

Title:
  Youtube Videos in Video Scope are not working

Status in YouTube Scope:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  I have a Meizu MX4 running the OTA-12 update as of this morning and
  since OTA-9 I think clicking on a youtube in the video, music or
  youtube scope doesn't do anything. Normally one would get a preview of
  the youtube video along with a discription below and then you could
  click the video again and the web browser would start up and play the
  video. This still works for videos on Vimeo but not on Youtube. This
  has been broken for months now. It also happens as mention in the
  Music scope and Youtube scope. I was hopng that this would have been
  fixed with the OTA-12 update since this update focused on bugs and
  that you now could play videos directly from the Video scope. But
  sadly no... Has there been an API change with Youtube that caused this
  breakage maybe?

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scope-youtube/+bug/1607169/+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 1607169] Re: Youtube Videos in Video Scope are not working

[André Fettouhi]

Here is the log you asked for after I tried tap a video under youtube in
the Video scope.

** Attachment added: "log"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1607169/+attachment/4811041/+files/scope-registry.log

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

Title:
  Youtube Videos in Video Scope are not working

Status in YouTube Scope:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  I have a Meizu MX4 running the OTA-12 update as of this morning and
  since OTA-9 I think clicking on a youtube in the video, music or
  youtube scope doesn't do anything. Normally one would get a preview of
  the youtube video along with a discription below and then you could
  click the video again and the web browser would start up and play the
  video. This still works for videos on Vimeo but not on Youtube. This
  has been broken for months now. It also happens as mention in the
  Music scope and Youtube scope. I was hopng that this would have been
  fixed with the OTA-12 update since this update focused on bugs and
  that you now could play videos directly from the Video scope. But
  sadly no... Has there been an API change with Youtube that caused this
  breakage maybe?

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scope-youtube/+bug/1607169/+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 1607169] Re: Youtube Videos in Video Scope are not working

[André Fettouhi]

It is the former. When in the Video scope tapping a video from Youtube
doesn't bring up a preview. I just get a empty screen and I can see the
progress bar below running for a few seconds and then it stops/gives up.
On the other hand if you tap a video from Vimeo then the preview shows
up fine and you tap the preview and the browser opens as expected.

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

Title:
  Youtube Videos in Video Scope are not working

Status in YouTube Scope:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  I have a Meizu MX4 running the OTA-12 update as of this morning and
  since OTA-9 I think clicking on a youtube in the video, music or
  youtube scope doesn't do anything. Normally one would get a preview of
  the youtube video along with a discription below and then you could
  click the video again and the web browser would start up and play the
  video. This still works for videos on Vimeo but not on Youtube. This
  has been broken for months now. It also happens as mention in the
  Music scope and Youtube scope. I was hopng that this would have been
  fixed with the OTA-12 update since this update focused on bugs and
  that you now could play videos directly from the Video scope. But
  sadly no... Has there been an API change with Youtube that caused this
  breakage maybe?

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scope-youtube/+bug/1607169/+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 1607169] Re: Youtube Videos in Video Scope are not working

[André Fettouhi]

What, I just tried on my Meizu MX4 and it doesn't for me still. I just
get a white screen when clicking the youtube video in the scope.

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

Title:
  Youtube Videos in Video Scope are not working

Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  I have a Meizu MX4 running the OTA-12 update as of this morning and
  since OTA-9 I think clicking on a youtube in the video, music or
  youtube scope doesn't do anything. Normally one would get a preview of
  the youtube video along with a discription below and then you could
  click the video again and the web browser would start up and play the
  video. This still works for videos on Vimeo but not on Youtube. This
  has been broken for months now. It also happens as mention in the
  Music scope and Youtube scope. I was hopng that this would have been
  fixed with the OTA-12 update since this update focused on bugs and
  that you now could play videos directly from the Video scope. But
  sadly no... Has there been an API change with Youtube that caused this
  breakage maybe?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1607169/+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 1650763] Re: zesty 17.0.4.1 installation fails (2016-12-16 image)

[André Verwijs]

remove this bug, incorrect


** Attachment removed: "full installation logs.."
   
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1650763/+attachment/4792769/+files/debug.log

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

Title:
  zesty 17.0.4.1 installation fails (2016-12-16 image)

Status in gpgme1.0 package in Ubuntu:
  New

Bug description:
  zesty 17.0.4.1 installation fails (2016-12-16 image)  when i click "next" on 
installation
  (after initial copy of core packages), installer crashes... 

  
  -- 

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", line 145, in 
process_line
  return self.dbfilter.process_line()
File "/usr/lib/ubiquity/ubiquity/debconffilter.py", line 287, in 
process_line
  if not input_widgets[0].run(priority, question):
File "/usr/lib/ubiquity/plugins/ubi-console-setup.py", line 502, in run
  self.ui.set_keyboard(misc.utf8(self.db.get(question)))
File "/usr/lib/ubiquity/ubiquity/plugin.py", line 48, in wrapper
  return target(self, *args, **kwargs)
File "/usr/lib/ubiquity/plugins/ubi-console-setup.py", line 350, in 
set_keyboard
  ly = keyboard_names.layout_id('C', misc.utf8(layout))
File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 142, in layout_id
  return kn.layout_id(lang, value)
File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 90, in layout_id
  return self._layout_by_human[value]
  KeyError: 'English (US)'
  QSocketNotifier: Invalid socket 20 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 20 and type 'Exception', disabling...
  Exception in KDE frontend (invoking crash handler):
  Traceback (most recent call last):
File "/usr/lib/ubiquity/bin/ubiquity", line 655, in 
  main(oem_config)
File "/usr/lib/ubiquity/bin/ubiquity", line 641, in main
  install(query=options.query)
File "/usr/lib/ubiquity/bin/ubiquity", line 274, in install
  ret = wizard.run()
File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 512, in run
  if self.backup or self.dbfilter_handle_status():
File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 857, in 
dbfilter_handle_status
  QtWidgets.QMessageBox.Close)
  TypeError: warning(QWidget, str, str, buttons: 
Union[QMessageBox.StandardButtons, QMessageBox.StandardButton] = 
QMessageBox.Ok, defaultButton: QMessageBox.StandardButton = 
QMessageBox.NoButton): too many arguments

  QSocketNotifier: Invalid socket 20 and type 'Write', disabling...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1650763/+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 1650763] Re: zesty 17.0.4.1 installation fails (2016-12-16 image)

[André Verwijs]

** Attachment added: "full installation logs.."
   
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1650763/+attachment/4792769/+files/debug.log

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

Title:
  zesty 17.0.4.1 installation fails (2016-12-16 image)

Status in gpgme1.0 package in Ubuntu:
  New

Bug description:
  zesty 17.0.4.1 installation fails (2016-12-16 image)  when i click "next" on 
installation
  (after initial copy of core packages), installer crashes... 

  
  -- 

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", line 145, in 
process_line
  return self.dbfilter.process_line()
File "/usr/lib/ubiquity/ubiquity/debconffilter.py", line 287, in 
process_line
  if not input_widgets[0].run(priority, question):
File "/usr/lib/ubiquity/plugins/ubi-console-setup.py", line 502, in run
  self.ui.set_keyboard(misc.utf8(self.db.get(question)))
File "/usr/lib/ubiquity/ubiquity/plugin.py", line 48, in wrapper
  return target(self, *args, **kwargs)
File "/usr/lib/ubiquity/plugins/ubi-console-setup.py", line 350, in 
set_keyboard
  ly = keyboard_names.layout_id('C', misc.utf8(layout))
File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 142, in layout_id
  return kn.layout_id(lang, value)
File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 90, in layout_id
  return self._layout_by_human[value]
  KeyError: 'English (US)'
  QSocketNotifier: Invalid socket 20 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 20 and type 'Exception', disabling...
  Exception in KDE frontend (invoking crash handler):
  Traceback (most recent call last):
File "/usr/lib/ubiquity/bin/ubiquity", line 655, in 
  main(oem_config)
File "/usr/lib/ubiquity/bin/ubiquity", line 641, in main
  install(query=options.query)
File "/usr/lib/ubiquity/bin/ubiquity", line 274, in install
  ret = wizard.run()
File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 512, in run
  if self.backup or self.dbfilter_handle_status():
File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 857, in 
dbfilter_handle_status
  QtWidgets.QMessageBox.Close)
  TypeError: warning(QWidget, str, str, buttons: 
Union[QMessageBox.StandardButtons, QMessageBox.StandardButton] = 
QMessageBox.Ok, defaultButton: QMessageBox.StandardButton = 
QMessageBox.NoButton): too many arguments

  QSocketNotifier: Invalid socket 20 and type 'Write', disabling...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1650763/+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 1650763] [NEW] zesty 17.0.4.1 installation fails (2016-12-16 image)

[André Verwijs]

Public bug reported:

zesty 17.0.4.1 installation fails (2016-12-16 image)  when i click "next" on 
installation
(after initial copy of core packages), installer crashes... 


-- 

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", line 145, in 
process_line
return self.dbfilter.process_line()
  File "/usr/lib/ubiquity/ubiquity/debconffilter.py", line 287, in process_line
if not input_widgets[0].run(priority, question):
  File "/usr/lib/ubiquity/plugins/ubi-console-setup.py", line 502, in run
self.ui.set_keyboard(misc.utf8(self.db.get(question)))
  File "/usr/lib/ubiquity/ubiquity/plugin.py", line 48, in wrapper
return target(self, *args, **kwargs)
  File "/usr/lib/ubiquity/plugins/ubi-console-setup.py", line 350, in 
set_keyboard
ly = keyboard_names.layout_id('C', misc.utf8(layout))
  File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 142, in layout_id
return kn.layout_id(lang, value)
  File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 90, in layout_id
return self._layout_by_human[value]
KeyError: 'English (US)'
QSocketNotifier: Invalid socket 20 and type 'Read', disabling...
QSocketNotifier: Invalid socket 20 and type 'Exception', disabling...
Exception in KDE frontend (invoking crash handler):
Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 655, in 
main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 641, in main
install(query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 274, in install
ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 512, in run
if self.backup or self.dbfilter_handle_status():
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 857, in 
dbfilter_handle_status
QtWidgets.QMessageBox.Close)
TypeError: warning(QWidget, str, str, buttons: 
Union[QMessageBox.StandardButtons, QMessageBox.StandardButton] = 
QMessageBox.Ok, defaultButton: QMessageBox.StandardButton = 
QMessageBox.NoButton): too many arguments

QSocketNotifier: Invalid socket 20 and type 'Write', disabling...

** Affects: gpgme1.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "full installation logs.."
   
https://bugs.launchpad.net/bugs/1650763/+attachment/4792768/+files/installer.tar.gz

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

Title:
  zesty 17.0.4.1 installation fails (2016-12-16 image)

Status in gpgme1.0 package in Ubuntu:
  New

Bug description:
  zesty 17.0.4.1 installation fails (2016-12-16 image)  when i click "next" on 
installation
  (after initial copy of core packages), installer crashes... 

  
  -- 

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", line 145, in 
process_line
  return self.dbfilter.process_line()
File "/usr/lib/ubiquity/ubiquity/debconffilter.py", line 287, in 
process_line
  if not input_widgets[0].run(priority, question):
File "/usr/lib/ubiquity/plugins/ubi-console-setup.py", line 502, in run
  self.ui.set_keyboard(misc.utf8(self.db.get(question)))
File "/usr/lib/ubiquity/ubiquity/plugin.py", line 48, in wrapper
  return target(self, *args, **kwargs)
File "/usr/lib/ubiquity/plugins/ubi-console-setup.py", line 350, in 
set_keyboard
  ly = keyboard_names.layout_id('C', misc.utf8(layout))
File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 142, in layout_id
  return kn.layout_id(lang, value)
File "/usr/lib/ubiquity/ubiquity/keyboard_names.py", line 90, in layout_id
  return self._layout_by_human[value]
  KeyError: 'English (US)'
  QSocketNotifier: Invalid socket 20 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 20 and type 'Exception', disabling...
  Exception in KDE frontend (invoking crash handler):
  Traceback (most recent call last):
File "/usr/lib/ubiquity/bin/ubiquity", line 655, in 
  main(oem_config)
File "/usr/lib/ubiquity/bin/ubiquity", line 641, in main
  install(query=options.query)
File "/usr/lib/ubiquity/bin/ubiquity", line 274, in install
  ret = wizard.run()
File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 512, in run
  if self.backup or self.dbfilter_handle_status():
File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 857, in 
dbfilter_handle_status
  QtWidgets.QMessageBox.Close)
  TypeError: warning(QWidget, str, str, buttons: 
Union[QMessageBox.StandardButtons, QMessageBox.StandardButton] = 
QMessageBox.Ok, defaultButton: QMessageBox.StandardButton = 
QMessageBox.NoButton): too many arguments

  QSocketNotifier: Invalid socket 20 and type 'Write', disabling...

To manage notifications about this 

[Touch-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

[André Fettouhi]

I can confirm this behaviour. I have at home a wifi extender from tp
link (RE450) and I have given SSID on the extender the same names as on
my wifi router. Both in the case of 2,4 GHz and 5 GHz. Since OTA13 I
have constant disconnects with my Meizu MX4 running Ubuntu Touch.

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

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  current build number: 68
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-24 08:00:20
  version version: 68
  version ubuntu: 20150724
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  My ISP (Free in France) provides a hotspot service so that customers
  can use the connection of any other customer using a generic open Wifi
  connection (for reference http://www.free.fr/assistance/2303.html - in
  French)

  The SSID is called 'FreeWifi' on all the boxes but obviously APs are
  all different since it's customers' DSL routers.

  When I connect  to one of this access point, suspend the phone and
  resume it in another location where the SSID is available but from a
  different AP, the phone doesn't connect to this AP and the list of
  networks in the network-indicator doesn't refresh and still show the
  list of network from the previous location. I have to forget the
  network called 'FreeWifi' and reconnect in order to refresh the list
  and make it work.

  It's 100% reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+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 1626032] Re: Video and Music Scopes don't work with Youtube

[André Fettouhi]

But this is before the launch of the webbrowser. It is the detailed
preview of the video on youtube in the scopes that doesn't work anymore
for Youtube. It works fine for Vimeo videos.

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

Title:
  Video and Music Scopes don't work with Youtube

Status in Canonical System Image:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Under the Music and Video scope the is a section showing the most
  popular youtube videos right now. If one clicks one of these you get a
  larger preview of the video along with a description. Then you can
  click the preview and the browser opens up and the video starts. This
  hasn't worked since OTA-8 or OTA-9. Right now if you click one of
  these popular videos then you just get a white screen. There is a
  progress bar at the bottom for at few seconds so it seem to be loading
  something but like I said before you end up with a white screen. So
  one has to load the browser manually look for the video via different
  methods. There reason for this could be something has chenged on the
  youtube side so it doesn't support whatever Ubuntu Touch is trying to
  load with the preview of the video along with the discription.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626032/+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 1624211] [NEW] Network-manager randomly won't recognize wireless card after resuming from sleep or hibernation or when disabling/reenabling the card

[André Brait Carneiro Fabotti]

Public bug reported:

When resuming from sleep or coming out of hibernation and sometimes when
disabing and reenabling the wireless card (using Fn + the corresponding
key), network-manager will stop recognizing that there's a wireless card
in my laptop. The bluetooth applet and the card themselves still work. I
can still connect to the same network it was connected before putting it
to sleep/hibernate (because it's a known network and it does so
automatically) but network-manager won't display anything regarding me
having a wireless card, displaying the icon and information I would
expect if I were connected using an ethernet cable.

A workaround consists in restarting the network-manager service using
systemctl

sudo service network-manager restart

or

sudo systemctl restart network-manager.service


The system is a Dell Vostro 5470 running a fresh installation of Ubuntu 
16.04.1. If I recall correctly, this also happened with Ubuntu 14.04.4 too. 
BIOS version is A12 (the latest).

I've seen several people with problems like this one that were solved by
restarting network-manager (a quick Googling shows a handful of such
cases). This can be a huge turn off for a newcomer.

Some people also suggested creating a systemd service to restart the
network-manager service when resuming, etc. but since this bug also
occurs when disabling/reenabling the card, it might have another cause
that's unrelated to resuming from sleep.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.0-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep 16 01:26:01 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-09-10 (6 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.1.1 dev wlp8s0  proto static  metric 600 
 169.254.0.0/16 dev wlp8s0  scope link  metric 1000 
 192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.248  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

 wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
That's no moon! 1  2a59043a-02a4-4da0-ab5c-3c89c52bd15f  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
  ----  
   
 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  --   
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug network-manager wireless xenial

** Attachment added: "This is what happens."
   
https://bugs.launchpad.net/bugs/1624211/+attachment/4741747/+files/Espa%C3%A7o%20de%20Trabalho%201_005.png

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

Title:
  Network-manager randomly won't recognize wireless card after resuming
  from sleep or hibernation or when disabling/reenabling the card

Status in network-manager package in Ubuntu:
  New

Bug description:
  When resuming from sleep or coming out of hibernation and sometimes
  when disabing and reenabling the wireless card (using Fn + the
  corresponding key), network-manager will stop recognizing that there's
  a wireless card in my laptop. The bluetooth applet and the card
  themselves still work. I can still connect to the same network it was
  connected before putting it to sleep/hibernate (because it's a known
  network and it does so automatically) but network-manager won't
  display anything regarding me having a wireless card, displaying the
  icon and information I would expect if I were connected using an
  ethernet cable.

  A workaround consists in restarting the network-manager service using
  systemctl

  sudo service network-manager restart

  or

  sudo systemctl restart network-manager.service

  
  The system is a Dell Vostro 5470 running a fresh installation of 

[Touch-packages] [Bug 1607169] [NEW] Youtube Videos in Video Scope are not working

[André Fettouhi]

Public bug reported:

I have a Meizu MX4 running the OTA-12 update as of this morning and
since OTA-9 I think clicking on a youtube in the video, music or youtube
scope doesn't do anything. Normally one would get a preview of the
youtube video along with a discription below and then you could click
the video again and the web browser would start up and play the video.
This still works for videos on Vimeo but not on Youtube. This has been
broken for months now. It also happens as mention in the Music scope and
Youtube scope. I was hopng that this would have been fixed with the
OTA-12 update since this update focused on bugs and that you now could
play videos directly from the Video scope. But sadly no... Has there
been an API change with Youtube that caused this breakage maybe?

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: music scope video youtube

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

Title:
  Youtube Videos in Video Scope are not working

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  I have a Meizu MX4 running the OTA-12 update as of this morning and
  since OTA-9 I think clicking on a youtube in the video, music or
  youtube scope doesn't do anything. Normally one would get a preview of
  the youtube video along with a discription below and then you could
  click the video again and the web browser would start up and play the
  video. This still works for videos on Vimeo but not on Youtube. This
  has been broken for months now. It also happens as mention in the
  Music scope and Youtube scope. I was hopng that this would have been
  fixed with the OTA-12 update since this update focused on bugs and
  that you now could play videos directly from the Video scope. But
  sadly no... Has there been an API change with Youtube that caused this
  breakage maybe?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1607169/+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 1574892] Re: IDLE 3.5.1+ runtime error on Options -> Configure IDLE

[André S .]

I see the same error when using IDLE for _Python 2.7_ when trying to open 
Options -> Configure IDLE:
$ idle
Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1540, in __call__
return self.func(*args)
  File "/usr/lib/python2.7/idlelib/EditorWindow.py", line 543, in config_dialog
configDialog.ConfigDialog(self.top,'Settings')
  File "/usr/lib/python2.7/idlelib/configDialog.py", line 72, in __init__
self.LoadConfigs()
  File "/usr/lib/python2.7/idlelib/configDialog.py", line 1103, in LoadConfigs
self.LoadFontCfg()
  File "/usr/lib/python2.7/idlelib/configDialog.py", line 1005, in LoadFontCfg
self.SetFontSample()
  File "/usr/lib/python2.7/idlelib/configDialog.py", line 883, in SetFontSample
self.labelFontSample.config(font=newFont)
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1329, in configure
return self._configure('configure', cnf, kw)
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1320, in _configure
self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
TclError: expected integer but got ""
$ idle
Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1540, in __call__
return self.func(*args)
  File "/usr/lib/python2.7/idlelib/EditorWindow.py", line 543, in config_dialog
configDialog.ConfigDialog(self.top,'Settings')
  File "/usr/lib/python2.7/idlelib/configDialog.py", line 72, in __init__
self.LoadConfigs()
  File "/usr/lib/python2.7/idlelib/configDialog.py", line 1103, in LoadConfigs
self.LoadFontCfg()
  File "/usr/lib/python2.7/idlelib/configDialog.py", line 1005, in LoadFontCfg
self.SetFontSample()
  File "/usr/lib/python2.7/idlelib/configDialog.py", line 883, in SetFontSample
self.labelFontSample.config(font=newFont)
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1329, in configure
return self._configure('configure', cnf, kw)
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1320, in _configure
self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
TclError: expected integer but got ""

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

Title:
  IDLE 3.5.1+ runtime error on Options -> Configure IDLE

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Open IDLE for Python 3 on Ubuntu 16.04 (idle3 3.5.1-3) and click Options -> 
Configure IDLE.
  The menus of IDLE stop responding and the terminal shows the following 
message:

  Exception in Tkinter callback
  Traceback (most recent call last):
File "/usr/lib/python3.5/tkinter/__init__.py", line 1553, in __call__
  return self.func(*args)
File "/usr/lib/python3.5/idlelib/EditorWindow.py", line 516, in 
config_dialog
  configDialog.ConfigDialog(self.top,'Settings')
File "/usr/lib/python3.5/idlelib/configDialog.py", line 74, in __init__
  self.LoadConfigs()
File "/usr/lib/python3.5/idlelib/configDialog.py", line 1086, in LoadConfigs
  self.LoadFontCfg()
File "/usr/lib/python3.5/idlelib/configDialog.py", line 988, in LoadFontCfg
  self.SetFontSample()
File "/usr/lib/python3.5/idlelib/configDialog.py", line 866, in 
SetFontSample
  self.labelFontSample.config(font=newFont)
File "/usr/lib/python3.5/tkinter/__init__.py", line 1333, in configure
  return self._configure('configure', cnf, kw)
File "/usr/lib/python3.5/tkinter/__init__.py", line 1324, in _configure
  self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
  _tkinter.TclError: expected integer but got ""

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1574892/+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 1565589] [NEW] package libasn1-8-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to install/upgrade: package libasn1-8-heimdal:i386 is already installed and configured

[André Luiz de Ávila]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libasn1-8-heimdal:i386 1.6~rc2+dfsg-10ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Sun Apr  3 23:33:50 2016
DuplicateSignature: 
package:libasn1-8-heimdal:i386:1.6~rc2+dfsg-10ubuntu1:package 
libasn1-8-heimdal:i386 is already installed and configured
ErrorMessage: package libasn1-8-heimdal:i386 is already installed and configured
InstallationDate: Installed on 2016-03-29 (6 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu1
SourcePackage: heimdal
Title: package libasn1-8-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to 
install/upgrade: package libasn1-8-heimdal:i386 is already installed and 
configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed apport-package i386 wily

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

Title:
  package libasn1-8-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to
  install/upgrade: package libasn1-8-heimdal:i386 is already installed
  and configured

Status in heimdal package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libasn1-8-heimdal:i386 1.6~rc2+dfsg-10ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Sun Apr  3 23:33:50 2016
  DuplicateSignature: 
package:libasn1-8-heimdal:i386:1.6~rc2+dfsg-10ubuntu1:package 
libasn1-8-heimdal:i386 is already installed and configured
  ErrorMessage: package libasn1-8-heimdal:i386 is already installed and 
configured
  InstallationDate: Installed on 2016-03-29 (6 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: heimdal
  Title: package libasn1-8-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to 
install/upgrade: package libasn1-8-heimdal:i386 is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1565589/+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 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***

[Jean Christophe André]

I confirm the Python scopes are now, after having applied the pygobject
update, working on a Xenial 64-bit system and still working (= no
regression) on a 32-bit one. Thanks!

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

Title:
  scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3':
  free(): invalid next size (fast): 0x01ca17b0 ***

Status in Ubuntu Kylin:
  New
Status in libunity package in Ubuntu:
  Invalid
Status in pygobject package in Ubuntu:
  Fix Released

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/python3': free(): invalid next size 
(fast): 0x01ca17b0 ***
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Jan 27 10:41:54 2016
  Dependencies:
   
  ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
  InstallationDate: Installed on 2015-04-30 (271 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s 
info/calculator.scope
  Signal: 6
  SourcePackage: libunity
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd789926128 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ptr=, str=0x7fd7899261a0 "free(): invalid 
next size (fast)", action=1) at malloc.c:4965
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3834
   __GI___libc_free (mem=) at malloc.c:2950
   ?? () from 
/usr/lib/python3/dist-packages/gi/_gi.cpython-35m-x86_64-linux-gnu.so
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': 
free(): invalid next size (fast): 0x01ca17b0 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1538471/+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 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***

[Jean Christophe André]

After having installed 2 identical VM (PXE + preseed), with the only
difference being the architecture (32-bit vs 64-bit), I can now confirm
that the Python scopes are working on a 32-bit install and crashing on a
64-bit install, with exactly the same requests made on both sides
(calc:1+1, man:calc).

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

Title:
  scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3':
  free(): invalid next size (fast): 0x01ca17b0 ***

Status in Ubuntu Kylin:
  New
Status in libunity package in Ubuntu:
  Confirmed
Status in pygobject package in Ubuntu:
  New

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/python3': free(): invalid next size 
(fast): 0x01ca17b0 ***
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Jan 27 10:41:54 2016
  Dependencies:
   
  ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
  InstallationDate: Installed on 2015-04-30 (271 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s 
info/calculator.scope
  Signal: 6
  SourcePackage: libunity
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd789926128 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ptr=, str=0x7fd7899261a0 "free(): invalid 
next size (fast)", action=1) at malloc.c:4965
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3834
   __GI___libc_free (mem=) at malloc.c:2950
   ?? () from 
/usr/lib/python3/dist-packages/gi/_gi.cpython-35m-x86_64-linux-gnu.so
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': 
free(): invalid next size (fast): 0x01ca17b0 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1538471/+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 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***

[Jean Christophe André]

Not sure if this helps but it appears this problem only occurs on a
64-bit system. I did a Xenial 32-bit installation recently and the
Python scopes (I tested calc: and manpages:) worked properly. On a
Xenial 64-bit installation, even with the very last updates (especially
the recent libunity-core), it still crashes.

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

Title:
  scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3':
  free(): invalid next size (fast): 0x01ca17b0 ***

Status in Ubuntu Kylin:
  New
Status in libunity package in Ubuntu:
  Confirmed
Status in pygobject package in Ubuntu:
  New

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/python3': free(): invalid next size 
(fast): 0x01ca17b0 ***
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Jan 27 10:41:54 2016
  Dependencies:
   
  ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
  InstallationDate: Installed on 2015-04-30 (271 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s 
info/calculator.scope
  Signal: 6
  SourcePackage: libunity
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd789926128 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ptr=, str=0x7fd7899261a0 "free(): invalid 
next size (fast)", action=1) at malloc.c:4965
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3834
   __GI___libc_free (mem=) at malloc.c:2950
   ?? () from 
/usr/lib/python3/dist-packages/gi/_gi.cpython-35m-x86_64-linux-gnu.so
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': 
free(): invalid next size (fast): 0x01ca17b0 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1538471/+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 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***

[Jean Christophe André]

I forgot to mention: I rely on on the Python scopes infrastructure to
work as expected to endorse the deployment of this Xenial LTS over 400
computers in the NGO I'm working for… Since I love Ubuntu and advocate
for it at work, if you need any more tests, it will be my pleasure to
volunteer!

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

Title:
  scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3':
  free(): invalid next size (fast): 0x01ca17b0 ***

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/python3': free(): invalid next size 
(fast): 0x01ca17b0 ***
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Jan 27 10:41:54 2016
  Dependencies:
   
  ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
  InstallationDate: Installed on 2015-04-30 (271 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s 
info/calculator.scope
  Signal: 6
  SourcePackage: libunity
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd789926128 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ptr=, str=0x7fd7899261a0 "free(): invalid 
next size (fast)", action=1) at malloc.c:4965
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3834
   __GI___libc_free (mem=) at malloc.c:2950
   ?? () from 
/usr/lib/python3/dist-packages/gi/_gi.cpython-35m-x86_64-linux-gnu.so
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': 
free(): invalid next size (fast): 0x01ca17b0 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1538471/+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 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***

[Jean Christophe André]

On my side, the error only shows once per session, yes, but… my request
also never works as expected, ever.

I just want to use the unity-scope-calculator as usual — “Dashing” for
calc:1+2 — but it doesn't work, neither the first time nor the next
ones. Is this scope obsolete? Or is it supposed to still work?

If the whole scope-runner-dbus.py thing is affected, it means this
problem is affecting all Python scopes, that is:

$ ls -l /usr/share/unity-scopes/*/*_daemon.py
-rw-r--r-- 1 root root  7028 mar 28  2014 
/usr/share/unity-scopes/calculator/unity_calculator_daemon.py
-rw-r--r-- 1 root root 10731 jui 23  2013 
/usr/share/unity-scopes/chromiumbookmarks/unity_chromiumbookmarks_daemon.py
-rw-r--r-- 1 root root 10087 jui 23  2013 
/usr/share/unity-scopes/colourlovers/unity_colourlovers_daemon.py
-rw-r--r-- 1 root root  9772 mar 28  2014 
/usr/share/unity-scopes/devhelp/unity_devhelp_daemon.py
-rwxr-xr-x 1 root root 25607 mar 18  2014 
/usr/share/unity-scopes/facebook/unity_facebook_daemon.py
-rw-r--r-- 1 root root  8922 aoû  9  2013 
/usr/share/unity-scopes/firefoxbookmarks/unity_firefoxbookmarks_daemon.py
-rwxr-xr-x 1 root root 26075 mar 18  2014 
/usr/share/unity-scopes/flickr/unity_flickr_daemon.py
-rwxr-xr-x 1 root root 13883 nov 25 11:34 
/usr/share/unity-scopes/gdrive/unity_gdrive_daemon.py
-rwxr-xr-x 1 root root  6939 mar 24  2014 
/usr/share/unity-scopes/manpages/unity_manpages_daemon.py
-rw-r--r-- 1 root root  8485 jui 23  2013 
/usr/share/unity-scopes/openclipart/unity_openclipart_daemon.py
-rwxr-xr-x 1 root root 21877 mar 18  2014 
/usr/share/unity-scopes/picasa/unity_picasa_daemon.py
-rwxr-xr-x 1 root root 24576 mar 18  2014 
/usr/share/unity-scopes/shotwell/unity_shotwell_daemon.py
-rw-r--r-- 1 root root  8213 mar 28  2014 
/usr/share/unity-scopes/texdoc/unity_texdoc_daemon.py
-rw-r--r-- 1 root root  8574 jui 23  2013 
/usr/share/unity-scopes/tomboy/unity_tomboy_daemon.py
-rw-r--r-- 1 root root  8993 jui 23  2013 
/usr/share/unity-scopes/virtualbox/unity_virtualbox_daemon.py
-rw-r--r-- 1 root root  9967 jui 23  2013 
/usr/share/unity-scopes/yelp/unity_yelp_daemon.py
-rw-r--r-- 1 root root 11082 jui 23  2013 
/usr/share/unity-scopes/zotero/unity_zotero_daemon.py

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

Title:
  scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3':
  free(): invalid next size (fast): 0x01ca17b0 ***

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/python3': free(): invalid next size 
(fast): 0x01ca17b0 ***
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Jan 27 10:41:54 2016
  Dependencies:
   
  ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
  InstallationDate: Installed on 2015-04-30 (271 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s 
info/calculator.scope
  Signal: 6
  SourcePackage: libunity
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd789926128 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ptr=, str=0x7fd7899261a0 "free(): invalid 
next size (fast)", action=1) at malloc.c:4965
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3834
   __GI___libc_free (mem=) at malloc.c:2950
   ?? () from 
/usr/lib/python3/dist-packages/gi/_gi.cpython-35m-x86_64-linux-gnu.so
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': 
free(): invalid next size (fast): 0x01ca17b0 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1538471/+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 1554570] [NEW] package libpcsclite1 1.8.14-1ubuntu1 [modified: usr/share/doc/libpcsclite1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/d

[André Eduardo Trevisan]

Public bug reported:

I was trying to install a smart card reader to a digital certificate.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libpcsclite1 1.8.14-1ubuntu1 [modified: 
usr/share/doc/libpcsclite1/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
AptOrdering:
 libpcsclite1: Install
 libpcsclite1: Configure
 libpcsclite1: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Mar  8 12:13:18 2016
Dependencies:
 gcc-5-base 5.2.1-22ubuntu2
 libc6 2.21-0ubuntu4.1
 libgcc1 1:5.2.1-22ubuntu2
DpkgTerminalLog:
 Preparing to unpack .../libpcsclite1_1.8.14-1ubuntu1_i386.deb ...
 Unpacking libpcsclite1:i386 (1.8.14-1ubuntu1) over (1.8.5-1ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libpcsclite1_1.8.14-1ubuntu1_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libpcsclite1/changelog.Debian.gz', 
which is different from other instances of package libpcsclite1:i386
DuplicateSignature: package:libpcsclite1:1.8.14-1ubuntu1 [modified: 
usr/share/doc/libpcsclite1/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from 
other instances of package libpcsclite1:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from 
other instances of package libpcsclite1:i386
InstallationDate: Installed on 2016-03-08 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu1
SourcePackage: pcsc-lite
Title: package libpcsclite1 1.8.14-1ubuntu1 [modified: 
usr/share/doc/libpcsclite1/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libpcsclite1/changelog.Debian.gz', 
which is different from other instances of package libpcsclite1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict wily

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

Title:
  package libpcsclite1 1.8.14-1ubuntu1 [modified:
  usr/share/doc/libpcsclite1/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different
  from other instances of package libpcsclite1:i386

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I was trying to install a smart card reader to a digital certificate.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libpcsclite1 1.8.14-1ubuntu1 [modified: 
usr/share/doc/libpcsclite1/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  AptOrdering:
   libpcsclite1: Install
   libpcsclite1: Configure
   libpcsclite1: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Mar  8 12:13:18 2016
  Dependencies:
   gcc-5-base 5.2.1-22ubuntu2
   libc6 2.21-0ubuntu4.1
   libgcc1 1:5.2.1-22ubuntu2
  DpkgTerminalLog:
   Preparing to unpack .../libpcsclite1_1.8.14-1ubuntu1_i386.deb ...
   Unpacking libpcsclite1:i386 (1.8.14-1ubuntu1) over (1.8.5-1ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpcsclite1_1.8.14-1ubuntu1_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from 
other instances of package libpcsclite1:i386
  DuplicateSignature: package:libpcsclite1:1.8.14-1ubuntu1 [modified: 
usr/share/doc/libpcsclite1/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from 
other instances of package libpcsclite1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from 
other instances of package libpcsclite1:i386
  InstallationDate: Installed on 2016-03-08 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: pcsc-lite
  Title: package libpcsclite1 1.8.14-1ubuntu1 [modified: 
usr/share/doc/libpcsclite1/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libpcsclite1/changelog.Debian.gz', 
which is different from other instances of package libpcsclite1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 740506]

[André Guerreiro]

Thanks Albert for merging it. 
Yes it's not finished and I'm intending to pick up last summer's work on the 
glib frontend part.

I agree that we should close this bug and open specific ones to track
the frontend development or any other issue we find with the core code.

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+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 1553494] Re: Intermec PC43t prints only the first job, usb-no-reattach-default=true solves the issue

[André Campos Rodovalho]

CUPS upstream bug report link:
https://www.cups.org/str.php?L4780+P-1+S-2+C0+I0+E0+Q4780

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

Title:
  Intermec PC43t prints only the first job, usb-no-reattach-default=true
  solves the issue

Status in cups package in Ubuntu:
  New

Bug description:
  I had a bad time until I get this printer working. In the beggining I
  could not set it up because bad commands makes the printer freeze.
  After strugling for about a week I found the ideal combination of
  driver and configurations, but the printer was printing only the first
  job sent, after this it won't accept anymore.

  I installed the Intermec CUPS drivers (version 1.2-56) available at:
  http://apps.intermec.com/EFulfillment/SoftwareListForm.aspx?SoftwareID=3149

  Searching for syslog I found that the printer was disconnecting after
  a job sent. "DebuggingPrintingProblems" Wiki Page helped me to solve
  the issue. After installing the printer, I ran (lpstat -p -d) to find
  the printer name, then (lpadmin -p Intermec-PC43t-203-FP -o usb-no-
  reattach-default=true) to fix the disconnecting behaiver.

  On research I found that is possible to fix the issue also editing the
  file (/usr/share/cups/usb/org.cups.usb-quirks) but I will wait untill
  a fix is released, probably using this configuration file.

  I'm now using Direct Protocol with specific PC43t drivers (not generic
  Intermec drivers) and eveything is working properly. I will also
  report this problem to CUPS upstream at http://www.cups.org/str.php
  and past the link here.

  $ lsusb
  Bus 008 Device 003: ID 067e:0042 Intermec Technologies Corp.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.16.0-62.83~14.04.1-generic 3.16.7-ckt23
  Uname: Linux 3.16.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CupsErrorLog: W [05/Mar/2016:09:00:18 -0300] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
'Intermec-PC43t-203-FP-Gray..' already exists
  CurrentDesktop: LXDE
  Date: Sat Mar  5 09:24:38 2016
  Lpstat:
   device for DCP7065DN: lpd://BRN001BA976321F/BINARY_P1
   device for HP-8100-antiga: hp:/net/Officejet_Pro_8100?zc=HPC7E7F8
   device for HP-8100-nova: hp:/net/Officejet_Pro_8100?zc=HP92316B
   device for Intermec-PC43t-203-FP: 
usb://Intermec/PC43t-203-FP?serial=128C1230268
   device for L355-Series: lpd://192.168.254.15:515/PASSTHRU
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Papersize: a4
  PpdFiles:
   DCP7065DN: Brother DCP7065DN for CUPS
   Intermec-PC43t-203-FP: Intermec PC43t (203dpi)
   HP-8100-antiga: HP Officejet Pro 8100, hpcups 3.14.3
   HP-8100-nova: HP Officejet Pro 8100, hpcups 3.14.3
   L355-Series: Epson L355 Series - epson-inkjet-printer 1.0.0-1lsb3.2 (Seiko 
Epson Corporation LSB 3.2)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-62-generic 
root=UUID=49a849d6-d410-4fee-8447-d08bdd5af3ef ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1503:bd01/11/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx: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/1553494/+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 1553494] [NEW] Intermec PC43t prints only the first job, usb-no-reattach-default=true solves the issue

[André Campos Rodovalho]

Public bug reported:

I had a bad time until I get this printer working. In the beggining I
could not set it up because bad commands makes the printer freeze. After
strugling for about a week I found the ideal combination of driver and
configurations, but the printer was printing only the first job sent,
after this it won't accept anymore.

I installed the Intermec CUPS drivers (version 1.2-56) available at:
http://apps.intermec.com/EFulfillment/SoftwareListForm.aspx?SoftwareID=3149

Searching for syslog I found that the printer was disconnecting after a
job sent. "DebuggingPrintingProblems" Wiki Page helped me to solve the
issue. After installing the printer, I ran (lpstat -p -d) to find the
printer name, then (lpadmin -p Intermec-PC43t-203-FP -o usb-no-reattach-
default=true) to fix the disconnecting behaiver.

On research I found that is possible to fix the issue also editing the
file (/usr/share/cups/usb/org.cups.usb-quirks) but I will wait untill a
fix is released, probably using this configuration file.

I'm now using Direct Protocol with specific PC43t drivers (not generic
Intermec drivers) and eveything is working properly. I will also report
this problem to CUPS upstream at http://www.cups.org/str.php and past
the link here.

$ lsusb
Bus 008 Device 003: ID 067e:0042 Intermec Technologies Corp.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.7
ProcVersionSignature: Ubuntu 3.16.0-62.83~14.04.1-generic 3.16.7-ckt23
Uname: Linux 3.16.0-62-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CupsErrorLog: W [05/Mar/2016:09:00:18 -0300] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
'Intermec-PC43t-203-FP-Gray..' already exists
CurrentDesktop: LXDE
Date: Sat Mar  5 09:24:38 2016
Lpstat:
 device for DCP7065DN: lpd://BRN001BA976321F/BINARY_P1
 device for HP-8100-antiga: hp:/net/Officejet_Pro_8100?zc=HPC7E7F8
 device for HP-8100-nova: hp:/net/Officejet_Pro_8100?zc=HP92316B
 device for Intermec-PC43t-203-FP: 
usb://Intermec/PC43t-203-FP?serial=128C1230268
 device for L355-Series: lpd://192.168.254.15:515/PASSTHRU
MachineType: To be filled by O.E.M. To be filled by O.E.M.
Papersize: a4
PpdFiles:
 DCP7065DN: Brother DCP7065DN for CUPS
 Intermec-PC43t-203-FP: Intermec PC43t (203dpi)
 HP-8100-antiga: HP Officejet Pro 8100, hpcups 3.14.3
 HP-8100-nova: HP Officejet Pro 8100, hpcups 3.14.3
 L355-Series: Epson L355 Series - epson-inkjet-printer 1.0.0-1lsb3.2 (Seiko 
Epson Corporation LSB 3.2)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-62-generic 
root=UUID=49a849d6-d410-4fee-8447-d08bdd5af3ef ro
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/11/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1503
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 LE R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1503:bd01/11/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx: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 cups intermec label pc43 printer trusty

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

Title:
  Intermec PC43t prints only the first job, usb-no-reattach-default=true
  solves the issue

Status in cups package in Ubuntu:
  New

Bug description:
  I had a bad time until I get this printer working. In the beggining I
  could not set it up because bad commands makes the printer freeze.
  After strugling for about a week I found the ideal combination of
  driver and configurations, but the printer was printing only the first
  job sent, after this it won't accept anymore.

  I installed the Intermec CUPS drivers (version 1.2-56) available at:
  http://apps.intermec.com/EFulfillment/SoftwareListForm.aspx?SoftwareID=3149

  Searching for syslog I found that the printer was disconnecting after
  a job sent. "DebuggingPrintingProblems" Wiki Page helped me to solve
  the issue. After installing the printer, I ran (lpstat -p -d) to find
  the printer name, then (lpadmin -p Intermec-PC43t-203-FP -o usb-no-
  reattach-default=true) to fix the disconnecting behaiver.

  On research I found that is possible to fix the issue also editing the
  file (/usr/share/cups/usb/org.cups.usb-quirks) but I will wait untill
  a fix is released, probably using this configuration file.

  I'm now using Direct Protocol with specific 

[Touch-packages] [Bug 740506]

[André Guerreiro]

Created attachment 120992
Load NSS root certs module

This change is needed to actually do certificate validation, because as
it is NSS is trying to load the module which contains all the builtin
root certs from the Firefox profile directory where it is usually
missing. This way it will load the module from a system library
directory.

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

I'm in favour of Adrian's patch. It's an improvement with additional sanity 
checks on the ByteRange values. 
Indeed I tried to see if you could check if a given ByteRange covers the whole 
document and also found no easy way to do it with existing poppler 
functions/APIs.

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+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 1384503] Re: rsync fails on large files with compression

[André Freitas]

I am also suffering from this bug with a 1GB file with the --compress
flag in Ubuntu 14.04 with Rsync 3.1.0. The bug is pretty consistent and
after I removed the compress flag I got no more broken pipes.

I will try to make this bug reproducible with Docker and publish here.

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

Title:
  rsync fails on large files with compression

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Trusty:
  Incomplete

Bug description:
  Copying large (>10GB) files with rsync -z (compression) leads to a
  long hang and eventual error after transferring part of the file.  The
  error is consistent.  The file copies at normal speed until it reaches
  its maximum size (1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for
  another).  Then nothing happens for a while (many minutes).  Finally,
  there is an error:

  []
  jh/.VirtualBox/win7/win7.vbox
  jh/.VirtualBox/win7/win7.vbox-prev
  jh/.VirtualBox/win7/win7.vdi
  rsync: [sender] write error: Broken pipe (32)
  rsync error: error in rsync protocol data stream (code 12) at io.c(837) 
[sender=3.1.0]

  In this case, 6.9 GB of 29 GB transferred.  Without -z, it works.

  See the following upstream report, with a comment at the end from the
  rsync maintainer:

  https://bugzilla.samba.org/show_bug.cgi?id=10372

  According to this report, version 3.1.0 (included in 14.04) uses a
  different compression package from prior versions.  Prior versions did
  not have this problem for me using the same command on the same
  systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04
  now, in each case with all updates applied, Intel hardware.  Network
  connection between them is gigabit ethernet through one switch.  A
  shell ssh between them in a terminal works and stays up during the
  failure, so it is not a network issue.  There are no relevant entries
  in syslog on either machine.  There is sufficient capacity on the
  receiving disk.  All filesystems are ext4.

  rsync command:

  /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found
  --exclude=.gvfs --exclude=/nonlaptop /home/
  backup.host.edu:/bu/host/home/

  (yes, I changed the machine names)

  Current release (both hosts):

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Current package (both hosts):

  rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
   *** 3.1.0-2ubuntu0.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.1.0-2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Thanks,

  --jh--

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+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 1384503] Re: rsync fails on large files with compression

[André Freitas]

Hi, I have just published a docker compose stack to test this issue:
https://github.com/NDrive/rsync-compress-bug

Actually, I couldn't reproduce the bug with success. Maybe it only
happens in some certain files.

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

Title:
  rsync fails on large files with compression

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Trusty:
  Incomplete

Bug description:
  Copying large (>10GB) files with rsync -z (compression) leads to a
  long hang and eventual error after transferring part of the file.  The
  error is consistent.  The file copies at normal speed until it reaches
  its maximum size (1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for
  another).  Then nothing happens for a while (many minutes).  Finally,
  there is an error:

  []
  jh/.VirtualBox/win7/win7.vbox
  jh/.VirtualBox/win7/win7.vbox-prev
  jh/.VirtualBox/win7/win7.vdi
  rsync: [sender] write error: Broken pipe (32)
  rsync error: error in rsync protocol data stream (code 12) at io.c(837) 
[sender=3.1.0]

  In this case, 6.9 GB of 29 GB transferred.  Without -z, it works.

  See the following upstream report, with a comment at the end from the
  rsync maintainer:

  https://bugzilla.samba.org/show_bug.cgi?id=10372

  According to this report, version 3.1.0 (included in 14.04) uses a
  different compression package from prior versions.  Prior versions did
  not have this problem for me using the same command on the same
  systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04
  now, in each case with all updates applied, Intel hardware.  Network
  connection between them is gigabit ethernet through one switch.  A
  shell ssh between them in a terminal works and stays up during the
  failure, so it is not a network issue.  There are no relevant entries
  in syslog on either machine.  There is sufficient capacity on the
  receiving disk.  All filesystems are ext4.

  rsync command:

  /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found
  --exclude=.gvfs --exclude=/nonlaptop /home/
  backup.host.edu:/bu/host/home/

  (yes, I changed the machine names)

  Current release (both hosts):

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Current package (both hosts):

  rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
   *** 3.1.0-2ubuntu0.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.1.0-2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Thanks,

  --jh--

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

[André Guerreiro]

Created attachment 120434
Improve robustness of SignatureHandler::validateCertificate

This patch adds additional NULL-checking in
SignatureHandler::validateCertificate() which avoids segfault for some
signatures like the one contained here:
http://www.gpo.gov/fdsys/pkg/BUDGET-2015-BUD/pdf/BUDGET-2015-BUD.pdf

It also removes a useless branch in validateCertificate()

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

Created attachment 119283
Manpage improvement

Here's an improvement to the manpage. 
Corrected a typo and added some missing context

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

(In reply to Adrian Johnson from comment #79)
> +  r_values[0] = r2.isInt64() ? r2.getInt64() : r2.getInt();
> +  r_values[1] = r3.isInt64() ? r3.getInt64() : r3.getInt();
> +  r_values[2] = r4.isInt64() ? r4.getInt64() : r4.getInt();
>  
> According the PDF Reference, the ByteRange array contains pairs of
> (offset,length).
> 
> Why do we ignore the first offset and later assume it is 0? Why do we assume
> there are exactly two pairs.
> 
> I only skimmed over the digital signatures section so maybe I missed
> something.

Actually the PDF spec allows for more than 2 pairs of values in /ByteRange but 
it would mean that there is more than one gap in the signed data apart from the 
signature itself. Quoting from ISO 32000-1 section 12.8.1: 
"This range should be the entire file, including the signature dictionary but 
excluding the signature value itself (the Contents entry). Other ranges may be 
used but since they do not check for all changes to the document, their use is 
not recommended."

Obviously in a file with multiple signatures each signature should cover
the latest revision present in the file when the signature was appended.

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+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 214786] Re: Apple USB ISO keyboard has incorrectly swapped keys

[André]

@joao-pimentel-ferreira read the previous comment (#73)

Error still present in 15.10

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

Title:
  Apple USB ISO keyboard has incorrectly swapped keys

Status in Mactel Support:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel to version 2.6.24-12.22 two keys are now
  swapped on my Apple USB aluminium keyboard with danish layout. Now the
  keys "<" and "½" are swapped and no longer matches the actual print on
  the keycaps.

  The error is isolated to the following commit:
  http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
  hardy.git;a=commitdiff;h=efb3031b446d441dca5b10619503ac0bba7f9748

  This commit introduced a key swapping for all "ISO" type Apple
  keyboards. In my case this swapping is incorrect, and generally it
  seems like a very bad idea to perform hard coded locale specific key
  mapping in kernel space as this is also done several places in user
  space.

  The included patch reverts the behavior to the default that matches
  the keycap printing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mactel-support/+bug/214786/+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 740506]

[André Guerreiro]

Created attachment 118745
Incremental hashing + large file support

With this patch I've implemented the incremental hashing plus the large
file support.

This is still untested with files larger than 2GB but is correct for all
the regular test cases I gathered before.

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+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 1434591] Re: [mako] Cannot connect to a secure, shared "ap" hotspot

[André Gregor-Herrmann]

I'm facing the same issue with my nexus 4 which I bought for getting
Ubuntu Touch working on this device. Due Hotspot is an essential feature
for me I former thought of switching to an Android based Image despite I
really like the way Ubuntu-Touch works. Additionally  I'm now used to
its Gesture-Based interface. Then I heard that Hotspot is coming via
OTA-6 and I rather waited, instead of newly flashing the device. Too bad
that is still not working on my device then.

If this feature will be a "won't fix for mako", I see no other Chance to
regret the further Usage of Ubuntu Touch, which would make me really sad
but is then without any alternative for me :-(

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

Title:
  [mako] Cannot connect to a secure, shared "ap" hotspot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  $ system-image-cli -i
  current build number: 138
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-17 15:04:46
  version version: 138
  version ubuntu: 20150317.1
  version device: 20150210
  version custom: 20150317.1

  I have tried most types of security, but the spec [2] says for maximum
  compatibility, most of the options should be left blank. Blank
  settings failed on both a and bg bands.

  How to reproduce:
  1. Create a secure hotspot (I am using this [1] script)
  2. Confirm that the hotspot is active and appears secured for other devices

  What happens:
  Connecting to it fails.

  What should have happened:
  Connecting to it should not fail.

  Excerpt from syslog
  http://pastebin.ubuntu.com/10627959/

  Insecure hotspots should work using this [3] script.

  [1] http://pastebin.ubuntu.com/10683465/
  [2] https://developer.gnome.org/NetworkManager/stable/ref-settings.html
  [3] 
http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1434591/+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 740506]

[André Guerreiro]

Created attachment 118398
Fix for Buffer overflow

Regarding the illegal ByteRange values which would cause overflow this
patch should fix it

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

Created attachment 118449
Support for adbe.pkcs7.sha1 signatures

This patch, to be applied over the previous one, adds support for
adbe.pkcs7.sha1 signatures so now we should have a more complete
coverage of actual signed PDFs.

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

Created attachment 118446
NSS conditional build

This patch makes the NSS dependency optional in the CMake and Autotools
build systems.

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

@Adrian

Thanks for the tips on support for large files, progressive hashing and
the NSS includes. We'll be posting our attempts to improve these issues
as individual patches.

I also thought of adding the feature to pdfinfo but it seems wrong to
mix up something which performs various computations and relies on
external state (NSS cert DB) to pdfinfo which just reads metadata from
the file itself.

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

@Albert

Thanks for the improvements.
Regarding your 3 questions:

1- I've no objection to make the feature optional. I understand there
are people building more minimal versions of poppler that dislike
additional dependencies.

2- Yes we should. Our defaults are meant to take advantage of the
already configured and implicitly trusted NSS cert DBs in Firefox but we
shouldn't limit the user's options.

3- We're already looking into supporting adbe.pkcs7.sha1 signatures
which we found are very widespread. In Portugal we found that several
big companies are still using this kind of signatures in signed PDF
invoices as of now.

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

Created attachment 118193
poppler nss signature support - v5 - refactor

Here's a new patch following Albert's recommendations.
We've expanded the FormFieldSignature and FormFieldWidget classes to expose the 
signature method.

We also added checking for non-supported signature types as we only
support pkcs7.detached signatures at the moment.

This patch only includes the changes to poppler core and the
pdfsigverify utility, glib still needs changes to move the validation
from poppler_document to poppler_form_field.

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

Created attachment 118195
poppler nss signature support - v6

Sorry, there were still some missing NULL checks and a useless new(),
here's a new one.

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

Sorry for the succession of patches. This one fixes some remaining leaks
in the new PDFDoc methods and improves the indentation

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

Created attachment 118036
poppler nss signature support  - v3

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by 
  Date:  
  Reason: 
  Location: 
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

Sorry for the long absence and here's another attempt at solving this
issue.

I just attached a patch developed by me and André Esser which adds signature 
verification support to poppler core and the glib frontend.
It uses the NSS CMS API for the crypto operations (signature and certificate 
Validations).

4 new functions were added at the glib wrapper level: 
poppler_document_is_signed
poppler_document_signature_validate
poppler_document_signature_get_time
poppler_document_signature_get_signername

We added a new test utility for this feature in utils/pdfsigverify and
exposed the number of signatures in poppler-glib-demo.

The trusted certificate issue for Linux systems is tackled in the following way:
we try to load the NSS certificate DB in the default Firefox profile and if 
that fails we try to load certificates from the standard directory 
/etc/pki/nssdb which may or may not be populated depending on the distro setup. 
We're obviously open to suggestions in this area.

Current limitation:
- The CMake changes we're not done yet so Autotools build is required for now 
(we couldn't find an easy/clean way to find the NSS dependency using CMake)

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by signer
  Date:  time stamp
  Reason: reason
  Location: location
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

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

[André Guerreiro]

Created attachment 117885
PDF signature verification using NSS

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

Title:
  verify digital signatures

Status in Evince:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by signer
  Date:  time stamp
  Reason: reason
  Location: location
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+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 1441847] Re: Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3

[André Correia]

https://github.com/ValveSoftware/steam-for-linux/issues/3506

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768045

using new git version and everything works again

** Bug watch added: Debian Bug tracker #768045
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768045

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

Title:
  Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.6 package in Ubuntu:
  Invalid
Status in xtrans package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in llvm-toolchain-3.6 source package in Trusty:
  In Progress
Status in xtrans source package in Trusty:
  Fix Committed

Bug description:
  The vivid X11 stack backport needs libdrm and xtrans backported to
  trusty.

  libdrm 2.4.56-1 - 2.4.60-2 important changes:
  - new SI  CIK pci-ids (radeon)
  - SKL pci-ids (intel)
  - tegra support

  
  xtrans 1.3.4-1 - 1.3.5-1 changes
  - a bunch of const fixes
  - a new Listen function which the X server wants to allow -nolisten tcp by 
default
  http://launchpadlibrarian.net/189120642/xtrans_1.3.4-1_1.3.5-1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1441847/+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 1441847] Re: Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3

[André Correia]

this version of libdrm do not work with some valve games using bumblebee

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

Title:
  Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.6 package in Ubuntu:
  Invalid
Status in xtrans package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in llvm-toolchain-3.6 source package in Trusty:
  In Progress
Status in xtrans source package in Trusty:
  Fix Committed

Bug description:
  The vivid X11 stack backport needs libdrm and xtrans backported to
  trusty.

  libdrm 2.4.56-1 - 2.4.60-2 important changes:
  - new SI  CIK pci-ids (radeon)
  - SKL pci-ids (intel)
  - tegra support

  
  xtrans 1.3.4-1 - 1.3.5-1 changes
  - a bunch of const fixes
  - a new Listen function which the X server wants to allow -nolisten tcp by 
default
  http://launchpadlibrarian.net/189120642/xtrans_1.3.4-1_1.3.5-1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1441847/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

Libreoffice landscape test

** Attachment added: 2015-03-17 08.10.19.jpg
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+attachment/4347725/+files/2015-03-17%2008.10.19.jpg

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

Till Kamppeter, thank you very much for your attention.  I will follow the 
instructions and attach relevant files. 
Best regards.

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

/var/log/cups/error_log

** Attachment added: /var/log/cups/error_log
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+attachment/4347724/+files/var-log-cups-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/1424609

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

Capturing print job data

Libreoffice landscape test


** Attachment added: d05823-001
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+attachment/4347765/+files/d05823-001

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

Capturing print job data

Gedit landscape test

** Attachment added: d05822-001
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+attachment/4347775/+files/d05822-001

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

If there is any other thing I can do to help, please let me know. 
Best regards. 
Thank you.

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

Gedit landscape test

** Attachment added: 2015-03-17 08.11.31.jpg
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+attachment/4347727/+files/2015-03-17%2008.11.31.jpg

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

Another workaround: 
1. Print to pdf file choosing the format A5 Portrait;
2. Open the pdf and print choosing the format A4 Landscape.

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  New

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

** Attachment added: test.odt
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+attachment/4342905/+files/test.odt

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  New

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

Finally I found a workaround. The attached odt file can be printed correctly in 
landscape. 
So I guess the problem can be with custom page format (size).

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  New

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

** Attachment added: correct.pdf
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+attachment/4342645/+files/correct.pdf

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  New

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

Attached two files: one that prints in landscape correctly, and other
that don't. The first was created with Gedit and the second with
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/1424609

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  New

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

** Attachment added: incorret.pdf
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+attachment/4342646/+files/incorret.pdf

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  New

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] Re: Can not print in landscape

[André Desgualdo Pereira]

Gedit can print in landscape without problems. But that does not solves
this issue.

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  New

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1424609] [NEW] Can not print in landscape

[André Desgualdo Pereira]

Public bug reported:

All jobs are printed in portrait.

No matter which file is (pdf, odt, jpg).

Even from command line (lp -o landscape file.pdf) the problem persist.

Different paper sizes also do not matter (A4, A5).

Changing printer makes no difference.

Changing connection (usb, network attached) also makes no difference.

Attached an example file that could not be printed in landscape.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
CurrentDesktop: Unity
Date: Mon Feb 23 08:48:37 2015
InstallationDate: Installed on 2014-05-01 (297 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
KernLog:
 
Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
Papersize: a5
PpdFiles: ML-1860: Samsung ML-1860 Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3659
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 32.23
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 049D212412102
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug trusty

** Attachment added: odtfile
   https://bugs.launchpad.net/bugs/1424609/+attachment/4325353/+files/odtfile

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

Title:
  Can not print in landscape

Status in cups package in Ubuntu:
  New

Bug description:
  All jobs are printed in portrait.

  No matter which file is (pdf, odt, jpg).

  Even from command line (lp -o landscape file.pdf) the problem persist.

  Different paper sizes also do not matter (A4, A5).

  Changing printer makes no difference.

  Changing connection (usb, network attached) also makes no difference.

  Attached an example file that could not be printed in landscape.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) 
stopped with status 127!
  CurrentDesktop: Unity
  Date: Mon Feb 23 08:48:37 2015
  InstallationDate: Installed on 2014-05-01 (297 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  KernLog:
   
  Lpstat: device for ML-1860: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  Papersize: a5
  PpdFiles: ML-1860: Samsung ML-1860 Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+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 1415888] [NEW] package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 10

[André Gomes]

Public bug reported:

O erro ocorre durante uma atualizacao indicada pelo sistema

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: rsyslog 7.4.4-1ubuntu2.5
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Wed Jan 28 15:44:36 2015
DuplicateSignature: package:rsyslog:7.4.4-1ubuntu2.5:sub-processo script 
post-installation instalado retornou estado de saída de erro 10
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 10
InstallationDate: Installed on 2014-12-10 (49 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
SourcePackage: rsyslog
Title: package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 10

Status in rsyslog package in Ubuntu:
  New

Bug description:
  O erro ocorre durante uma atualizacao indicada pelo sistema

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.5
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Wed Jan 28 15:44:36 2015
  DuplicateSignature: package:rsyslog:7.4.4-1ubuntu2.5:sub-processo script 
post-installation instalado retornou estado de saída de erro 10
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 10
  InstallationDate: Installed on 2014-12-10 (49 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: rsyslog
  Title: package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1415888/+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 1411490] [NEW] package libnss3:amd64 2:3.17.1-0ubuntu0.14.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[André Gomes]

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libnss3:amd64 2:3.17.1-0ubuntu0.14.04.2
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Fri Jan 16 00:39:18 2015
DuplicateSignature: package:libnss3:amd64:2:3.17.1-0ubuntu0.14.04.2:package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2014-12-10 (36 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
SourcePackage: nss
Title: package libnss3:amd64 2:3.17.1-0ubuntu0.14.04.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: nss (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package libnss3:amd64 2:3.17.1-0ubuntu0.14.04.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in nss package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libnss3:amd64 2:3.17.1-0ubuntu0.14.04.2
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Fri Jan 16 00:39:18 2015
  DuplicateSignature: package:libnss3:amd64:2:3.17.1-0ubuntu0.14.04.2:package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-12-10 (36 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: nss
  Title: package libnss3:amd64 2:3.17.1-0ubuntu0.14.04.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/nss/+bug/1411490/+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 1029289] Re: Need to authorize my google account each time I boot the computer

[André Canha]

Hello

I started having this problem a few days back and posted a question here. 
https://answers.launchpad.net/ubuntu/+question/252680

My Google account is a non-business and everyting has been working fine
until now.

I've tried deleting my google account on Ubuntu Online accounts, revoged access 
to ubuntu and gnove evolution on my google account security settings and adding 
the account again on ubuntu.
That time it asked me for the google authenticator code, which I entered, but 
when I logged out and back in... it still was'nt working...

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  In Progress
Status in Online Accounts: OAuth2 plug-in:
  Unknown
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in “account-plugins” package in Ubuntu:
  Fix Released
Status in “signon-plugin-oauth2” package in Ubuntu:
  Fix Released
Status in “account-plugins” source package in Quantal:
  Fix Released
Status in “signon-plugin-oauth2” source package in Quantal:
  Fix Released

Bug description:
  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google account will be marked
  as needing reauthentication. Time can vary, but any period shorter
  than one month is a symptom of the bug.

  [Regression Potential] Minimal: the change to the Google plugin (in
  account-plugins) simply changes the authentication method, in a way
  that is well-documented. The change in signon-plugin-oauth2 affects
  only those accounts/providers which use the OAuth refresh tokens --
  which is only Google, at the moment -- and in a way that can't
  possibly break any existing functionality; if the new code had some
  mistake, the refresh token would be unusable and the system would
  automatically fall back to requesting a new access token (which is
  exactly what happens now, with this bug).

  I'll try to find why the account-plugins package was not uploaded;
  indeed, both are required in order to fix this bug.

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