[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2018-01-30 Thread Yuan-Chen Cheng
** Changed in: oem-priority
   Status: Confirmed => Fix Committed

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Fix Committed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Committed
Status in libqmi source package in Xenial:
  Fix Committed
Status in modemmanager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+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 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

2018-01-30 Thread Yuan-Chen Cheng
** Description changed:

  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.
  
  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb
  
   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/
  
  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.
  
  # environment information:
  
   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.
  
   * uname -r: 4.4.0-73-generic
  
   * lsusb -v: http://paste.ubuntu.com/24662332/
  
  FCC authentication reference:
-  * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
-  * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704
+  * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
+  * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704
+ 
+ - wait landing: LP: #1725190

** Changed in: oem-priority/xenial
   Status: Confirmed => Fix Committed

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project xenial series:
  Fix Committed
Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

  - wait landing: LP: #1725190

To manage notifications about this bug go to:
https://bugs.launchpad.net/modemmanager/+bug/1693756/+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 1745350] Re: whoopsie id is not unique

2018-01-30 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1636954 ***
https://bugs.launchpad.net/bugs/1636954

** This bug has been marked a duplicate of bug 1636954
   Whoopsie should use something else if non-unique uuid

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

Title:
  whoopsie id is not unique

Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  The list of reports for a system actually includes reports for several
  different systems:

  For example in this report:
  https://errors.ubuntu.com/oops/374ff29e-fb53-11e7-83ad-fa163e192766
  the system has been installed on 2018-01-12 (user is mickymouse)

  when you open the list of reports for this system
  
https://errors.ubuntu.com/user/ca33fcf9202a7f0e2941820648d407f607ae410d3ef3ca17769a2ab321dc8315b82f3e155845ce915e5efca4b9da29b9ef506adc11149c0f7d11e577508c4590

  there are several reports which pre-dates the installation. Selecting other 
reports in the list show different systems. For example this report is from 
another system:
  https://errors.ubuntu.com/oops/a614887e-acad-11e7-b1f8-fa163e839e11

  whoopsie uses first tries to use /sys/class/dmi/id/product_uuid then
  falls back to other things.

  It seems that /sys/class/dmi/id/product_uuid is sometimes a bogus
  value e.g.

  00020003-0004-0005-0006-000700080009

  As seen in http://launchpad.net/bugs/1323081.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: whoopsie 0.2.58
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CrashReports: 640:1000:114:1986326:2018-01-25 09:03:26.946560382 
+0100:2018-01-25 09:03:27.946560382 
+0100:/var/crash/_usr_bin_gnome-calculator.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 11:44:49 2018
  InstallationDate: Installed on 2013-09-03 (1604 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1745350/+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 1743710] Re: Since 2018 text in combo boxes is dark and unreadable

2018-01-30 Thread linuxcub
Sorry, removing /gtk-2.0/ was not a good idea! A few apps were missing
then. Restored it and keep my 'style "menu" = "white" {' solution.

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

Title:
  Since 2018 text in combo boxes is dark and unreadable

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

Bug description:
  Since 2018 all dropdown menus in my Ubuntu 16.04 LTS have a black background 
and the text, i.e., file-save-as options are unreadable. After a fresh install 
the menus are ok, but after the first necessary updates, same problem! The 
menus if firefox and thunderbird are readable, but e.g., Libreoffice writer, 
Gimp you name it, are not. I have described this in detail in
  https://ubuntuforums.org/showthread.php?t=2382505&p=13730458#post13730458
  and also my workaround to solve it,
  changing the file /usr/share/themes/Ambiance/gtk-2.0/gtkrc
  But I am afraid, with the next bigger Ubuntu update the error will be back 
again?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1743710/+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 1743710] Re: Since 2018 text in combo boxes is dark and unreadable

2018-01-30 Thread Daniel van Vugt
The workaround we recommend is to just install:
https://launchpad.net/ubuntu/+archive/primary/+files/light-themes_14.04+16.04.20160415-0ubuntu1_all.deb

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

Title:
  Since 2018 text in combo boxes is dark and unreadable

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

Bug description:
  Since 2018 all dropdown menus in my Ubuntu 16.04 LTS have a black background 
and the text, i.e., file-save-as options are unreadable. After a fresh install 
the menus are ok, but after the first necessary updates, same problem! The 
menus if firefox and thunderbird are readable, but e.g., Libreoffice writer, 
Gimp you name it, are not. I have described this in detail in
  https://ubuntuforums.org/showthread.php?t=2382505&p=13730458#post13730458
  and also my workaround to solve it,
  changing the file /usr/share/themes/Ambiance/gtk-2.0/gtkrc
  But I am afraid, with the next bigger Ubuntu update the error will be back 
again?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1743710/+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 1746164] Re: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity]

2018-01-30 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  Enable Bluetooth-Wifi coexistence by default [bluetooth audio and
  network skip on Wifi activity]

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

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+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 1744328] Re: libfreebl3.so should be public, not in the nss subdir

2018-01-30 Thread ChristianEhrhardt
It seems this has some (non encouraging) history:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855879
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732201

I'll combine the approach in the former with what I have prepared for my report 
to Debian.
Packaging for the binary packages might follow the naming that Fedora uses.

Once/If I have something that works fine I'd open up an MP for Ubuntu to let 
people comment on it.
I'll take a look at that after getting some other (unrelated) blockers out of 
the way.

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

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

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

Title:
  libfreebl3.so should be public, not in the nss subdir

Status in nss package in Ubuntu:
  New
Status in nss package in Debian:
  Unknown

Bug description:
  Hi,
  I tried to move the chrony dependency from tomcrypt to libnss to avoid 
universe dependencies.
  While doing so I found that libfreebl3 is not "normally" linkable being 
outside the normal ld paths.

  E.g. sample program
  #include 
  #include 
  #include 
  int main(int argc, char **argv) {
  NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
  return 0;
  }

  Build:
  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3 
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss

  Then:
  ldd docheck
  will give you
  libfreebl3.so => not found

  Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
  needs some more consideration if that is the thing we want (there
  might be a reason it is where it is).

  Note: Required to go on with the chrony MIR which is rather urgent to
  be sorted out as it has a lot of other dependencies that need to be
  adapted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1744328/+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 840942] Re: set_size_request is ignored [update-manager details is one line]

2018-01-30 Thread sam tygier
Still an issue in Bionic. Can't see how to add the release. If I
understand comment #31 the bug is in update-manager now not apt-daemon

** Also affects: update-manager (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: update-manager (Ubuntu Oneiric)

** No longer affects: update-manager (Ubuntu Precise)

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

Title:
  set_size_request is ignored [update-manager details is one line]

Status in aptdaemon package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  New
Status in aptdaemon source package in Oneiric:
  Won't Fix
Status in gtk+3.0 source package in Oneiric:
  Won't Fix
Status in aptdaemon source package in Precise:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Confirmed

Bug description:
  update-manager details is one line (the terminal when expanding the
  details expander). This way you can't see what happens and is the
  function useless

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: update-manager 1:0.152.17
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Sun Sep  4 14:04:42 2011
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/840942/+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 1744328] Re: libfreebl3.so should be public, not in the nss subdir

2018-01-30 Thread ChristianEhrhardt
Discussion spun forward - TL;DR:
- we have time for the nss-pem changes and tjaalton will drive those in debian
- for our current need we might not even want to move the libs
  - but instead provide symlinks (least invasive change for now until Debian 
decided on our bug)

I'll revamp my current ppa fix, maybe merge the latest nss from Debian
and retest for an MP/upload later on.

Thansk xnox and tjaalton for the great discussion on IRC.

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

Title:
  libfreebl3.so should be public, not in the nss subdir

Status in nss package in Ubuntu:
  New
Status in nss package in Debian:
  Unknown

Bug description:
  Hi,
  I tried to move the chrony dependency from tomcrypt to libnss to avoid 
universe dependencies.
  While doing so I found that libfreebl3 is not "normally" linkable being 
outside the normal ld paths.

  E.g. sample program
  #include 
  #include 
  #include 
  int main(int argc, char **argv) {
  NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
  return 0;
  }

  Build:
  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3 
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss

  Then:
  ldd docheck
  will give you
  libfreebl3.so => not found

  Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
  needs some more consideration if that is the thing we want (there
  might be a reason it is where it is).

  Note: Required to go on with the chrony MIR which is rather urgent to
  be sorted out as it has a lot of other dependencies that need to be
  adapted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1744328/+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 840942] Re: set_size_request is ignored [update-manager details is one line]

2018-01-30 Thread dino99
** Tags removed: oneiric
** Tags added: artful bionic

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

Title:
  set_size_request is ignored [update-manager details is one line]

Status in aptdaemon package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  New
Status in aptdaemon source package in Oneiric:
  Won't Fix
Status in gtk+3.0 source package in Oneiric:
  Won't Fix
Status in aptdaemon source package in Precise:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Confirmed

Bug description:
  update-manager details is one line (the terminal when expanding the
  details expander). This way you can't see what happens and is the
  function useless

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: update-manager 1:0.152.17
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Sun Sep  4 14:04:42 2011
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/840942/+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 1660619] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B

2018-01-30 Thread ybdjkfd
I apologize for not being specific enough.  I found a fix for this on my
machine, but I am unsure what options you may need that I have gathered
together to get things to work but found that I had missed replying to
this bug.  I can post material more in depth as needed.  Some of these
options helped me with other fixes for bbswitch.  There are many options
for grub2 below, but mostly I wanted to mention the i915 material that
helps this bug.

I currently running:
* Linux 4.13.0-32-generic x86_64 GNU/Linux
* An MSI laptop with Intel HD Graphics 530 (Nvidia modules blacklisted so 
bbswitch can load them as needed)

Added the following in my /etc/default/grub helping with this bug and disabling 
Nvidia until bbswtich loads it ; note that 'acpi_osi' items may not be useful 
on your system so search that part up as needed; note the '{your version #}' 
meaning the package you have installed such as nvidia-384 or nvidia-387:
GRUB_CMDLINE_LINUX="nogpumanager 
modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia,nvidia-{your
 version #} acpi_osi=! acpi_osi=\"Windows 2009\" intel_iommu=igfx_off 
i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 i915.enable_rc=7 
i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 
i915.lvds_channel_mode=2 i915.lvds_use_ssc=1"

Added the following to /etc/modules :
i915
bbswitch load_state=0


Finally, ran the following manually to make sure things got updated:
sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo grub-mkconfig -o /boot/efi/EFI/ubuntu/grub.cfg
sudo update-initramfs -u -k all 
sudo update-grub2

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've a dual monitor setup and I'm running latest version of kubuntu.

  After a few days of uptime the desktop becomes so slow that I've to
  reboot it.

  In the log I find those errors, I don't know if they are related:

  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B (start=150051 end=150052) time 110 us, min 1073, max
  1079, scanline start 1072, end 1080

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 31 14:06:17 2017
  DistUpgraded: 2016-10-16 19:45:53,200 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7978]
  InstallationDate: Installed on 2013-04-25 (1376 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=f848f2e6-9d53-4c75-823a-fa97cfe10aa6 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (106 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A 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.:bvrA.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnZ170AGAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1u

[Touch-packages] [Bug 1332623] Re: Thunar behaves inconsistently with USB flash drive FAT32 partitions

2018-01-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Thunar behaves inconsistently with USB flash drive FAT32 partitions

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Fix Released

Bug description:
  I installed Xubuntu 14.04 and performed no customizations or
  reconfigurations.

  Observation:  Thunar 1.6.3 ("File Manager" from menu) on Xubuntu 14.04 
handles write permission to inserted USB flash drives inconsistently:
  * I am able to create a nil file on the flash drive with Thunar and edit it.  
Clearly, the flash drive is not read-only.
  * Using Thunar, I cannot copy an existing file (E.g. ~/.profile) and paste it 
on the flash drive - "destination is read-only" (not true!).
  * However, in a terminal window, `cp` with the flash drive as a destination 
succeeds.

  I tried this on drives by different manufacturers and with differing
  capacities and on two different Xubuntu 14.04 installations.

  There might be a configuration change for Thunar to allow paste to
  flash drives.  If so, this should be enabled when Thunar is installed
  as this behaviour is what users expect.

  Note: I created the FAT32 partition with `gparted` on Linux.  I also
  got the same results after creating a FAT32 partition using an MACOSX
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: thunar 1.6.3-1ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jun 20 11:30:40 2014
  InstallationDate: Installed on 2014-06-19 (1 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: thunar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1332623/+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 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

2018-01-30 Thread Sergio Callegari
Does not work in artful either.

On 17.10, the HSP/HFP option is shown in dropdown menus (pavucontrol,
kde audio config, etc.). However, selecting them does not work and when
one checks again the setting has gone back automatically to a2dp sink.

Please reopen. Otherwise advise whether a new identical bug should be
opened for artful.

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+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 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

2018-01-30 Thread Kai-Heng Feng
Folks,
This underlying problem may be quite different for each different BT controller.
Please file a separate bug for this.

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+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 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

2018-01-30 Thread Stefan Lobas
I can confirm that the workaround suggested in #15 works for my Asus
UX305CA, too. I attached my hdparm output...

** Attachment added: "hdparm.sda"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726930/+attachment/5045486/+files/hdparm.sda

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change

[Touch-packages] [Bug 1732997] Re: bionic bash 4.4-5 failed to unpack

2018-01-30 Thread Chanho Park
Hi,
I have same error when I tried to run debootstrap --second-stage.
Anyone who have the solution?

Here is my test sequence.

1. Environment
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial
$ $ uname -a
Linux cometzero-ubuntu 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

2. debootstrap stage1
$ sudo debootstrap --verbose --foreign --arch armhf bionic ./ubuntu 
http://ports.ubuntu.com

3. debootstrap stage2
$ sudo mount --bind /proc ubuntu/proc
$ sudo mount --bind /dev ubuntu/dev
$ sudo mount --bind /sys ubuntu/sys
$ sudo cp /usr/bin/qemu-arm-static ubuntu/usr/bin
$ sudo chroot ubuntu

(inside chroot)
$ /debootstrap/debootstrap --second-stage
I: Keyring file not available at 
/usr/share/keyrings/ubuntu-archive-keyring.gpg; switching to https mirror 
https://mirrors.kernel.org/debian
I: Installing core packages...
I: Unpacking required packages...

snip..

W: Failure while unpacking required packages. This will be attempted up to five 
times.
W: See //debootstrap/debootstrap.log for details (possibly the package 
/var/cache/apt/archives/bash_4.4-5ubuntu1_armhf.deb is at fault)

>From /debootstrap/debootstrap.log)

dpkg: warning: ignoring pre-dependency problem!
Preparing to unpack .../bash_4.4-5ubuntu1_armhf.deb ...
preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 
0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_armhf.deb (--unpack):
 new bash package pre-installation script subprocess was killed by signal 
(Aborted), core dumped

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

Title:
  bionic bash 4.4-5 failed to unpack

Status in bash package in Ubuntu:
  New

Bug description:
  Failure while unpacking required packages  In debootstrap
  bash_4.4-5ubuntu1_armhf.deb is at fault.
   my question is can i get an eta on when the file will be updated/fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1732997/+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 1744328] Re: libfreebl3.so should be public, not in the nss subdir

2018-01-30 Thread Launchpad Bug Tracker
** Merge proposal linked:
   https://code.launchpad.net/~paelzer/ubuntu/+source/nss/+git/nss/+merge/336838

** Merge proposal linked:
   https://code.launchpad.net/~paelzer/ubuntu/+source/nss/+git/nss/+merge/336839

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

Title:
  libfreebl3.so should be public, not in the nss subdir

Status in nss package in Ubuntu:
  New
Status in nss package in Debian:
  Unknown

Bug description:
  Hi,
  I tried to move the chrony dependency from tomcrypt to libnss to avoid 
universe dependencies.
  While doing so I found that libfreebl3 is not "normally" linkable being 
outside the normal ld paths.

  E.g. sample program
  #include 
  #include 
  #include 
  int main(int argc, char **argv) {
  NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
  return 0;
  }

  Build:
  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3 
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss

  Then:
  ldd docheck
  will give you
  libfreebl3.so => not found

  Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
  needs some more consideration if that is the thing we want (there
  might be a reason it is where it is).

  Note: Required to go on with the chrony MIR which is rather urgent to
  be sorted out as it has a lot of other dependencies that need to be
  adapted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1744328/+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 1746245] [NEW] .ovpn file "cipher" does not work if it is lowercase

2018-01-30 Thread Gleb Mazovetskiy
Public bug reported:

Network Manager Import VPN configuration does not work correctly if a
file contains a lowercase cipher.

Worst is, the import appears to work (no errors). The connection fails
with "Invalid HMAC signature" and no other errors.

I only figured out what the problem was by going to the advanced
settings and opening the cipher dropdown.

Perhaps the easiest fix to this would be to convert the "cipher" value
to upper case when importing.

Using the `openvpn` command directly does work with lowercase "cipher"
value, it's only when importing it via the Network Manager where there
is a problem.

Example .ovpn file contents (the lowercase cipher value here is
"aes-128-cbc"):

client
dev tun
proto udp
remote austria.privateinternetaccess.com 1198
resolv-retry infinite
nobind
persist-key
persist-tun
cipher aes-128-cbc
auth sha1
tls-client
remote-cert-tls server
auth-user-pass
comp-lzo
verb 1
reneg-sec 0
crl-verify crl.rsa.2048.pem
ca ca.rsa.2048.crt
disable-occ

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


** Tags: vpn

** Description changed:

  Network Manager Import VPN configuration does not work correctly if a
  file contains a lowercase cipher.
  
  Worst is, the import appears to work (no errors). The connection fails
  with "Invalid HMAC signature" and no other errors.
  
  I only figured out what the problem was by going to the advanced
  settings and opening the cipher dropdown.
  
  Perhaps the easiest fix to this would be to convert the "cipher" value
  to upper case when importing.
  
- Example .ovpn file contents:
+ Using the `openvpn` command directly does work with lowercase "cipher"
+ value, it's only when importing it via the Network Manager where there
+ is a problem.
+ 
+ Example .ovpn file contents (the lowercase cipher value here is
+ "aes-128-cbc"):
  
  client
  dev tun
  proto udp
  remote austria.privateinternetaccess.com 1198
  resolv-retry infinite
  nobind
  persist-key
  persist-tun
  cipher aes-128-cbc
  auth sha1
  tls-client
  remote-cert-tls server
  auth-user-pass
  comp-lzo
  verb 1
  reneg-sec 0
  crl-verify crl.rsa.2048.pem
  ca ca.rsa.2048.crt
  disable-occ

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

Title:
  .ovpn file "cipher" does not work if it is lowercase

Status in network-manager package in Ubuntu:
  New

Bug description:
  Network Manager Import VPN configuration does not work correctly if a
  file contains a lowercase cipher.

  Worst is, the import appears to work (no errors). The connection fails
  with "Invalid HMAC signature" and no other errors.

  I only figured out what the problem was by going to the advanced
  settings and opening the cipher dropdown.

  Perhaps the easiest fix to this would be to convert the "cipher" value
  to upper case when importing.

  Using the `openvpn` command directly does work with lowercase "cipher"
  value, it's only when importing it via the Network Manager where there
  is a problem.

  Example .ovpn file contents (the lowercase cipher value here is
  "aes-128-cbc"):

  client
  dev tun
  proto udp
  remote austria.privateinternetaccess.com 1198
  resolv-retry infinite
  nobind
  persist-key
  persist-tun
  cipher aes-128-cbc
  auth sha1
  tls-client
  remote-cert-tls server
  auth-user-pass
  comp-lzo
  verb 1
  reneg-sec 0
  crl-verify crl.rsa.2048.pem
  ca ca.rsa.2048.crt
  disable-occ

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1746245/+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 1746245] Re: .ovpn file "cipher" does not work if it is lowercase

2018-01-30 Thread Gleb Mazovetskiy
** Attachment added: "openvpn-dropdown.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1746245/+attachment/5045554/+files/openvpn-dropdown.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/1746245

Title:
  .ovpn file "cipher" does not work if it is lowercase

Status in network-manager package in Ubuntu:
  New

Bug description:
  Network Manager Import VPN configuration does not work correctly if a
  file contains a lowercase cipher.

  Worst is, the import appears to work (no errors). The connection fails
  with "Invalid HMAC signature" and no other errors.

  I only figured out what the problem was by going to the advanced
  settings and opening the cipher dropdown.

  Perhaps the easiest fix to this would be to convert the "cipher" value
  to upper case when importing.

  Using the `openvpn` command directly does work with lowercase "cipher"
  value, it's only when importing it via the Network Manager where there
  is a problem.

  Example .ovpn file contents (the lowercase cipher value here is
  "aes-128-cbc"):

  client
  dev tun
  proto udp
  remote austria.privateinternetaccess.com 1198
  resolv-retry infinite
  nobind
  persist-key
  persist-tun
  cipher aes-128-cbc
  auth sha1
  tls-client
  remote-cert-tls server
  auth-user-pass
  comp-lzo
  verb 1
  reneg-sec 0
  crl-verify crl.rsa.2048.pem
  ca ca.rsa.2048.crt
  disable-occ

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1746245/+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 1744328] Re: libfreebl3.so should be public, not in the nss subdir

2018-01-30 Thread ChristianEhrhardt
** Branch unlinked: lp:~paelzer/britney/hints-ubuntu-mask-389-ds-base

** Merge proposal unlinked:
   https://code.launchpad.net/~paelzer/ubuntu/+source/nss/+git/nss/+merge/336838

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

Title:
  libfreebl3.so should be public, not in the nss subdir

Status in nss package in Ubuntu:
  New
Status in nss package in Debian:
  Unknown

Bug description:
  Hi,
  I tried to move the chrony dependency from tomcrypt to libnss to avoid 
universe dependencies.
  While doing so I found that libfreebl3 is not "normally" linkable being 
outside the normal ld paths.

  E.g. sample program
  #include 
  #include 
  #include 
  int main(int argc, char **argv) {
  NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
  return 0;
  }

  Build:
  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3 
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss

  Then:
  ldd docheck
  will give you
  libfreebl3.so => not found

  Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
  needs some more consideration if that is the thing we want (there
  might be a reason it is where it is).

  Note: Required to go on with the chrony MIR which is rather urgent to
  be sorted out as it has a lot of other dependencies that need to be
  adapted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1744328/+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 1192719] Re: [pam-auth-update] add support for enabling non-default configs

2018-01-30 Thread Timo Aaltonen
this patch adds --enable option to enable configs that are not on by
default

** Patch added: "add-enable-option.diff"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1192719/+attachment/5045559/+files/add-enable-option.diff

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

Title:
  [pam-auth-update] add support for enabling non-default configs

Status in pam package in Ubuntu:
  Confirmed

Bug description:
  It would be nice if pam-auth-update supported enabling configs that
  are not enabled by default. The mechanism would be the same as with
  --remove but reversed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libpam-runtime 1.1.3-8ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Thu Jun 20 00:07:27 2013
  InstallationDate: Installed on 2012-11-07 (224 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/zsh
  SourcePackage: pam
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1192719/+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 1746249] Re: gst-plugin-scanner crashed with SIGSEGV in tcache_get()

2018-01-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1724649 ***
https://bugs.launchpad.net/bugs/1724649

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1724649, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1746249/+attachment/5045560/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1746249/+attachment/5045562/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1746249/+attachment/5045566/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1746249/+attachment/5045567/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1746249/+attachment/5045568/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1746249/+attachment/5045569/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1746249/+attachment/5045570/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1724649

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gst-plugin-scanner crashed with SIGSEGV in tcache_get()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  gst-plugin-scanner crashed with SIGSEGV in tcache_get()

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.12.4-1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 30 14:47:11 2018
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  InstallationDate: Installed on 2017-12-26 (34 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171225)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l
  SegvAnalysis:
   Segfault happened at: 0x7fd1be72200b <__GI___libc_malloc+379>:   mov
(%rdx),%rsi
   PC (0x7fd1be72200b) ok
   source "(%rdx)" (0x0003007a) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2978
   __GI___libc_malloc (bytes=bytes@entry=100) at malloc.c:3078
   __GI___vasprintf_chk (result_ptr=0x7fd18c5a1380, flags=1, 
format=0x7fd1bf093c04 "\nERROR: ", args=0x7fd18c5a13b0) at vasprintf_chk.c:48
   g_vasprintf () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strdup_vprintf () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gst-plugin-scanner crashed with SIGSEGV in tcache_get()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1746249/+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 697498] Re: [Realtek ALC269VB] No sound from internal speakers, but headphone jack works

2018-01-30 Thread ALberto Beltran
Hi everyone, I'm just new using Linux. Installed Zorin 12 in my netbook
and I have exactly the same problem with the Realtek ALC269VB, no sound
with the speakers but headphones work well. Thanks in advance for your
help. looking at the alsamixer, the speaker channel is apparently not
connected with the speakers.

The channel of the headphones is muted but once I plug the headphones,
it works well. If I proceed and manually unmute the same headphone
channel without headphones, I can get sound from the speakers. However,
once the pc is rebooted comes back to the same problem.


Big Regards and thanks in advance.

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

Title:
  [Realtek ALC269VB] No sound from internal speakers, but headphone jack
  works

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Following the instructions in this troubleshooting guide:
 https://help.ubuntu.com/community/SoundTroubleshooting
  I couldn't find my codec (Realtek ALC259) in the list of ALSA-supported 
codecs.

  Sound does not come out of the internal speakers. However when I plug
  headphones into the headphone jack, I can hear sound. This is an Asus
  EeePC 1015PEM.

  Alsa system configuration dump:
 http://www.alsa-project.org/db/?f=f92e22d0373cd586b553b9964d8f6e1d4e86d6b6

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic i686
  AlsaVersion:
   Advanced Linux Sound Architecture Driver Version 1.0.23.
   Compiled on Jan  5 2011 for kernel 2.6.35-24-generic (SMP).
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tlau   1547 F pulseaudio
   /dev/snd/pcmC0D0p:   tlau   1547 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 46'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,1043841c,00100100'
 Controls  : 11
 Simple ctrls  : 7
  Date: Tue Jan  4 19:56:00 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ALC269VB] ALSA test tone not correctly played back
  dmi.bios.date: 10/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1015PE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/27/2010:svnASUSTeKComputerINC.:pn1015PEM:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1015PEM
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/697498/+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 1746258] [NEW] Local servers not reachable as NetworkManager adds spurious nameserver 127.0.1.1 to resolv.conf

2018-01-30 Thread Karl Kastner
Public bug reported:

Since upgrade to 17.04/17.10 I cannot reach any server within my
university domain over LAN:

>From within the university network:
ping webmail.wur.nl
ping: webmail.wur.nl: Name or service not known

>From outside:
ping webmail.wur.nl
PING webmail.wur.nl (137.224.252.102) 56(84) bytes of data.

This is caused by the entry of the local host as nameserver in
resolf.conf as "nameserver 127.0.1.1".

When this line is manually removed the server is reached. However,
NetworkManager persistently restores the line to /etc/resolf.conf. This
can be avoided by stopping NetworkManager, adding dns=none to the [main]
section to /etc/NetworkManager/NetworkManager.conf and then restarting
NetworkManager.

NetworkManager should not add the line nameserver 127.0.1.1 to
resolv.conf on default, as this almost surely causes problems.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-29.32-generic 4.13.13
Uname: Linux 4.13.0-29-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jan 30 15:18:38 2018
InstallationDate: Installed on 2015-11-05 (817 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IpRoute:
 default via 10.75.15.254 dev eth0 proto static metric 100 
 10.75.0.0/20 dev eth0 proto kernel scope link src 10.75.0.58 metric 100 
 169.254.0.0/16 dev eth0 scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to artful on 2018-01-16 (14 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-30T15:14:52.823904
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 eth0ethernet  connected/org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  8bdd2177-0b8e-3365-82d1-1d5ea4cc3bc2  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 wlan0   wifi  unavailable  /org/freedesktop/NetworkManager/Devices/3  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
disabled  enabled  enabled

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


** Tags: amd64 apport-bug artful package-from-proposed

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

Title:
  Local servers not reachable as NetworkManager adds spurious nameserver
  127.0.1.1 to resolv.conf

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since upgrade to 17.04/17.10 I cannot reach any server within my
  university domain over LAN:

  From within the university network:
  ping webmail.wur.nl
  ping: webmail.wur.nl: Name or service not known

  From outside:
  ping webmail.wur.nl
  PING webmail.wur.nl (137.224.252.102) 56(84) bytes of data.

  This is caused by the entry of the local host as nameserver in
  resolf.conf as "nameserver 127.0.1.1".

  When this line is manually removed the server is reached. However,
  NetworkManager persistently restores the line to /etc/resolf.conf.
  This can be avoided by stopping NetworkManager, adding dns=none to the
  [main] section to /etc/NetworkManager/NetworkManager.conf and then
  restarting NetworkManager.

  NetworkManager should not add the line nameserver 127.0.1.1 to
  resolv.conf on default, as this almost surely causes problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-29.32-generic 4.13.13
  Uname: Linux 4.13.0-29-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 15:18:38 2018
  InstallationDate: Installed on 2015-11-05 (817 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 10.75.15.254 dev eth0 proto static metric 100 
   10.75.0.0/20 dev eth0 proto kernel scope link src 10.75.0.58 metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to artful on 2018-01-16 (14 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-30T15:14:52.823904
  nmcli-dev:
   DEVICE  TYPE  STATE 

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

2018-01-30 Thread Julian Andres Klode
Wow, store method opens a socket. I wonder what for. This is
frustrating. Workaround for that would probably be

  apt::sandbox::seccomp::allow { "socket" };

+ some more socket operations.

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Triaged

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1732030/+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 1732030] Re: 'apt update' dies with seccomp error

2018-01-30 Thread Turi Peter
Sorry I don't have the old log.

But it's also happening now:
turip@turip-xps-ws:~$ sudo -i
root@turip-xps-ws:~# apt-get update
Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease   
Get:3 http://hu.archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
Ign:4 http://hu.archive.canonical.com/ubuntu bionic InRelease  
Get:5 http://hu.archive.ubuntu.com/ubuntu bionic-updates InRelease [65.4 kB]   
Err:6 http://hu.archive.canonical.com/ubuntu bionic Release
  404  Not Found
Get:7 http://hu.archive.ubuntu.com/ubuntu bionic-backports InRelease [65.5 kB] 
Hit:8 http://dl.google.com/linux/chrome/deb stable Release 
Hit:9 https://packages.microsoft.com/repos/vscode stable InRelease 
Get:10 http://hu.archive.ubuntu.com/ubuntu bionic/main Sources [833 kB]
0% [10 Sources store 0 B] [5 InRelease gpgv 65.4 kB] [Waiting for headers] [Con
  Seccomp prevented execution of syscall 41 on architecture amd64 

   
Reading package lists... Done
E: The repository 'http://hu.archive.canonical.com/ubuntu bionic Release' does 
not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
W: Skipping acquire of configured file 'non-free/binary-amd64/Packages' as 
repository 'http://security.ubuntu.com/ubuntu bionic-security InRelease' 
doesn't have the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/binary-i386/Packages' as 
repository 'http://security.ubuntu.com/ubuntu bionic-security InRelease' 
doesn't have the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/i18n/Translation-en' as 
repository 'http://security.ubuntu.com/ubuntu bionic-security InRelease' 
doesn't have the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/i18n/Translation-en_US' as 
repository 'http://security.ubuntu.com/ubuntu bionic-security InRelease' 
doesn't have the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/dep11/Components-amd64.yml' as 
repository 'http://security.ubuntu.com/ubuntu bionic-security InRelease' 
doesn't have the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/dep11/icons-64x64.tar' as 
repository 'http://security.ubuntu.com/ubuntu bionic-security InRelease' 
doesn't have the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/Contents-amd64' as repository 
'http://security.ubuntu.com/ubuntu bionic-security InRelease' doesn't have the 
component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/Contents-i386' as repository 
'http://security.ubuntu.com/ubuntu bionic-security InRelease' doesn't have the 
component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/binary-amd64/Packages' as 
repository 'http://hu.archive.ubuntu.com/ubuntu bionic InRelease' doesn't have 
the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/binary-i386/Packages' as 
repository 'http://hu.archive.ubuntu.com/ubuntu bionic InRelease' doesn't have 
the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/i18n/Translation-en' as 
repository 'http://hu.archive.ubuntu.com/ubuntu bionic InRelease' doesn't have 
the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/i18n/Translation-en_US' as 
repository 'http://hu.archive.ubuntu.com/ubuntu bionic InRelease' doesn't have 
the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/dep11/Components-amd64.yml' as 
repository 'http://hu.archive.ubuntu.com/ubuntu bionic InRelease' doesn't have 
the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/dep11/icons-64x64.tar' as 
repository 'http://hu.archive.ubuntu.com/ubuntu bionic InRelease' doesn't have 
the component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/Contents-amd64' as repository 
'http://hu.archive.ubuntu.com/ubuntu bionic InRelease' doesn't have the 
component 'non-free' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free/Contents-i386' as repository 
'http://hu.archive.ubuntu.com/ubuntu bionic InRelease' doesn't have the 
component 'non-free' (compon

[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2018-01-30 Thread Jens Finkhäuser
I can confirm the workaround in #92 for my 16.04.3 LTS installation.

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed

Bug description:
  [Triage Notes]

  Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions.
  Please see wall of text on comment 50 for a long excuse.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1745828] Re: Ubuntu 16.04 can't find any Bluetooth devices

2018-01-30 Thread George Hunter
apport information

** Tags added: apport-collected xenial

** Description changed:

  It is ON and VISIBLE in the control panel.  My iPhone can see two other
  devices but it can't see the computer, and the computer  can't see
  anything, even if left searching for tens of minutes.
  
  The previous answers listed below suggest the following diagnostics
  
  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem
  
  The service seems to be running
  
  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd
  
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  
  and not blocked
  
  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  
  I have edited /etc/bluetooth/main.conf to include
  
  AutoEnable=true
  
  but I noted that the entire file was commented out.
  
  The kernel seems reasonably up to date
  
   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  
  I wonder if I need a device driver, but I have no idea how to find out.
  The following diagnostics may help some of you knowledgeable people find
  out.
  
   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86
  
  and the output of dmsg is
  
  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11
  
  and of lsusb is
  
  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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
  
  Thanking you in anticipation
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: amd64
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2017-09-06 (145 days ago)
+ InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ MachineType: ASUSTeK Computer INC. CM6330_CM6630_CM6730_CM6830_M11AA-8
+ Packag

[Touch-packages] [Bug 1745828] Lspci.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1745828/+attachment/5045632/+files/Lspci.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  ApportVersion: 2.20.1-0ub

[Touch-packages] [Bug 1745828] Lsusb.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1745828/+attachment/5045633/+files/Lsusb.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  ApportVersion: 2.20.1-0ub

[Touch-packages] [Bug 1745828] JournalErrors.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1745828/+attachment/5045631/+files/JournalErrors.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  ApportVe

[Touch-packages] [Bug 1745828] Dependencies.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1745828/+attachment/5045630/+files/Dependencies.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  ApportVers

[Touch-packages] [Bug 1745828] ProcCpuinfo.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1745828/+attachment/5045634/+files/ProcCpuinfo.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  ApportVersio

[Touch-packages] [Bug 1745828] ProcCpuinfoMinimal.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1745828/+attachment/5045635/+files/ProcCpuinfoMinimal.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 

[Touch-packages] [Bug 1745828] ProcEnviron.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1745828/+attachment/5045636/+files/ProcEnviron.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  ApportVersio

[Touch-packages] [Bug 1745828] ProcInterrupts.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1745828/+attachment/5045637/+files/ProcInterrupts.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  Apport

[Touch-packages] [Bug 1745828] ProcModules.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1745828/+attachment/5045638/+files/ProcModules.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  ApportVersio

[Touch-packages] [Bug 1745828] syslog.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1745828/+attachment/5045643/+files/syslog.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  ApportVersion: 2.20.1-0

[Touch-packages] [Bug 1745828] getfacl.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1745828/+attachment/5045640/+files/getfacl.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  ApportVersion: 2.20.

[Touch-packages] [Bug 1745828] UdevDb.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1745828/+attachment/5045639/+files/UdevDb.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  ApportVersion: 2.20.1-0

[Touch-packages] [Bug 1745828] rfkill.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1745828/+attachment/5045642/+files/rfkill.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  --- 
  ApportVersion: 2.20.1-0

[Touch-packages] [Bug 1745828] modified.conffile..etc.bluetooth.main.conf.txt

2018-01-30 Thread George Hunter
apport information

** Attachment added: "modified.conffile..etc.bluetooth.main.conf.txt"
   
https://bugs.launchpad.net/bugs/1745828/+attachment/5045641/+files/modified.conffile..etc.bluetooth.main.conf.txt

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 

[Touch-packages] [Bug 1746277] [NEW] change volume or mute it

2018-01-30 Thread Jean da Silva Nascimento
Public bug reported:

The keyboard sound funcitions aren't working when I try to use it, but a few 
minutes later, sometimes 5 minutes... sometimes 20 min; starts to work, turning 
the velumes up or down, mute on or off.
I just realised that the other keyboard commands are working too much late 
after I use them, simple commands like Ctrl+Alt+T (for the terminal) etc.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   djeant 2000 F...m pulseaudio
 /dev/snd/controlC0:  djeant 2000 F pulseaudio
Date: Tue Jan 30 13:50:54 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2018-01-29 (0 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
ProcEnviron:
 LANGUAGE=pt_BR:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to artful on 2018-01-30 (0 days ago)
dmi.bios.date: 01/06/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.1
dmi.board.name: 07F37C
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd01/06/2017:svnDellInc.:pnInspiron3268:pvr:rvnDellInc.:rn07F37C:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3268
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug artful

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

Title:
  change volume or mute it

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The keyboard sound funcitions aren't working when I try to use it, but a few 
minutes later, sometimes 5 minutes... sometimes 20 min; starts to work, turning 
the velumes up or down, mute on or off.
  I just realised that the other keyboard commands are working too much late 
after I use them, simple commands like Ctrl+Alt+T (for the terminal) etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   djeant 2000 F...m pulseaudio
   /dev/snd/controlC0:  djeant 2000 F pulseaudio
  Date: Tue Jan 30 13:50:54 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-01-29 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   LANGUAGE=pt_BR:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to artful on 2018-01-30 (0 days ago)
  dmi.bios.date: 01/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 07F37C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd01/06/2017:svnDellInc.:pnInspiron3268:pvr:rvnDellInc.:rn07F37C:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3268
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1746277/+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 1192719] Re: [pam-auth-update] add support for enabling non-default configs

2018-01-30 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  [pam-auth-update] add support for enabling non-default configs

Status in pam package in Ubuntu:
  Confirmed

Bug description:
  It would be nice if pam-auth-update supported enabling configs that
  are not enabled by default. The mechanism would be the same as with
  --remove but reversed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libpam-runtime 1.1.3-8ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Thu Jun 20 00:07:27 2013
  InstallationDate: Installed on 2012-11-07 (224 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/zsh
  SourcePackage: pam
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1192719/+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 1582950] Re: broken apport hook: TypeError: a bytes-like object is required, not 'str'

2018-01-30 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu/bionic/apport/ubuntu

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

Title:
  broken apport hook: TypeError: a bytes-like object is required, not
  'str'

Status in apport package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Invalid
Status in apport source package in Artful:
  Fix Released

Bug description:
  The apport hook for ubiquity appears broken. (Ignore the Wnck error,
  that's bug 1580412).

  $ ubuntu-bug ubiquity
  /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
  dpkg-query: no packages found matching ubiquity
  ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 61, in 
add_info
  if 'Buffer I/O error on device' in syslog:
  TypeError: a bytes-like object is required, not 'str'

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 17 17:31:33 2016
  InstallationDate: Installed on 2012-10-18 (1307 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1582950/+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 1745828] Re: Ubuntu 16.04 can't find any Bluetooth devices

2018-01-30 Thread George Hunter
bug 1542743 takes me into uncharted territory - patching the kernel is
well outside my comfort zone. But the fix suggested at #14 does not work
(see #35) for the kernel version 4.13 which I believe is the one I have.

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

Title:
  Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Founda

[Touch-packages] [Bug 1746286] [NEW] Update libharfbuzz to 1.7.4

2018-01-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Available here: https://www.freedesktop.org/software/harfbuzz/release/


Current version of libharfbuzz-dev is 1.4.2-1, same with libharfbuzz0b (strange 
name?). 

It's used in the pretty awesome terminal Kitty;
https://github.com/kovidgoyal/kitty

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


** Tags: needs-packaging
-- 
Update libharfbuzz to 1.7.4
https://bugs.launchpad.net/bugs/1746286
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to harfbuzz in Ubuntu.

-- 
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 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present

2018-01-30 Thread Brian Murray
** Changed in: friendly-recovery (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: friendly-recovery (Ubuntu)
   Importance: Undecided => High

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

Title:
  during recovery mode, enable network failed due to /etc/resolv.conf
  not being present

Status in friendly-recovery package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid
Status in thermald package in Ubuntu:
  Invalid

Bug description:
  Something went wrong that required me to boot to recovery mode via
  grub.  The important part here, is that while I got as far as the
  recovery screen asking to "Enable Networking" and other options fsck
  filesystems, drop to root shell, etc.

  and selected "Enable Networking":

  the result was:

  grep: /etc/resolv.conf: No such File or directory.

  Unknown group "power" in message bus configuration file.


  (Networking did not enable, leaving me stranded at root shell without
  network which would have made adding/removing packages to troubleshoot
  easier)

  Ubuntu: zesty 17.04
  Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  network-manager: 1.4.4-1ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 13 16:40:19 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-09 (1009 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  IpRoute:
   default via 192.168.250.1 dev wlan1 proto static metric 600 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
   192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   lxcbr0  bridgeconnected/org/freedesktop/NetworkManager/Devices/3  
lxcbr0  46595dd8-757b-4d93-ade3-c066f72d9e2e  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan1   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Brisbane House  2b25e748-f9c5-4c84-9fe6-0f64071fcf0b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+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 1746286] Re: Update libharfbuzz to 1.7.4

2018-01-30 Thread Hans Joachim Desserud
** Package changed: ubuntu => harfbuzz (Ubuntu)

** Tags removed: needs-packaging
** Tags added: upgrade-software-version

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

Title:
  Update libharfbuzz to 1.7.4

Status in harfbuzz package in Ubuntu:
  New

Bug description:
  Available here: https://www.freedesktop.org/software/harfbuzz/release/

  
  Current version of libharfbuzz-dev is 1.4.2-1, same with libharfbuzz0b 
(strange name?). 

  It's used in the pretty awesome terminal Kitty;
  https://github.com/kovidgoyal/kitty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/harfbuzz/+bug/1746286/+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 1746286] Re: Update libharfbuzz to 1.7.4

2018-01-30 Thread Jeremy Bicha
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The harfbuzz packaging comes from Debian and it would be
nice if somebody having it could send the bug to Debianby following the
instructions at https://wiki.ubuntu.com/Debian/Bugs . If you have done
so, please tell us the number of the upstream bug (or the link), so we
can add a bugwatch that will inform us about its status. Thanks in
advance.

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

Title:
  Update libharfbuzz to 1.7.4

Status in harfbuzz package in Ubuntu:
  New

Bug description:
  Available here: https://www.freedesktop.org/software/harfbuzz/release/

  
  Current version of libharfbuzz-dev is 1.4.2-1, same with libharfbuzz0b 
(strange name?). 

  It's used in the pretty awesome terminal Kitty;
  https://github.com/kovidgoyal/kitty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/harfbuzz/+bug/1746286/+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 1738582] Re: [MIR] ibus-libpinyin and dependencies

2018-01-30 Thread Matthias Klose
Override component to main
ibus-libpinyin 1.9.2-1~exp1ubuntu1 in bionic: universe/utils -> main
ibus-libpinyin 1.9.2-1~exp1ubuntu1 in bionic amd64: 
universe/utils/optional/100% -> main
ibus-libpinyin 1.9.2-1~exp1ubuntu1 in bionic arm64: 
universe/utils/optional/100% -> main
ibus-libpinyin 1.9.2-1~exp1ubuntu1 in bionic armhf: 
universe/utils/optional/100% -> main
ibus-libpinyin 1.9.2-1~exp1ubuntu1 in bionic i386: universe/utils/optional/100% 
-> main
ibus-libpinyin 1.9.2-1~exp1ubuntu1 in bionic ppc64el: 
universe/utils/optional/100% -> main
ibus-libpinyin 1.9.2-1~exp1ubuntu1 in bionic s390x: 
universe/utils/optional/100% -> main
7 publications overridden.


** Changed in: ibus-libpinyin (Ubuntu)
   Status: New => Fix Released

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

Title:
  [MIR] ibus-libpinyin and dependencies

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released

Bug description:
  Please include these packages in Ubuntu's component main:

  * ibus-libpinyin
  * libpinyin (the ibus-libpinyin binary depends on libpinyin13)

  As has been discussed at bug #1735362 we would like to replace ibus-
  sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
  and as the default input method for typing Simplified Chinese. Reasons
  for the switch are:

  - ibus-libpinyin is better maintained
  - ibus-libpinyin is built with and depends on Python3
  - ibus-libpinyin is default input method in GNOME

  Bugs ibus-libpinyin
  ---
  https://github.com/libpinyin/ibus-libpinyin/issues

  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin

  https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin

  Bugs libpinyin
  --
  https://github.com/libpinyin/libpinyin/issues

  (no open Debian or Ubuntu bugs)

  I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements,
  and haven't found any issues that would prevent the proposed main
  inclusion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1738582/+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 1738582] Re: [MIR] ibus-libpinyin and dependencies

2018-01-30 Thread Matthias Klose
Override component to main
libpinyin 2.1.0-1~exp3 in bionic: universe/libs -> main
libpinyin-common-dev 2.1.0-1~exp3 in bionic amd64: 
universe/libdevel/optional/100% -> main
libpinyin-common-dev 2.1.0-1~exp3 in bionic arm64: 
universe/libdevel/optional/100% -> main
libpinyin-common-dev 2.1.0-1~exp3 in bionic armhf: 
universe/libdevel/optional/100% -> main
libpinyin-common-dev 2.1.0-1~exp3 in bionic i386: 
universe/libdevel/optional/100% -> main
libpinyin-common-dev 2.1.0-1~exp3 in bionic ppc64el: 
universe/libdevel/optional/100% -> main
libpinyin-common-dev 2.1.0-1~exp3 in bionic s390x: 
universe/libdevel/optional/100% -> main
libpinyin-data 2.1.0-1~exp3 in bionic amd64: universe/libs/optional/100% -> main
libpinyin-data 2.1.0-1~exp3 in bionic arm64: universe/libs/optional/100% -> main
libpinyin-data 2.1.0-1~exp3 in bionic armhf: universe/libs/optional/100% -> main
libpinyin-data 2.1.0-1~exp3 in bionic i386: universe/libs/optional/100% -> main
libpinyin-data 2.1.0-1~exp3 in bionic ppc64el: universe/libs/optional/100% -> 
main
libpinyin-data 2.1.0-1~exp3 in bionic s390x: universe/libs/optional/100% -> main
libpinyin-utils 2.1.0-1~exp3 in bionic amd64: universe/utils/optional/100% -> 
main
libpinyin-utils 2.1.0-1~exp3 in bionic arm64: universe/utils/optional/100% -> 
main
libpinyin-utils 2.1.0-1~exp3 in bionic armhf: universe/utils/optional/100% -> 
main
libpinyin-utils 2.1.0-1~exp3 in bionic i386: universe/utils/optional/100% -> 
main
libpinyin-utils 2.1.0-1~exp3 in bionic ppc64el: universe/utils/optional/100% -> 
main
libpinyin-utils 2.1.0-1~exp3 in bionic s390x: universe/utils/optional/100% -> 
main
libpinyin13 2.1.0-1~exp3 in bionic amd64: universe/libs/optional/100% -> main
libpinyin13 2.1.0-1~exp3 in bionic arm64: universe/libs/optional/100% -> main
libpinyin13 2.1.0-1~exp3 in bionic armhf: universe/libs/optional/100% -> main
libpinyin13 2.1.0-1~exp3 in bionic i386: universe/libs/optional/100% -> main
libpinyin13 2.1.0-1~exp3 in bionic ppc64el: universe/libs/optional/100% -> main
libpinyin13 2.1.0-1~exp3 in bionic s390x: universe/libs/optional/100% -> main
libpinyin13-dev 2.1.0-1~exp3 in bionic amd64: universe/libdevel/optional/100% 
-> main
libpinyin13-dev 2.1.0-1~exp3 in bionic arm64: universe/libdevel/optional/100% 
-> main
libpinyin13-dev 2.1.0-1~exp3 in bionic armhf: universe/libdevel/optional/100% 
-> main
libpinyin13-dev 2.1.0-1~exp3 in bionic i386: universe/libdevel/optional/100% -> 
main
libpinyin13-dev 2.1.0-1~exp3 in bionic ppc64el: universe/libdevel/optional/100% 
-> main
libpinyin13-dev 2.1.0-1~exp3 in bionic s390x: universe/libdevel/optional/100% 
-> main
libzhuyin-dev 2.1.0-1~exp3 in bionic amd64: universe/libdevel/optional/100% -> 
main
libzhuyin-dev 2.1.0-1~exp3 in bionic arm64: universe/libdevel/optional/100% -> 
main
libzhuyin-dev 2.1.0-1~exp3 in bionic armhf: universe/libdevel/optional/100% -> 
main
libzhuyin-dev 2.1.0-1~exp3 in bionic i386: universe/libdevel/optional/100% -> 
main
libzhuyin-dev 2.1.0-1~exp3 in bionic ppc64el: universe/libdevel/optional/100% 
-> main
libzhuyin-dev 2.1.0-1~exp3 in bionic s390x: universe/libdevel/optional/100% -> 
main
libzhuyin13 2.1.0-1~exp3 in bionic amd64: universe/libs/optional/100% -> main
libzhuyin13 2.1.0-1~exp3 in bionic arm64: universe/libs/optional/100% -> main
libzhuyin13 2.1.0-1~exp3 in bionic armhf: universe/libs/optional/100% -> main
libzhuyin13 2.1.0-1~exp3 in bionic i386: universe/libs/optional/100% -> main
libzhuyin13 2.1.0-1~exp3 in bionic ppc64el: universe/libs/optional/100% -> main
libzhuyin13 2.1.0-1~exp3 in bionic s390x: universe/libs/optional/100% -> main
43 publications overridden.


** Changed in: libpinyin (Ubuntu)
   Status: New => Fix Released

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

Title:
  [MIR] ibus-libpinyin and dependencies

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released

Bug description:
  Please include these packages in Ubuntu's component main:

  * ibus-libpinyin
  * libpinyin (the ibus-libpinyin binary depends on libpinyin13)

  As has been discussed at bug #1735362 we would like to replace ibus-
  sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
  and as the default input method for typing Simplified Chinese. Reasons
  for the switch are:

  - ibus-libpinyin is better maintained
  - ibus-libpinyin is built with and depends on Python3
  - ibus-libpinyin is default input method in GNOME

  Bugs ibus-libpinyin
  ---
  https://github.com/libpinyin/ibus-libpinyin/issues

  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin

  https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin

  Bugs libpinyin
  --
  https://github.com/libpinyin/libpinyin/issues

  (no open Debian or Ubuntu bugs)

  I have read https://wiki.ubuntu.com/UbuntuMainInclusionRe

[Touch-packages] [Bug 1729491] Re: ubuntu-bug says that snap packages are not installed

2018-01-30 Thread Brian Murray
** Changed in: apport (Ubuntu)
   Status: Confirmed => Triaged

** Tags added: rls-bb-incoming

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

Title:
  ubuntu-bug says that snap packages are not installed

Status in apport package in Ubuntu:
  Triaged

Bug description:
  1. 
  I installed the package gnome-recipes, tried to send an error report program 
in response to the received message:you cannot report a problem:
  The report belongs to a package that was not installed. 

  2. 
  Expected that the program will be identified as installed. 

  3. 
  sudo apt -f install 
  [sudo] password for Alexander: 
  Reading package lists... Done
  Building dependency tree 
  Reading state information... Ready
  0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 
packages are not updated.
  sudo gnome-sudo recipes: gnome-recipes: command not found
  sudo apt install gnome-recipes Reading package lists... Done
  Building dependency tree 
  Reading state information... Ready
  E: unable to locate package gnome-recipes 

  I installed via software-center

  gnome-recipes 
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: template gnome-recipes no corresponding package
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+ Stopped ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg
  ---

  1. 
  произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке 
программы, в ответ получил сообщение:Не удаётся сообщить о неполадке:
  Отчёт относится к пакету , который не был установлен. 

  2. 
  Ожидал что программа будет идентифицироваться как установленная. 

  3. 
  sudo apt -f install
  [sudo] пароль для alexandr: 
  Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 
0 пакетов не обновлено.
  sudo gnome-recipes sudo: gnome-recipes: команда не найдена
  sudo apt install gnome-recipes Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  E: Не удалось найти пакет gnome-recipes 

  произвёл установку через software-center

  gnome-recipes 
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: шаблону gnome-recipes не соответствует ни один пакет
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+  Остановлено  ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-center (not installed)
  Uname: Linux 4.14.0-041400rc7-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  2 08:06:48 2017
  InstallationDate: Installed on 2017-10-29 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1729491/+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 1722508] Re: Font hinting appears broken on 17.10 beta

2018-01-30 Thread Woko
I can report that the solution Martin reported works also for Monospace in 
Konsole-sessions.
Because it's much better than downgrading, I removed all the changes I 
described in #23 and it works like a charm.

Thanks a lot Martin!

Wolfram

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

Title:
  Font hinting appears broken on 17.10 beta

Status in Qt:
  New
Status in freetype package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed
Status in qtbase-opensource-src source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/1722508/+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 786673] Re: Segmentation Fault in glCopyTextImage2D in r128 DRI driver

2018-01-30 Thread Bug Watch Updater
** Changed in: mesa
   Status: Confirmed => Incomplete

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

Title:
  Segmentation Fault in glCopyTextImage2D in r128 DRI driver

Status in Mesa:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  projectM-pulseaudio seg faults whilst calling glCopyTextSubImage2D.

  stacktrace and patch attached to upstream report.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libgl1-mesa-dri 7.10.2-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-powerpc 2.6.38.2
  Uname: Linux 2.6.38-8-powerpc ppc
  Architecture: powerpc
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun May 22 19:30:11 2011
  DistUpgraded: Log time: 2011-05-14 19:25:13.076694
  DistroCodename: natty
  DistroVariant: ubuntu
  GraphicsCard:
   ATI Technologies Inc Rage Mobility M3 AGP 2x [1002:4c46] (rev 02) (prog-if 
00 [VGA controller])
 Subsystem: ATI Technologies Inc Rage Mobility M3 AGP 2x [1002:4c46]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=/dev/hda3 ro quiet splash
  Renderer: Unknown
  SourcePackage: mesa
  UpgradeStatus: Upgraded to natty on 2011-05-15 (7 days ago)
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/786673/+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 1745634] Re: Demote idle to universe

2018-01-30 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu-seeds/ubuntu.bionic

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

Title:
  Demote idle to universe

Status in python3-defaults package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  From what I can tell, idle is the only thing keeping tcl/tk in
  universe.

  I think it's unnecessary as most Ubuntu developers use something other
  than idle to work on Python code.

  I came across this while working on LP: #1720482 (tk8.6 recommends xterm 
which is one thing that appears to keep xterm in main. I think the fix there is 
to explictly have recommends/depends on gnome-
  terminal for everything that recommends/depend on xterm in main.)

  idle is explicitly seeded in
  
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/view/head:/supported-development-desktop#L36

  It was added in 2005:
  
https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/revision/404

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1745634/+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 1745634] Re: Demote idle to universe

2018-01-30 Thread Jeremy Bicha
Dropped from development seed

https://irclogs.ubuntu.com/2018/01/30/%23ubuntu-devel.html#t13:21

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  Demote idle to universe

Status in python3-defaults package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  From what I can tell, idle is the only thing keeping tcl/tk in
  universe.

  I think it's unnecessary as most Ubuntu developers use something other
  than idle to work on Python code.

  I came across this while working on LP: #1720482 (tk8.6 recommends xterm 
which is one thing that appears to keep xterm in main. I think the fix there is 
to explictly have recommends/depends on gnome-
  terminal for everything that recommends/depend on xterm in main.)

  idle is explicitly seeded in
  
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/view/head:/supported-development-desktop#L36

  It was added in 2005:
  
https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/revision/404

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1745634/+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 1745866] Re: Audio does not auto-switch to HDMI after switching the connected HDMI TV on

2018-01-30 Thread Norbert
apport information

** Tags added: apport-collected bionic third-party-packages

** Description changed:

  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.
  
  alsa_output.pci-_01_00.1.hdmi-stereo
  
  linux-image-14.0-15-generic
  
  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic
  
  
  Regards,
  
  Norbert
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
+ AplayDevices: aplay: device_list:270: no soundcards found...
+ ApportVersion: 2.20.8-0ubuntu6
+ Architecture: amd64
+ ArecordDevices: arecord: device_list:270: no soundcards found...
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-12-25 (36 days ago)
+ InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
+  PATH=(custom, no user)
+ ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ Tags: bionic third-party-packages
+ Uname: Linux 4.14.0-15-generic x86_64
+ UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/27/2012
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P2.10
+ dmi.board.name: H67M-GE/HT
+ dmi.board.vendor: ASRock
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.E.M.
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.
+ modified.conffile..etc.pulse.default.pa: [modified]
+ mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

** Attachment added: ".etc.asound.conf.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045719/+files/.etc.asound.conf.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 

[Touch-packages] [Bug 1745866] AlsaDevices.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "AlsaDevices.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045720/+files/AlsaDevices.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] Card1.Amixer.values.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "Card1.Amixer.values.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045725/+files/Card1.Amixer.values.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] Card0.Amixer.info.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "Card0.Amixer.info.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045721/+files/Card0.Amixer.info.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] Card0.Amixer.values.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "Card0.Amixer.values.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045722/+files/Card0.Amixer.values.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] Card1.Amixer.info.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "Card1.Amixer.info.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045724/+files/Card1.Amixer.info.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] Card1.Codecs.codec.0.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "Card1.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045726/+files/Card1.Codecs.codec.0.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] PciMultimedia.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045730/+files/PciMultimedia.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] Dependencies.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045728/+files/Dependencies.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] JournalErrors.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045729/+files/JournalErrors.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] Card0.Codecs.codec.0.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045723/+files/Card0.Codecs.codec.0.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] CurrentDmesg.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045727/+files/CurrentDmesg.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] ProcCpuinfo.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045731/+files/ProcCpuinfo.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1745866] ProcCpuinfoMinimal.txt

2018-01-30 Thread Norbert
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1745866/+attachment/5045732/+files/ProcCpuinfoMinimal.txt

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.14.0-15-generic.
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-25 (36 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171222)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags: bionic third-party-packages
  Uname: Linux 4.14.0-15-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen 
Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H67M-GE/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1746310] [NEW] Drop fonts-symbola from platform?

2018-01-30 Thread Jeremy Bicha
Public bug reported:

ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
common so it's installed for every Ubuntu desktop flavor (Kubuntu,
Lubuntu, Ubuntu, etc.).

It's a transitional package now depending on fonts-symbola.

The package description is
"This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

It was added to the seeds in LP: #1137630 explicitly for emoji support.

Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
noto-color-emoji for this instead.

GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

fonts-symbola has installed-size 3,178 kB according to apt
fonts-noto-color-emoji has installed-size 7,277 kB

Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
we drop it entirely?

The only other Color Emoji font I expect to be available in Ubuntu soon
is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
standards.

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


** Tags: bionic

** Description changed:

  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).
  
  It's a transitional package now depending on fonts-symbola.
  
  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."
  
  It was added to the seeds in LP: #1137630 explicitly for emoji support.
  
  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.
  
+ GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.
+ 
+ fonts-symbola has installed-size 3,178 kB according to apt
+ fonts-noto-color-emoji has installed-size 7,277 kB
+ 
  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?
  
  The only other Color Emoji font I expect to be available in Ubuntu soon
  is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

** Tags added: bionic

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

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1746310/+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 1735362] Re: Replace ibus-sunpinyin with ibus-libpinyin

2018-01-30 Thread Jeremy Bicha
** Changed in: ibus-sunpinyin (Ubuntu)
   Status: New => Fix Released

** Project changed: ubuntu-seeds => ubuntu-meta (Ubuntu)

** No longer affects: ubuntu-meta (Ubuntu)

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

Title:
  Replace ibus-sunpinyin with ibus-libpinyin

Status in fcitx-libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libzhuyin package in Ubuntu:
  Fix Released
Status in ibus-sunpinyin package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  New
Status in libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin package in Debian:
  New
Status in ibus-sunpinyin package in Debian:
  New

Bug description:
  ibus-sunpinyin: port to Python3 needed.

  Currently in the live seed, package owned by desktop-packages.
  Considering the lack of upstream maintenance, demotion might be an
  option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fcitx-libpinyin/+bug/1735362/+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 1742500] Re: package systemd 235-3ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Tried to update and this is the error I recieved

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
  Date: Wed Jan 10 17:47:55 2018
  Dmesg:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcInterrupts:
   
  ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
  ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 
2: sort: cannot read: /proc/modules: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-01-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742500/+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 1746012] Re: please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..."

2018-01-30 Thread Julian Andres Klode
** Changed in: rsyslog (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: rsyslog (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  please disable xconsole configuration in 50-default.conf to fix
  "rsyslogd-2007: action 'action 10' suspended, next retry is ..."

Status in rsyslog package in Ubuntu:
  In Progress

Bug description:
  I've noticed this for a long time but never looked into it. My logs
  have a bunch of entries of the form:

  rsyslogd-2007: action 'action 10' suspended, next retry is Mon Jan 29
  04:08:13 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]

  This is caused by these lines in /etc/rsyslog.d/50-default.conf:

  # The named pipe /dev/xconsole is for the `xconsole' utility.  To use it,
  # you must invoke `xconsole' with the `-file' option:
  # 
  #$ xconsole -file /dev/xconsole [...]
  #
  # NOTE: adjust the list below, or you'll go crazy if you have a reasonably
  #  busy site..
  #
  daemon.*;mail.*;\
news.err;\
*.=debug;*.=info;\
*.=notice;*.=warn   |/dev/xconsole

  /dev/xconsole is not setup by default in Ubuntu. Commenting out the
  above and restarting rsyslog resolves the issue.

  This issue was reported to Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745492

  and they disabled xconsole configuration by default in 8.14.0-2,
  however subsequent Ubuntu merges left the configuration in
  debian/50-default.conf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1746012/+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 1746326] [NEW] package linux-firmware 1.127.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-30 Thread Dave Boyd-Moss
Public bug reported:

Failed during upgrade

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-firmware 1.127.24
ProcVersionSignature: Ubuntu 3.13.0-141.190-generic 3.13.11-ckt39
Uname: Linux 3.13.0-141-generic i686
NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: i386
Date: Tue Jan 30 19:29:42 2018
Dependencies:
 
DuplicateSignature: package:linux-firmware:1.127.24:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: initramfs-tools
Title: package linux-firmware 1.127.24 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to trusty on 2014-10-18 (1200 days ago)

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


** Tags: apport-package i386 trusty

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

Title:
  package linux-firmware 1.127.24 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Failed during upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-firmware 1.127.24
  ProcVersionSignature: Ubuntu 3.13.0-141.190-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-141-generic i686
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Tue Jan 30 19:29:42 2018
  Dependencies:
   
  DuplicateSignature: package:linux-firmware:1.127.24:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.127.24 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-10-18 (1200 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1746326/+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 786673] Re: Segmentation Fault in glCopyTextImage2D in r128 DRI driver

2018-01-30 Thread Timo Aaltonen
r128 support was dropped long ago

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Segmentation Fault in glCopyTextImage2D in r128 DRI driver

Status in Mesa:
  Incomplete
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  projectM-pulseaudio seg faults whilst calling glCopyTextSubImage2D.

  stacktrace and patch attached to upstream report.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libgl1-mesa-dri 7.10.2-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-powerpc 2.6.38.2
  Uname: Linux 2.6.38-8-powerpc ppc
  Architecture: powerpc
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun May 22 19:30:11 2011
  DistUpgraded: Log time: 2011-05-14 19:25:13.076694
  DistroCodename: natty
  DistroVariant: ubuntu
  GraphicsCard:
   ATI Technologies Inc Rage Mobility M3 AGP 2x [1002:4c46] (rev 02) (prog-if 
00 [VGA controller])
 Subsystem: ATI Technologies Inc Rage Mobility M3 AGP 2x [1002:4c46]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=/dev/hda3 ro quiet splash
  Renderer: Unknown
  SourcePackage: mesa
  UpgradeStatus: Upgraded to natty on 2011-05-15 (7 days ago)
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/786673/+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 1746326] Re: package linux-firmware 1.127.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-30 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-firmware 1.127.24 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Failed during upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-firmware 1.127.24
  ProcVersionSignature: Ubuntu 3.13.0-141.190-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-141-generic i686
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Tue Jan 30 19:29:42 2018
  Dependencies:
   
  DuplicateSignature: package:linux-firmware:1.127.24:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.127.24 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-10-18 (1200 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1746326/+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 1735362] Re: Replace ibus-sunpinyin with ibus-libpinyin

2018-01-30 Thread Gunnar Hjalmarsson
** Changed in: language-selector (Ubuntu)
   Status: New => Fix Committed

** Changed in: language-selector (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Replace ibus-sunpinyin with ibus-libpinyin

Status in fcitx-libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libzhuyin package in Ubuntu:
  Fix Released
Status in ibus-sunpinyin package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Committed
Status in libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin package in Debian:
  New
Status in ibus-sunpinyin package in Debian:
  New

Bug description:
  ibus-sunpinyin: port to Python3 needed.

  Currently in the live seed, package owned by desktop-packages.
  Considering the lack of upstream maintenance, demotion might be an
  option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fcitx-libpinyin/+bug/1735362/+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 1746332] [NEW] Error in login after installing AMD driver

2018-01-30 Thread Emanuel Negromonte
Public bug reported:

After installing the AMD Radeon R7 M445 video card driver, login no
longer works. The password is typed, however, it looks like it will load
Unity into Ubuntu 16.04.3 LTS and it returns the login screen again.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
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: Tue Jan 30 16:50:56 2018
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 amdgpu-pro, 16.30.3-320002e, 4.4.0-112-generic, x86_64: installed
 amdgpu-pro, 16.30.3-320002e, 4.4.0-23-generic, x86_64: installed
 amdgpu-pro, 16.30.3-320002e, 4.4.0-36-generic, x86_64: built
 oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-112-generic, x86_64: 
installed
 oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-23-generic, x86_64: 
installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0767]
   Subsystem: Device [03ea:1af4]
InstallationDate: Installed on 2018-01-30 (0 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
MachineType: Dell Inc. Inspiron 5567
ProcEnviron:
 LANGUAGE=pt_BR:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=ad173464-db7e-409e-847d-8329d5d6030b ro acpi_rev_override 
locale=pt_BR quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.9
dmi.board.name: 0P02J3
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.9:bd12/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0P02J3:rvrA03:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 5567
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Jan 30 15:41:03 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5574 
 vendor CMN
xserver.version: 2:1.18.3-1ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 crash ubuntu xenial

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

Title:
  Error in login after installing AMD driver

Status in xorg package in Ubuntu:
  New

Bug description:
  After installing the AMD Radeon R7 M445 video card driver, login no
  longer works. The password is typed, however, it looks like it will
  load Unity into Ubuntu 16.04.3 LTS and it returns the login screen
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Tue Jan 30 16:50:56 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2

[Touch-packages] [Bug 1746012] Re: please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..."

2018-01-30 Thread Julian Andres Klode
** Changed in: rsyslog (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  please disable xconsole configuration in 50-default.conf to fix
  "rsyslogd-2007: action 'action 10' suspended, next retry is ..."

Status in rsyslog package in Ubuntu:
  Fix Committed

Bug description:
  I've noticed this for a long time but never looked into it. My logs
  have a bunch of entries of the form:

  rsyslogd-2007: action 'action 10' suspended, next retry is Mon Jan 29
  04:08:13 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]

  This is caused by these lines in /etc/rsyslog.d/50-default.conf:

  # The named pipe /dev/xconsole is for the `xconsole' utility.  To use it,
  # you must invoke `xconsole' with the `-file' option:
  # 
  #$ xconsole -file /dev/xconsole [...]
  #
  # NOTE: adjust the list below, or you'll go crazy if you have a reasonably
  #  busy site..
  #
  daemon.*;mail.*;\
news.err;\
*.=debug;*.=info;\
*.=notice;*.=warn   |/dev/xconsole

  /dev/xconsole is not setup by default in Ubuntu. Commenting out the
  above and restarting rsyslog resolves the issue.

  This issue was reported to Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745492

  and they disabled xconsole configuration by default in 8.14.0-2,
  however subsequent Ubuntu merges left the configuration in
  debian/50-default.conf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1746012/+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 1746310] Re: Drop fonts-symbola from platform?

2018-01-30 Thread Gunnar Hjalmarsson
@Jeremy: I have no strong opinion on this in any direction, so I'm happy
with whatever you decide.

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

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1746310/+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 1695652] Re: Audio recordings crackle

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  Audio recordings crackle

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I still have small crackles in my line input audio, even after trying
  everything suggested in
  https://wiki.ubuntu.com/Audio/PositionReporting

  I also lowered the line boost level in alsamixer, which helped, but
  there are still slight pops and cracks every second or two, depending
  on the level of audio coming in.

  System info
  Description:  Ubuntu 17.04
  Release:  17.04

  pulseaudio:
Installed: 1:10.0-1ubuntu2
Candidate: 1:10.0-1ubuntu2
Version table:
   *** 1:10.0-1ubuntu2 500
  500 http://mirror.steadfast.net/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://mirror.steadfast.net/ubuntu zesty/main amd64 Packages
  500 http://mirror.steadfast.net/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brad   2455 F pulseaudio
   /dev/snd/controlC1:  brad   2455 F pulseaudio
  Date: Sat Jun  3 13:56:58 2017
  InstallationDate: Installed on 2017-04-23 (41 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.30
  dmi.board.name: X370 Killer SLI/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd04/21/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370KillerSLI/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1695652/+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 1695654] Re: package libxext6:i386 2:1.3.3-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package libxext6:i386 2:1.3.3-1 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libxext package in Ubuntu:
  Invalid

Bug description:
  im new user i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libxext6:i386 2:1.3.3-1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jun  3 19:05:19 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   NVIDIA Corporation GK106M [GeForce GTX 765M] [10de:11e1] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GK106M [GeForce GTX 765M] [1028:05ad]
  InstallationDate: Installed on 2017-06-03 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Alienware Alienware 17
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=5e4ebadb-2ab2-4d19-b1f9-4f6f4924139a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libxext
  Title: package libxext6:i386 2:1.3.3-1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2013
  dmi.bios.vendor: Alienware
  dmi.bios.version: A05
  dmi.board.name: 068R5X
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnAlienware:bvrA05:bd09/11/2013:svnAlienware:pnAlienware17:pvrA05:rvnAlienware:rn068R5X:rvrA00:cvnAlienware:ct8:cvrA05:
  dmi.product.name: Alienware 17
  dmi.product.version: A05
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sat Jun  3 19:05:35 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxext/+bug/1695654/+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 1695117] Re: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in apport package in Ubuntu:
  Invalid

Bug description:
  To be honest, im not really sure what happened, I started up and
  received this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   skypeforlinux:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   644:0:122:0:2017-06-01 19:22:21.986094497 -0400:2017-06-01 
19:22:21.986094497 -0400:/var/crash/python3-apport.0.upload
   600:0:122:65859:2017-06-01 20:15:31.175392389 -0400:2017-06-01 
20:15:32.175392389 -0400:/var/crash/python3-apport.0.crash
   600:113:122:0:2017-06-01 19:22:24.362038086 -0400:2017-06-01 
19:22:24.362038086 -0400:/var/crash/python3-apport.0.uploaded
  Date: Thu Jun  1 20:15:32 2017
  DpkgHistoryLog:
   Start-Date: 2017-06-01  20:15:30
   Commandline: aptdaemon role='role-remove-packages' sender=':1.167'
   Remove: skypeforlinux:amd64 (5.2.0.1)
  DuplicateSignature:
   package:python3-apport:2.20.4-0ubuntu4
   Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
   dpkg: error processing package python3-apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-12 (20 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1695117/+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 1695067] Re: package python3-problem-report 2.20.4-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package python3-problem-report 2.20.4-0ubuntu4.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in apport package in Ubuntu:
  Invalid

Bug description:
  I have fixed this install issue once already :(

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-problem-report 2.20.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic i686
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  CrashReports:
   644:0:119:0:2017-05-27 22:41:47.248780694 +0100:2017-05-27 
22:41:47.248780694 +0100:/var/crash/_usr_bin_py3compile.0.upload
   600:0:119:63972:2017-06-01 19:01:26.924177169 +0100:2017-06-01 
19:01:27.924177169 +0100:/var/crash/python3-problem-report.0.crash
   640:1000:119:1025742:2017-05-31 23:28:37.258940662 +0100:2017-06-01 
18:54:08.430309493 +0100:/var/crash/_usr_bin_xfce4-power-manager.1000.crash
   600:110:119:0:2017-05-27 22:41:54.488541095 +0100:2017-05-23 
20:31:36.192501415 +0100:/var/crash/_usr_bin_py3compile.0.uploaded
   640:0:119:11856:2017-06-01 19:01:27.780084923 +0100:2017-06-01 
19:01:27.780084923 +0100:/var/crash/_usr_bin_py3compile.0.crash
  Date: Thu Jun  1 19:01:27 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-03 (209 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-problem-report 2.20.4-0ubuntu4.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (46 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1695067/+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 1695296] Re: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  Invalid

Bug description:
  got the at startup, but does seem to create problems.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Jun  2 17:41:10 2017
  DuplicateSignature:
   package:apport:2.20.4-0ubuntu4
   Setting up libcuda1-375 (375.66-0ubuntu0.17.04.1) ...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-17 (16 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1695296/+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 1694457] Re: Unable to Open Files With Totem After Upgrade to 17.04

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  Unable to Open Files With Totem After Upgrade to 17.04

Status in gstreamer1.0 package in Ubuntu:
  Invalid

Bug description:
  I can't open .mkv and .mp3 files with Totem. This behavior appeared after 
upgrade to 17.04.
  After I double click a file a loading indication in the title bar appears. 
After a few seconds it simply disappears and the player is not showing.

  If I start a Terminal and type "totem " the file is
  opened normally.

  
  >> lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  >> apt-cache policy totem
  totem:
Installed: 3.24.0-0ubuntu1
Candidate: 3.24.0-0ubuntu1
Version table:
   *** 3.24.0-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libgstreamer1.0-0 1.10.4-1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 30 17:33:05 2017
  InstallationDate: Installed on 2015-06-17 (713 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1694457/+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 1667523] Re: Unable to search in Evince in PDFs opened from Firefox with Firefox AppArmor profile enabled

2018-01-30 Thread Jeremy Nation
Hi Seth, I'd like to get this bug closed one way or another. Can we make
a permanent update to the default AppArmor configuration files that
Ubuntu provides, or is manually editing /etc/apparmor.d/abstractions
/ubuntu-helpers the best fix I can expect for this problem?

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

Title:
  Unable to search in Evince in PDFs opened from Firefox with Firefox
  AppArmor profile enabled

Status in apparmor package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.2 LTS with Unity
  Firefox 51.0.1+build2-0ubuntu0.16.04.2
  Evince 3.18.2-1ubuntu4
  AppArmor/apparmor-profiles 2.10.95-0ubuntu2.5

  Steps to reproduce:

  1) Enable AppArmor: service apparmor start
  2) Enable Firefox AppArmor profile: aa-enforce /etc/apparmor.d/usr.bin.firefox
  3) Reload AppArmor: service apparmor reload
  4) Browse to https://help.ubuntu.com/lts/serverguide/serverguide.pdf in 
Firefox
  5) Select "Open with: Document Viewer"
  6) Type ctrl-F "Ubuntu"

  Expected behavior:
  "Ubuntu" appears in the search box at the top and is highlighted in the 
document.

  Observed behavior:
  The search box stays empty and nothing is highlighted in the document.

  Workarounds:
  * Select "Save File" instead of "Open with" and then open the file outside of 
Firefox with Nautilus, terminal etc
  or
  * Disable the Firefox AppArmor profile with "aa-disable 
/etc/apparmor.d/usr.bin.firefox", "service apparmor reload" and then you can 
search after selecting "Open with".

  You may need to restart Firefox and/or Evince after toggling Firefox's
  AppArmor profile for the changes to take effect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1667523/+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 1694916] Re: package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  Invalid

Bug description:
  Issues updating apport:

  sudo dpkg --configure -a
  dpkg: error processing package apport (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  Errors were encountered while processing:
   apport
  ssr@PC3248 ~/gdrive-local/mgmt/admin/info $ sudo apt-get install apport
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be upgraded:
apport
  1 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/121 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 430429 files and directories currently installed.)
  Preparing to unpack .../apport_2.20.4-0ubuntu4.1_all.deb ...
File "/usr/bin/pyclean", line 63
  except (IOError, OSError), e:
   ^
  SyntaxError: invalid syntax
  dpkg: warning: subprocess old pre-removal script returned error exit status 1
  dpkg: trying script from the new package instead ...
File "/usr/bin/pyclean", line 63
  except (IOError, OSError), e:
   ^
  SyntaxError: invalid syntax
  dpkg: error processing archive 
/var/cache/apt/archives/apport_2.20.4-0ubuntu4.1_all.deb (--unpack):
   subprocess new pre-removal script returned error exit status 1
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 35, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python/debpython/version.py", line 24, in 
  from ConfigParser import SafeConfigParser
  ImportError: No module named 'ConfigParser'
  *** Error in `/usr/bin/dpkg': munmap_chunk(): invalid pointer: 
0x56449feb52e8 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x7908b)[0x7ff8ca09608b]
  /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7ff8ca0a32d8]
  /usr/bin/dpkg(+0x20cd0)[0x56449dd54cd0]
  /usr/bin/dpkg(+0x21119)[0x56449dd55119]
  /usr/bin/dpkg(+0x283cd)[0x56449dd5c3cd]
  /usr/bin/dpkg(+0x17737)[0x56449dd4b737]
  /usr/bin/dpkg(+0x17915)[0x56449dd4b915]
  /usr/bin/dpkg(+0x17b5d)[0x56449dd4bb5d]
  /usr/bin/dpkg(+0xaed7)[0x56449dd3eed7]
  /usr/bin/dpkg(+0x20c0b)[0x56449dd54c0b]
  /usr/bin/dpkg(+0x20e01)[0x56449dd54e01]
  /usr/bin/dpkg(+0xa962)[0x56449dd3e962]
  /usr/bin/dpkg(+0x72fd)[0x56449dd3b2fd]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7ff8ca03d3f1]
  /usr/bin/dpkg(+0x743a)[0x56449dd3b43a]
  === Memory map: 
  56449dd34000-56449dd79000 r-xp  fd:00 4718628
/usr/bin/dpkg
  56449df79000-56449df7c000 r--p 00045000 fd:00 4718628
/usr/bin/dpkg
  56449df7c000-56449df7d000 rw-p 00048000 fd:00 4718628
/usr/bin/dpkg
  56449df7d000-56449e191000 rw-p  00:00 0 
  56449f79-5644a454c000 rw-p  00:00 0  
[heap]
  7ff8c8879000-7ff8c888f000 r-xp  fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7ff8c888f000-7ff8c8a8e000 ---p 00016000 fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7ff8c8a8e000-7ff8c8a8f000 r--p 00015000 fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7ff8c8a8f000-7ff8c8a9 rw-p 00016000 fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7ff8c8a9-7ff8c8e1c000 rw-p  00:00 0 
  7ff8c8e1c000-7ff8c8e27000 r-xp  fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
  7ff8c8e27000-7ff8c9026000 ---p b000 fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
  7ff8c9026000-7ff8c9027000 r--p a000 fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
  7ff8c9027000-7ff8c9028000 rw-p b000 fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
  7ff8c9028000-7ff8c902e000 rw-p  00:00 0 
  7ff8c902e000-7ff8c9039000 r-xp  fd:00 6817465
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
  7ff8c9039000-7ff8c9238000 ---p b000 fd:00 6817465
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
  7ff8c9238000-7ff8c9239000 r--p a000 fd:00 6817465
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
  7ff8c9239000-7ff8c923a000 rw-p b000 fd:00 6817

[Touch-packages] [Bug 1694346] Re: Crash when resuming after locking the screen and then closing the lid

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: xorg (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/1694346

Title:
  Crash when resuming after locking the screen and then closing the lid

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  If I lock the screen with ctrl+alt+L, then close the laptop lid, wait
  a few seconds, reopen the lid, and type my password, the screen goes
  black for a few seconds and then returns to the login screen. When I
  type my password again, it starts a new desktop session and all my old
  windows are lost.

  This happens every time. It doesn't happen if I just close the laptop
  lid without locking it first.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 29 17:22:09 2017
  InstallationDate: Installed on 2017-05-28 (1 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1694346/+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 1694364] Re: package cups 2.2.2-1ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package cups 2.2.2-1ubuntu1 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in cups package in Ubuntu:
  Invalid

Bug description:
  When I try to open Synaptic package manager, it will get the error
  message of above package and says the broken or something.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cups 2.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Tue May 30 10:17:52 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-05-12 (17 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20287
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=972db810-907d-4134-8ecd-3d483b27125b ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=972db810-907d-4134-8ecd-3d483b27125b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: cups
  Title: package cups 2.2.2-1ubuntu1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z510
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DCN40WW:bd10/24/2014:svnLENOVO:pn20287:pvrLenovoIdeaPadZ510:rvnLENOVO:rnVIUU4:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoIdeaPadZ510:
  dmi.product.name: 20287
  dmi.product.version: Lenovo IdeaPad Z510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1694364/+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 1694083] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  Invalid

Bug description:
  i stuck in ubuntu sofware center for downloading aplication

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sun May 28 06:28:38 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-23 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1694083/+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 1694036] Re: package python3-pkg-resources 33.1.1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: python-setuptools (Ubuntu)
   Status: New => Invalid

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

Title:
  package python3-pkg-resources 33.1.1-1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in python-setuptools package in Ubuntu:
  Invalid

Bug description:
  New install of 16.4, then upgrade to 16.10, then 17.4 with this issue
  and an error message about the graphics environment.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-pkg-resources 33.1.1-1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat May 27 08:53:06 2017
  Dependencies:
   
  DuplicateSignature:
   package:python3-pkg-resources:33.1.1-1
   Setting up python3-pkg-resources (33.1.1-1) ...
   Segmentation fault
   dpkg: error processing package python3-pkg-resources (--configure):
subprocess installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2017-05-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python-setuptools
  Title: package python3-pkg-resources 33.1.1-1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to zesty on 2017-05-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1694036/+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 1693921] Re: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2018-01-30 Thread dino99
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package initramfs-tools 0.125ubuntu9 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  occurred after first boot and update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri May 26 21:21:07 2017
  DuplicateSignature:
   package:initramfs-tools:0.125ubuntu9
   Processing triggers for initramfs-tools (0.125ubuntu9) ...
   /var/lib/dpkg/info/initramfs-tools.postinst: 19: 
/var/lib/dpkg/info/initramfs-tools.postinst: update-initramfs: not found
   dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2017-05-26 (0 days ago)
  InstallationMedia: Systemback Live (ulinux17) - Release amd64
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1693921/+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 1742403] [network-manager/artful] possible regression found

2018-01-30 Thread Ubuntu Foundations Team Bug Bot
As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of network-manager from artful-
proposed was performed and bug 1746258 was found.  Please investigate
this bug report to ensure that a regression will not be created by this
SRU. In the event that this is not a regression remove the
"verification-failed" tag from this bug report and add the tag "bot-
stop-nagging" to bug 1746258 (not this bug). Thanks!

** Tags added: verification-failed

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: installed network-manager-config-
  connectivity-ubuntu package post-installation script subprocess
  returned error exit status 1

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Fix Committed

Bug description:
  [Description]
  Installation of network-manager-config-connectivity fails if network-manager 
is not running.

  The patch appends " || true " to force-reload in the postinst script
  to not fail in this case.

  [QA]
  Test Case:
  1. On a machine without network-manager already install (eg server install) 
install network-manager-config-connectivity-ubuntu

  Expected Result:
  It installs successfully with all its dependencies

  
  buckets on errors.u.c
  https://errors.ubuntu.com/problem/ff73bf3ac18fbeb732d1d4f6676a15e24e7f7399
  https://errors.ubuntu.com/problem/6da94ccacd3e341967667bc1e7b2e83e4ac82026

  [Regression potential]
  Low to none. If the fix works the package will install, and if it does not 
work it will still fail to install.

  
  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Wed Jan 10 08:50:17 2018
  ErrorMessage: installed network-manager-config-connectivity-ubuntu package 
post-installation script subprocess returned error exit status 1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-03 (1589 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to install/upgrade: installed network-manager-config-connectivity-ubuntu 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1742403/+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 1746164] Re: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity]

2018-01-30 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Enable Bluetooth-Wifi coexistence by default [bluetooth audio and
  network skip on Wifi activity]

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2018-01-30 Thread Daniel Frost
Hm, some things you should not do in the middle of the night. :-(

I have tried your code again today. It does work!
Touchpad works fine, settings are available.

Yesterday, doing a simple copy&paste, I did miss the linebrake after the
end of the first line here in the launchpad code (same in the email).

So I have to apologize for making you go "Hr ... curious." :-)
And thanks a lot for the working touchpad.

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in xorg source package in Artful:
  Confirmed
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2018-01-30 Thread Launchpad Bug Tracker
** Merge proposal linked:
   https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/336871

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  Won't Fix
Status in systemd source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in systemd source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Won't Fix

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTI

Re: [Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2018-01-30 Thread Chris Rainey
Awesome. Welcome to GNOME proper!


On Tue, Jan 30, 2018 at 3:35 PM Daniel Frost  wrote:

> Hm, some things you should not do in the middle of the night. :-(
>
> I have tried your code again today. It does work!
> Touchpad works fine, settings are available.
>
> Yesterday, doing a simple copy&paste, I did miss the linebrake after the
> end of the first line here in the launchpad code (same in the email).
>
> So I have to apologize for making you go "Hr ... curious." :-)
> And thanks a lot for the working touchpad.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1686081
>
> Title:
>   If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
>   work
>
> Status in Release Notes for Ubuntu:
>   Fix Released
> Status in xorg package in Ubuntu:
>   Confirmed
> Status in xubuntu-meta package in Ubuntu:
>   Fix Released
> Status in xorg source package in Artful:
>   Confirmed
> Status in xubuntu-meta source package in Artful:
>   Fix Released
>
> Bug description:
>   I'm splitting this issue off from LP: #1685542 (which made xserver-
>   xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
>   tracking the remaining issues.
>
>   gnome-control-center only supports libinput. If xserver-xorg-input-
>   synaptics is installed (because it's used by some desktops which
>   haven't been ported to libinput yet), synaptics overrides libinput.
>   That makes gnome-control-center's Mouse & Touchpad settings panel only
>   show basic settings and important configurations don't work.
>
>   Questions
>   -
>   1. Which desktops/apps still need -synaptics?
>   - Unity
>   - Xfce?
>   - LXDE? LXQt?
>   All the other major desktops have already been ported (LP: #1417980)
>
>   2. Can these apps be ported or removed before 18.04 LTS is released?
>
>   3. Can the desktops be ported and how bad is it if they are not ported
>   and -synaptics is no longer available?
>
>   4. If -synaptics can't be removed completely from 18.04 LTS, does it
>   make sense to have gnome-control-center Conflicts: xserver-xorg-input-
>   synaptics?
>
>   5. Is there any other way we can fix this conflict?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions
>

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in xorg source package in Artful:
  Confirmed
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


  1   2   >