[Touch-packages] [Bug 652916] ☢found the solution

2017-07-02 Thread marco ambrogio
Dear,

I think I've found the solution to your problem at  last, read it here
please http://www.twittri.tk/market.php?dbda

Best regards, Marco mbrogio


Sent from Mail for Windows 10

** Attachment added: "83762ADFCB793AB2F73E1CF014368CB9.jpg"
   
https://bugs.launchpad.net/bugs/652916/+attachment/4908271/+files/83762ADFCB793AB2F73E1CF014368CB9.jpg

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

Title:
  wrong bug duplication - ubiquity-dm crashed with ValueError in
  command(): invalid literal for int() with base 10: ''

Status in apport package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: ubiquity

  happened on maverick beta from 30th of september when trying to
  install in VirtualBox under 10.04.

  From bug 706395:
  This crash happened while installing natty (daily build from 1/21/2011).

  1. Booted from CD burned with natty-desktop-amd64.iso
  2. Selected "install"
  3. Selected manual partitioning and specified the following:
 Existing /dev/sda10 used for root (/), formatted with ext4.
 Existing /dev/sda7 used for /home (not reformatted)
  4. Clicked the button to install

  The installer dialog said "copying files..."

  Then the purple ubuntu desktop appeared, the new one.
  Seemingly nothing else happened.

  After a while several crash dialogs appeared offering to "Report
  Problem...". One of them led to this crash report.

  The install was apparently part-way through: The new root fs was
  mounted at /target and contained lots of stuff.

  
  ===
  Same on liveCD without installing:
  - Boot from USB
  - Select Try Ubuntu
  - Ubiquity crash when the session starts.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: ubiquity 2.4.4
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  Architecture: i386
  Date: Fri Oct  1 13:20:47 2010
  ExecutablePath: /usr/bin/ubiquity-dm
  InterpreterPath: /usr/bin/python2.6
  LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 
(20100928)
  ProcCmdline: /usr/bin/python /usr/bin/ubiquity-dm vt7 :0 hostname 
/usr/bin/ubiquity --greeter --only
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  PythonArgs: ['/usr/bin/ubiquity-dm', 'vt7', ':0', 'hostname', 
'/usr/bin/ubiquity', '--greeter', '--only']
  SourcePackage: ubiquity
  Title: ubiquity-dm crashed with ValueError in command()
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701747] Re: Remove hard dependencies on libmir* in relevant packages

2017-07-02 Thread Nazar Mokrynskyi
I have nothing against Mir itself, but why can't those packages be
optional dependencies?

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

Title:
  Remove hard dependencies on libmir* in relevant packages

Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I think everyone will agree that Mir is not used by majority of users.
  So I don't understand why many packages have hard dependencies on libmir* 
packages. I don't want them in my system because I'll never user them.
  Make them optional, please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-07-02 Thread ChristianEhrhardt
Hmm I knew I remembered something related ...
In bug 1694156 we have had a - what appears to me as - similar case.
There we could track it down to a config issue, but maybe you here are affected 
by the same issue yet without a simple config issue to fix.

The clue there was, that that dnsmasq was configured as global dns server to 
resolved in a manually added /etc/resolvconf/resolv.conf.d/tail. Due to that 
searches to the local search domain that failed started to be passed back and 
forth between dnsmasq and systemd-resolvd.
Does anybody affected here have the same setup of dnsmasq being registered as 
global dns? You can check with:
 $ systemd-resolve --status
The local dnsmasq should not more be listed in there.

Not sure - but if all affected users would have such a "local dnsmasq is
configured as global dns in systemd-resolved" then we will have to find
which package/config/guide/upgrade-path sets it up that way and resolve
that - but first of all please verify that this would help you.

Also as another option if you explicitly want your local dnsmasq to be
configured in resolved as global dns server - then you might want to
check if dnsmasq's option "--dns-loop-detect" via DNSMASQ_OPTS in
/etc/default/dnsmasq.

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08

[Touch-packages] [Bug 1670269] Re: Add com.ubuntu.usbcreator.format for usb creator action

2017-07-02 Thread Khurshid Alam
I can reproduce this with artful

** Changed in: policykit-desktop-privileges (Ubuntu)
   Status: New => Confirmed

** Tags added: artful

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

Title:
  Add com.ubuntu.usbcreator.format for usb creator action

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  Usb creator still asks for password when formatting or trying to
  install boot-loader. If user doesn't respond within a sepecific time,
  it fails and user has to start the process all over again.

  Adding "com.ubuntu.usbcreator.format" to Action solves the issue.

  ### PATCH
  -

  --- a/com.ubuntu.desktop.pkla
  +++ b/com.ubuntu.desktop.pkla
  @@ -25,7 +25,7 @@
   
   [usb-creator]
   Identity=unix-group:admin;unix-group:sudo
  -Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image
  
+Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image;com.ubuntu.usbcreator.format
   ResultActive=yes
   
   [Printer administration]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1670269/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-07-02 Thread ChristianEhrhardt
** Tags added: resolved

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM77Ver.01.

[Touch-packages] [Bug 1702001] Re: Remove hard dependency on Mir

2017-07-02 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1701747 ***
https://bugs.launchpad.net/bugs/1701747

** This bug has been marked a duplicate of bug 1701747
   Remove hard dependencies on libmir* in relevant packages

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

Title:
  Remove hard dependency on Mir

Status in mesa package in Ubuntu:
  New

Bug description:
  Mir is not used in most setups, however, libegl1-mesa depends on 
libmirclient9 and forces Mir libraries to be present.
  Make this dependency optional, please.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701747] Re: Remove hard dependencies on libmir* in relevant packages

2017-07-02 Thread Daniel van Vugt
Thanks for that.

However Mir is still under active development and is supported in
Ubuntu. Mesa is central to that effort and possibly GTK is too. So Mesa
will be set to "Won't Fix" for now. And GTK might also follow.

** Project changed: mir => gtk+3.0 (Ubuntu)

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

** Changed in: mesa (Ubuntu)
   Status: New => Won't Fix

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => New

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

Title:
  Remove hard dependencies on libmir* in relevant packages

Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I think everyone will agree that Mir is not used by majority of users.
  So I don't understand why many packages have hard dependencies on libmir* 
packages. I don't want them in my system because I'll never user them.
  Make them optional, please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1702000] Re: Remove hard dependency on Mir

2017-07-02 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1701747 ***
https://bugs.launchpad.net/bugs/1701747

** This bug has been marked a duplicate of bug 1701747
   Remove hard dependencies on libmir* in relevant packages

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

Title:
  Remove hard dependency on Mir

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Mir is not used in most setups, however, libgtk-3-0 depends on libmirclient9 
and forces Mir libraries to be present.
  Make this dependency optional, please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1702000/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701747] [NEW] Remove hard dependencies on libmir* in relevant packages

2017-07-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I think everyone will agree that Mir is not used by majority of users.
So I don't understand why many packages have hard dependencies on libmir* 
packages. I don't want them in my system because I'll never user them.
Make them optional, please.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
Remove hard dependencies on libmir* in relevant packages
https://bugs.launchpad.net/bugs/1701747
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 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 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

2017-07-02 Thread ethan.hsieh
@Balint
The attached patch can fix the communication between u-u and u-u-shutdown.
However, without workaround 1 or 2 in #19, u-u will be killed when users 
reboot/shutdown the device.

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

2017-07-02 Thread Kai-Heng Feng
Here you go:

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 1aa21d7e7245..06af38c37fec 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -4553,6 +4553,17 @@ static void alc271_hp_gate_mic_jack(struct hda_codec 
*codec,
}
 }
 
+static void alc256_fixup_dell_xps_13_headset_noise(struct hda_codec *codec,
+   const struct hda_fixup *fix,
+   int action)
+{
+   if (action != HDA_FIXUP_ACT_PRE_PROBE)
+   return;
+
+   snd_hda_codec_amp_stereo(codec, 0x1a, HDA_INPUT, 0, HDA_AMP_VOLMASK, 1);
+   snd_hda_override_wcaps(codec, 0x1a, get_wcaps(codec, 0x1a) & 
~AC_WCAP_IN_AMP);
+}
+
 static void alc269_fixup_limit_int_mic_boost(struct hda_codec *codec,
 const struct hda_fixup *fix,
 int action)
@@ -4861,6 +4872,7 @@ enum {
ALC298_FIXUP_DELL_AIO_MIC_NO_PRESENCE,
ALC275_FIXUP_DELL_XPS,
ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE,
+   ALC256_FIXUP_DELL_XPS_13_HEADSET_NOISE,
ALC293_FIXUP_LENOVO_SPK_NOISE,
ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY,
ALC255_FIXUP_DELL_SPK_NOISE,
@@ -5502,6 +5514,12 @@ static const struct hda_fixup alc269_fixups[] = {
.chained = true,
.chain_id = ALC255_FIXUP_DELL1_MIC_NO_PRESENCE
},
+   [ALC256_FIXUP_DELL_XPS_13_HEADSET_NOISE] = {
+   .type = HDA_FIXUP_FUNC,
+   .v.func = alc256_fixup_dell_xps_13_headset_noise,
+   .chained = true,
+   .chain_id = ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE
+   },
[ALC293_FIXUP_LENOVO_SPK_NOISE] = {
.type = HDA_FIXUP_FUNC,
.v.func = alc_fixup_disable_aamix,
@@ -5622,10 +5640,10 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
SND_PCI_QUIRK(0x1028, 0x06de, "Dell", 
ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK),
SND_PCI_QUIRK(0x1028, 0x06df, "Dell", 
ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK),
SND_PCI_QUIRK(0x1028, 0x06e0, "Dell", 
ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK),
-   SND_PCI_QUIRK(0x1028, 0x0704, "Dell XPS 13 9350", 
ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE),
+   SND_PCI_QUIRK(0x1028, 0x0704, "Dell XPS 13 9350", 
ALC256_FIXUP_DELL_XPS_13_HEADSET_NOISE),
SND_PCI_QUIRK(0x1028, 0x0706, "Dell Inspiron 7559", 
ALC256_FIXUP_DELL_INSPIRON_7559_SUBWOOFER),
SND_PCI_QUIRK(0x1028, 0x0725, "Dell Inspiron 3162", 
ALC255_FIXUP_DELL_SPK_NOISE),
-   SND_PCI_QUIRK(0x1028, 0x075b, "Dell XPS 13 9360", 
ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE),
+   SND_PCI_QUIRK(0x1028, 0x075b, "Dell XPS 13 9360", 
ALC256_FIXUP_DELL_XPS_13_HEADSET_NOISE),
SND_PCI_QUIRK(0x1028, 0x075d, "Dell AIO", ALC298_FIXUP_SPK_VOLUME),
SND_PCI_QUIRK(0x1028, 0x0798, "Dell Inspiron 17 7000 Gaming", 
ALC256_FIXUP_DELL_INSPIRON_7559_SUBWOOFER),
SND_PCI_QUIRK(0x1028, 0x164a, "Dell", 
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),

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

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1702000] [NEW] Remove hard dependency on Mir

2017-07-02 Thread Nazar Mokrynskyi
Public bug reported:

Mir is not used in most setups, however, libgtk-3-0 depends on libmirclient9 
and forces Mir libraries to be present.
Make this dependency optional, please.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Remove hard dependency on Mir

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Mir is not used in most setups, however, libgtk-3-0 depends on libmirclient9 
and forces Mir libraries to be present.
  Make this dependency optional, please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1702000/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1702001] [NEW] Remove hard dependency on Mir

2017-07-02 Thread Nazar Mokrynskyi
Public bug reported:

Mir is not used in most setups, however, libegl1-mesa depends on libmirclient9 
and forces Mir libraries to be present.
Make this dependency optional, please.

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

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

Title:
  Remove hard dependency on Mir

Status in mesa package in Ubuntu:
  New

Bug description:
  Mir is not used in most setups, however, libegl1-mesa depends on 
libmirclient9 and forces Mir libraries to be present.
  Make this dependency optional, please.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1102700] Re: bluetoothd crash when parsing invalid HIDP SDP record

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetoothd crash when parsing invalid HIDP SDP record

Status in bluez package in Ubuntu:
  Expired

Bug description:
  If a remote Bluetooth device contains HIDP SDP records in a specific
  invalid format, it is possible to crash BlueZ with SIGSEGV due to
  invalid memory reads, either by buffer overflow due to improper
  strncpy() usage or usage of arbitrary input as pointer.

  The several patches that address this problem are already upstream and
  are present on the 5.1 release. These are the commits (some are
  cosmetic but required to avoid conflicts of next patches):

  
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=21acf2283cacf0c029f2cea82380f4744a1dbcb5
  
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=df29632772171d5fd0e71c518fc3753adb11d0c0
  
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=fce691bd0bd08710ffd379025e894bcffaa5acb6
  
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=90228fc151bac5f19b2d21c18d51ef90f3b0d1b5
  
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=0f8aca093099d4fc693adc6270b9b0bd02287017
  
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=ce376961fb3a667ef35360c222bc3928d4657f4b
  
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=b41a46ef4c2bd9dc30998c6726ab6232a299c8e8
  
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=0305cfa11a06dea356f699a46da96f7146210466
  
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=5ba183dc82b4e8a1b3caa58648d6ac02b9325cb6
  
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=a35f83e113c1c58dd1c6cf8bda2b1bf99d07a695

  A patch backported from the above commits to the current BlueZ version
  on 12.04.1 LTS is attached. It was tested only on precise, but should
  apply just fine on more recent releases. Let me know you need specific
  versions of this patch.

  I will also attach a script that reproduces the crash using an
  emulated BT dongle. Usage instructions are at
  https://github.com/lizardo/bluez-tests/blob/master/README.rst

  NOTE: I tried to send a report which includes the crash information
  using apport-bug, but it did not seem to create a bug report here
  after 2 days.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 941130] Re: package bluez 4.98-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package bluez 4.98-2ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  bluez:
Installed: 4.98-2ubuntu1
Candidate: 4.98-2ubuntu1
Version table:
   *** 4.98-2ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  I issued "apt-get update && apt-get dist-upgrade -y" and during the
  upgrading I got the errormessage.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-17.26-virtual 3.2.6
  Uname: Linux 3.2.0-17-virtual i686
  NonfreeKernelModules: vboxsf vboxguest
  ApportVersion: 1.93-0ubuntu2
  Architecture: i386
  Date: Sat Feb 25 22:53:49 2012
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 
(2029.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: root=UUID=c7306e62-454a-4b0a-923f-b2db60518aee ro quiet 
splash
  SourcePackage: bluez
  Title: package bluez 4.98-2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig: Error: command hciconfig failed with exit code 1: Can't open HCI 
socket.: Address family not supported by protocol
  rfkill:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1072234] Re: 050d:0017 Bluetooth mouse randomly disconnects

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  050d:0017 Bluetooth mouse randomly disconnects

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Since upgrading to Quantal, my Belkin bluetooth mouse disconnects
  sporadically from my computer. Sometimes this will happen several
  times a day, at other times it will stay connected for almost the
  entire day without a problem.

  After the connection is dropped, Bluetooth seems to become
  unresponsive. Generally unplugging and replugging the USB adapter is
  necessary to return it to a usable state.

  It was extremely reliable under Precise.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: bluetooth 4.101-0ubuntu6
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sat Oct 27 23:58:59 2012
  InstallationDate: Installed on 2012-03-08 (233 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=62a1305b-ef07-4168-8292-c82e0718a496 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (7 days ago)
  dmi.bios.date: 07/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785TD-V EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd07/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:19:0E:0A:2A:A1  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:458652 acl:26915 sco:0 events:74 errors:0
TX bytes:1125 acl:19 sco:0 commands:29 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1458228] Re: improve error "Device is not available: No such device" of hcitool scan

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  improve error "Device is not available: No such device" of hcitool
  scan

Status in bluez package in Ubuntu:
  Expired

Bug description:
  The feedback `Device is not available: No such device` of `hcitool
  scan` is unhelpful and should be replaced with a feedback explaining
  the state (at least which device isn't there) and instructions how fix
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bluez 4.101-0ubuntu25
  Uname: Linux 4.0.1-040001-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May 23 21:31:08 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-02 (50 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20221
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.0.1-040001-generic 
root=UUID=0d646fdd-bb34-4e1c-9271-86a59deb3bf9 ro rootflags=subvol=@
  SourcePackage: bluez
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 68:17:29:77:05:46  ACL MTU: 310:10  SCO MTU: 64:8
DOWN 
RX bytes:34853 acl:308 sco:0 events:1087 errors:0
TX bytes:10432 acl:322 sco:0 commands:265 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1474324] Re: Sound indicator disappeared after headset connection issue

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Sound indicator disappeared after headset connection issue

Status in bluez package in Ubuntu:
  Expired
Status in indicator-sound package in Ubuntu:
  Invalid

Bug description:
  I switched my bluetooth headset on, it says it's connected.
  Selecting it in the audio settings doesn't enable it, sound still comes from 
the internal speakers.
  Switched my headset off and on again, no effect - usually this would have 
made it work. The headset doesn't indicate it's connected this time.
  Headset is still visible as a non-functional device in the audio settings.
  Meanwhile the sound indicator has disappeared.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150413-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 14 07:38:07 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-13 (62 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: indicator-sound
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1074792] Re: Bluetooth Mouse is laggy/sluggish/erratic behaviour in Linux but not Windows

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth Mouse is laggy/sluggish/erratic behaviour in Linux but not
  Windows

Status in bluez package in Ubuntu:
  Expired

Bug description:
  My Prolink PMO624B Bluetooth Mouse movement is laggy/sluggish/erratic
  in Ubuntu 12.04 and 12.10 on a Asus EeePC 1215B. However, it works
  completely normal in Windows 7 on the same machine, so I believe that
  the issue is with Linux/BlueZ. Please advise?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1193072] Re: bluetooth dialup network disconnection problem

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetooth dialup network disconnection problem

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Scenario- added my phone via Bluetooth> Dialup Network connection setup 
successful> and browsing ok
  Bug - at the unity bar there some icon like 0004 and below 'disconnect'
  when i try to disconnect the connection or shut down the pc then a huge 
errors on black screen and says "bug a c1063f99" and other ppp- somethings 
  Legacy - i can't share the screen shot and bug text because of black console 
screen

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 778236] Re: bluetooth adapter not found after wakeup

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetooth adapter not found after wakeup

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Kubuntu 11.04 amd64
  Microstar GX623
  When laptop wakes up from sleep mode it cannot see the bluetooth adapter 
anymore and bluetooth mouse does not work.
  This worked with Kubuntu 9.04, 9.10, 10.10 and does not work after upgrade to 
11.04.
  After wake up the bluetooth adapter is on, when I do 'lsusb' I can see:
  ...
  Bus 007 Device 002: ID 0db0:a97a Micro Star International Bluetooth EDR Device
  ...
  but the graphic configurator tells "No bluetooth adapter found".
  Bluetooth works well after normal boot.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1001825] Re: apple bluetooth keyboard and mouse: conflict between ubuntu and OS X

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  apple bluetooth keyboard and mouse: conflict between ubuntu and OS X

Status in bluez package in Ubuntu:
  Expired

Bug description:
  First of all, ubuntu 12.04(tested with mac specific iso and 64 bits)
  and grub 2(tested grub efi amd64 of course) do not acknowledge apple
  bluetooth keyboard(and mouse for ubuntu); installing blueman at ubuntu
  seems to be the only way to get both working on ubuntu, a very
  difficult process, which required an usb mouse because there are no
  working bluetooth apple devices; the issue is never fixed, only made
  less worse as shown below, please check these four threads for more
  information(the issue affect plenty of users, and has not been
  adressed properly since 2011?!):

  http://ubuntuforums.org/showthread.php?t=1980171

  http://ubuntuforums.org/showthread.php?t=1874245

  http://ubuntuforums.org/showthread.php?p=11949032#post11949032

  http://ubuntuforums.org/showthread.php?t=1980593

  If ubuntu gets control of mac keyboard and mouse, Os X lose it(and pre
  boot keyboard pairing cease to exist, no more pre boot hotkeys
  possible); if OS X have control of keyboard and mouse, ubuntu lose it;
  switching from one to another requires quite painfull keyboard and
  mouse redetection with blueman from ubuntu, or, at osx side, osx take
  quite some time to detect them again after an ubuntu login.

  The mac ubuntu community is quite insatisfied with this issue, and
  demands a fix; if any additional information is needed to help in this
  task, let us know.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1445408] Re: USB-bluetooth-mouse not detected

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  USB-bluetooth-mouse not detected

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Upgraded from Kubuntu 14.04 to 14.10 to 15.04 beta2 yesterday

  After finishing the final upgrade and rebooting my USB mouse is no longer 
working.
  Plugging in the USB dongle (it's a Logitech mouse with bluetooth connection, 
worked fine so far) I get the following in syslog:

  Apr 17 11:22:33 tp220 kernel: [13867.118079] usb 4-1.1: new full-speed USB 
device number 8 using ehci-pci
  Apr 17 11:22:34 tp220 kernel: [13867.213829] usb 4-1.1: New USB device found, 
idVendor=046d, idProduct=c52e
  Apr 17 11:22:34 tp220 kernel: [13867.213840] usb 4-1.1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
  Apr 17 11:22:34 tp220 kernel: [13867.213845] usb 4-1.1: Product: USB Receiver
  Apr 17 11:22:34 tp220 kernel: [13867.213850] usb 4-1.1: Manufacturer: Logitech
  Apr 17 11:22:34 tp220 mtp-probe: checking bus 4, device 8: 
"/sys/devices/pci:00/:00:1d.0/usb4/4-1/4-1.1"
  Apr 17 11:22:34 tp220 mtp-probe: bus: 4, device: 8 was not an MTP device

  I remember having seen messages that the USB device list could not be
  accessed, but these are gone now.

  Please let me know if I can be of further help to track this down.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr 17 11:18:08 2015
  InstallationDate: Installed on 2014-09-09 (219 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 4291S7Z
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-14-generic 
root=UUID=8c3ff90d-58e2-4696-9e3a-eddf92c84a41 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-04-17 (0 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291S7Z
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 4291S7ZR9M0ZD3
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4291S7Z:pvrThinkPadX220:rvnLENOVO:rn4291S7Z:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291S7Z
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1221524] Re: bluetoothd crashed with SIGSEGV in g_main_context_dispatch

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetoothd crashed with SIGSEGV in g_main_context_dispatch

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Using ubuntu 12.04 LTS, the bluetoothd just crash whenever my thinkpad t420 
starts. This happens each time & very much reproducible. None of the exisiting 
bugs were filed for 12.04 LTS, hence i'm filing this one.
  The crash report is attached below.

  1) $ lsb_release -rd
  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04

  2) $ apt-cache policy bluez
  bluez:
Installed: 4.98-2ubuntu7
Candidate: 4.98-2ubuntu7
Version table:
   *** 4.98-2ubuntu7 0
  500 http://in.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  3) bluetoothd should start working normally after boot.

  4) bluetoothd crashing during each boot.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1112554] Re: Bluetooth mouse 3.0 reconnection fail

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth mouse 3.0 reconnection fail

Status in bluez package in Ubuntu:
  Expired

Bug description:
  I use Ubuntu 12.04 (updated 2013.02.01)

  The bluetooth chipset used is a broadcom 2070

  I use the Bluetooth setting UI to connect a Mouse Bluetooth 3.0 
(Broadcom20730 chip) 
  Bluetooth HID 2.0-> encryption is mandatory

  After the pairing, the mouse is working, but when I try to reconnect
  the mouse (power Off power ON the Bluez stack) the mouse don't
  reconnect.

  I try the same but I use the cmd line (not the bluetooth wizard) to pair the 
mouse
  bluez-simple-agent hci0 xx:xx:xx:xx:xx:xx

  and this time all work correctly, the mouse is encrypted with the pin
  code  and the reconnection work.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1258753] Re: package bluez 4.101-0ubuntu8b1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package bluez 4.101-0ubuntu8b1 failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Can't manage a2dp profile to work. Using xubuntu 13.10 connected to an
  external bluetooth speaker. I can add it with blueman but can't send
  audio stream. It worked with xubutu 12.04.3 .

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sat Dec  7 11:58:56 2013
  DuplicateSignature: package:bluez:4.101-0ubuntu8b1:il sottoprocesso 
installato script di post-installation ha restituito lo stato di errore 1
  ErrorMessage: il sottoprocesso installato script di post-installation ha 
restituito lo stato di errore 1
  InstallationDate: Installed on 2013-12-06 (0 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  InterestingModules: rfcomm btusb bluetooth
  MachineType: ASUSTeK Computer Inc. U36SG
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic 
root=UUID=1728c978-09d7-49eb-835d-8030ded608e5 ro quiet splash 
i915.i915_enable_rc6=1
  SourcePackage: bluez
  Title: package bluez 4.101-0ubuntu8b1 failed to install/upgrade: il 
sottoprocesso installato script di post-installation ha restituito lo stato di 
errore 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U36SG.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U36SG
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU36SG.202:bd10/19/2011:svnASUSTeKComputerInc.:pnU36SG:pvr1.0:rvnASUSTeKComputerInc.:rnU36SG:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U36SG
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 4C:80:93:75:41:4D  ACL MTU: 310:10  SCO MTU: 64:8
    DOWN
    RX bytes:484 acl:0 sco:0 events:20 errors:0
    TX bytes:323 acl:0 sco:0 commands:20 errors:0
  modified.conffile..etc.dbus.1.system.d.bluetooth.conf: [deleted]
  mtime.conffile..etc.bluetooth.audio.conf: 2013-12-07T11:53:30.463114

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1272622] Re: bluetooth manager is crashing. I cant browse files from my bluetooth device when its connected via FTp

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetooth manager is crashing. I cant browse files from my bluetooth
  device when its connected via FTp

Status in bluez package in Ubuntu:
  Expired

Bug description:
  I am using dell inspiron-3521 and i am using ubuntu 12.04. Bluetooth
  was working without any bugs but today when i tried to access it, it
  want even turn on. I have download bluetooth manager from ubuntu
  store. After it i am able to turn on bluetooth. But i cant browse any
  files from my bluetooth connected mobile. Its hanging and suddenly
  crashed...

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1169776] Re: Bluetooth audio fails on 64-bit architecture

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth audio fails on 64-bit architecture

Status in bluez package in Ubuntu:
  Expired

Bug description:
  * Headset works fine on 32-bit machines under Ubuntu 12.04, 12.10
   (Samsung NC-20, Dell D420)

  * Same headset pairs, but fails to do audio on a 64-bit machine, Ubuntu 
32-bit or 64-bit 12.10 or 64-bit 13.04
  (Lenovo S206 with AMD E1-1200)

  AGAIN: it fails on 64-bit *machines* regardless of the Ubuntu version,
  and works on 32-bit machines.

  * At first sometimes I see the hardware in the Sound Settings.
but only hear some tinny, scratchy sounds briefly.
Then the device disappears from the Sound Settings.  Re-starting bluetooth 
has no effect.

  On a working system, see syslog lines like
  bluetoothd[825]: /org/bluez/825/hci0/dev_: fd(32) ready
  ...
  bluetoothd[825]: Audio connection got disconnected

  But on the non-working systems, I don't see such bluetooth lines at all (I 
presume due to the logging level)
  Anyway, no *errors* are showing, after pairing with the headset.  The audio 
just doesn't work.

  Please advise how to debug.

  (Of course I don't know if the blame lies with the Bluetooth software
  or with PulseAudio, and of course I don't care.)

  Please fix this soon!  I have been using this on a daily basis, and
  need to move to a newer machine.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1048944] Re: Bluetooth keyboard and mouse connects, but is not functional - Motorola KZ500

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth keyboard and mouse connects, but is not functional -
  Motorola KZ500

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Followed the steps on this thread to get the keyboard to pair, but
  even though hci-dump shows keypresses, no keypresses or mouse movement
  get passed to any shell (graphical or terminals).

  http://ubuntuforums.org/showthread.php?t=2054148

  If any dev in Austin wants to borrow my keyboard, or wants to meet up
  to help sort this out let me know.  Otherwise I'll be taking a stab at
  fixing it once I find some time.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Tue Sep 11 01:09:24 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: BIOSTAR Group TP55
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=UUID=fd58abb9-56f2-4094-8191-d931dea02669 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: None
  dmi.board.name: TP55
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/02/2010:svnBIOSTARGroup:pnTP55:pvr6.0:rvnBIOSTARGroup:rnTP55:rvr:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: TP55
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:BF:3A:3A  ACL MTU: 1022:8  SCO MTU: 121:3
UP RUNNING PSCAN 
RX bytes:12598 acl:617 sco:0 events:113 errors:0
TX bytes:967 acl:10 sco:0 commands:61 errors:0
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1196788] Re: Bluetooth does not work in Ubuntu 12.04.2, AMD AMD® Trinity APU A10-4655M 2.0 GHz

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth does not work in Ubuntu 12.04.2, AMD AMD® Trinity APU
  A10-4655M 2.0 GHz

Status in bluez package in Ubuntu:
  Expired

Bug description:
  In the bluetooth indicator/global menu, options are available to turn 
  it on/off. However, in the bluetooth settings window, it is indicated 
  that bluetooth is disabled and it cannot be turned on.  Furthermore,
  trying to setup a new device returns "No Adapters Found".

  Here is the output of lsusb : 
  Bus 001 Device 002: ID 0bda:0139 Realtek Semiconductor Corp.  
  Bus 001 Device 003: ID 04f2:b364 Chicony Electronics Co., Ltd  
  Bus 004 Device 010: ID 13d3:3392 IMC Networks  
  Bus 004 Device 003: ID 0eef:7907 D-WAV Scientific Co., Ltd  
  Bus 005 Device 002: ID 046d:c052 Logitech, Inc.  
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 
  Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
  Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 
  Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
  Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub. 

  Here is the output of rfkill list :  
  0: phy0: Wireless LAN 
  Soft blocked: no  
  Hard blocked: no 

  1: brcmwl-0: Wireless LAN 
  Soft blocked: no  Hard blocked: no 
  2: asus-wlan: Wireless LAN
  Soft blocked: no  Hard blocked: no 
  3: asus-bluetooth: Bluetooth 
  Soft blocked: no  
  Hard blocked: no. 

  Here is the output of sudo hcitool dev : 
  Devices : . 

  In windows 8, the bluetooth works flowlessly. If I login Windows 8, 
  keep the bluetooth on before restarting to Ubuntu, the bluetooth 
  is still disabled. 

  In the BIOS/UEFI settings, the bluetooth is enabled.

  Furthermore, the wifi and bluetooth share the same set of keys : 
  Fn + F2. In Windows 8, If i turn on the bluetooth a small dot in the 
  F2 key is lit. In ubuntu pressing, Fn + F2 enables/disables wifi and
  the bluetooth indicator menu swaps between on/off but the bluetooth
  is still really off.

  Side Note : This is a new machine (2013) and I couldn't try the settings
  for Ubuntu 13.04 and 13.10. Installation of Ubuntu 13.04 and 13.10
  resulted to corrupted display. [This will be a different bug.]

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-34.55~precise1-generic 3.5.7.13
  Uname: Linux 3.5.0-34-generic x86_64
  NonfreeKernelModules: wl fglrx
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Tue Jul  2 12:37:36 2013
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  InterestingModules: rfcomm bnep bluetooth
  MachineType: ASUSTeK COMPUTER INC. U38N
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-34-generic 
root=UUID=d3189321-36df-497c-a331-8e942669bf3e ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U38N.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U38N
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU38N.204:bd11/22/2012:svnASUSTeKCOMPUTERINC.:pnU38N:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnU38N:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: U38N
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   
  syslog:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 758804] Re: Add support for ST-Ericsson CG2900 Bluetooth chip

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Add support for ST-Ericsson CG2900 Bluetooth chip

Status in bluez package in Ubuntu:
  Expired
Status in bluez source package in Oneiric:
  Won't Fix

Bug description:
  Binary package hint: bluez

  Add support for ST-Ericsson CG2900 Bluetooth chip found on Snowball.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1277871] Re: bluetooth mouse ceases to work

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetooth mouse ceases to work

Status in bluez package in Ubuntu:
  Expired

Bug description:
  After the initial boot, the bluetooth connected mouse is working ok.
  Up to a point where all over a sudden, it stops. The only thing being logged 
is:

  [ 6089.525351] Bluetooth: hci0 command 0x0c03 tx timeout
  [ 6097.530209] Bluetooth: hci0 sending initial HCI reset command failed (-110)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Feb  8 14:48:03 2014
  InstallationDate: Installed on 2014-02-07 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E7240
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed 
root=UUID=052bd6e1-db02-4bca-9f9c-d5600c0237e1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0531FD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/05/2013:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0531FD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: FC:F8:AE:45:3C:05  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:148805 acl:9777 sco:0 events:244 errors:0
TX bytes:17582 acl:12 sco:0 commands:115 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 921115] Re: package bluez (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package bluez (not installed) failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Upon upgrade to Ubuntu 12.04, I made modifications to
  /etc/default/bluetooh to stop the module, because my laptop do not
  have bluetooth so I disabled it, nonetheless bluez, gnome-shell,
  gnome-user-share and gnome-bluetooth do not install either.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: bluez (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
  Uname: Linux 3.2.0-10-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Tue Jan 24 10:28:09 2012
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: bluez
  Title: package bluez (not installed) failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.bluetooth: 2012-01-22T16:10:53.936238

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1036704] Re: Unable to configure device with bluez-simple-agent

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Unable to configure device with bluez-simple-agent

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Unable to use bluez-simple-agent to set up connection in Xubuntu 12.04
  on Asus T91m laptop with internal or USB Bluetooth hardware.

  onebir@T91:~$ lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04
  onebir@T91:~$ apt-cache show bluez python-gobject python-dbus | egrep 
"Package|Version"
  Package: bluez
  Version: 4.98-2ubuntu7
  Package: python-gobject
  Version: 3.2.2-1~precise
  Package: python-gobject
  Version: 3.2.0-3
  Package: python-dbus
  Version: 1.0.0-1ubuntu1

  #Trying inbulit card - not sure of hardware
  onebir@T91:~$ hcitool dev
  Devices:
  hci000:25:D3:A4:4A:A7
  onebir@T91:~$ hcitool scan
  Scanning ...
  onebir@T91:~$ sudo bluez-simple-agent hci 00:25:D3:A4:4A:A7
  [sudo] password for bir:
  Traceback (most recent call last):
File "/usr/bin/bluez-simple-agent", line 102, in 
  path = manager.FindAdapter(args[0])
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
  **keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter

  # Plug in USB Bluetooth dongle  as used in *
  onebir@T91:~$ hcitool dev
  Devices:
  hci000:25:D3:A4:4A:A7
  hci100:1F:81:00:08:30
  onebir@T91:~$ sudo bluez-simple-agent hci 00:1F:81:00:08:30
  Traceback (most recent call last):
File "/usr/bin/bluez-simple-agent", line 102, in 
  path = manager.FindAdapter(args[0])
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
  **keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter

  *https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1036106

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

2017-07-02 Thread Ubuntu Foundations Team Bug Bot
The attachment "unattended-upgrades_0.90ubuntu0.7.patch" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1473043] Re: bluetoothd -n consuming 100% after device disconnects

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetoothd -n consuming 100% after device disconnects

Status in bluez package in Ubuntu:
  Expired

Bug description:
  On a regular basis after disconnecting a bluetooth device, usually my
  headset, the laptop starts to heat up and "/usr/sbin/bluetoothd -n"
  consumes 100% CPU. A temporary solution is to run "sudo service
  bluetooth restart".

  This is bluez 4.101-0ubuntu25 on 15.04 with all updates.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 434007] Re: Apple bluetooth keyboard non-responsive after reboot

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Apple bluetooth keyboard non-responsive after reboot

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Binary package hint: bluez

  (Originally posed this as a question, and was encouraged to report it
  as a bug here. Despite the numerous similar problems reported over the
  last several years, I believe this one to be distinct, mainly because
  of the recently disappeared /etc/default/bluetooth file, as per my
  description below.) bluez version is 4.51-0ubuntu1, according to
  synaptic.

  After much hanky-panky, I had eventually gotten the keyboard to
  persistently work in 9.04, but unfortunately needed to update to 9.10
  because of the catastrophically broken intel video drivers in 9.04.

  The keyboard still works, but after reboot it is in an odd state where
  the "bluetooth preferences" show it as connected even though it is
  completely non-responsive. Cycling the connection (disconnect, then
  reconnect) will bring it right back up, but this requires (at minimum)
  another wired keyboard present to log in with. (Had to borrow a wired
  keyboard from work to accomplish this.)

  From what I was able to understand during the setup process in 9.04,
  one of the key steps was modifying /etc/default/bluetooth, which
  apparently no longer exists in the version of bluez shipping with
  9.10. Can anyone enlighten me as to where the settings which were once
  contained therein have relocated to?

  Some details about the system, which is a mac mini purchased in
  December 2008 (probably missing all the important stuff, but give me a
  little slack; it's my first attempt at asking a question) ---

  $ uname -a
  Linux elliot 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009 
x86_64 GNU/Linux
  $ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=9.10
  DISTRIB_CODENAME=karmic
  DISTRIB_DESCRIPTION="Ubuntu karmic (development branch)"
  $ lsusb
  Bus 001 Device 004: ID 1058:1003 Western Digital Technologies, Inc.
  Bus 001 Device 003: ID 1058:1001 Western Digital Technologies, Inc. External 
Hard Disk
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 004: ID 05ac:8205 Apple, Inc. Bluetooth HCI
  Bus 005 Device 003: ID 05ac:8240 Apple, Inc. IR Receiver [build-in]
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 002: ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96 Optical 
Wheel Mouse
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  $ hciconfig
  hci0: Type: USB
   BD Address: 00:22:41:D8:06:AD ACL MTU: 384:8 SCO MTU: 64:8
   UP RUNNING PSCAN
   RX bytes:62256 acl:3366 sco:0 events:76 errors:0
   TX bytes:813 acl:22 sco:0 commands:40 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 224389] Re: bluetoothd-service-network fails to bring up the server side bnep interface after reconnection

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetoothd-service-network fails to bring up the server side bnep
  interface after reconnection

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Binary package hint: bluez-utils

  After connecting to a server once, bnep0 is created and brought up,
  however after disconnecting, bnep0 disappears and after reconnecting
  is not brought back up, which makes the connection unusable

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 548720] Re: BCM2046 Bluetooth not working

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  BCM2046 Bluetooth not working

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Binary package hint: bluez

  Bluetooth BCM2046 no longer works on Macbook Pro 5.5 since today's updates 
(2010-03-26)
  It use to work perfecly yesterday and earlier.

  (Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth))
  --
  mart@mart-laptop:~$ hcitool scan
  Device is not available: No such device
  mart@mart-laptop:~$ hcitool dev
  Devices:
  mart@mart-laptop:~$
  --
  The gnome bluetooth applet says that bluetooth is on, but preferences show 
only the large "bluetooth is forbidden", "turn on bluetooth" button. Clicking 
this button makes it gray but nothing happens - bluetooth is till no working.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Mar 26 13:04:29 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
  InterestingModules: sco bnep l2cap btusb bluetooth
  MachineType: Apple Inc. MacBookPro5,5
  NonfreeKernelModules: wl nvidia
  Package: bluez 4.60-0ubuntu6
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-17-generic 
root=UUID=8e2051c9-574d-46e5-9d84-06a3919bd614 ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=et_EE.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  SourcePackage: bluez
  Uname: Linux 2.6.32-17-generic i686
  dmi.bios.date: 06/15/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP55.88Z.00AC.B03.0906151708
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F2268AC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268AC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8:
  dmi.product.name: MacBookPro5,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 585592] Re: Bluetooth PIN always random

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth PIN always random

Status in bluez package in Ubuntu:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Expired

Bug description:
  Binary package hint: bluez

  Hello,

  when I want to connect my SE W800i mobile phone to my Asus Eee PC 1005
  HA netbook i go to the bluetooth-manager gui and add it. Selecting a
  different than "Automatic PIN" (e.g. ) has no effect however.
  There is always a random PIN generated.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: bluetooth 4.60-0ubuntu8
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  Architecture: i386
  Date: Tue May 25 21:20:54 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
  MachineType: ASUSTeK Computer INC. 1005HA
  PackageArchitecture: all
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic 
root=UUID=7ab1ecbd-0b96-4920-99b1-8426f94a20df ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: bluez
  dmi.bios.date: 02/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1005HA
  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.:bvr1401:bd02/26/2010:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1005HA
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.
  hciconfig:
   hci0:Type: USB
BD Address: 00:22:43:FD:5C:E3 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1007 acl:0 sco:0 events:33 errors:0
TX bytes:1103 acl:0 sco:0 commands:33 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 554431] Re: Bluetooth is disabled. Pressing "Turn on bluetooth" not working

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth is disabled. Pressing "Turn on bluetooth" not working

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Binary package hint: bluez

  Lucid on Dell xps studio 1340.
  After the updates of April 1-3, bluetooth icon appears grayed out. Clicking 
it states that bluetooth is on. Using preferences and pressing the button "Turn 
on Bluetooth" makes the button go gray, but nothing more. Basically this is 
identical behavior to bug #441800, which is supposedly fixed.
  I will be happy to supply further details if necessary.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: bluez 4.60-0ubuntu7
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic x86_64
  NonfreeKernelModules: nvidia wl
  Architecture: amd64
  Date: Sat Apr  3 07:15:29 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  InterestingModules: sco bnep l2cap btusb bluetooth
  MachineType: Dell Inc. Studio XPS 1340
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic 
root=UUID=c3257748-07cc-46a6-baa4-f0f5d8b79d53 ro quiet splash
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: bluez
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0K183D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.asset.tag: 1234567890
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0K183D:rvrA11:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Studio XPS 1340
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN 
RX bytes:6 acl:0 sco:0 events:1 errors:0
TX bytes:24 acl:0 sco:0 commands:8 errors:0
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 592790] Re: Microsoft Bluetooth Keyboard freaks after sleep

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Microsoft Bluetooth Keyboard freaks after sleep

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Have a Microsoft Mobile Keyboard 6000 (new, slim one with separate
  number pad). Works perfectly with Windows (tried it out at work), but
  have a major issue with Ubuntu (both 9.10 and 10.04, latter running
  bluez 4.60-0ubuntu8):

  If the keyboard enters sleep mode, when re-awakened, it has a tendency
  to kind of get stuck: it starts repeating the latest key pressed and
  won't respond to new keypresses. To stop the repetition requires
  pressing something on a USB keyboard or some other intervention (via a
  mouse, for example). After this "stuck key" the keyboard usually
  becomes unresponsive except for periodically repeating the behaviour.

  To get the keyboard working again, requires deleting the old
  connection in Bluetooth manager and setting up a new connection. This
  new connection will work until the keyboard goes to sleep again and
  wakes up, after which we're back in square one.

  I don't really know anything about tracking down the problem. Will
  offer more information if you'll point me at the right direction.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 585592] Re: Bluetooth PIN always random

2017-07-02 Thread Launchpad Bug Tracker
[Expired for gnome-bluetooth (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-bluetooth (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth PIN always random

Status in bluez package in Ubuntu:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Expired

Bug description:
  Binary package hint: bluez

  Hello,

  when I want to connect my SE W800i mobile phone to my Asus Eee PC 1005
  HA netbook i go to the bluetooth-manager gui and add it. Selecting a
  different than "Automatic PIN" (e.g. ) has no effect however.
  There is always a random PIN generated.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: bluetooth 4.60-0ubuntu8
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  Architecture: i386
  Date: Tue May 25 21:20:54 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
  MachineType: ASUSTeK Computer INC. 1005HA
  PackageArchitecture: all
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic 
root=UUID=7ab1ecbd-0b96-4920-99b1-8426f94a20df ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: bluez
  dmi.bios.date: 02/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1005HA
  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.:bvr1401:bd02/26/2010:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1005HA
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.
  hciconfig:
   hci0:Type: USB
BD Address: 00:22:43:FD:5C:E3 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1007 acl:0 sco:0 events:33 errors:0
TX bytes:1103 acl:0 sco:0 commands:33 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 677959] Re: Internal bluetooth adapter is not detected only additional external ones are

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Internal bluetooth adapter is not detected only additional external
  ones are

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Binary package hint: bluez

  Dell inspiron 1545 internal bluetooth device is not detected or
  installed by ubuntu (worked when I had windows but does not work now
  and ubuntu is the only OS).

  Tried installing KDE software because some bug reports suggested that
  it may work but had could not register OBEX service error.

  No idea what any of this means but hope it helps.

  Am using Lucid Lynix and have kept it updated.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: bluez 4.60-0ubuntu8
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  CheckboxSubmission: d743a8dfddebc6560384cd2159c9d1dd
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Sat Nov 20 21:24:30 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  InterestingModules: rfcomm l2cap bluetooth
  MachineType: Dell Inc. Inspiron 1545
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-generic 
root=UUID=7167e221-41d3-4ef1-9226-8d4b33e9e1bd ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: bluez
  dmi.bios.date: 06/03/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd06/03/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   
  rfkill:
   0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 660347] Re: Bluetooth daemon writes something to disk without any reason

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth daemon writes something to disk without any reason

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Binary package hint: bluez

  Sometimes bluetooth daemon starts writing something to disk for no reason 
what so ever. It does about 1486.46 K/s and never stop doing so, I've been 
watching it for few hours.
  It happened to me twice now. Restarting bluetooth helps in resolving the 
issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: bluez 4.69-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.35-22.33~phc0-generic-phc 2.6.35.4
  Uname: Linux 2.6.35-22-generic-phc i686
  Architecture: i386
  Date: Thu Oct 14 18:35:12 2010
  ExecutablePath: /usr/sbin/bluetoothd
  InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
  MachineType: IBM 2529FKG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-phc 
root=UUID=53a8389d-7f29-45bb-a5c7-7bfcd9631035 ro quiet splash
  ProcEnviron:
   
  SourcePackage: bluez
  dmi.bios.date: 02/27/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: 77ET64WW (1.24 )
  dmi.board.name: 2529FKG
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr77ET64WW(1.24):bd02/27/2007:svnIBM:pn2529FKG:pvrThinkPadZ60m:rvnIBM:rn2529FKG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2529FKG
  dmi.product.version: ThinkPad Z60m
  dmi.sys.vendor: IBM
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:14:A4:DC:A1:12  ACL MTU: 1017:8  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:327594 acl:0 sco:0 events:50157 errors:0
TX bytes:176080 acl:0 sco:0 commands:50158 errors:1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1278615] Re: bluetoothd crashed with SIGSEGV in __GI___libc_free()

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetoothd crashed with SIGSEGV in __GI___libc_free()

Status in bluez package in Ubuntu:
  Expired

Bug description:
  bluetoothd crashes at startup

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
  Uname: Linux 3.2.0-58-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Feb 10 21:46:15 2014
  ExecutablePath: /usr/sbin/bluetoothd
  InstallationMedia: Xubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 0769B2G
  MarkForUpload: True
  ProcCmdline: /usr/sbin/bluetoothd
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-58-generic 
root=UUID=4153a498-00f0-466e-a060-6af1785b63ec ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7fccf795154c :  mov-0x8(%rdi),%rsi
   PC (0x7fccf795154c) ok
   source "-0x8(%rdi)" (0xfffb) not located in a known VMA region 
(needed readable region)!
   destination "%rsi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   free () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
   ?? ()
   ?? ()
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: bluetoothd crashed with SIGSEGV in free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/11/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET37WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769B2G:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769B2G
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:19:7E:FF:48:39  ACL MTU: 1017:8  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:1282 acl:0 sco:0 events:51 errors:0
TX bytes:491 acl:0 sco:0 commands:51 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1286621] Re: bluetooth keeps turning off

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetooth keeps turning off

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Bluetooth turned off (without me turning it off), as it already
  happened a lot of times.

  Now i can't turn it on.
  I run Bluetooth from the Dash, I turn on Bluetooth with the On/Off button. 
Then it goes back to off.
  It will probably work after reboot.

  Just one more bluetooth bug making bluetooth completely unusable under
  Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Mar  1 22:21:46 2014
  InstallationDate: Installed on 2013-10-11 (141 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (6 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1301962] Re: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10
  (Trusty) fails

Status in bluez package in Ubuntu:
  Expired

Bug description:
  During an upgrade of a vanilla Precise install to Trusty I've
  encountered already twice this issue:

  $ sudo dpkg --configure bluez
  Setting up bluez (4.101-0ubuntu10) ...
  reload: Method "Reload" with signature "" on interface 
"com.ubuntu.Upstart0_6.Instance" doesn't exist

  invoke-rc.d: initscript dbus, action "force-reload" failed.
  start: Job failed to start
  invoke-rc.d: initscript bluetooth, action "start" failed.
  dpkg: error processing package bluez (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   bluez

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1306508] Re: package bluez 4.98-2ubuntu7 failed to install/upgrade: Pakiet jest w złym stanie - powinien zostać przeinstalowany przed usunięciem.

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package bluez 4.98-2ubuntu7 failed to install/upgrade: Pakiet jest w
  złym stanie - powinien zostać przeinstalowany  przed usunięciem.

Status in bluez package in Ubuntu:
  Expired

Bug description:
  trying just a regular upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
  Uname: Linux 3.2.0-60-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  AptOrdering:
   bluez-gstreamer: Remove
   bluez-alsa: Remove
   bluez: Remove
  Architecture: amd64
  Date: Fri Apr 11 09:56:22 2014
  DpkgTerminalLog:
   Usuwanie bluez-gstreamer ...
   Usuwanie bluez-alsa ...
   dpkg: błąd przetwarzania bluez (--remove):
Pakiet jest w złym stanie - powinien zostać przeinstalowany
przed usunięciem.
  DuplicateSignature: package:bluez:4.98-2ubuntu7:Pakiet jest w złym stanie - 
powinien zostać przeinstalowany  przed usunięciem.
  ErrorMessage: Pakiet jest w złym stanie - powinien zostać przeinstalowany  
przed usunięciem.
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  InterestingModules: bnep rfcomm bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 010: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 
LTE/UMTS/GSM Modem/Networkcard
  MachineType: innotek GmbH VirtualBox
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-60-generic 
root=UUID=fac924da-e1b1-45ee-b5b4-32f1f0f3237c ro quiet splash vt.handoff=7
  SourcePackage: bluez
  Title: package bluez 4.98-2ubuntu7 failed to install/upgrade: Pakiet jest w 
złym stanie - powinien zostać przeinstalowany  przed usunięciem.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   
  rfkill:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1295339] Re: USB bluetooth head set doesn't get reactivated

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  USB bluetooth head set doesn't get reactivated

Status in bluez package in Ubuntu:
  Expired

Bug description:
  I have a usb bt headset and a seperate mouse both attached to a KVM
  switch.

  Until a few weeks ago I could switch between the two machines easily.
  Now when I switch back to Kubuntu, I can't reactivate the headset
  somehow.

  The BT connection gets established, when I press volume buttons on the
  headset I see the onscreen display. However no sound is being played
  from apps and stuff. Also KDE multimedia settings has the headset
  greyed out.

  I tried to disconnect and reconnect the dongle but that didn't help
  either. ONly rebooting helps.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1342568] Re: bluetooth connect fails

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetooth connect fails

Status in bluez package in Ubuntu:
  Expired

Bug description:
  I want to connect to a BT-serial adapter. Always get the error
  "Unknown command complete for opcode 37".

  If I supply the correct pin, connection is reported successful, but
  the device immediately disappears.

  I tried three different host BT hardware and two different PCs. always
  the same.

  Kubuntu 14.04
  Bluez-4.101-ubuntu13

  syslog: First with correct pin, second using wrong pin:

  bluetoothd[1107]: Discovery session 0x7f66d5221040 with :1.117 activated
  bluetoothd[1107]: Unknown command complete for opcode 37
  bluetoothd[1107]: Stopping discovery

  bluetoothd[1107]: Discovery session 0x7f66d52209a0 with :1.118 activated
  bluetoothd[1107]: Unknown command complete for opcode 37
  bluetoothd[1107]: Stopping discovery
  bluetoothd[1107]: hci0: Cancel Pair Device (0x001a) failed: Invalid 
Parameters (0x0d) 

  How do I enable more detailed logging?

  I am quite sure this is no duplicate of those BT-suspend bugs. Because
  it always fails and the rfkill workaround doesn't help.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1319256] Re: package bluez 4.98-2ubuntu7.2 failed to install/upgrade: subproses skrip post-installation terpasang menghasilkan kesalahan status keluaran: 1

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package bluez 4.98-2ubuntu7.2 failed to install/upgrade: subproses
  skrip post-installation terpasang menghasilkan kesalahan status
  keluaran: 1

Status in bluez package in Ubuntu:
  Expired

Bug description:
  ive been getting this bug since i update my Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7.2
  ProcVersionSignature: Ubuntu 3.11.0-20.34~precise1-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  AptOrdering:
   bluez: Configure
   bluez-alsa: Configure
   bluez-gstreamer: Configure
   gnome-bluetooth: Configure
  Architecture: amd64
  Date: Thu May  8 04:32:34 2014
  DuplicateSignature: package:bluez:4.98-2ubuntu7.2:subproses skrip 
post-installation terpasang menghasilkan kesalahan status keluaran: 1
  ErrorMessage: subproses skrip post-installation terpasang menghasilkan 
kesalahan status keluaran: 1
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. K45VD
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-20-generic 
root=UUID=2E2A7F7B2A7F3EC1 loop=/hostname/disks/root.disk ro quiet splash 
vt.handoff=7
  SourcePackage: bluez
  Title: package bluez 4.98-2ubuntu7.2 failed to install/upgrade: subproses 
skrip post-installation terpasang menghasilkan kesalahan status keluaran: 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 221
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K45VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr221:bd08/31/2012:svnASUSTeKCOMPUTERINC.:pnK45VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK45VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K45VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: DC:85:DE:A5:58:B6  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:902 acl:0 sco:0 events:42 errors:0
TX bytes:944 acl:0 sco:0 commands:42 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1311368] Re: Won't install on precise (over ssh), blocking installation of ia32-libs

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Won't install on precise (over ssh), blocking installation of
  ia32-libs

Status in bluez package in Ubuntu:
  Expired

Bug description:
  bluez package fails to install via apt-get, which prevents me from
  installing ia32-libs, on precise.  Running over ssh, not sure if that
  could be relevant.  I'm not interested in using the bluez package at
  all, this is a server.

  # apt-get install bluez
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following NEW packages will be installed:
bluez
  0 upgraded, 1 newly installed, 0 to remove and 39 not upgraded.
  Need to get 0 B/969 kB of archives.
  After this operation, 2,525 kB of additional disk space will be used.
  Selecting previously unselected package bluez.
  (Reading database ... 89815 files and directories currently installed.)
  Unpacking bluez (from .../bluez_4.98-2ubuntu7.1_amd64.deb) ...
  Processing triggers for man-db ...
  Processing triggers for ureadahead ...
  Setting up bluez (4.98-2ubuntu7.1) ...
  reload: Unknown instance: 
  invoke-rc.d: initscript dbus, action "force-reload" failed.
  start: Job failed to start
  invoke-rc.d: initscript bluetooth, action "start" failed.
  dpkg: error processing bluez (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   bluez
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  # apt-get install ia32-libs
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
bluez bluez-alsa:i386 ia32-libs-multiarch:i386
  Suggested packages:
libpam-ldap:i386 libpam-winbind:i386 libnss-ldap:i386
  The following NEW packages will be installed:
bluez bluez-alsa:i386 ia32-libs ia32-libs-multiarch:i386
  0 upgraded, 4 newly installed, 0 to remove and 39 not upgraded.
  Need to get 0 B/1,111 kB of archives.
  After this operation, 2,987 kB of additional disk space will be used.
  Do you want to continue [Y/n]? 
  Selecting previously unselected package bluez.
  (Reading database ... 89815 files and directories currently installed.)
  Unpacking bluez (from .../bluez_4.98-2ubuntu7.1_amd64.deb) ...
  Selecting previously unselected package bluez-alsa:i386.
  Unpacking bluez-alsa:i386 (from .../bluez-alsa_4.98-2ubuntu7.1_i386.deb) ...
  Selecting previously unselected package ia32-libs-multiarch:i386.
  Unpacking ia32-libs-multiarch:i386 (from 
.../ia32-libs-multiarch_20090808ubuntu36_i386.deb) ...
  Selecting previously unselected package ia32-libs.
  Unpacking ia32-libs (from .../ia32-libs_20090808ubuntu36_amd64.deb) ...
  Processing triggers for man-db ...
  Processing triggers for ureadahead ...
  Setting up bluez (4.98-2ubuntu7.1) ...
  reload: Unknown instance: 
  invoke-rc.d: initscript dbus, action "force-reload" failed.
  start: Job failed to start
  invoke-rc.d: initscript bluetooth, action "start" failed.
  dpkg: error processing bluez (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of bluez-alsa:i386:
   bluez-alsa:i386 depends on bluez; however:
Package bluez is not configured yet.
  dpkg: error processing bluez-alsa:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of ia32-libs-multiarch:i386:
   ia32-libs-multiarch:i386 depends on bluez-alsa; however:
Package bluez-alsa:i386 is not configured yet.
  dpkg: error processing ia32-libs-multiarch:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of ia32-libs:
   ia32-libs depends on ia32-libs-multiarch; however:
Package ia32-libs-multiarch is not installed.
Package ia32-libs-multiarch:i386 is not configured yet.
  dpkg: error processing ia32-libs (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Errors were encountered while processing:
   bluez
   bluez-alsa:i386
   ia32-libs-multiarch:i386
   ia32-libs
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://la

[Touch-packages] [Bug 1362180] Re: can't connect my mouse

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  can't connect my mouse

Status in bluez package in Ubuntu:
  Expired

Bug description:
  the mouse is Navigator 905BT (Genius), the laptop is Acer Aspire
  E1-731. i'm using Kubuntu 14.04 (64-bit). the os just won't see the
  mouse. the mouse works fine though in windows. i tried the latest
  fedora, no luck.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1362538] Re: bluetoothd crashed with SIGSEGV in server_disconnect()

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetoothd crashed with SIGSEGV in server_disconnect()

Status in bluez package in Ubuntu:
  Expired

Bug description:
  at startup

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu19
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 21 02:15:28 2014
  ExecutablePath: /usr/sbin/bluetoothd
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V5-551
  ProcCmdline: /usr/sbin/bluetoothd
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic.efi.signed 
root=UUID=bdba8918-495e-47cf-bc7c-8dc076ec2212 ro text nomodeset noplymouth 
console=tty1 radeon.dpm=1 acpi_backlight=vendor nomdmonddf nomdmonisw
  SegvAnalysis:
   Segfault happened at: 0x7fbb97d33e1c <__GI___libc_free+28>:  mov
-0x8(%rdi),%rax
   PC (0x7fbb97d33e1c) ok
   source "-0x8(%rdi)" (0x0019) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   __GI___libc_free (mem=0x21) at malloc.c:2929
   ?? ()
   ?? ()
   ?? ()
   dbus_connection_try_register_fallback () from 
/lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: bluetoothd crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/19/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.16:bd04/19/2013:svnAcer:pnAspireV5-551:pvrV2.16:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551
  dmi.product.version: V2.16
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: F4:B7:E2:88:01:EE  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1224 acl:0 sco:0 events:74 errors:0
TX bytes:2300 acl:0 sco:0 commands:74 errors:0
  mtime.conffile..etc.bluetooth.audio.conf: 2014-06-10T23:38:40.331777

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1392829] Re: bluez-test-discovery ERROR:dbus.connection:Exception

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluez-test-discovery ERROR:dbus.connection:Exception

Status in bluez package in Ubuntu:
  Expired

Bug description:
  ~$ bluez-test-discovery 
  [ 50:85:69:EF:9B:23 ]
  Trusted = 0
  Class = 0x08043c
  ERROR:dbus.connection:Exception in handler for D-Bus signal:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  self._handler(*args, **kwargs)
File "/usr/bin/bluez-test-discovery", line 15, in device_found
  value = unicode(value).encode('ascii', 'replace')
  NameError: name 'unicode' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 19:24:49 2014
  InstallationDate: Installed on 2014-11-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
  rfkill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1416505] Re: When booting computer, I have no network before I shutdown bluetoothd

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  When booting computer, I have no network before I shutdown bluetoothd

Status in bluez package in Ubuntu:
  Expired

Bug description:
  It is repeating itself. On every start, I log into my user account on
  the computer and there is no network, neither on the ethernetcable nor
  on wlan0. When I click the top-right bluetooth-symbol with the little
  lock symbol on it and turn bluetooth off, wlan0 "awakens" and I get
  connected. (At work I have a docking station, same procedure there,
  only difference is I also have a cable connection. Both connections
  appear after I turn bluetooth off)

  hy@laptop:~/$ lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: bluez 4.101-0ubuntu22
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Jan 30 19:13:34 2015
  ExecutablePath: /usr/sbin/bluetoothd
  InstallationDate: Installed on 2014-08-19 (164 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. Precision M4700
  ProcCmdline: /usr/sbin/bluetoothd
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic 
root=UUID=5c35fbae-b2aa-441a-a0ff-4bfe1a8b6aa3 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f8ea506e25d:cmpq   $0x0,0x8(%rax)
   PC (0x7f8ea506e25d) ok
   source "$0x0" ok
   destination "0x8(%rax)" (0x746e693c090a3e6d) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: bluetoothd crashed with SIGSEGV in dbus_connection_dispatch()
  UpgradeStatus: Upgraded to vivid on 2014-10-23 (98 days ago)
  UserGroups:
   
  dmi.bios.date: 05/20/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0WWPJY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/20/2013:svnDellInc.:pnPrecisionM4700:pvr01:rvnDellInc.:rn0WWPJY:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4700
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1411075] Re: bluez-simple-agent crashes

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluez-simple-agent crashes

Status in bluez package in Ubuntu:
  Expired

Bug description:
  bluez-simple-agent crashes, in utopic, on a fresh install and fresh
  boot.  same crash after updating packages and reboot:

  $ bluez-simple-agent hci0 00:0C:8A:AA:FE:70 x
  Traceback (most recent call last):
File "/usr/bin/bluez-simple-agent", line 127, in 
  device = adapter.FindDevice(args[1])
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  **keywords)
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.bluez.Error.DoesNotExist: Does Not Exist

  this appears similar to Bug #1227584, but the dbus exception is not
  the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic i686
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Jan 14 20:30:08 2015
  InstallationDate: Installed on 2015-01-11 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=9212f425-c8f3-4c80-8d62-41faf2b27d30 panic=30
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: K8M800-8237
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2008:svn:pn:pvr:rvn:rnK8M800-8237:rvr:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:15:83:6A:58:96  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:1170 acl:0 sco:0 events:65 errors:0
TX bytes:1056 acl:0 sco:0 commands:65 errors:0
  mtime.conffile..etc.bluetooth.audio.conf: 2015-01-11T15:59:05.078489
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1408444] Re: bluetooth-wizard cannot pair keyboard with given pin

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetooth-wizard cannot pair keyboard with given pin

Status in bluez package in Ubuntu:
  Expired

Bug description:
  To pair e.g. an Iconia W700 type cover using bluetooth-wizard a
  further line in /etc/bluetooth/main.conf is necessary:

  pin_helper = /usr/bin/bluepin

  Without it pairing fails without any comment.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan  7 21:48:39 2015
  InstallationDate: Installed on 2014-10-22 (77 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: btusb bnep rfcomm bluetooth
  MachineType: Acer TP-W700-53334G12
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=f732ccc6-b7f0--8bcf-da659f0321d0 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to utopic on 2014-10-23 (75 days ago)
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SAGE
  dmi.board.vendor: Acer
  dmi.board.version: V2.14
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.14
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd05/24/2013:svnAcer:pnTP-W700-53334G12:pvrV2.14:rvnAcer:rnSAGE:rvrV2.14:cvnInsydeCorp.:ct10:cvrV2.14:
  dmi.product.name: TP-W700-53334G12
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 24:FD:52:1E:C7:CF  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:612 acl:0 sco:0 events:37 errors:0
TX bytes:942 acl:0 sco:0 commands:37 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-01-07T13:38:43.304721

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1442941] Re: Bluetooth Built-in HP 650 does not work in Ubuntu 14.10.

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
   Bluetooth Built-in HP 650 does not work in Ubuntu 14.10.

Status in bluez package in Ubuntu:
  Expired

Bug description:
  When I purchased the HP 650 Laptop, 12.04LTS have installed Ubuntu,
  built-in Bluetooth function and F12 light was white. I made updates to
  12.10 to 14.10. Since then, bluetooth built fails, the F12 LED is
  orange. USB works.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1419186] Re: bluetooth doesn't recover well from interruption

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bluetooth doesn't recover well from interruption

Status in bluez package in Ubuntu:
  Expired

Bug description:
  logged in using twm, i used blueman to pair my bose soundlink iii and
  set it as audio sink, and pair my plantronics 8xx and set it as
  headset service.  i'm using mplayer to play radio via alsa
  /etc/asound.conf defined pcm to the bose.  i've opened linphone merely
  to test if it will work.  it's default settings are "ALSA: default
  device".  pulseaudio is installed but not being used iiuc.  i click on
  linphone's "play" button to test the ring sound.  the ring sound does
  arrive onto the plantronics 8xx, albeit with the first fraction of a
  second missing, but so far no complaint.

  immediately thereafter, a series of skips is heard in the bose audio,
  spanning several seconds.

  now i'm no expert regarding bluetooth bandwidth or other bluetooth
  limitations, but what i hear is poor recovery from an interruption.
  the test ring sound was less than two seconds, so it's not like there
  were several seconds of overlapping audio.  even if bluetooth
  bandwidth is so narrow as to not accomodate the two parallel channels,
  should it really take several seconds of numerous dropouts before the
  audio stream settles again?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bluez-alsa 4.101-0ubuntu22
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  Date: Fri Feb  6 17:13:08 2015
  InstallationDate: Installed on 2015-01-16 (21 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150114)
  InterestingModules: bnep rfcomm btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=5116dd42-c618-49a4-885e-84c697b53abd panic=30
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: K8M800-8237
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2008:svn:pn:pvr:rvn:rnK8M800-8237:rvr:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:15:83:6A:58:96  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:3226118 acl:43 sco:6565 events:405902 errors:0
TX bytes:196839358 acl:683492 sco:6529 commands:24015 errors:7
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1432043] Re: DX... Not work Bluethoot after update

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  DX... Not work Bluethoot after update

Status in bluez package in Ubuntu:
  Expired

Bug description:
  I update Ubuntu vivid and  upgrade Bluez(?) and not on Bluethoot in
  gnome-control-center.

  bluez 4.101-0ubuntu23 to bluez 4.101-0ubuntu24

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-control-center 1:3.14.2-2ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 13 17:32:02 2015
  InstallationDate: Installed on 2014-09-25 (169 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 32.0-0ubuntu5

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1442361] Re: Pairing with bluetooth devices not working on 15.04

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Pairing with bluetooth devices not working on 15.04

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Devices paired on 14.10 are working normally but I'm not able to pair
  with any new device

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  15.04
  3) What you expected to happen
  Window with pairing key and confirmation button should appear 
  4) What happened instead
  It doesn't appear 
  e.g: when trying to pair from Windows PC there is window with PIN and 
"Confirm" button, but it doesn't appear on Ubuntu. When I click "Confirm" on 
WIndows PC it shows pairing error.
  (Similar things happen when trying to pair with Android phone and etc.)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1436976] Re: cannot enable bluetooth

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  cannot enable bluetooth

Status in bluez package in Ubuntu:
  Expired

Bug description:
  One day I decided pairing my computer with my bluetooth headset. I
  enabled bluetooth via the basic bluetooth manager, and was able to
  connect my headset. Then I turned off my computer, and since then,
  bluetooth isn't working anymore.

  When I go on the bluetooth manager (Applications>System
  Tools>Preferences>Bluetooth), bluetooth is disabled. I can switch it
  to the "on" position, but it stays disabled.

  Ubuntu release : 14.10
  bluetooth package : 4.101-0ubuntu20
  Computer model : Aspire V3-771
  Wireless card : Qualcomm Atheros AR9462

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1443985] Re: Apple magic mouse does not pair with Ubuntu

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Apple magic mouse does not pair with Ubuntu

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Same phenomenon as previously:

  Connection to Apple magic mouse fails.

  In the pairing window, the device flickers.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bluez 4.101-0ubuntu25
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.359
  CurrentDesktop: Unity
  Date: Tue Apr 14 14:28:33 2015
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150414)
  MachineType: Apple Inc. MacBookPro10,1
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --- keyboard-configuration/layoutcode=de
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 14:10:9F:D2:25:F8  ACL MTU: 1021:6  SCO MTU: 64:1
    UP RUNNING PSCAN
    RX bytes:7000 acl:15 sco:0 events:318 errors:0
    TX bytes:2665 acl:15 sco:0 commands:155 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1485378] Re: [REGRESSION] bluetooth visibility turns off by itself after 3 minutes

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [REGRESSION] bluetooth visibility turns off by itself after 3 minutes

Status in bluez package in Ubuntu:
  Expired

Bug description:
  I had Ubuntu 14.04 and I had the Bluetooth Visibility set to On. (in
  the submenu under the bluetooth tray icon, where it reads "Visible")

  It used to be always on, I didn't have to turn it on every time I
  wanted my computer to be visible.

  I upgraded to 14.10 and then to 15.04, and then when failing to send a file 
over bluetooth to my computer, I found out Visible was off.
  I turned it on, and it worked.

  However, after a few minutes, it had turned off again.

  I can't find a setting anywhere to automatically turn off after N seconds. It 
would make sense to have that. If there is, it should be accessible through 
Bluetooth settings.
  If such a settings doesn't exist and once turned on bluetooth visibility is 
supposed to remain on, then there's some bug which is causing it to randomly 
turn off.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug 16 23:17:42 2015
  InstallationDate: Installed on 2013-10-11 (674 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:630 acl:0 sco:0 events:40 errors:0
    TX bytes:988 acl:0 sco:0 commands:40 errors:0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1479229] Re: Bluetooth First Pairing OK then no more connection

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth First Pairing OK then no more connection

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Hello

  my bug looks like a lot like Bug #27687

  the var/lib/bluetooth//linkey is own by root so enable to
  reconnect my device (mouse in this case)

  and if i remove the device of known devices bluetooth manager is not
  able to discover the device again

  Thanks for the help in advance

  Kind Regards

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1492441] Re: Cannot connect to 1byone bluetooth keyboard (after successfully pairing)

2017-07-02 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Cannot connect to 1byone bluetooth keyboard (after successfully
  pairing)

Status in bluez package in Ubuntu:
  Expired

Bug description:
  I own a 1byone bluetooth keyboard/touchpad combo device.  I'm using
  wily.

  I have managed to successfully pair it (the UI did not work for this
  -- bug 1492443).  But doing it via the console did pair it:

  $ bluetoothctl
  [NEW] Device 08:73:00:13:CC:45 1byone Keyboard
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# pair 08:73:00:13:CC:45
  Attempting to pair with 08:73:00:13:CC:45
  [CHG] Device 08:73:00:13:CC:45 Connected: yes
  [agent] PIN code: 420005
  [CHG] Device 08:73:00:13:CC:45 Modalias: usb:v04E8p7021d011B
  [CHG] Device 08:73:00:13:CC:45 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 08:73:00:13:CC:45 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 08:73:00:13:CC:45 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 08:73:00:13:CC:45 Paired: yes
  Pairing successful
  [CHG] Device 08:73:00:13:CC:45 Connected: no
  [CHG] Device 60:03:08:C9:C0:87 RSSI: -59
  [CHG] Device 60:03:08:C9:C0:87 RSSI: -48
  [CHG] Device 60:03:08:C9:C0:87 RSSI: -60
  [CHG] Device 60:03:08:C9:C0:87 RSSI: -48
  etc, etc (kept outputting RSSI bits every now and then)

  OK.  So it paired.  (which means it's not bug 1490347)

  But now I can't connect.  You can see above that it says "Connected:
  no".  If I go to the Bluetooth panel in System Settings, its
  "Connection" switch is set to Off and disabled.  But it otherwise
  seems to be successfully paired.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep  4 15:16:58 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-09 (967 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Dell System XPS L322X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=0719ea95-7c02-4d0a-a969-1ba285c420f2 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to wily on 2013-01-31 (945 days ago)
  dmi.bios.date: 12/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0CK86J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd12/03/2012:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0CK86J:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: C4:85:08:FB:58:0A  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:19494 acl:0 sco:0 events:721 errors:0
    TX bytes:3449 acl:0 sco:0 commands:234 errors:1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 861642] Re: upowerd uses 100% cpu till killed

2017-07-02 Thread Jesus Cea
I am having the same problem with an iPhone too. "Trusting" the computer
in the Phone temporally solves it but I don't want to trust the computer
if I can avoid it :-).

Any debug we can help out?

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

Title:
  upowerd uses 100% cpu till killed

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  top - 12:57:54 up  2:56,  3 users,  load average: 1.06, 1.12, 1.35
  Tasks: 219 total,   2 running, 216 sleeping,   0 stopped,   1 zombie
  Cpu0  : 70.2%us, 29.8%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu1  :  2.3%us,  1.3%sy,  0.0%ni, 96.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu2  :  1.0%us,  0.3%sy,  0.0%ni, 98.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu3  :  0.7%us,  1.6%sy,  0.0%ni, 97.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu4  :  0.0%us,  0.3%sy,  0.0%ni, 99.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu5  :  0.0%us,  0.3%sy,  0.0%ni, 98.3%id,  1.4%wa,  0.0%hi,  0.0%si,  0.0%st
  Mem:   5994176k total,  4198260k used,  1795916k free,63308k buffers
  Swap:  8193144k total,   355188k used,  7837956k free,   334316k cached

PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND  
  
   2268 root  20   0  148m 1572  680 R  100  0.0 111:08.37 upowerd

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: upower 0.9.9-4
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Sep 28 12:53:23 2011
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  ProcEnviron:
   
  SourcePackage: upower
  UpgradeStatus: Upgraded to natty on 2011-04-06 (175 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701995] [NEW] package python3-click-package 0.4.43+16.04.20170613-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-07-02 Thread Mef45
Public bug reported:

Ubuntu 16.04 update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python3-click-package 0.4.43+16.04.20170613-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
Date: Mon Jul  3 08:22:23 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-06-16 (381 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: click
Title: package python3-click-package 0.4.43+16.04.20170613-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check third-party-packages xenial

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

Title:
  package python3-click-package 0.4.43+16.04.20170613-0ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in click package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-click-package 0.4.43+16.04.20170613-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Mon Jul  3 08:22:23 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-06-16 (381 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: click
  Title: package python3-click-package 0.4.43+16.04.20170613-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701990] [NEW] package bsdutils 1:2.27.1-6ubuntu3.3 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')

2017-07-02 Thread ramakrishnaiah Gurram
Public bug reported:

OS updates are not working

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bsdutils 1:2.27.1-6ubuntu3.3
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sun Jul  2 22:26:26 2017
DpkgTerminalLog:
 dpkg: error processing package bsdutils (--configure):
  package bsdutils is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package bsdutils is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2017-04-01 (93 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: util-linux
Title: package bsdutils 1:2.27.1-6ubuntu3.3 failed to install/upgrade: package 
bsdutils is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package bsdutils 1:2.27.1-6ubuntu3.3 failed to install/upgrade:
  package bsdutils is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in util-linux package in Ubuntu:
  New

Bug description:
  OS updates are not working

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bsdutils 1:2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jul  2 22:26:26 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package bsdutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-04-01 (93 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package bsdutils 1:2.27.1-6ubuntu3.3 failed to install/upgrade: 
package bsdutils is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1701990/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701563] Re: Qt apps crash in mir_create_menu_window_spec (parent == NULL)

2017-07-02 Thread Daniel van Vugt
Probably the same as bug 1671047 (and others I can't find right now).

** Summary changed:

- On Artful Kate crashes when run on Mir
+ Qt apps crash in mir_create_menu_window_spec (parent == NULL)

** Summary changed:

- Qt apps crash in mir_create_menu_window_spec (parent == NULL)
+ Some Qt apps crash in mir_create_menu_window_spec (parent == NULL)

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

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

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

Title:
  Some Qt apps crash in mir_create_menu_window_spec (parent == NULL)

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New

Bug description:
  $ sudo apt install miral-examples kate
  $ miral-app
  [in the app terminal] $ gdb kate

  Expect: kate runs
  Actual:

  Thread 1 "kate" received signal SIGABRT, Aborted.
  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
  58../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
  (gdb) bt
  #0  0x725da77f in __GI_raise (sig=sig@entry=6)
  at ../sysdeps/unix/sysv/linux/raise.c:58
  #1  0x725dc37a in __GI_abort () at abort.c:89
  #2  0x7fffe1463b78 in mir::require(bool) ()
  at ./src/include/common/mir/require.h:28
  #3  0x7fffe1463b78 in mir_create_menu_window_spec (connection=
  0x55959f40, width=640, height=480, parent=0x0, rect=0x7fffcb90, 
edge=mir_edge_attachment_any) at ./src/client/mir_surface_api.cpp:79
  #4  0x7fffe1716f31 in  ()
  at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #5  0x7fffe17180eb in  ()
  at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #6  0x7fffe170506b in  ()
  at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #7  0x73f200c9 in QWindowPrivate::create(bool) ()
  at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  #8  0x746e5585 in QWidgetPrivate::create_sys(unsigned long long, 
bool, bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #9  0x746e4d7d in QWidget::create(unsigned long long, bool, bool) ()
  at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #10 0x746e51e9 in QWidget::winId() const ()
  at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1701563/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1671047] Re: Starting rsibreak aborts in mir_create_menu_window_spec

2017-07-02 Thread Daniel van Vugt
Incomplete due to lack of debug info. But I suspect the same issue
continues in -> bug 1701563

** Changed in: mir
   Status: New => Incomplete

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

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

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

Title:
  Starting rsibreak aborts in mir_create_menu_window_spec

Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in qtubuntu package in Ubuntu:
  Incomplete

Bug description:
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
  #1  0x73a6f3ea in __GI_abort () at abort.c:89
  #2  0x7fffe5ea1378 in mir_create_menu_window_spec ()
 from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fffe61515a1 in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #4  0x7fffe615279d in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #5  0x7fffe613fe1b in ?? ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #6  0x74be60c9 in QWindowPrivate::create (this=0x55aff260, 
  recursive=recursive@entry=false) at kernel/qwindow.cpp:406
  #7  0x74be64db in QWindow::create (this=this@entry=0x55aff200)
  at kernel/qwindow.cpp:584
  #8  0x753ab585 in QWidgetPrivate::create_sys 
(this=this@entry=0x55b8cb30, 
  window=window@entry=0, initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1480
  #9  0x753aad7d in QWidget::create (this=0x55b91a60, 
window=window@entry=0, 
  initializeWindow=initializeWindow@entry=true, 
  destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1342
  #10 0x753ab1ae in QWidgetPrivate::createWinId (this=)
  at kernel/qwidget.cpp:2579
  #11 0x753ab1e9 in QWidget::winId (this=0x55b91a60) at 
kernel/qwidget.cpp:2547
  #12 0x5557f68c in ?? ()
  #13 0x5557fb7d in ?? ()
  #14 0x55568ddf in ?? ()
  #15 0x5557010b in ?? ()
  #16 0x555709e6 in ?? ()
  #17 0x55566955 in ?? ()
  #18 0x73a583f1 in __libc_start_main (main=0x55566230, argc=3, 
  argv=0x7fffe718, init=, fini=, 
  rtld_fini=, stack_end=0x7fffe708) at 
../csu/libc-start.c:291
  #19 0x55566a2a in _start ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1671047/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701512] Re: Ambiance and Radiance Gtk theme do not properly support GtkTreeView separators

2017-07-02 Thread Daniel van Vugt
** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Ambiance and Radiance Gtk theme do not properly support GtkTreeView
  separators

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

Bug description:
  When using a GtkTreeView with separators (via set_row_separator_func),
  the Ambiance (and Radiance) themes do not render the treeview
  correctly, and it glitches the rows as you move your mouse over it.
  This issue is not present with the default Gtk+ theme, Adwaita.

  A simple python script to show a treeview that exhibits the bug is
  attached.

  Behavior is exhibited on Ubuntu 17.04
  (https://github.com/exaile/exaile/issues/362#issuecomment-308685640)

  Originally reported to the Exaile project at
  https://github.com/exaile/exaile/issues/362.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1701512/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

2017-07-02 Thread Daniel van Vugt
Yes, we released pulseaudio 1:8.0-0ubuntu3.3 last week. But in testing
that I too started to suspect that the v4.8 kernel (introduced in
16.04.2?) was helping to further reduce bluetooth bugs.

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

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

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

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

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

  After hard blocking and unblocking

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

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

  Workaround: After a

  sudo service bluetooth restart

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

  Suggested fix: Make the workaround obsolete.

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701816] Re: Annoying beeps on Lubuntu 16.04

2017-07-02 Thread Daniel van Vugt
This sounds like a duplicate of bug 1585084 (which could occur in
different shells slightly differently). And the beeps might be brief
distortions of the normal volume changing sound...

Please use this command to help us get more information about your system:
  apport-collect 1701816

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

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

Title:
  Annoying beeps on Lubuntu 16.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a fresh install of Lubuntu 16.04 on my old Vaio VGN-FS730F and there 
are some annoying beeps that sound always in a randomly way. They have no 
defined pattern.
  I thought it was the pc speaker so I disabled from BIOS but it doesn't change 
anything. I realized that the beeps are  emitted by the soundcard because when 
I can listen it by headphones when I connect them. Sometimes the sound tray 
icon blinks at the sound of the beeps.

  The patterns of beeps changes randomly at every machine restart.
  -Not beep at all.
  -Beep every minute
  -Beep every second.
  -Sometimes the beeps lower their frequency when I play some video in firefox.

  Seems to be worst when the battery is low, but this is not a ruler.

  If you have problems figuring my situation, check this video of the
  issue https://youtu.be/GetcRSn2OJ4

  For me, it's enough to find a way to mute these annoying beeps.

  Model : Vaio VGN-FS730F

  >lsb_release -rd
  Description:   Ubuntu 16.0.4.2 LTS
  Release:   16.04

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1181106] Re: Failed to change profile to A2DP

2017-07-02 Thread Daniel van Vugt
Bluetooth audio (A2DP pairing in particular) was improved last week in:

  pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

The bluez release you mention was released on 2016-03-09 and has
remained unchanged :)

It's confusing and unexpected, but Bluetooth audio is mostly implemented
in 'pulseaudio' and not in 'bluez'.

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

Title:
  Failed to change profile to A2DP

Status in Bluez Utilities:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the 
device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is 
now connected and will "show in the PulseAudio mixer"
  * After connecting the external speaker to the audio sink, I can also see the 
device in the "Play sound through" listing in the Sound system control panel, 
but the icon has a circle with a line through it.
  * but if I right-click the device and choose "Audio Profile" from the context 
menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I 
get an error message stating "failed to change profile to a2dp"

  I've already added "Enable=Socket" in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no 
transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

2017-07-02 Thread Balint Reczey
Could you please test the attached patch on Xenial either by rebuilding the 
package or by grabbing it from 
https://launchpad.net/~rbalint/+archive/ubuntu/scratch ?
It is expected to fix the communication between u-u and u-u-shutdown and make 
u-u-shutdown wait properly for u-u to finish.


** Patch added: "unattended-upgrades_0.90ubuntu0.7.patch"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1690980/+attachment/4908156/+files/unattended-upgrades_0.90ubuntu0.7.patch

** Changed in: unattended-upgrades (Ubuntu)
   Status: In Progress => Incomplete

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701967] [NEW] package linux-image-generic 4.8.0.58.71 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2017-07-02 Thread Tasos Agriogiannis
Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: linux-image-generic 4.8.0.58.71
ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  tasos  2329 F pulseaudio
 /dev/snd/controlC0:  tasos  2329 F pulseaudio
 /dev/snd/controlC1:  tasos  2329 F pulseaudio
Date: Wed Jun 28 00:45:58 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=4e8cd5c6-9fd0-499f-b212-c9458002202a
InstallationDate: Installed on 2016-12-19 (195 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
IwConfig:
 enp4s0no wireless extensions.
 
 lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-56-generic 
root=UUID=d4b21a16-2b70-456b-9374-3df0d5206c01 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-generic 4.8.0.58.71 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
UpgradeStatus: Upgraded to yakkety on 2017-06-30 (1 days ago)
dmi.bios.date: 07/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6508
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A85-M
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6508:bd07/11/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package linux-image-generic 4.8.0.58.71 failed to install/upgrade:
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return
  code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-generic 4.8.0.58.71
  ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  tasos  2329 F pulseaudio
   /dev/snd/controlC0:  tasos  2329 F pulseaudio
   /dev/snd/controlC1:  tasos  2329 F pulseaudio
  Date: Wed Jun 28 00:45:58 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=4e8cd5c6-9fd0-499f-b212-c9458002202a
  InstallationDate: Installed on 2016-12-19 (195 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-56-generic 
root=UUID=d4b21a16-2b70-456b-9374-3df0d5206c01 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-generic 4.8.0.58.71 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  UpgradeStatus: Upgraded to yakkety on 2017-06-30 (1 days ago)
  dmi.bios.date: 07/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6508
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6508:bd07/11/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: S

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

2017-07-02 Thread Photon
A followup on my report about skypeonlinux: It looks like the problem is
related to some user config in this case. If I create a clean user,
gnome-keyring works as expected. However, I wasn't able to find where
exactly the problematic configuration file is located yet.

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701963] [NEW] package libjpeg-turbo8-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/turbojpeg.h', que também está no pacote libjpeg-turbo:i

2017-07-02 Thread Charles
Public bug reported:

install alegro sound

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libjpeg-turbo8-dev (not installed)
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sun Jul  2 18:03:26 2017
ErrorMessage: a tentar sobre-escrever '/usr/include/turbojpeg.h', que também 
está no pacote libjpeg-turbo:i386 1.0.1-20100909
InstallationDate: Installed on 2017-01-15 (168 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libjpeg-turbo
Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: a 
tentar sobre-escrever '/usr/include/turbojpeg.h', que também está no pacote 
libjpeg-turbo:i386 1.0.1-20100909
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libjpeg-turbo (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package libjpeg-turbo8-dev (not installed) failed to install/upgrade:
  a tentar sobre-escrever '/usr/include/turbojpeg.h', que também está no
  pacote libjpeg-turbo:i386 1.0.1-20100909

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  install alegro sound

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-turbo8-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jul  2 18:03:26 2017
  ErrorMessage: a tentar sobre-escrever '/usr/include/turbojpeg.h', que também 
está no pacote libjpeg-turbo:i386 1.0.1-20100909
  InstallationDate: Installed on 2017-01-15 (168 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: 
a tentar sobre-escrever '/usr/include/turbojpeg.h', que também está no pacote 
libjpeg-turbo:i386 1.0.1-20100909
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1701963/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

2017-07-02 Thread Coeur Noir
Well… now the problem happens on all the users-sessions but the error
message is little different :

alessandra@Asgard:~$ chromium-browser 
Using PPAPI flash.
 --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
[5958:5995:0702/224636.598323:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-118233930601834352306

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

2017-07-02 Thread Coeur Noir
Affected here on Ubuntu 16.04 Unity.

I noticed it on trying to launch chromium-browser, it takes very long
with errors

coeurnoir@Asgard:~$ chromium-browser 
Using PPAPI flash.
 --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
[14639:14687:0702/211518.780149:ERROR:crx_installer.cc(735)] Impossible de 
charger l'icône de l'extension "icons/192.png". 
edcifkpoamnkimdpjiabhfjahoinbpbps

Only one user-session out of 3 on the same machine seems affected for
the moment.

On the affected session I installed yesterday flatpak from
ppa:alexlarsson/flatpak in order to try latest version of pitivi.
Installing pitivi through flatpak asked to connect to gnome3.22 related
stuff … any hint there ? Because chromium get slow right after that
installation.

I did uninstall pitivi through flatpak command, then ppa-purged flatpak
but things did not get better.

Screen-capture by keyboard-shortcut is also very slow ( it finally
happens when chromium stops hanging ).

Same story in french there → https://forum.ubuntu-
fr.org/viewtopic.php?id=2011625

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701960] [NEW] package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')

2017-07-02 Thread tong
Public bug reported:

failed to update.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bsdutils 1:2.29-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic i686
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: i386
Date: Mon Jul  3 02:36:19 2017
DpkgTerminalLog:
 dpkg: error processing package bsdutils (--configure):
  package bsdutils is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package bsdutils is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2017-06-15 (17 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: util-linux
Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package 
bsdutils is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 zesty

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package
  bsdutils is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in util-linux package in Ubuntu:
  New

Bug description:
  failed to update.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  Date: Mon Jul  3 02:36:19 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package bsdutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-15 (17 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package 
bsdutils is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1701960/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1684100] Re: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10

2017-07-02 Thread Dmitrii Shcherbakov
Worked for me:

cat /etc/NetworkManager/conf.d/tl-wn722n.conf 
[device]
match-device=wlx18a6f719681b
wifi.scan-rand-mac-address=0

Thanks for starting this thread.

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

Title:
  TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on
  16.10

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on
  16.10

  sudo apt-get update; sudo apt-get install usbutils pciutils hwinfo grep 
rfkill; sudo lshw -C network; rfkill list; sudo iwlist scan | grep -Ei 
'chan|ssid'; cat /etc/network/interfaces; cat /etc/lsb-release; lspci -nnk | 
grep -iA2 net; lsusb; nmcli nm status; sudo lshw -short; uname -a; sudo 
updatedb; dmesg | grep -E  
'02:00|80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|ireless|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|ound|p54|prism|rror|rtl|RTL|rt2|RT2|rt3|RT3|rt5|RT5|rt6|RT6|rt7|RT7|usb|witch|wl';sudo
 dmidecode|grep -E 'anufact|roduct|erial|elease'; iwconfig; grep -E 
'80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|p54|prism|rtl|rt2|rt3|rt6|rt7|wmi|witch|wl'
 /etc/modprobe.d/*; cat /var/lib/NetworkManager/NetworkManager.state; sudo 
hwinfo --netcard ; ps -aux|grep -E 'wpa|icd|etwork'; netstat -rn ; cat 
/etc/resolv.conf; ls -lia /boot; grep tmpfs /etc/fstab; ubuntu-support-status; 
sudo update-pciids; sudo update-usbids; sudo lsmod
  Get:1 http://security.ubuntu.com/ubuntu zesty-security InRelease [89.2 kB]
  Get:2 http://gb.archive.ubuntu.com/ubuntu zesty InRelease [243 kB]
  Get:3 http://gb.archive.ubuntu.com/ubuntu zesty-updates InRelease [89.2 kB]
  Hit:4 http://gb.archive.ubuntu.com/ubuntu zesty-backports InRelease
  Fetched 421 kB in 0s (873 kB/s)   
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  grep is already the newest version (2.27-2).
  pciutils is already the newest version (1:3.3.1-1.1ubuntu9).
  pciutils set to manually installed.
  rfkill is already the newest version (0.5-1ubuntu3).
  rfkill set to manually installed.
  usbutils is already the newest version (1:007-4).
  usbutils set to manually installed.
  The following additional packages will be installed:
libhd21 libx86emu1
  The following NEW packages will be installed
hwinfo libhd21 libx86emu1
  0 to upgrade, 3 to newly install, 0 to remove and 0 not to upgrade.
  Need to get 754 kB of archives.
  After this operation, 3,261 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 libx86emu1 
amd64 1.11-2 [47.8 kB]
  Get:2 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 libhd21 amd64 
21.38-1 [688 kB]
  Get:3 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 hwinfo amd64 
21.38-1 [17.7 kB]
  Fetched 754 kB in 0s (2,074 kB/s) 
  Selecting previously unselected package libx86emu1:amd64.
  (Reading database ... 177811 files and directories currently installed.)
  Preparing to unpack .../libx86emu1_1.11-2_amd64.deb ...
  Unpacking libx86emu1:amd64 (1.11-2) ...
  Selecting previously unselected package libhd21:amd64.
  Preparing to unpack .../libhd21_21.38-1_amd64.deb ...
  Unpacking libhd21:amd64 (21.38-1) ...
  Selecting previously unselected package hwinfo.
  Preparing to unpack .../hwinfo_21.38-1_amd64.deb ...
  Unpacking hwinfo (21.38-1) ...
  Setting up libx86emu1:amd64 (1.11-2) ...
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for man-db (2.7.6.1-2) ...
  Setting up libhd21:amd64 (21.38-1) ...
  Setting up hwinfo (21.38-1) ...
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
*-network 
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:04:00.0
 logical name: enp4s0
 version: 06
 serial: f4:6d:04:90:cb:7a
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl_nic/rtl8168e-2.fw latency=0 
link=no multicast=yes port=MII speed=10Mbit/s
 resources: irq:31 ioport:c000(size=256) memory:f0004000-f0004fff 
memory:f000-f0003fff
*-network:0
 description: Wireless interface
 physical id: 3
 bus info: usb@2:1.7
 logical name: wlxf81a6721bb82
 serial: 56:3e:54:48:50:00
 capabilities: eth

[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default

2017-07-02 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 233-8ubuntu2

---
systemd (233-8ubuntu2) artful; urgency=medium

  * Disable fallback DNS servers.
This causes resolved to call-home to google, attempt to access network when
none is available, and spams logs. (LP: #1449001, #1698734)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved.
CVE-2017-9445 (LP: #1695546)

 -- Dimitri John Ledkov   Wed, 28 Jun 2017 13:27:28
+0100

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

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

Title:
  systemd-resolved: please do not use Google public DNS by default

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.)
  in the absence of other configured DNS servers.

  systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
  installed by default and will behave in this way if enabled by the
  user.

  $ cat /etc/systemd/resolved.conf 
  (...)
  # Entries in this file show the compile time defaults.
  (...)
  #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

  This raises privacy concerns since in the event of accidental
  misconfiguration DNS queries will be sent unencrypted across the
  internet, and potentially also security concerns given systemd-
  resolved does not perform DNSSEC validation and is not particularly
  well hardened against malicious responses e.g. from a MITM
  (http://www.openwall.com/lists/oss-security/2014/11/12/5).

  I believe that it would be better to fail safe if no DNS server is
  configured -- i.e. have DNS lookups fail; it's better that the user is
  aware of their misconfiguration, rather than silently sending their
  queries to Google.  The user can intentionally opt to use Google
  public DNS if they wish.


  Steps to reproduce:
  1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
  2. Reboot, or otherwise clear relevant state
  3. sudo service systemd-resolved start
  4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
  5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by 
default), observe that DNS lookups probably still work, and queries are being 
sent to one of Google's servers

  
  Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS 
parameter.

  
  This issue has been discussed in the Debian BTS 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My interpretation 
of the Debian package maintainer's position is that a user concerned with the 
privacy implications shouldn't let systemd get into a state where it uses the 
fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf 
file or use DHCP").  I would argue that it's safest not to have fallback DNS 
servers configured at all by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1449001/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1698734] Re: systemd-resolved spams syslog whenever I'm disconnected

2017-07-02 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 233-8ubuntu2

---
systemd (233-8ubuntu2) artful; urgency=medium

  * Disable fallback DNS servers.
This causes resolved to call-home to google, attempt to access network when
none is available, and spams logs. (LP: #1449001, #1698734)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved.
CVE-2017-9445 (LP: #1695546)

 -- Dimitri John Ledkov   Wed, 28 Jun 2017 13:27:28
+0100

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

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

Title:
  systemd-resolved spams syslog whenever I'm disconnected

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  Fix Released

Bug description:
  Every time I suspend my laptop and resume in a situation where I don't have 
connectivity
  I get big syslog spam from systemd-resolved. See for instance yesterday when 
I went out:

  Jun 18 18:48:16 chiron systemd[1]: Starting Suspend...
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.4.4.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::.
  Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::8844.
  ...

  And the last messages of the "episode":

  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.4.4.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 2001:4860:4860::8844.
  Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS 
server 8.8.8.8.
  Jun 18 20:13:28 chiron NetworkManager[30674]:   [1497809608.0889] 
device (wlp2s0): supplicant interface state: associ
  ated -> 4-way handshake

  So this correspond to roughly 85 minutes of disconnection, during
  which I got...

  $ grep  "fallback DNS" /var/log/syslog.1 | wc -l
  444066

  This correspond to 5224 messages/minute,  87 messages/second

  I had a few other episodes in the last week, including a 4h train
  roundtrip:

  $ zgrep  "fallback DNS" /var/log/syslog* | wc -l
  1964217

  I noticed the bug during the trip, when the SSD activity was slowing
  my machine in a clearly noticeable way.

  I'm running:

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  $ apt-cache policy $(dpkg-query -S $(which systemd-resolve ) | awk '{print 
$1}')
  systemd:
Installed: 232-21ubuntu3
Candidate: 232-21ubuntu3
Version table:
   *** 232-21ubuntu3 500
  500 http://es.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   232-21ubuntu2 500
  500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1604010] Re: sntp missing

2017-07-02 Thread Doug Smythies
** Changed in: serverguide
   Status: In Progress => Fix Committed

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

Title:
  sntp missing

Status in Ubuntu Server Guide:
  Fix Committed
Status in ntp package in Ubuntu:
  Fix Released
Status in ntp package in Debian:
  Fix Released

Bug description:
  In Ubuntu 16.04, the binary file /usr/bin/sntp is missing from the
  package ntp. The associated man page /usr/share/man/man1/sntp.1.gz is
  still included.

  How to reproduce:

  $ sudo apt-get install ntp
  $ dpkg-query -L ntp | grep sntp
  /usr/share/man/man1/sntp.1.gz

  Expected result:

  /usr/bin/sntp was included in Ubuntu 14.04:

  $ dpkg-query -L ntp | grep sntp
  /usr/bin/sntp
  /usr/share/man/man1/sntp.1.gz

  The sntp program remains a very useful tool for interactively testing
  on the command line the offset of the local clock to a remote NTP
  server (like "ntpdate -qu [ntp-server]" previously). It should be
  included in the same package as its man page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/serverguide/+bug/1604010/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1604010] Re: sntp missing

2017-07-02 Thread Launchpad Bug Tracker
** Branch linked: lp:serverguide

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

Title:
  sntp missing

Status in Ubuntu Server Guide:
  Fix Committed
Status in ntp package in Ubuntu:
  Fix Released
Status in ntp package in Debian:
  Fix Released

Bug description:
  In Ubuntu 16.04, the binary file /usr/bin/sntp is missing from the
  package ntp. The associated man page /usr/share/man/man1/sntp.1.gz is
  still included.

  How to reproduce:

  $ sudo apt-get install ntp
  $ dpkg-query -L ntp | grep sntp
  /usr/share/man/man1/sntp.1.gz

  Expected result:

  /usr/bin/sntp was included in Ubuntu 14.04:

  $ dpkg-query -L ntp | grep sntp
  /usr/bin/sntp
  /usr/share/man/man1/sntp.1.gz

  The sntp program remains a very useful tool for interactively testing
  on the command line the offset of the local clock to a remote NTP
  server (like "ntpdate -qu [ntp-server]" previously). It should be
  included in the same package as its man page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/serverguide/+bug/1604010/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1700477] Re: package libmirprotobuf3:amd64 0.26.3+16.04.20170605-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before

2017-07-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mir (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libmirprotobuf3:amd64 0.26.3+16.04.20170605-0ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in mir package in Ubuntu:
  Confirmed

Bug description:
  i dont know what exactly is the issue here

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libmirprotobuf3:amd64 0.26.3+16.04.20170605-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libmirprotobuf3: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jun 20 13:37:00 2017
  DpkgTerminalLog:
   dpkg: error processing package libmirprotobuf3:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-02-15 (496 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: mir
  Title: package libmirprotobuf3:amd64 0.26.3+16.04.20170605-0ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2017-06-05 (20 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701928] [NEW] package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')

2017-07-02 Thread shanta
Public bug reported:

Installing Perl6 Though problem may be due to a previous failed upgrade.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bsdutils 1:2.29-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
AptOrdering:
 bsdutils:amd64: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Jul  1 15:22:47 2017
DpkgTerminalLog:
 dpkg: error processing package bsdutils (--configure):
  package bsdutils is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package bsdutils is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2016-10-24 (251 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: util-linux
Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package 
bsdutils is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: Upgraded to zesty on 2017-04-17 (75 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package
  bsdutils is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in util-linux package in Ubuntu:
  New

Bug description:
  Installing Perl6 Though problem may be due to a previous failed
  upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   bsdutils:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jul  1 15:22:47 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package bsdutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-10-24 (251 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package 
bsdutils is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (75 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1701928/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1683148] Re: Sound delay with ASUS GL552VW in 17.04

2017-07-02 Thread Jakub Jankiewicz
This is not related to nvidia because when I use nomodeset kernel option
I have the same delay.

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

Title:
  Sound delay with ASUS GL552VW in 17.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I had 16.10 everything was fine but when I've installed 17.04
  (update was failed because X server crashed because of nvidia drivers)
  there is few seconds delay after sound is played, the sound and video
  is in sync but it look like sound is muted when it starts it work when
  playing next sound or when pausing the sound (for instance in
  audacious) but I've got delay when I stop and play again.

  I've try this in /etc/modprobe.d/alsa-base.conf file as mention in
  this thread https://ubuntuforums.org/showthread.php?t=1308604

  options snd-hda-intel model=laptop enable=1 index=0
  options snd-hda-intel power save=0

  but got error in dmesg that those options are not supported:

  [   15.253198] snd_hda_intel: unknown parameter 'power' ignored
  [   15.253199] snd_hda_intel: unknown parameter 'save' ignored

  the first sound test was without delay but the second one was.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kuba  15418 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Apr 16 16:27:58 2017
  InstallationDate: Installed on 2017-04-15 (1 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: None of the above
  Title: [GL552VW, Conexant CX20751/2, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL552VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-04-16T15:59:40.113763

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1683148/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1100263] Re: adduser: mistake in german translation

2017-07-02 Thread Amr Ibrahim
** Changed in: ubuntu-translations
   Status: Fix Committed => Fix Released

** Changed in: adduser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  adduser: mistake in german translation

Status in adduser:
  Fix Released
Status in Ubuntu Translations:
  Fix Released
Status in adduser package in Ubuntu:
  Fix Released

Bug description:
  Section "Einen System-Benutzer einrichten" says:

  "Wird  adduser  ohne  die Option --system und mit einem nicht
  optionalen Argument aufgerufen, richtet adduser einen System-Benutzer
  ein."

  I checked the english mainpage and it should say:

  "Wird  adduser  mit der Option --system und mit einem nicht optionalen
  Argument aufgerufen, richtet adduser einen System-Benutzer ein."

  ProblemType: BugDistroRelease: Ubuntu 12.10
  Package: adduser 3.113+nmu1ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic i686
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  Date: Wed Jan 16 13:59:32 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-05-21 (606 days ago)InstallationMedia: 
Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zshSourcePackage: adduser
  UpgradeStatus: Upgraded to quantal on 2012-11-04 (72 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/adduser/+bug/1100263/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2017-07-02 Thread mirak
I have this problem on 17.04, it appeared just like that.

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1692365] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2017-07-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: avahi (Ubuntu)
   Status: New => Confirmed

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

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

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  I had installed gnome classic and also (to test it) the Mate desktop.
  I like Gnome classic best so I uninstalled the Mate desktop.
  And now this avari package is missing.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun May 21 23:32:35 2017
  DuplicateSignature:
   package:avahi-dnsconfd:0.6.32~rc+dfsg-1ubuntu2
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--remove):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-05-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701880] [NEW] package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 usr/lib/x86_64-linux-gnu/openss

2017-07-02 Thread Fernando Couto
Public bug reported:

I don't know details.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sun Jul  2 10:37:22 2017
ErrorMessage: el paquete libssl1.0.0:amd64 no está listo para configurarse  no 
se puede configurar (estado actual `half-installed')
InstallationDate: Installed on 2016-12-13 (200 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: el paquete libssl1.0.0:amd64 no está listo para
  configurarse  no se puede configurar (estado actual `half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  I don't know details.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jul  2 10:37:22 2017
  ErrorMessage: el paquete libssl1.0.0:amd64 no está listo para configurarse  
no se puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2016-12-13 (200 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701871] Re: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

2017-07-02 Thread Hans Joachim Desserud
*** This bug is a duplicate of bug 1574351 ***
https://bugs.launchpad.net/bugs/1574351

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1574351, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1574351
   package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different 
from other instances of package libperl5.22:i386

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

Title:
  package libperl5.22 5.22.2-3 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  New

Bug description:
  The Internet icon on the tool bar is lost

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libperl5.22 5.22.2-3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   libperl5.22:i386: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jul  2 10:05:10 2017
  DpkgHistoryLog:
   Start-Date: 2017-07-02  10:05:09
   Commandline: apt-get -f install
   Requested-By: mahdieh (1000)
   Install: libperl5.22:i386 (5.22.2-3, automatic)
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.2-3_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.2-3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.2-3_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   package:libperl5.22:5.22.2-3
   Unpacking libperl5.22:i386 (5.22.2-3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.2-3_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2017-03-30 (93 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: perl
  Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: Upgraded to yakkety on 2017-05-05 (57 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701875] [NEW] systemd crashing swap partitions

2017-07-02 Thread Hadmut Danisch
Public bug reported:

Hi,

systemd still kills the swap device sometimes.

I typically avoid lvm and prefer the partition scheme like

/dev/sda1   unencrypted boot
/dev/sda2   luks-encrypted swap
/dev/sda3   luks-encrypted /root


and haven an /etc/crypttab like

sda2_crypt UUID=a5b1de14-00e7-46a2-a18a-118af13d0ea7 none luks,swap,discard
sda3_crypt UUID=9ec0971c-605f-4045-a8e4-57f15c933441 none luks,discard


Since using systemd it sometimes happens that the system does not boot anymore. 
Analysis shows that for some reason the swap partition (the raw partition 
before encryption) contains just rubbish, and since systemd insists on getting 
this swap device for dependencies and thus never fulfills it's dependencies. 

I have no idea what happens insided that damned systemd, since I did not
found any debugging method to see what systemd does. If /etc/crypttab
contains a swap tag, systemd tries to run mkswap and something goes
wrong every now and then (not always, most of the time it works as
expected).

My current guess is that there is some race condition between the normal
mount and recreating the swap, and it looks as if systemd has
dependencies twice, for the device name (sda2 and sda2_crypt) and the
UUID, maybe two processes are spawned instead of one and interfere.

However, it makes systems unstable and unreliable.

regards

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu17
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Jul  2 09:06:42 2017
MachineType: Medion G24
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic 
root=UUID=4638a5a1-629c-477c-b1df-b370d0181be5 ro rootflags=subvol=@ splash 
quiet
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: H61TIW08.111
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-TI2
dmi.board.vendor: Medion
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Medion
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
dmi.product.name: G24
dmi.product.version: 1.0
dmi.sys.vendor: Medion

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


** Tags: amd64 apport-bug xenial

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

Title:
  systemd crashing swap partitions

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  systemd still kills the swap device sometimes.

  I typically avoid lvm and prefer the partition scheme like

  /dev/sda1   unencrypted boot
  /dev/sda2   luks-encrypted swap
  /dev/sda3   luks-encrypted /root

  
  and haven an /etc/crypttab like

  sda2_crypt UUID=a5b1de14-00e7-46a2-a18a-118af13d0ea7 none luks,swap,discard
  sda3_crypt UUID=9ec0971c-605f-4045-a8e4-57f15c933441 none luks,discard

  
  Since using systemd it sometimes happens that the system does not boot 
anymore. Analysis shows that for some reason the swap partition (the raw 
partition before encryption) contains just rubbish, and since systemd insists 
on getting this swap device for dependencies and thus never fulfills it's 
dependencies. 

  I have no idea what happens insided that damned systemd, since I did
  not found any debugging method to see what systemd does. If
  /etc/crypttab contains a swap tag, systemd tries to run mkswap and
  something goes wrong every now and then (not always, most of the time
  it works as expected).

  My current guess is that there is some race condition between the
  normal mount and recreating the swap, and it looks as if systemd has
  dependencies twice, for the device name (sda2 and sda2_crypt) and the
  UUID, maybe two processes are spawned instead of one and interfere.

  However, it makes systems unstable and unreliable.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jul  2 09:06:42 2017
  MachineType: Medion G24
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic