[Touch-packages] [Bug 1814611] Re: ubuntu-bug never (any longer) opens browser window

2019-07-03 Thread Thomas Mayer
A quick fix could be to document at
https://help.ubuntu.com/community/ReportingBugs that the error reporting
must be switch on first.

On top of that, ubuntu-bug could output a warning message that the error
reporting must be switched on first (and how/where this can be done).

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

Title:
  ubuntu-bug never (any longer) opens browser window

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.1 LTS, X11 gnome session.

  For some reason ubuntu-bug  no longer opens a browser
  window, so it is not possible to enter useful bug detauls, or even
  know the bug number.

  After prompting whether or not to Send the report, clicking "Send"
  just closes appport and nothing else ever happens.  The exit status of
  "ubuntu-bug" is zero.

  This worked fine before, but it has been many months since I tried to
  submit a bug.

  strace shows many stat calls on plausible browser paths, including the one 
that is correct (/usr/bin/firefox, which returned a successful stat call).  
I'll attach the trace output from
 
 strace -f -o /tmp/strace.log ubuntu-bug apport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1814611] Re: ubuntu-bug never (any longer) opens browser window

2019-07-03 Thread Thomas Mayer
For this to work, I had to enable the error reporting switch in system
settings/privacy protection.

With error reporting enabled, the browser window opened.

This is not a bug, but I'm not very happy with the behaviour:

- Having error reporting switched off, I should be able to enforce it via CLI. 
There should be a corresponding parameter like --ignore-reporting-disabled. 
(OPT-IN)
- OR: Ignoring the disabled reporting should be the default when executing 
ubuntu-bug manually. (OPT-OUT). If ubuntu-bug was _not_ started manually might 
require another parameter like --check-reporting-enabled.

Unwanted behaviour is:
- I have to switch error reporting on (plus, I have to know this by myself!)
- ... do my stuff with ubuntu-bug
- Switch error reporting off again

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

Title:
  ubuntu-bug never (any longer) opens browser window

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.1 LTS, X11 gnome session.

  For some reason ubuntu-bug  no longer opens a browser
  window, so it is not possible to enter useful bug detauls, or even
  know the bug number.

  After prompting whether or not to Send the report, clicking "Send"
  just closes appport and nothing else ever happens.  The exit status of
  "ubuntu-bug" is zero.

  This worked fine before, but it has been many months since I tried to
  submit a bug.

  strace shows many stat calls on plausible browser paths, including the one 
that is correct (/usr/bin/firefox, which returned a successful stat call).  
I'll attach the trace output from
 
 strace -f -o /tmp/strace.log ubuntu-bug apport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1814611] Re: ubuntu-bug never (any longer) opens browser window

2019-07-03 Thread Thomas Mayer
Documentation says (after having pressed the "send" button):

"Apport will then upload the problem information to Launchpad, and a new
browser window will then open to inform you that the bug report is being
processed."

https://help.ubuntu.com/community/ReportingBugs

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

Title:
  ubuntu-bug never (any longer) opens browser window

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.1 LTS, X11 gnome session.

  For some reason ubuntu-bug  no longer opens a browser
  window, so it is not possible to enter useful bug detauls, or even
  know the bug number.

  After prompting whether or not to Send the report, clicking "Send"
  just closes appport and nothing else ever happens.  The exit status of
  "ubuntu-bug" is zero.

  This worked fine before, but it has been many months since I tried to
  submit a bug.

  strace shows many stat calls on plausible browser paths, including the one 
that is correct (/usr/bin/firefox, which returned a successful stat call).  
I'll attach the trace output from
 
 strace -f -o /tmp/strace.log ubuntu-bug apport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1814611] Re: ubuntu-bug never (any longer) opens browser window

2019-07-03 Thread Thomas Mayer
I'm using ubuntu 18.04 with all updates installed.

When I type

ubuntu-bug gnome-applets

then it does not open the browser window when I click on the "send"
button.

When i type

xdg-open http://bugs.launchpad.net

then the corresponding page opens perfectly fine in Firefox 67.0.4.

This is pretty much consistent with the previous description.

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

Title:
  ubuntu-bug never (any longer) opens browser window

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.1 LTS, X11 gnome session.

  For some reason ubuntu-bug  no longer opens a browser
  window, so it is not possible to enter useful bug detauls, or even
  know the bug number.

  After prompting whether or not to Send the report, clicking "Send"
  just closes appport and nothing else ever happens.  The exit status of
  "ubuntu-bug" is zero.

  This worked fine before, but it has been many months since I tried to
  submit a bug.

  strace shows many stat calls on plausible browser paths, including the one 
that is correct (/usr/bin/firefox, which returned a successful stat call).  
I'll attach the trace output from
 
 strace -f -o /tmp/strace.log ubuntu-bug apport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css

2018-09-24 Thread Thomas Mayer
I've hit this issue right after upgrading from 16.04 to 18.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/1773045

Title:
  Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
  builder.css

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

Bug description:
  The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
  line

  @import url("apps/gnome-builder.css");

  But this file does not exist in this package or any other, as far as I
  can tell from apt-file.  This triggers an annoying warning when
  running various applications (e.g. evince):

  (evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
  gtk-main.css:73:38: Failed to import: Error opening file
  /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
  file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 18:58:41 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+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 1592948] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess installiertes post-installation-Skript wurde durch Signal (Beendet) getötet

2018-08-27 Thread Thomas Mayer
@gf I'm still on 16.04 and plan to upgrade this year.

I think this issue should still be about upgrading from 14.04 to 16.04
because 14.04 still is supported and people still upgrade from 14.04 to
16.04 until EOL.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript wurde durch Signal (Beendet)
  getötet

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  happened after failed upgrade from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 15 20:25:32 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript wurde durch 
Signal (Beendet) getötet
  InstallationDate: Installed on 2014-11-29 (564 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat:
   device for FS-1020D: socket://fs1020d.fritz.box:9100
   device for FS-C5150DN: socket://192.168.178.33:9100
   device for FS-C5150DN-COLOR: socket://192.168.178.33:9100
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0c45:6419 Microdia Integrated Webcam
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E5510
  Papersize: a4
  PpdFiles:
   FS-C5150DN-COLOR: Kyocera FS-C5150DN (KPDL)
   FS-C5150DN: Kyocera FS-C5150DN (KPDL)
   FS-1020D: Kyocera Mita FS-1020D
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript wurde durch Signal (Beendet) getötet
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (0 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-07-23T00:20:18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1592948/+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 1592948] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess installiertes post-installation-Skript wurde durch Signal (Beendet) getötet

2018-08-26 Thread Thomas Mayer
@gf I have not upgraded from 14.04.x to 16.04 for a long time. I'm not
sure if this has been fixed in the mean time. I'd rather have a look at
#1592917, and according to #1592917, no fix has been released yet which
would address this issue. When in doubt, I'd rather guess it is not
fixed, but only a test with recent version would ensure that.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript wurde durch Signal (Beendet)
  getötet

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  happened after failed upgrade from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 15 20:25:32 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript wurde durch 
Signal (Beendet) getötet
  InstallationDate: Installed on 2014-11-29 (564 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat:
   device for FS-1020D: socket://fs1020d.fritz.box:9100
   device for FS-C5150DN: socket://192.168.178.33:9100
   device for FS-C5150DN-COLOR: socket://192.168.178.33:9100
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0c45:6419 Microdia Integrated Webcam
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E5510
  Papersize: a4
  PpdFiles:
   FS-C5150DN-COLOR: Kyocera FS-C5150DN (KPDL)
   FS-C5150DN: Kyocera FS-C5150DN (KPDL)
   FS-1020D: Kyocera Mita FS-1020D
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript wurde durch Signal (Beendet) getötet
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (0 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-07-23T00:20:18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1592948/+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 1701572] Re: [regression] bluetooth headset not connecting after regular update

2017-06-30 Thread Thomas Mayer
** Changed in: bluez (Ubuntu)
   Status: New => Invalid

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

Title:
  [regression] bluetooth headset not connecting after regular update

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Hi, my bluetooth headset Arctic P311 was connecting until I installed
  these updates:

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

  For pulseaudio changes, I got this changelog:

  --- Änderungen für pulseaudio (libpulsedsp libpulse-mainloop-glib0 pulseaudio 
pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-x11 
pulseaudio-module-zeroconf pulseaudio-utils) ---
  Holen:1 http://changelogs.ubuntu.com pulseaudio 1:8.0-0ubuntu3.3 Changelog 
[216 kB]
  pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

[Luke Yelavich, Konrad Zapałowicz]
* Fixed multiple interrelated problems with using Bluetooth audio (A2DP),
  where users would experience some combination of:
  - Bluetooth headset/speakers listed but not selectable in Sound settings
(LP: #1283003)
  - [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
mode) (LP: #1438510)
  - [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set
to HSP/HFP first (LP: #1582213)
* Specific patches from upstream used to address the above problems:
  - 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch
  - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch
  - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch
. Backport from upstream to fix a bug in Xenial where an incorrect
  audio profile is applied for a headset connected over Bluetooth
  making using it impossible.
  - 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch
. Fix a crash that happens if the BT headset is the only non-monitor
  source in the system and the last "phone" stream dies.
  - 0700-pulsecore-add-new-card-profile-hook.patch
. Backport from upstream (commit 7b6260140149) to allow for correct
  profile selection.
  - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch
. Backport from upstream waiting for all profiles to connect before
  creating a card.

  Before, the P311 headset was connecting, after the update, it's not.
  Looks like a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluetooth 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 16:06:36 2017
  InstallationDate: Installed on 2014-11-29 (944 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E5510
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-58-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (379 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 5C:AC:4C:F8:E1:98  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:2055 acl:26 sco:0 events:96 errors:0
TX bytes

[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2017-06-30 Thread Thomas Mayer
I just reproduced the freeze again after switching off wireless devices
with a physical switch in my laptop. After reenabling wireless devices,
videos froze again. Worked around it by changing bluetooth profiles
(away from A2DP and back again).

So this issue is still not fixed.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2017-06-30 Thread Thomas Mayer
I think that one of the recent updates fixed it (and it also survives
S2RAM):

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

I could not reproduce this issue at least. This time, I repaired my
device with Blueman as pure audio device. Could also be that this works
around the issue. At least does it seem to work now.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

2017-06-30 Thread Thomas Mayer
Looks as if one of these updates improved it for S2RAM, but not for
hardware switch (I mean a real physical switch in my laptop for all
wireless hardware)

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

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

Title:
  bluetooth unavailable after rfkill hard (or soft) unblocking and after
  suspend/resume

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  DELL Latitude E5510 has a hardware switch to disable and enable
  bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
  terms of wifi, this works great: After hard unblocking, the device
  resumes back to normal operation without any manual intervention. That
  was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

  In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
  is not working any more:

  After hard blocking and unblocking

  - bluetooth is not working at all
  - the applet-indicator remains gray
  - bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
  - rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
  rfkill list bluetooth
  2: dell-bluetooth: Bluetooth
   Soft blocked: no
   Hard blocked: no
  8: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no

  The device is a
  sudo lsusb
  Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

  Workaround: After a

  sudo service bluetooth restart

  the bluetooth device turns back to normal operation and the applet-
  indicator turns from gray to black (available).

  Suggested fix: Make the workaround obsolete.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jul 17 04:00:58 2016
  InstallationDate: Installed on 2014-11-29 (595 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5510
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1603715/+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 1701572] Re: [regression] bluetooth headset not connecting after regular update

2017-06-30 Thread Thomas Mayer
I worked around it.

I had to remove --purge
bluetooth bluez blueman bluetooth pulseaudio pulseaudio-module-bluetooth

Then I removed all pairing information with devices, both in
~/.config/pulse and /var/lib/bluetooth

Then rebooted

Then paired my A2DP device again, this time with blueman.

Then everything was working.

I think the main problem here is that I once had device discovery
disabled in /etc/pulse/default.pa. But that's not a bug in ubuntu.

Issue can be closed.

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

Title:
  [regression] bluetooth headset not connecting after regular update

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi, my bluetooth headset Arctic P311 was connecting until I installed
  these updates:

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

  For pulseaudio changes, I got this changelog:

  --- Änderungen für pulseaudio (libpulsedsp libpulse-mainloop-glib0 pulseaudio 
pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-x11 
pulseaudio-module-zeroconf pulseaudio-utils) ---
  Holen:1 http://changelogs.ubuntu.com pulseaudio 1:8.0-0ubuntu3.3 Changelog 
[216 kB]
  pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

[Luke Yelavich, Konrad Zapałowicz]
* Fixed multiple interrelated problems with using Bluetooth audio (A2DP),
  where users would experience some combination of:
  - Bluetooth headset/speakers listed but not selectable in Sound settings
(LP: #1283003)
  - [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
mode) (LP: #1438510)
  - [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set
to HSP/HFP first (LP: #1582213)
* Specific patches from upstream used to address the above problems:
  - 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch
  - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch
  - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch
. Backport from upstream to fix a bug in Xenial where an incorrect
  audio profile is applied for a headset connected over Bluetooth
  making using it impossible.
  - 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch
. Fix a crash that happens if the BT headset is the only non-monitor
  source in the system and the last "phone" stream dies.
  - 0700-pulsecore-add-new-card-profile-hook.patch
. Backport from upstream (commit 7b6260140149) to allow for correct
  profile selection.
  - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch
. Backport from upstream waiting for all profiles to connect before
  creating a card.

  Before, the P311 headset was connecting, after the update, it's not.
  Looks like a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluetooth 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 16:06:36 2017
  InstallationDate: Installed on 2014-11-29 (944 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E5510
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-58-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (379 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.

[Touch-packages] [Bug 1701572] Re: [regression] bluetooth headset not connecting after regular update

2017-06-30 Thread Thomas Mayer
When I try to connect the headset (which still seems to pair), I see the
little lock next to the bluetooth device for ~0.5 seconds. Then the lock
disappears.

Syslog reports:
Jun 30 16:00:40 lat61 bluetoothd[1235]: a2dp-sink profile connect failed for 
00:1A:7D:70:08:7E: Protocol not available
Jun 30 16:00:45 lat61 bluetoothd[1235]: a2dp-sink profile connect failed for 
00:1A:7D:D0:24:5D: Protocol not available

Enabling the line
AutoEnable=true
in /etc/bluetooth/main.conf
does not fix this issue

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

Title:
  [regression] bluetooth headset not connecting after regular update

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi, my bluetooth headset Arctic P311 was connecting until I installed
  these updates:

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

  For pulseaudio changes, I got this changelog:

  --- Änderungen für pulseaudio (libpulsedsp libpulse-mainloop-glib0 pulseaudio 
pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-x11 
pulseaudio-module-zeroconf pulseaudio-utils) ---
  Holen:1 http://changelogs.ubuntu.com pulseaudio 1:8.0-0ubuntu3.3 Changelog 
[216 kB]
  pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

[Luke Yelavich, Konrad Zapałowicz]
* Fixed multiple interrelated problems with using Bluetooth audio (A2DP),
  where users would experience some combination of:
  - Bluetooth headset/speakers listed but not selectable in Sound settings
(LP: #1283003)
  - [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
mode) (LP: #1438510)
  - [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set
to HSP/HFP first (LP: #1582213)
* Specific patches from upstream used to address the above problems:
  - 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch
  - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch
  - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch
. Backport from upstream to fix a bug in Xenial where an incorrect
  audio profile is applied for a headset connected over Bluetooth
  making using it impossible.
  - 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch
. Fix a crash that happens if the BT headset is the only non-monitor
  source in the system and the last "phone" stream dies.
  - 0700-pulsecore-add-new-card-profile-hook.patch
. Backport from upstream (commit 7b6260140149) to allow for correct
  profile selection.
  - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch
. Backport from upstream waiting for all profiles to connect before
  creating a card.

  Before, the P311 headset was connecting, after the update, it's not.
  Looks like a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluetooth 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 16:06:36 2017
  InstallationDate: Installed on 2014-11-29 (944 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E5510
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-58-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (379 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.mod

[Touch-packages] [Bug 1701572] [NEW] [regression] bluetooth headset not connecting after regular update

2017-06-30 Thread Thomas Mayer
Public bug reported:

Hi, my bluetooth headset Arctic P311 was connecting until I installed
these updates:

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

For pulseaudio changes, I got this changelog:

--- Änderungen für pulseaudio (libpulsedsp libpulse-mainloop-glib0 pulseaudio 
pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-x11 
pulseaudio-module-zeroconf pulseaudio-utils) ---
Holen:1 http://changelogs.ubuntu.com pulseaudio 1:8.0-0ubuntu3.3 Changelog [216 
kB]
pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

  [Luke Yelavich, Konrad Zapałowicz]
  * Fixed multiple interrelated problems with using Bluetooth audio (A2DP),
where users would experience some combination of:
- Bluetooth headset/speakers listed but not selectable in Sound settings
  (LP: #1283003)
- [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode) (LP: #1438510)
- [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set
  to HSP/HFP first (LP: #1582213)
  * Specific patches from upstream used to address the above problems:
- 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch
- 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch
- 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch
  . Backport from upstream to fix a bug in Xenial where an incorrect
audio profile is applied for a headset connected over Bluetooth
making using it impossible.
- 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch
  . Fix a crash that happens if the BT headset is the only non-monitor
source in the system and the last "phone" stream dies.
- 0700-pulsecore-add-new-card-profile-hook.patch
  . Backport from upstream (commit 7b6260140149) to allow for correct
profile selection.
- 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch
  . Backport from upstream waiting for all profiles to connect before
creating a card.

Before, the P311 headset was connecting, after the update, it's not.
Looks like a regression.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bluetooth 5.37-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Jun 30 16:06:36 2017
InstallationDate: Installed on 2014-11-29 (944 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Latitude E5510
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-58-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to xenial on 2016-06-15 (379 days ago)
dmi.bios.date: 12/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 023HKR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 5C:AC:4C:F8:E1:98  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:2055 acl:26 sco:0 events:96 errors:0
TX bytes:3977 acl:28 sco:0 commands:62 errors:0

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


** Tags: amd64 apport-bug xenial

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

Title:
  [regression] bluetooth headset not connecting after regular update

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi, my bluetooth headset Arctic P3

[Touch-packages] [Bug 1515972] Re: Xorg crash

2017-06-08 Thread Thomas Mayer
I've just seen this error in up-to-date ubuntu 16.04, HES Kernel 4.8.

** Changed in: xorg (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  xorg randomly and quite often (once an hour) crashes back to loginscreen, 
when klicking on various buttons (you can never say which button).
  ProblemType: Crash
  Architecture: amd64
  Date: Fri Nov 13 12:20:39 2015
  DistroRelease: Ubuntu 15.10
  ExecutablePath: /usr/bin/Xorg
  ExecutableTimestamp: 1443604291
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov 13 12:34:50 2015
  DistUpgraded: 2015-10-20 12:22:39,151 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.26: added
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2014-06-29 (501 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 4291QS0
  ProcEnviron:
   LANGUAGE=de_AT:de
   TERM=screen
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to wily on 2015-10-20 (24 days ago)
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QS0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET51WW(1.21):bd08/02/2011:svnLENOVO:pn4291QS0:pvrThinkPadX220:rvnLENOVO:rn4291QS0:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291QS0
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Nov 13 12:20:48 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9

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

2017-06-08 Thread Thomas Mayer
For me, it's

sudo ls -lah /var/crash/
[sudo] Passwort für thomas: 
insgesamt 189M
drwxrwsrwt 1 root   whoopsie  682 Jun  9 07:52 .
drwxr-xr-x 1 root   root  130 Jul 26  2015 ..
-rwxrwxrwx 1 root   whoopsie0 Jun  8 17:19 .lock
-rw-r- 1 thomas whoopsie 155M Jun  6 12:04 
_opt_phpstorm_PhpStorm-2017.1.1_jre64_bin_java.1000.crash
-rw-r- 1 thomas whoopsie 7,9M Mai 31 12:33 _usr_bin_gedit.1000.crash
-rw-r--r-- 1 thomas whoopsie0 Mai 31 12:33 _usr_bin_gedit.1000.upload
-rw-r- 1 thomas whoopsie 1,3M Jun  8 22:46 
_usr_bin_gnome-flashback.1000.crash
-rw-r--r-- 1 thomas whoopsie0 Mai 31 12:35 
_usr_bin_gnome-flashback.1000.upload
-rw-r- 1 thomas whoopsie 1,9M Jun  2 08:02 
_usr_bin_kactivitymanagerd.1000.crash
-rw-r- 1 thomas whoopsie  15M Jun  9 07:19 _usr_bin_shutter.1000.crash
-rw-r--r-- 1 thomas whoopsie0 Jun  4 06:53 _usr_bin_shutter.1000.upload
-rw-r- 1 root   whoopsie 2,9M Jun  9 07:53 _usr_lib_xorg_Xorg.0.crash
-rw-r- 1 thomas whoopsie 5,1M Jun  2 08:21 
_usr_share_apport_apport-gtk.1000.crash

Seems that shutter played a role in my case. I load shutter as a tray
Icon. If shutter (or any other tiny tray-iconed program) brings down the
whole desktop, that should not be (even if the program itself crashes).

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  xorg randomly and quite often (once an hour) crashes back to loginscreen, 
when klicking on various buttons (you can never say which button).
  ProblemType: Crash
  Architecture: amd64
  Date: Fri Nov 13 12:20:39 2015
  DistroRelease: Ubuntu 15.10
  ExecutablePath: /usr/bin/Xorg
  ExecutableTimestamp: 1443604291
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov 13 12:34:50 2015
  DistUpgraded: 2015-10-20 12:22:39,151 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.26: added
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2014-06-29 (501 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 4291QS0
  ProcEnviron:
   LANGUAGE=de_AT:de
   TERM=screen
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to wily on 2015-10-20 (24 days ago)
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QS0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET51WW(1.21):bd08/02/2011:svnLENOVO:pn4291QS0:pvrThinkPadX220:rvnLENOVO:rn4291QS0:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291QS0
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Nov 13 12:20:48 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LG

[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2017-05-29 Thread Thomas Mayer
As bluetooth headsets tend to deal with audio, I assume that the cause
of this issue is somewhere between pulseaudio and bluetooth.

Pulseaudio also deals with bluetooth directly, like in issue #508522. As
long as it is unclear where this issue really comes from, I'll add
pulseaudio package to this issue. Would still be helpful if pulseaudio
maintainers could state if or if not this issue should be fixed via
pulseaudio.

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 508522] Re: Mic is not available with A2DP Bluetooth profile

2017-05-29 Thread Thomas Mayer
@vanvugt Given that this issue is for pulseaudio and deals with
bluetooth, a backport fixing this issue eventually also fixes #1589008.
In case it does, #1589008 eventually is a duplicate, or vice-versa.

In respect to #1589008: I'm really frightened that one day I still
switch bluetooth profiles for no reason after this is fixed (could be
classified as an obsessive-compulsive disorder on my side then).

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

Title:
  Mic is not available with A2DP Bluetooth profile

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+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 508522] Re: Mic is not available with A2DP Bluetooth profile

2017-05-29 Thread Thomas Mayer
Off-topic in terms of this issue:

@b2109455 I have two Arctic P311 (one is ~3 years old and one is ~5
years old). For both, the quality of the microphone is not sufficient to
talk with somebody. I can only use A2DP with it, which is perfectly fine
for me (most of the time).

Can you practically talk in an understandable manner to someone, using
the microphone of the P311? How old is your P311 (there's multiple
generations with same name)?

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

Title:
  Mic is not available with A2DP Bluetooth profile

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+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 1688933] [NEW] systemd restart-loops logind

2017-05-06 Thread Thomas Mayer
Public bug reported:

Syslog logs systemd trying to restart logind every few seconds:

May  7 00:51:29 server systemd[1]: Starting Login Service...
May  7 00:51:54 server systemd[1]: systemd-logind.service: Main process exited, 
code=exited, status=1/FAILURE
May  7 00:51:54 server systemd[1]: Failed to start Login Service.
May  7 00:51:54 server systemd[1]: systemd-logind.service: Unit entered failed 
state.
May  7 00:51:54 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
May  7 00:51:54 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
May  7 00:51:54 server systemd[1]: Stopped Login Service.
May  7 00:51:54 server systemd[1]: Starting Login Service...
May  7 00:52:19 server systemd[1]: systemd-logind.service: Main process exited, 
code=exited, status=1/FAILURE
May  7 00:52:19 server systemd[1]: Failed to start Login Service.
May  7 00:52:19 server systemd[1]: systemd-logind.service: Unit entered failed 
state.
May  7 00:52:19 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
May  7 00:52:19 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
May  7 00:52:19 server systemd[1]: Stopped Login Service.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu17
ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun May  7 00:51:07 2017
InstallationDate: Installed on 2013-08-21 (1353 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcEnviron:
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-51-generic 
root=UUID=16120d81-8cde-4e81-87cd-f55f65a4923b ro rootflags=subvol=@
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 
 2 overridden configuration files found.
UpgradeStatus: Upgraded to xenial on 2016-10-24 (193 days ago)
dmi.bios.date: 03/13/2014
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SWQ6710H.86A.0067.2014.0313.1347
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DQ67OW
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG12528-309
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0067.2014.0313.1347:bd03/13/2014:svn:pn:pvr:rvnIntelCorporation:rnDQ67OW:rvrAAG12528-309:cvn:ct3:cvr:

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


** Tags: amd64 apport-bug xenial

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

Title:
  systemd restart-loops logind

Status in systemd package in Ubuntu:
  New

Bug description:
  Syslog logs systemd trying to restart logind every few seconds:

  May  7 00:51:29 server systemd[1]: Starting Login Service...
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Main process 
exited, code=exited, status=1/FAILURE
  May  7 00:51:54 server systemd[1]: Failed to start Login Service.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Unit entered 
failed state.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
  May  7 00:51:54 server systemd[1]: Stopped Login Service.
  May  7 00:51:54 server systemd[1]: Starting Login Service...
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Main process 
exited, code=exited, status=1/FAILURE
  May  7 00:52:19 server systemd[1]: Failed to start Login Service.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Unit entered 
failed state.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
  May  7 00:52:19 server systemd[1]: Stopped Login Service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun May  7 00:51:07 2017
  InstallationDate: Installed on 2013-08-21 (1353 days ago)
  InstallationMedia: Ubunt

[Touch-packages] [Bug 1509622] Re: Xorg crash

2017-03-02 Thread Thomas Mayer
I'm getting this error for 16.04, since upgrading to latest HWE Kernel
4.8.0-39. Note that I also updated the Xorg packages to

xserver-xorg-*-hwe-16.04.

On top of that, I can also confirm that I get the error message

"Invalid core dump: BFD: Warning: /tmp/apport_core_aiu21o8t
is truncated: expected core file size"

That message is reported after every reboot.

** Changed in: xorg (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This is the full apport data from the crash reported as bug #1507461.
  It occurred whilst watching a full-screen Flash video in Google
  Chrome.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Oct 24 18:04:11 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21fa]
  MachineType: LENOVO CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=/dev/mapper/peleg0-lv01 ro splash quiet nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET33WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET33WW(1.13):bd07/24/2012:svnLENOVO:pnCTO:pvrThinkPadX230:rvnLENOVO:rnCTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Oct 24 17:58:31 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622/+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 1665853] Re: HWE 16.04.2: Login Screen goes partially black after upgrade (Dual Screen)

2017-02-18 Thread Thomas Mayer
I still get syslog entries

Feb 18 20:16:52 lat61 gnome-session[3090]: ** (gnome-flashback:3185): WARNING 
**: Could not assign CRTC to outputs, ignoring configuration
Feb 18 20:16:52 lat61 gnome-session[3090]: ** (gnome-flashback:3185): WARNING 
**: Could not make default configuration for current output layout, leaving 
unconfigured

Now that the login screen works correctly (after manual intervention), I
think this is a separate issue, which should be handled with a separate
bug #1665922

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

Title:
  HWE 16.04.2: Login Screen goes partially black after upgrade (Dual
  Screen)

Status in gnome-flashback package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using ubuntu 16.04, up-to-date, HWE kernel 4.8.0-36-generic.

  On dual screen setup, during system login, the first screen stretches
  over a part of the second screen (about 25% of it), whereas the rest
  of the second screen is black. Like this:

  
   
  #  # #<<|...#
  # Login# #<<|.Black.#
  #  # #<<|...#
   

  The part marked with "<<" is the rightest part of the background image
  of the first screen. I've seen this after updating to xorg/xserver-
  hwe-16.04, whereas installing the hwe kernel alone did not make this
  happen.

  Nevertheless, I can login and everything is fine again. Both screens
  look as they should. (I had to reconfigure monitors once after
  updating to xorg/xserver-hwe-16.04).

  sylog shows:

  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not assign CRTC to outputs, ignoring configuration
  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not make default configuration for current output layout, leaving 
unconfigured

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-flashback 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Feb 18 07:46:46 2017
  InstallationDate: Installed on 2014-11-29 (812 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-flashback
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1665853/+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 1665853] Re: HWE 16.04.2: Login Screen goes partially black after upgrade (Dual Screen)

2017-02-18 Thread Thomas Mayer
** Summary changed:

- Gnome Flashback: Could not assign CRTC to outputs, ignoring configuration
+ HWE 16.04.2: Login Screen goes partially black after upgrade (Dual Screen)

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

Title:
  HWE 16.04.2: Login Screen goes partially black after upgrade (Dual
  Screen)

Status in gnome-flashback package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using ubuntu 16.04, up-to-date, HWE kernel 4.8.0-36-generic.

  On dual screen setup, during system login, the first screen stretches
  over a part of the second screen (about 25% of it), whereas the rest
  of the second screen is black. Like this:

  
   
  #  # #<<|...#
  # Login# #<<|.Black.#
  #  # #<<|...#
   

  The part marked with "<<" is the rightest part of the background image
  of the first screen. I've seen this after updating to xorg/xserver-
  hwe-16.04, whereas installing the hwe kernel alone did not make this
  happen.

  Nevertheless, I can login and everything is fine again. Both screens
  look as they should. (I had to reconfigure monitors once after
  updating to xorg/xserver-hwe-16.04).

  sylog shows:

  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not assign CRTC to outputs, ignoring configuration
  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not make default configuration for current output layout, leaving 
unconfigured

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-flashback 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Feb 18 07:46:46 2017
  InstallationDate: Installed on 2014-11-29 (812 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-flashback
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1665853/+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 1665853] Re: Gnome Flashback: Could not assign CRTC to outputs, ignoring configuration

2017-02-18 Thread Thomas Mayer
The path was wrong in #6 (I forgot the /.config/

Copying

/home//.config/monitors.xml

to

/var/lib/lightdm/.config/monitors.xml

fixes this issue for me (see image attached).

Btw.: After upgrade to new HWE/Xorg I had to resize my monitors to get
rid of similar situations for the gnome session itself. That could be
done by reajusting resolution two times (go for wrong resolution and
back to right resolution). But that could be done via GUI (system
settings/displax devices). Be that a bug in itself or not, I think it is
not convenient, at least.

However, the GUI setting did not affect lightdm monitor settings. Only
copying monitors.xml to /var/lib/lightdm/.config/ did.

For lightdm, I think this is a bug, just because it requires non-GUI
user interaction. Average users should not be tricked into such
situations.

** Attachment added: "CIMG1107.JPG"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1665853/+attachment/4821679/+files/CIMG1107.JPG

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

Title:
  Gnome Flashback: Could not assign CRTC to outputs, ignoring
  configuration

Status in gnome-flashback package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using ubuntu 16.04, up-to-date, HWE kernel 4.8.0-36-generic.

  On dual screen setup, during system login, the first screen stretches
  over a part of the second screen (about 25% of it), whereas the rest
  of the second screen is black. Like this:

  
   
  #  # #<<|...#
  # Login# #<<|.Black.#
  #  # #<<|...#
   

  The part marked with "<<" is the rightest part of the background image
  of the first screen. I've seen this after updating to xorg/xserver-
  hwe-16.04, whereas installing the hwe kernel alone did not make this
  happen.

  Nevertheless, I can login and everything is fine again. Both screens
  look as they should. (I had to reconfigure monitors once after
  updating to xorg/xserver-hwe-16.04).

  sylog shows:

  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not assign CRTC to outputs, ignoring configuration
  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not make default configuration for current output layout, leaving 
unconfigured

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-flashback 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Feb 18 07:46:46 2017
  InstallationDate: Installed on 2014-11-29 (812 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-flashback
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1665853/+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 1665853] Re: Gnome Flashback: Could not assign CRTC to outputs, ignoring configuration

2017-02-18 Thread Thomas Mayer
@mitya57 @muktupavels thanks for reporting back.

Directory /var/lib/lightdm was empty in my case:

/var/lib/lightdm# ls -lh #as root user
insgesamt 0

Copying

/home//.config/monitors.xml

to

/var/lib/lightdm/monitors.xml

does not fix this issue.

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

Title:
  Gnome Flashback: Could not assign CRTC to outputs, ignoring
  configuration

Status in gnome-flashback package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using ubuntu 16.04, up-to-date, HWE kernel 4.8.0-36-generic.

  On dual screen setup, during system login, the first screen stretches
  over a part of the second screen (about 25% of it), whereas the rest
  of the second screen is black. Like this:

  
   
  #  # #<<|...#
  # Login# #<<|.Black.#
  #  # #<<|...#
   

  The part marked with "<<" is the rightest part of the background image
  of the first screen. I've seen this after updating to xorg/xserver-
  hwe-16.04, whereas installing the hwe kernel alone did not make this
  happen.

  Nevertheless, I can login and everything is fine again. Both screens
  look as they should. (I had to reconfigure monitors once after
  updating to xorg/xserver-hwe-16.04).

  sylog shows:

  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not assign CRTC to outputs, ignoring configuration
  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not make default configuration for current output layout, leaving 
unconfigured

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-flashback 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Feb 18 07:46:46 2017
  InstallationDate: Installed on 2014-11-29 (812 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-flashback
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1665853/+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 1665853] Re: Gnome Flashback: Could not assign CRTC to outputs, ignoring configuration

2017-02-18 Thread Thomas Mayer
** Also affects: xorg (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-flashback (Ubuntu)
   Status: New => Invalid

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

Title:
  Gnome Flashback: Could not assign CRTC to outputs, ignoring
  configuration

Status in gnome-flashback package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using ubuntu 16.04, up-to-date, HWE kernel 4.8.0-36-generic.

  On dual screen setup, during system login, the first screen stretches
  over a part of the second screen (about 25% of it), whereas the rest
  of the second screen is black. Like this:

  
   
  #  # #<<|...#
  # Login# #<<|.Black.#
  #  # #<<|...#
   

  The part marked with "<<" is the rightest part of the background image
  of the first screen. I've seen this after updating to xorg/xserver-
  hwe-16.04, whereas installing the hwe kernel alone did not make this
  happen.

  Nevertheless, I can login and everything is fine again. Both screens
  look as they should. (I had to reconfigure monitors once after
  updating to xorg/xserver-hwe-16.04).

  sylog shows:

  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not assign CRTC to outputs, ignoring configuration
  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not make default configuration for current output layout, leaving 
unconfigured

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-flashback 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Feb 18 07:46:46 2017
  InstallationDate: Installed on 2014-11-29 (812 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-flashback
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1665853/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2017-01-31 Thread Thomas Mayer
Im on xenial 16.04, Kernel 4.4.0-59-generic. Still get this message.

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2017-01-31 Thread Thomas Mayer
I get this message in a row with cups messages:

Jan 31 07:35:09 lat61 systemd[1]: Stopping Make remote CUPS printers available 
locally...
Jan 31 07:35:09 lat61 systemd[1]: Stopped Make remote CUPS printers available 
locally.
Jan 31 07:35:09 lat61 systemd[1]: Stopping CUPS Scheduler...
Jan 31 07:35:09 lat61 systemd[1]: Stopped CUPS Scheduler.
Jan 31 07:35:09 lat61 systemd[1]: Started CUPS Scheduler.
Jan 31 07:35:09 lat61 systemd[1]: Started Make remote CUPS printers available 
locally.
Jan 31 07:35:09 lat61 colord[1368]: (colord:1368): Cd-WARNING **: failed to get 
session [pid 24360]: Kein passendes Gerät bzw. keine passende Adresse gefunden


Note that I have a Kyocera FS-1020D printer. Which is _not_ from HP.

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1660314] Re: apparmor blocks recently used files (in firefox)

2017-01-30 Thread Thomas Mayer
FF's apparmor profile shipped with 51.0.1 contains a line

deny @{HOME}/.local/share/recently-used.xbel r,

which leads to this issue.

I removed the line in a patch named "VERSION 6" provided at
https://bugs.launchpad.net/bugs/1659988

That said, this issue
- is 100% related to the firefox package (which contains that profile
- not related to apparmor itself

** Also affects: firefox
   Importance: Undecided
   Status: New

** No longer affects: apparmor (Ubuntu)

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

Title:
  apparmor blocks recently used files (in firefox)

Status in Mozilla Firefox:
  New

Bug description:
  Taken from syslog:

  Jan 30 12:55:35 lat61 gnome-session[3140]: (firefox:4627): Gtk-WARNING
  **: Attempting to read the recently used resources file at
  '/home/thomas/.local/share/recently-used.xbel', but the parser failed:
  Datei »/home/thomas/.local/share/recently-used.xbel« konnte nicht
  geöffnet werden: Keine Berechtigung.

  
  It says 'no permission' whereas I can perfectly read it with the same system 
user:

  wc -l recently-used.xbel
  4 recently-used.xbel

  
  That said, I assume it's apparmor related, similar to 
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1377140

  ... just that the path changed AGAIN.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jan 30 13:01:07 2017
  InstallationDate: Installed on 2014-11-29 (793 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-59-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (228 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1660314/+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 1660314] [NEW] apparmor blocks recently used files (in firefox)

2017-01-30 Thread Thomas Mayer
Public bug reported:

Taken from syslog:

Jan 30 12:55:35 lat61 gnome-session[3140]: (firefox:4627): Gtk-WARNING
**: Attempting to read the recently used resources file at
'/home/thomas/.local/share/recently-used.xbel', but the parser failed:
Datei »/home/thomas/.local/share/recently-used.xbel« konnte nicht
geöffnet werden: Keine Berechtigung.


It says 'no permission' whereas I can perfectly read it with the same system 
user:

wc -l recently-used.xbel
4 recently-used.xbel


That said, I assume it's apparmor related, similar to 
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1377140

... just that the path changed AGAIN.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor 2.10.95-0ubuntu2.5
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Mon Jan 30 13:01:07 2017
InstallationDate: Installed on 2014-11-29 (793 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-59-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: apparmor
UpgradeStatus: Upgraded to xenial on 2016-06-15 (228 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  apparmor blocks recently used files (in firefox)

Status in apparmor package in Ubuntu:
  New

Bug description:
  Taken from syslog:

  Jan 30 12:55:35 lat61 gnome-session[3140]: (firefox:4627): Gtk-WARNING
  **: Attempting to read the recently used resources file at
  '/home/thomas/.local/share/recently-used.xbel', but the parser failed:
  Datei »/home/thomas/.local/share/recently-used.xbel« konnte nicht
  geöffnet werden: Keine Berechtigung.

  
  It says 'no permission' whereas I can perfectly read it with the same system 
user:

  wc -l recently-used.xbel
  4 recently-used.xbel

  
  That said, I assume it's apparmor related, similar to 
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1377140

  ... just that the path changed AGAIN.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jan 30 13:01:07 2017
  InstallationDate: Installed on 2014-11-29 (793 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-59-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (228 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1660314/+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 1628956] Re: From v49.0, Firefox needs read access to @{PROC}/net/arp

2017-01-28 Thread Thomas Mayer
A patch which might fix this issue, too, is available at 1659988.

https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988

Everyone affected, please give it a try and report back.

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

Title:
  From v49.0, Firefox needs read access to @{PROC}/net/arp

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Since the latest upgrade of Firefox to 49.0, it will need read access
  to @{PROC}/net/arp

  I don't know what the security implications are, so I don't know if we
  want to give read access to explicitely deny it. Both seem to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor-profiles 2.10.95-0ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 29 16:55:21 2016
  InstallationDate: Installed on 2015-10-04 (361 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet 
splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   Sep 29 10:37:52 franck-ThinkPad-T430s dbus[2546]: [system] AppArmor D-Bus 
mediation is enabled
   Sep 29 16:50:57 franck-ThinkPad-T430s dbus[2410]: [system] AppArmor D-Bus 
mediation is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.sbin.klogd: [modified]
  modified.conffile..etc.apparmor.d.sbin.syslogd: [modified]
  modified.conffile..etc.apparmor.d.usr.bin.chromium-browser: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified]
  mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535
  mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968
  mtime.conffile..etc.apparmor.d.usr.bin.chromium-browser: 
2015-10-05T12:02:05.273141
  mtime.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: 
2016-04-13T19:13:25.829679
  mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-13T19:13:05.941424
  mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323
  mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403
  mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523
  mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794
  mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2016-04-13T19:14:17.520643
  mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628956/+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 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab

2017-01-13 Thread Thomas Mayer
The warning appears although I use UUIDs all over the place in my
/etc/fstab.

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

Title:
  update-initramfs cryptsetup must correctly take into account PARTLABEL
  inside /etc/fstab

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Systematically,

  -  With a /etc/fstab using UUID or LABEL, update-initramfs works
  correctly

  -  With a /etc/fstab using PARTLABEL, update-initramfs displays following 
error messages :
  cryptsetup: WARNING: failed to detect canonical device of 
PARTLABEL=Ubuntu-Gnome
  cryptsetup: WARNING: could not determine root device from /etc/fstab
  cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu

  The cryptsetup part of update-initramfs must correctly take into
  account PARTLABEL inside /etc/fstab

  Thank you in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue May 10 21:14:24 2016
  InstallationDate: Installed on 2014-11-03 (553 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+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 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab

2017-01-13 Thread Thomas Mayer
A also need to add that my hard disks are unencrypted from the
perspective of the OS (I use hardware encrypted SSDs).

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

Title:
  update-initramfs cryptsetup must correctly take into account PARTLABEL
  inside /etc/fstab

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Systematically,

  -  With a /etc/fstab using UUID or LABEL, update-initramfs works
  correctly

  -  With a /etc/fstab using PARTLABEL, update-initramfs displays following 
error messages :
  cryptsetup: WARNING: failed to detect canonical device of 
PARTLABEL=Ubuntu-Gnome
  cryptsetup: WARNING: could not determine root device from /etc/fstab
  cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu

  The cryptsetup part of update-initramfs must correctly take into
  account PARTLABEL inside /etc/fstab

  Thank you in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue May 10 21:14:24 2016
  InstallationDate: Installed on 2014-11-03 (553 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+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 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab

2017-01-13 Thread Thomas Mayer
Doing updates with apt-get, I get messages like

cryptsetup: WARNING: failed to detect canonical device of /dev/sdXY

Besides the warning message, everything seems to run fine.

I'm using ubuntu 16.04 with recent updates.

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

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

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

Title:
  update-initramfs cryptsetup must correctly take into account PARTLABEL
  inside /etc/fstab

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Systematically,

  -  With a /etc/fstab using UUID or LABEL, update-initramfs works
  correctly

  -  With a /etc/fstab using PARTLABEL, update-initramfs displays following 
error messages :
  cryptsetup: WARNING: failed to detect canonical device of 
PARTLABEL=Ubuntu-Gnome
  cryptsetup: WARNING: could not determine root device from /etc/fstab
  cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu

  The cryptsetup part of update-initramfs must correctly take into
  account PARTLABEL inside /etc/fstab

  Thank you in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue May 10 21:14:24 2016
  InstallationDate: Installed on 2014-11-03 (553 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+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 1639413] Re: network-manager only shows one wifi

2016-11-05 Thread Thomas Mayer
** Attachment added: "This is how it looks like after restarting 
network-manager"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639413/+attachment/4772822/+files/Men%C3%BC_056.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/1639413

Title:
  network-manager only shows one wifi

Status in network-manager package in Ubuntu:
  New

Bug description:
  First of all, my wifi is working great most of the time, at least as
  long as I don't use other network connections (rj45) and as long as I
  do not suspend/resume and as long as I don't touch my hardware rfkill-
  switch.

  But, as it turns out, from time to time network manager
  - can't see my wifi SSID any more ("net" in the screen shot is some 
other random wifi in the neighborhood).
  - can't see any SSID in the neighborhood except one

  Result: I can't reconnect to my wifi

  Suggested Fix: network-manager should not loose the connection in the
  first place or at least rescan the wifi neighborhood and reconnect to
  my wifi.

  Additional information: The configuration of my wifi is not lost. As
  soon as a scan is performed, network-manager finds it and connects to
  it. To initiate such a scan, I'm using this

  Workaround:
  sudo service network-manager restart

  After that, network-manager performs a new scan, all SSIDs which are
  available are found again and network-manager connects me to my wifi
  automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Nov  5 07:53:26 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-11-29 (707 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (142 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-12-14T17:38:01.900655
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639413/+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 1639413] [NEW] network-manager only shows one wifi

2016-11-05 Thread Thomas Mayer
Public bug reported:

First of all, my wifi is working great most of the time, at least as
long as I don't use other network connections (rj45) and as long as I do
not suspend/resume and as long as I don't touch my hardware rfkill-
switch.

But, as it turns out, from time to time network manager
- can't see my wifi SSID any more ("net" in the screen shot is some 
other random wifi in the neighborhood).
- can't see any SSID in the neighborhood except one

Result: I can't reconnect to my wifi

Suggested Fix: network-manager should not loose the connection in the
first place or at least rescan the wifi neighborhood and reconnect to my
wifi.

Additional information: The configuration of my wifi is not lost. As
soon as a scan is performed, network-manager finds it and connects to
it. To initiate such a scan, I'm using this

Workaround:
sudo service network-manager restart

After that, network-manager performs a new scan, all SSIDs which are
available are found again and network-manager connects me to my wifi
automatically.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sat Nov  5 07:53:26 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-11-29 (707 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to xenial on 2016-06-15 (142 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-12-14T17:38:01.900655
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug xenial

** Attachment added: "Scan reports one wify only (which is not mine but a 
random one)"
   
https://bugs.launchpad.net/bugs/1639413/+attachment/4772802/+files/Men%C3%BC_054.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/1639413

Title:
  network-manager only shows one wifi

Status in network-manager package in Ubuntu:
  New

Bug description:
  First of all, my wifi is working great most of the time, at least as
  long as I don't use other network connections (rj45) and as long as I
  do not suspend/resume and as long as I don't touch my hardware rfkill-
  switch.

  But, as it turns out, from time to time network manager
  - can't see my wifi SSID any more ("net" in the screen shot is some 
other random wifi in the neighborhood).
  - can't see any SSID in the neighborhood except one

  Result: I can't reconnect to my wifi

  Suggested Fix: network-manager should not loose the connection in the
  first place or at least rescan the wifi neighborhood and reconnect to
  my wifi.

  Additional information: The configuration of my wifi is not lost. As
  soon as a scan is performed, network-manager finds it and connects to
  it. To initiate such a scan, I'm using this

  Workaround:
  sudo service network-manager restart

  After that, network-manager performs a new scan, all SSIDs which are
  available are found again and network-manager connects me to my wifi
  automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Nov  5 07:53:26 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-11-29 (707 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (142 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-12-14T17:38:01.900655
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  en

[Touch-packages] [Bug 1502173] Re: Python warnings: modules imported without specifying a version first

2016-08-10 Thread Thomas Mayer
Numan's workaround did the trick for me (with up-to-date ubuntu 16.04).
The warning does not occur after that.

https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1502173/comments/3

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

Title:
  Python warnings: modules imported without specifying a version first

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here is the problem:

  $ /usr/share/apport/apport-gtk
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
  /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without 
specifying a version first. Use gi.require_version('GdkX11', '3.0') before 
import to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apport-gtk 2.19-0ubuntu1
  Uname: Linux 4.2.2-040202-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Oct  2 16:17:14 2015
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1502173/+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 1447099] Re: /sbin/upstart:indicator-session-unknown-user-error

2016-07-19 Thread Thomas Mayer
I updated from 14.04 to 16.04. That said, xenial is also affected.
Apport error message was shown shortly after login.

Apport forwarded me to https://bugs.launchpad.net/bugs/1452849 which
duplicates this issue.

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

Title:
  /sbin/upstart:indicator-session-unknown-user-error

Status in upstart :
  New
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Vivid:
  Confirmed
Status in upstart source package in Wily:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding upstart.  This problem was most recently seen with version
  1.13.2-0ubuntu13, the problem page at
  https://errors.ubuntu.com/problem/09ab1b2ed4cff7556ed135307deb9f99c107193a
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1447099/+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 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking

2016-07-16 Thread Thomas Mayer
Plus, is bluetooth not operational after suspend/resume, while blocks
are not set:

rfkill list bluetooth
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
13: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

Again, a "sudo service bluetooth restart" helps after suspend/resume.


** Summary changed:

- bluetooth unavailable after rfkill hard (or soft) unblocking
+ bluetooth unavailable after rfkill hard (or soft) unblocking and after 
suspend/resume

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

Title:
  bluetooth unavailable after rfkill hard (or soft) unblocking and after
  suspend/resume

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  DELL Latitude E5510 has a hardware switch to disable and enable
  bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
  terms of wifi, this works great: After hard unblocking, the device
  resumes back to normal operation without any manual intervention. That
  was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

  In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
  is not working any more:

  After hard blocking and unblocking

  - bluetooth is not working at all
  - the applet-indicator remains gray
  - bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
  - rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
  rfkill list bluetooth
  2: dell-bluetooth: Bluetooth
   Soft blocked: no
   Hard blocked: no
  8: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no

  The device is a
  sudo lsusb
  Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

  Workaround: After a

  sudo service bluetooth restart

  the bluetooth device turns back to normal operation and the applet-
  indicator turns from gray to black (available).

  Suggested fix: Make the workaround obsolete.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jul 17 04:00:58 2016
  InstallationDate: Installed on 2014-11-29 (595 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5510
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1603715/+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 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking

2016-07-16 Thread Thomas Mayer
For the unreleased soft blocking, I can work around with a second

rfkill unblock bluetooth

Executing this twice makes applet-indicator black again and bluetooth is
operational (without "sudo service bluetooth restart" after a soft
unblock).

To sum it up: There's three cases:

- hard unblock with released hard block
- soft unblock with unreleased soft block for hci0
- soft unblock with released soft block for hci0

All of them with gray indicator-applet and bluetooth non-operational.

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

Title:
  bluetooth unavailable after rfkill hard (or soft) unblocking

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  DELL Latitude E5510 has a hardware switch to disable and enable
  bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
  terms of wifi, this works great: After hard unblocking, the device
  resumes back to normal operation without any manual intervention. That
  was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

  In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
  is not working any more:

  After hard blocking and unblocking

  - bluetooth is not working at all
  - the applet-indicator remains gray
  - bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
  - rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
  rfkill list bluetooth
  2: dell-bluetooth: Bluetooth
   Soft blocked: no
   Hard blocked: no
  8: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no

  The device is a
  sudo lsusb
  Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

  Workaround: After a

  sudo service bluetooth restart

  the bluetooth device turns back to normal operation and the applet-
  indicator turns from gray to black (available).

  Suggested fix: Make the workaround obsolete.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jul 17 04:00:58 2016
  InstallationDate: Installed on 2014-11-29 (595 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5510
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1603715/+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 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking

2016-07-16 Thread Thomas Mayer
About every second time, I get a

rfkill unblock bluetooth
thomas@lat61:~$ rfkill list bluetooth
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
11: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

which is what debian bug 812150 is about.

Note that the soft block got released for "2: dell-bluetooth" but not
for "11: hci0"

This is different from the hard unblock, where both hard blocks were
released.

But no matter if hard or soft block and if released or not, bluetooth is
not working after any sort of unblocking operation.

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

Title:
  bluetooth unavailable after rfkill hard (or soft) unblocking

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  DELL Latitude E5510 has a hardware switch to disable and enable
  bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
  terms of wifi, this works great: After hard unblocking, the device
  resumes back to normal operation without any manual intervention. That
  was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

  In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
  is not working any more:

  After hard blocking and unblocking

  - bluetooth is not working at all
  - the applet-indicator remains gray
  - bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
  - rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
  rfkill list bluetooth
  2: dell-bluetooth: Bluetooth
   Soft blocked: no
   Hard blocked: no
  8: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no

  The device is a
  sudo lsusb
  Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

  Workaround: After a

  sudo service bluetooth restart

  the bluetooth device turns back to normal operation and the applet-
  indicator turns from gray to black (available).

  Suggested fix: Make the workaround obsolete.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jul 17 04:00:58 2016
  InstallationDate: Installed on 2014-11-29 (595 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5510
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1603715/+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 1603715] Re: bluetooth unavailable after rfkill hard blocking and unblocking

2016-07-16 Thread Thomas Mayer
Same behaviour for soft blocking the device:

rfkill block bluetooth

rfkill list bluetooth
2: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no

rfkill unblock bluetooth
rfkill list bluetooth
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
9: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

Result: Bluetooth not working and indicator-applet is gray.

There's already a debian bug for soft unblocking:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812150

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

** Also affects: systemd via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812150
   Importance: Unknown
   Status: Unknown

** Summary changed:

- bluetooth unavailable after rfkill hard blocking and unblocking
+ bluetooth unavailable after rfkill hard (or soft) unblocking

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

Title:
  bluetooth unavailable after rfkill hard (or soft) unblocking

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  DELL Latitude E5510 has a hardware switch to disable and enable
  bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
  terms of wifi, this works great: After hard unblocking, the device
  resumes back to normal operation without any manual intervention. That
  was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

  In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
  is not working any more:

  After hard blocking and unblocking

  - bluetooth is not working at all
  - the applet-indicator remains gray
  - bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
  - rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
  rfkill list bluetooth
  2: dell-bluetooth: Bluetooth
   Soft blocked: no
   Hard blocked: no
  8: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no

  The device is a
  sudo lsusb
  Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

  Workaround: After a

  sudo service bluetooth restart

  the bluetooth device turns back to normal operation and the applet-
  indicator turns from gray to black (available).

  Suggested fix: Make the workaround obsolete.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jul 17 04:00:58 2016
  InstallationDate: Installed on 2014-11-29 (595 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5510
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1603715/+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 1603715] Re: bluetooth unavailable after rfkill hard blocking and unblocking

2016-07-16 Thread Thomas Mayer
This issue is not tlp related as still occurs without tlp (with laptop-
mode-tools instead).

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

Title:
  bluetooth unavailable after rfkill hard blocking and unblocking

Status in systemd package in Ubuntu:
  New

Bug description:
  DELL Latitude E5510 has a hardware switch to disable and enable
  bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
  terms of wifi, this works great: After hard unblocking, the device
  resumes back to normal operation without any manual intervention. That
  was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

  In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
  is not working any more:

  After hard blocking and unblocking

  - bluetooth is not working at all
  - the applet-indicator remains gray
  - bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
  - rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
  rfkill list bluetooth
  2: dell-bluetooth: Bluetooth
   Soft blocked: no
   Hard blocked: no
  8: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no

  The device is a
  sudo lsusb
  Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

  Workaround: After a

  sudo service bluetooth restart

  the bluetooth device turns back to normal operation and the applet-
  indicator turns from gray to black (available).

  Suggested fix: Make the workaround obsolete.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jul 17 04:00:58 2016
  InstallationDate: Installed on 2014-11-29 (595 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5510
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1603715/+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 1603715] [NEW] bluetooth unavailable after rfkill hard blocking and unblocking

2016-07-16 Thread Thomas Mayer
Public bug reported:

DELL Latitude E5510 has a hardware switch to disable and enable
bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
terms of wifi, this works great: After hard unblocking, the device
resumes back to normal operation without any manual intervention. That
was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this is
not working any more:

After hard blocking and unblocking

- bluetooth is not working at all
- the applet-indicator remains gray
- bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
- rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
rfkill list bluetooth
2: dell-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: no
8: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

The device is a
sudo lsusb
Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

Workaround: After a

sudo service bluetooth restart

the bluetooth device turns back to normal operation and the applet-
indicator turns from gray to black (available).

Suggested fix: Make the workaround obsolete.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Jul 17 04:00:58 2016
InstallationDate: Installed on 2014-11-29 (595 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Latitude E5510
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
dmi.bios.date: 12/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 023HKR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

** Description changed:

  DELL Latitude E5510 has a hardware switch to disable and enable
- bluetooth and wifi devices ("hard blocking" in terms of rfkill. In terms
- of wifi, this works great: After hard unblocking the device resumes to
- normal operation with no manual intervention. That was also working with
- bluetooth as of 14.04, kernel 4.2.
+ bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
+ terms of wifi, this works great: After hard unblocking, the device
+ resumes back to normal operation without any manual intervention. That
+ was also working with bluetooth as of ubuntu 14.04, kernel 4.2.
  
  In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this is
  not working any more:
  
  After hard blocking and unblocking
  
  - bluetooth is not working at all
  - the applet-indicator remains gray
  - bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
  - rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
  rfkill list bluetooth
  2: dell-bluetooth: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  Soft blocked: no
+  Hard blocked: no
  8: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  Soft blocked: no
+  Hard blocked: no
  
  The device is a
  sudo lsusb
  Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
  
  Workaround: After a
  
  sudo service bluetooth restart
  
  the bluetooth device turns back to normal operation and the applet-
  indicator turns from gray to black (available).
  
  Suggested fix: Make the workaround obsolete.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jul 17 04:00:58 2016
  InstallationDate: Installed on 2014-11-29 (595 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5510
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016

[Touch-packages] [Bug 1528843] Re: Fonts missing after suspend

2016-07-07 Thread Thomas Mayer
Btw. why has this issue low priority only? It's nearly as bad as if
xserver crashes, including possible loss of unsaved data. User has to
reboot which can only be done "blind" or by pressing a hardware power
button (which can be harmful in itsself again).

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

Title:
  Fonts missing after suspend

Status in xorg package in Ubuntu:
  Expired

Bug description:
  After resuming from suspend cairo-dock disappears and all gnome
  applications show only the letters "s" and """. The rest of the
  letters is blank. Hope I still manage to file a bug report and to run
  apport-collect on it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+12ubuntu1
  Uname: Linux 4.4.0-040400rc5-lowlatency x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 23 13:46:41 2015
  EcryptfsInUse: Yes
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  Package: xorg 1:7.7+12ubuntu1
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 4.4.0-040400rc5-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1528843/+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 1528843] Re: Fonts missing after suspend

2016-07-07 Thread Thomas Mayer
I had the same issue for a long time in 14.04 at least together with
kernel 4.2 (and very likely 3.19 and maybe even before if I remember
right).

It is still not fixed in ubuntu 16.04, kernel 4.4.0-28-generic.

I get this problem mostly after suspend. But I rarely get the invisible
characters also during a normal session when I click something (about
every few days). I could not yet reproduce if it depends on the object I
click or if there is a pattern to reproduce it.

Tested hardware: Latitude E5510, CPU/GPU Intel core i5 520M, using the on-chip 
graphics.
I have an PR02X docking station and a dual monitor setup (2x external BenQ 
GW2460 via DVI) when this error happens. The problem does not occor when using 
the internal monitor of the laptop only.

Please note that my on-chip-GPU can handle two monitors only. Basically
that means that the internal monitor is switched off automatically as
soon as I use the two external monitors. So far this is working fine,
however.

uname -a
Linux lat61 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  Fonts missing after suspend

Status in xorg package in Ubuntu:
  Expired

Bug description:
  After resuming from suspend cairo-dock disappears and all gnome
  applications show only the letters "s" and """. The rest of the
  letters is blank. Hope I still manage to file a bug report and to run
  apport-collect on it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+12ubuntu1
  Uname: Linux 4.4.0-040400rc5-lowlatency x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 23 13:46:41 2015
  EcryptfsInUse: Yes
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  Package: xorg 1:7.7+12ubuntu1
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 4.4.0-040400rc5-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1528843/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2016-06-18 Thread Thomas Mayer
I guess I know why upstream cairo never made it into Firefox: Mozilla's
version of cairo is more like a fork than a version of cairo with a few
patches applied.

Not only that: Some of the patches are documented in .patch files and a
README. And some are not documented at all with just the change in the
lib's files. E. g. https://hg.mozilla.org/mozilla-
central/rev/0edb40641826 does not have a .patch file or README entry.

These days, it would make sense to maintain a git branch of cairo with
all the patches applied. Then they would be able to simply merge. And
have a dependency to that branch.

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  New
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2016-06-18 Thread Thomas Mayer
In ubuntu 16.04, I tried out the libcairo which ubuntu comes shipped
with and compiled FF47.0 myself, using the build-option --enable-system-
cairo.

After the change, it works: I can finally print https://www.dab-
bank.de/Service/Kontakt/ on my old Kyocera fs-1020d. Same for
https://boerse.dab-bank.de/maerkte-kurse/aktien.html.

This is the version of libcairo I used (and which also worked!):

apt-cache show libcairo2
Source: cairo
Version: 1.14.6-1

I made the build with:

sudo apt-get install packaging-dev libcairo2 libcairo2-dev
<= install all the dependencies for the build

pull-lp-source firefox xenial
cd firefox-47.0+build3/
echo "ac_add_options --enable-system-cairo" >> debian/config/mozconfig.in
dpkg-buildpackage -rfakeroot -uc -b
sudo dpkg -i firefox_47.0+build3-0ubuntu0.16.04.1_amd64.deb

@till-kamppeter Would it be possible to build FF and TB with --enable-
system-cairo in the distro, now that it works? I did not run any further
testing yet, however. Just my testcase works now and fixes this issue
for FF.

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  New
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2016-06-17 Thread Thomas Mayer
As of ubuntu 16.04, I can now print some PDFs in evince (16.04 ships
v3.18.2), which were not printable before. Therefore, I don't have to
use okular for that purpose any more (workaround for 14.04).

Basically, if FF knew about a new libcairo and that helped, this whole
issue would be fixed for 16.04 at least (in respect to my printer and my
scenarios). Please try the --enable-system-cairo compile option. If it
works, maybe a backport to 14.04 is possible as well.

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  New
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2016-06-17 Thread Thomas Mayer
@till-kamppeter As of Firefox 47.0, ubuntu 16.04, this is still not
fixed.

During the update (coming from 14.04) I got asked via cups configuration
if I wanted to opt-in for pre-filtering via cups. Which I opted in, in
the hope that pdfs get rendered in a way my old printer is capable to
understand. Still, it does not work.

I still think it's all about the ancient libcairo version FF is shipped
with.

There is a FF compiler option --enable-system-cairo which enables the
cairo version ubuntu comes shipped with. Would you like to give it a
try?

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  New
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/802942/+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 1592948] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess installiertes post-installation-Skript wurde durch Signal (Beendet) getötet

2016-06-15 Thread Thomas Mayer
The problem is gone as soon as cups is properly configured as described
in the workaround in #1592917. So this workaround is also suitable for
#1592948.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript wurde durch Signal (Beendet)
  getötet

Status in cups package in Ubuntu:
  New

Bug description:
  happened after failed upgrade from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 15 20:25:32 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript wurde durch 
Signal (Beendet) getötet
  InstallationDate: Installed on 2014-11-29 (564 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat:
   device for FS-1020D: socket://fs1020d.fritz.box:9100
   device for FS-C5150DN: socket://192.168.178.33:9100
   device for FS-C5150DN-COLOR: socket://192.168.178.33:9100
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0c45:6419 Microdia Integrated Webcam
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E5510
  Papersize: a4
  PpdFiles:
   FS-C5150DN-COLOR: Kyocera FS-C5150DN (KPDL)
   FS-C5150DN: Kyocera FS-C5150DN (KPDL)
   FS-1020D: Kyocera Mita FS-1020D
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript wurde durch Signal (Beendet) getötet
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (0 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-07-23T00:20:18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1592948/+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 1592948] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess installiertes post-installation-Skript wurde durch Signal (Beendet) getötet

2016-06-15 Thread Thomas Mayer
This happened AFTER the problem reported via issue #1592917 . It's what
ubuntu wanted to report automatically (cups failed because configuration
failed during upgrade from 14.04 to 16.04).

related: #1592917

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript wurde durch Signal (Beendet)
  getötet

Status in cups package in Ubuntu:
  New

Bug description:
  happened after failed upgrade from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 15 20:25:32 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript wurde durch 
Signal (Beendet) getötet
  InstallationDate: Installed on 2014-11-29 (564 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat:
   device for FS-1020D: socket://fs1020d.fritz.box:9100
   device for FS-C5150DN: socket://192.168.178.33:9100
   device for FS-C5150DN-COLOR: socket://192.168.178.33:9100
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0c45:6419 Microdia Integrated Webcam
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E5510
  Papersize: a4
  PpdFiles:
   FS-C5150DN-COLOR: Kyocera FS-C5150DN (KPDL)
   FS-C5150DN: Kyocera FS-C5150DN (KPDL)
   FS-1020D: Kyocera Mita FS-1020D
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript wurde durch Signal (Beendet) getötet
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (0 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-07-23T00:20:18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1592948/+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 1592948] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess installiertes post-installation-Skript wurde durch Signal (Beendet) getötet

2016-06-15 Thread Thomas Mayer
Public bug reported:

happened after failed upgrade from 14.04 to 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Jun 15 20:25:32 2016
ErrorMessage: Unterprozess installiertes post-installation-Skript wurde durch 
Signal (Beendet) getötet
InstallationDate: Installed on 2014-11-29 (564 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Lpstat:
 device for FS-1020D: socket://fs1020d.fritz.box:9100
 device for FS-C5150DN: socket://192.168.178.33:9100
 device for FS-C5150DN-COLOR: socket://192.168.178.33:9100
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0c45:6419 Microdia Integrated Webcam
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E5510
Papersize: a4
PpdFiles:
 FS-C5150DN-COLOR: Kyocera FS-C5150DN (KPDL)
 FS-C5150DN: Kyocera FS-C5150DN (KPDL)
 FS-1020D: Kyocera Mita FS-1020D
ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript wurde durch Signal (Beendet) getötet
UpgradeStatus: Upgraded to xenial on 2016-06-15 (0 days ago)
dmi.bios.date: 12/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 023HKR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.cups:
 # Cups configure options
 
 # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
 # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
 # LOAD_LP_MODULE=yes
mtime.conffile..etc.default.cups: 2014-07-23T00:20:18

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


** Tags: amd64 apport-package xenial

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript wurde durch Signal (Beendet)
  getötet

Status in cups package in Ubuntu:
  New

Bug description:
  happened after failed upgrade from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 15 20:25:32 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript wurde durch 
Signal (Beendet) getötet
  InstallationDate: Installed on 2014-11-29 (564 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat:
   device for FS-1020D: socket://fs1020d.fritz.box:9100
   device for FS-C5150DN: socket://192.168.178.33:9100
   device for FS-C5150DN-COLOR: socket://192.168.178.33:9100
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0c45:6419 Microdia Integrated Webcam
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E5510
  Papersize: a4
  PpdFiles:
   FS-C5150DN-COLOR: Kyocera FS-C5150DN (KPDL)
   FS-C5150DN: Kyocera FS-C5150DN (KPDL)
   FS-1020D: Kyocera Mita FS-1020D
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript wurde durch Signal (Beendet) getötet
  UpgradeStatu

[Touch-packages] [Bug 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2015-09-14 Thread Thomas Mayer
I reported upstream bug report
https://bugzilla.mozilla.org/show_bug.cgi?id=1204551

** Bug watch added: Mozilla Bugzilla #1204551
   https://bugzilla.mozilla.org/show_bug.cgi?id=1204551

** Also affects: cups via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1204551
   Importance: Unknown
   Status: Unknown

** No longer affects: cups

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1204551
   Importance: Unknown
   Status: Unknown

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  Unknown
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2015-09-13 Thread Thomas Mayer
As far as I can see, gecko ubstream uses cairo 1.9.5 from 2010-01-21
which they are patching over and over.

https://github.com/mozilla/gecko-dev/blob/master/gfx/cairo/README
http://cgit.freedesktop.org/cairo/commit/?id=12d521df8acc483b2daa844d4f05dc2fe2765ba6
 (where they forked at 2010-01-21)

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2015-09-13 Thread Thomas Mayer
I guess that Cairo is part of the Gecko engine which then is used by
firefox and thunderbird.

My Firefox 40.0.3 comes shipped with Gecko/20100101 according to
about:support tab:

Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101
Firefox/40.0

which basically explains why cairo is so old (as said, cairo 1.9.5 dates
to ~2009/2010).

To sum it up, either firefox needs to get a recent gecko engine and/or
the gecko engine used for firefox needs to have a recent cairo version.

If that does not solve the problem (maybe mozilla just will not fix it
for years), then cups-filters comes into play.

Same applies for thunderbird.

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2015-09-13 Thread Thomas Mayer
Cairo 1.9.5 dates back to ~2009/2010 according to
http://cairographics.org/news/.

. My ubuntu 14.04.3 came shipped with libcairo2 package version
1.13.0~20140204-0ubuntu1.1 which dates back to ~2013/2014 according to
http://cairographics.org/news/.

I guess that Firefox 40.0.3 still comes shipped with the old Cairo
1.9.5. Basically that means that the problem eventually is solved as
soon as firefox updates to Cairo 1.13.0+.

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in cups package in Ubuntu:
  Confirmed
Status in cups-filters package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2015-09-13 Thread Thomas Mayer
I've sent the pdf files to http://pdf-analyser.edpsciences.org to see
what the difference is.

All samples provide the same set of fonts.

But there is a difference between the non-working samples and working samples:
non-working test2.pdf and print-to-file.pdf are reported to be created by cairo 
1.9.5 (http://cairographics.org)

working print-to-file-cups-from-evince.pdf is reported to be created by
cairo 1.13.1 (http://cairographics.org). Plus, print-to-file-cups-from-
evince.pdf is reported to contain an image which is reported to not be
contained by non-working print-to-file.pdf (the original of print-to-
file-cups-from-evince.pdf)

That said, it could have to do with the cairo version or with some other
piece of software which is or is not integrating this image.

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in cups package in Ubuntu:
  Confirmed
Status in cups-filters package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2015-09-13 Thread Thomas Mayer
The only workaround I'm aware of is to use the "print to file" dialog
and then print the corresponding print-to-file.pdf with evince.

When I print the file with evince, I can find a file in /var/spool/cups
which I renamed to print-to-file-cups-from-evince.pdf. Note that this
file is 15% smaller than the original.

That said, I think it has something to do with the cups-filters package.
At least, the file created by firefox can be read by evince which
basically means that it seems to be somehow valid. The processing done
by evince renders this document printable via cups on my FS-1020D
printer.

Still, I'm not happy with this workaround because printing from firefox
and thunderbird is somehow not reliable and many times I think printing
is done while it has not even started.

** Attachment added: "print-to-file-cups-from-evince.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/802942/+attachment/4463506/+files/print-to-file-cups-from-evince.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/802942

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in cups package in Ubuntu:
  Confirmed
Status in cups-filters package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2015-09-13 Thread Thomas Mayer
When I choose the "print to file" in the printing dialog in firefox, I
get a pdf print-to-file.pdf created by firefox.

I have the same problem when I try print this file with cat print-to-
file.pdf |lpr -P fs-1020d -# 1

/var/spool/cups then contains a file which I renamed to pdf print-to-
file-cups.pdf

I have the same problem when I try print this file with cat print-to-
file-cups.pdf |lpr -P fs-1020d -# 1


** Attachment added: "print-to-file.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/802942/+attachment/4463499/+files/print-to-file.tar.gz

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in cups package in Ubuntu:
  Confirmed
Status in cups-filters package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2015-09-13 Thread Thomas Mayer
** Also affects: cups-filters (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in cups package in Ubuntu:
  Confirmed
Status in cups-filters package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2015-09-13 Thread Thomas Mayer
The guys at cups do not feel responsible for linux issues as documented
in https://www.cups.org/str.php?L4715

In the meantime I further tracked it down:

- Played around with printer drivers, using Kyocera's PPD, the PPD provided by 
ubuntu and also gave PPD from 
http://www.openprinting.org/download/printdriver/debian/dists/lsb3.2/main/binary-amd64/openprinting-ppds-postscript-kyocera_20130319-1lsb3.2_all.deb
 a try.
- Tried to install lsb-printing package with no changes
- Opened firefox tab about:config and resetted all user/custom variables which 
contain string "print" in variable name

As all that did not work, I have created at least a test case:

How-To-Repeat:
- Print web page in firefox with all printing variables in firefox reset
- Lookup the spooler file in /var/spool/cups
- Try to print it directly with lpr command

Test case 1 (works):
- Print https://boerse.dab-bank.de/maerkte-kurse/aktien.html in firefox
- top shows ghostscript (gs) and foomatic-rip process
- The page is printed perfectly
- I found a file in /var/spool/cups which I renamed to test1.pdf
- Direct printing with works fine with cat test1.pdf | lpr -P fs-1020d -# 1

Test case 2 (does not work):
- Print https://www.dab-bank.de/Service/Kontakt/ in firefox
- top shows ghostscript (gs) and foomatic-rip process
- The printer receives data (status LED) and heats up, but nothing is printed. 
Printer gets available again.
- I found a file in /var/spool/cups which I renamed to test2.pdf
- Direct printing also does not work with cat test2.pdf | lpr -P fs-1020d -# 1

Basically this could mean that my printer FS-1020d does not accept the
content of test2.pdf while it most of the time works as shown with
test1.pdf

** Attachment added: "test1.pdf and test2.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+attachment/4463487/+files/test-pdfs.tar.gz

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in cups package in Ubuntu:
  Confirmed
Status in cups-filters package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: Th

[Touch-packages] [Bug 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2015-09-13 Thread Thomas Mayer
Maybe related:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/369503

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2015-09-13 Thread Thomas Mayer
There's a cups bug report which was closed unresolved:

https://www.cups.org/str.php?L3950+P-1+S0+C0+I0+E0+Qfirefox

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+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 1404762] Re: apparmor profile usr.sbin.clamd does not allow ScanOnAccess via fanotify

2015-04-07 Thread Thomas Mayer
I was describing two issues: One is that root user was needed for
ScanOnAccess. Second was that the apparmor profile does not fit.

Basically, there should be an easy way to use ScanOnAccess with correct
apparmor profile.

Fanotify seems to be a basic feature in conjunction with a virus scanner
(which can simply run in user space without a kernel module, still
getting notified about changes in files).

With the two changes I described, ScanOnAccess is working for me with
root privileges and apparmor profile disabled. Therefore, it also
detects Eicar testfiles.

I'd suggest to make ScanOnAccess more accessible to an average user.

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

Title:
  apparmor profile usr.sbin.clamd does not allow ScanOnAccess via
  fanotify

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I tried to enable the ScanOnAccess option in /etc/clamav.conf to get
  on-access scanning.

  Doing so, /var/log/clamav/clamav.log tells me:
  ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted
  ScanOnAccess: clamd must be started by root

  Setting User to root in /etc/clamav/clamd.conf
  makes the clamav-daemon to fail with

  service clamav-daemon start
   * Starting ClamAV daemon clamd
  ERROR: initgroups() failed.

  I had to disable the apparmor.profile with a
  cd /etc/apparmor.d/disable
  ln -s ./../usr.sbin.clamd

  Then, the "ERROR: initgroups() failed." disappears.

  The apparmor itself came via apt-get packages. I did not edit it.

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  apt-cache policy apparmor-profiles
  apparmor-profiles:
Installiert:   (keine)
Installationskandidat: 2.8.95~2430-0ubuntu5.1
Versionstabelle:
   2.8.95~2430-0ubuntu5.1 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   2.8.95~2430-0ubuntu5 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apparmor-profiles (not installed)
  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: Mon Dec 22 01:23:04 2014
  InstallationDate: Installed on 2014-11-29 (22 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1404762/+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 1406952] Re: systemd-udevd[471]: Error calling EVIOCSKEYCODE: Invalid argument

2015-03-10 Thread Thomas Mayer
This bug still affects me on 14.04.2, using Kernel 3.16.0-31-generic
using the original /lib/udev/hwdb.d/60-keyboard.hwdb provided by ubuntu
and ubuntu updates

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

Title:
  systemd-udevd[471]: Error calling EVIOCSKEYCODE: Invalid argument

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  during boot systemd-udevd reports:  "Error calling EVIOCSKEYCODE:
  Invalid argument"

  error message has been noted during boot and collected via dmesg. No
  device name associated with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd-services 204-5ubuntu20.9
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan  1 17:16:55 2015
  InstallationDate: Installed on 2013-05-01 (609 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1406952/+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 1404762] [NEW] apparmor profile usr.sbin.clamd does not allow ScanOnAccess via fanotify

2014-12-21 Thread Thomas Mayer
Public bug reported:

I tried to enable the ScanOnAccess option in /etc/clamav.conf to get on-
access scanning.

Doing so, /var/log/clamav/clamav.log tells me:
ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted
ScanOnAccess: clamd must be started by root

Setting User to root in /etc/clamav/clamd.conf
makes the clamav-daemon to fail with

service clamav-daemon start
 * Starting ClamAV daemon clamd
ERROR: initgroups() failed.

I had to disable the apparmor.profile with a
cd /etc/apparmor.d/disable
ln -s ./../usr.sbin.clamd

Then, the "ERROR: initgroups() failed." disappears.

The apparmor itself came via apt-get packages. I did not edit it.

Description:Ubuntu 14.04.1 LTS
Release:14.04

apt-cache policy apparmor-profiles
apparmor-profiles:
  Installiert:   (keine)
  Installationskandidat: 2.8.95~2430-0ubuntu5.1
  Versionstabelle:
 2.8.95~2430-0ubuntu5.1 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 2.8.95~2430-0ubuntu5 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apparmor-profiles (not installed)
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: Mon Dec 22 01:23:04 2014
InstallationDate: Installed on 2014-11-29 (22 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
 
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  apparmor profile usr.sbin.clamd does not allow ScanOnAccess via
  fanotify

Status in apparmor package in Ubuntu:
  New

Bug description:
  I tried to enable the ScanOnAccess option in /etc/clamav.conf to get
  on-access scanning.

  Doing so, /var/log/clamav/clamav.log tells me:
  ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted
  ScanOnAccess: clamd must be started by root

  Setting User to root in /etc/clamav/clamd.conf
  makes the clamav-daemon to fail with

  service clamav-daemon start
   * Starting ClamAV daemon clamd
  ERROR: initgroups() failed.

  I had to disable the apparmor.profile with a
  cd /etc/apparmor.d/disable
  ln -s ./../usr.sbin.clamd

  Then, the "ERROR: initgroups() failed." disappears.

  The apparmor itself came via apt-get packages. I did not edit it.

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  apt-cache policy apparmor-profiles
  apparmor-profiles:
Installiert:   (keine)
Installationskandidat: 2.8.95~2430-0ubuntu5.1
Versionstabelle:
   2.8.95~2430-0ubuntu5.1 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   2.8.95~2430-0ubuntu5 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apparmor-profiles (not installed)
  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: Mon Dec 22 01:23:04 2014
  InstallationDate: Installed on 2014-11-29 (22 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

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