Re: [Touch-packages] [Bug 1626005] PulseList.txt

[Luke Yelavich]

You could either install/boot yakkety from live media, and see if the
same problem exists there, or you could upgrade ALSA hd audio drviers,
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS.

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

Title:
  X220 in dock doesn't mute external speakers when headphones connected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This worked in 14.04, and now "doesn't" in 16.04.

  Steps to reproduce:

  Have external speakers connected via the 3.5mm jack on the docking station 
and have the computer docked.
  Listen to some music.
  Notice that it's coming out of the external speakers.
  Plug headphones in to the 3.5mm jack on the laptop itself.
  Notice that music comes from the external speakers *and* the headphones.
  In the past the external speakers would have muted (I am 99% sure this is the 
case, but I will test with a live 14.04 image and report back) and the audio 
would have only come out of the headphones.

  I note that in the sound settings panel the external speakers are identified 
as "Headphones".
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  will   4045 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (152 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET50WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1626005/+subscriptions

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

Re: [Touch-packages] [Bug 1608820] Re: Cannot use BT speaker - sink is suspended

[Luke Yelavich]

*** This bug is a duplicate of bug 1574324 ***
https://bugs.launchpad.net/bugs/1574324

Ok, I am pretty sure the bug for this is actually 1574324. Plesae see
that bug, as I have just uploaded an SRU for xenial and yakkety. Bug
should be fixed in zesty.

I will markt his one as a dupe, please remove the duplciate marking if
the SRU does not fix the problem.

 duplicate 1574324


** This bug has been marked a duplicate of bug 1574324
   pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu 
changes?)

** This bug has been marked a duplicate of bug 1574324
   pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu 
changes?)

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

Title:
  Cannot use BT speaker - sink is suspended

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

Bug description:
  After a fresh boot or resuming from suspend it is possible to connect to a BT 
speaker but not possible to play anything.
  Furthermore, if I play a video from youtube, the stream plays fine if the 
output is the internal speaker, but as soon as I select the BT speaker the 
stream hangs. It resumes immediately if I switch back to the internal speaker.

  When I play something over the BT speaker the following lines are logged in 
the journal:
  pulseaudio[5340]: [pulseaudio] module-bluez5-device.c: Default profile not 
connected, selecting off profile
  bluetoothd[3230]: /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1: fd(24) ready
  rtkit-daemon[3950]: Supervising 5 threads of 1 processes of 1 users.
  rtkit-daemon[3950]: Successfully made thread 28532 of process 5340 (n/a) 
owned by '1000' RT at priority 5.
  rtkit-daemon[3950]: Supervising 6 threads of 1 processes of 1 users.
  pulseaudio[5340]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed 
for transport /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1 (Operation Not 
Authorized)
  kernel: input: B8:69:C2:3D:56:CE as /devices/virtual/input/input26
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.
  gnome-session[5383]: ** (zeitgeist-datahub:5874): WARNING **: 
zeitgeist-datahub.vala:212: Error during inserting events: 
GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: 
interpretation, manifestation and actor are required
  wpa_supplicant[3556]: wlan0: WPA: Group rekeying completed with 
14:0c:76:71:a1:f4 [GTK=CCMP]
  pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: 
sink is suspended.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  2 09:09:18 2016
  InstallationDate: Installed on 2013-09-03 (1063 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: C4:85:08:A7:45:76  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING
    RX bytes:3492 acl:70 sco:0 events:137 errors:0
    TX bytes:4838 acl:64 sco:0 commands:57 errors:0
  upstart.bluetooth.override: manual

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

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

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Luke Yelavich]

** Description changed:

+ Impact:
+ 
+ A patch we carry for Ubuntu touch introduced a change that originally
+ was required to make sure PulseAudio did not crash. This patch was
+ ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
+ hardware that was to hand at the time worked so was assumed to be ok.
+ However, the opposite is now happening, i.e PulseAudio is crashing with
+ a subset of Bluetooth hardware.
+ 
+ Regression potential:
+ 
+ Very low to none. As can be read in this report, much debugging and
+ testing has been done to find the problem, and the eventual fix.
+ Moreover the change is the removal of a patch hunk that removed a line
+ of code originally present in PulseAudio.
+ 
+ Test case:
+ 
+ NOTE that this test case applies to bluetooth hardware that is
+ identified as not working in this bug report.
+ 
+ 1. Install, or upgrade to Xenial or yakkety.
+ 2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
+ 3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
+ 4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
+ 5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
+ 6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.
+ 
+ 
+ Original bug report:
+ 
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads me
  to believe it's an intermittent problem with some hardware. This did not
  happen on Ubuntu 15.10 (which was an upgrade of 15.04).
  
  Ubuntu Release:
  
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  
  Pulseaudio Version:
  
  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  
  Device info:
  
  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)
  
  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  In Progress

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  When I attempt to con

[Touch-packages] [Bug 1573296] Re: obsolete conffiles not cleaned up on upgrade

[Luke Yelavich]

** Description changed:

+ Impact:
+ 
+ When upgrading to xenial from earlier releases, some files are left on
+ the user's system. They are not used, but may otherwise be mistaken for
+ being used by the user if they are attempting to fix a problem.
+ 
+ Regression potential:
+ 
+ Low to none, as the relevant files are not used, and are being removed
+ when the updated version of Pulseaudio is installed. These files are
+ already removed in yakkety and later.
+ 
+ Test case:
+ 
+ When updating from trusty to xenial, one will note the presence of the
+ below listed files on the system. Updating from pulseaudio in xenial or
+ pulseaudio in trusty to what is in xenial-proposed shoudl delete the
+ listed files. The /etc/init.d/pulseaudio script should also be
+ unregistered.
+ 
+ 
+ Original bug report:
+ 
  The following files are marked obsolete after the upgrade to 16.04:
  
   /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
   /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
   /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
   /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete
  
  
  Those files should be cleaned up and the sysv init script properly 
deregistered.

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress

Bug description:
  Impact:

  When upgrading to xenial from earlier releases, some files are left on
  the user's system. They are not used, but may otherwise be mistaken
  for being used by the user if they are attempting to fix a problem.

  Regression potential:

  Low to none, as the relevant files are not used, and are being removed
  when the updated version of Pulseaudio is installed. These files are
  already removed in yakkety and later.

  Test case:

  When updating from trusty to xenial, one will note the presence of the
  below listed files on the system. Updating from pulseaudio in xenial
  or pulseaudio in trusty to what is in xenial-proposed shoudl delete
  the listed files. The /etc/init.d/pulseaudio script should also be
  unregistered.

  
  Original bug report:

  The following files are marked obsolete after the upgrade to 16.04:

   /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
   /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
   /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
   /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete

  
  Those files should be cleaned up and the sysv init script properly 
deregistered.

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

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

[Touch-packages] [Bug 1592817] Re: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0, 0000'

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gdebi (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  gdebi-gtk crashed with ValueError in update_interface(): could not
  convert string to float: '0,'

Status in apt package in Ubuntu:
  Fix Released
Status in gdebi package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in gdebi source package in Xenial:
  Confirmed

Bug description:
  Errors Bucket
  -
  https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53
  and
  https://errors.ubuntu.com/problem/c349b36522b1d43e2604357f75f0215fdafe1c7a

  Gdebi crashed while installing Google Chrome .deb-fil bur the error
  didn't appear until I logged out and back in again

  ProblemType: CrashDistroRelease: Ubuntu 16.10
  Package: gdebi 0.9.5.7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 15 15:01:11 2016
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2016-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive 
/media/jimmy/Seagate\ Backup\ Plus\ 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb
  ProcEnviron:
   PATH=(custom, no user)
   LANG=da_DK.UTF-8
   LANGUAGE=da
   SHELL=/bin/bash
   TERM=unknown
  PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate 
Backup Plus 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb']SourcePackage: 
gdebi
  Title: gdebi-gtk crashed with ValueError in update_interface(): could not 
convert string to float: '0,'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 966568] Re: upowerd is consuming 100% of CPU

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: upower (Ubuntu)
   Status: New => Confirmed

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

Title:
  upowerd is consuming 100% of CPU

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  It may have started when I plugged in an iPad 2.

  Backtrace from gdb:

  (gdb) bt
  #0  0x7ffa83c3467c in __libc_send (fd=, buf=, n=, flags=) at 
../sysdeps/unix/sysv/linux/x86_64/send.c:33
  #1  0x7ffa816a3d2b in usbmuxd_send (sfd=, data=, len=37, sent_bytes=0x7fffd341761c) at 
/build/buildd/usbmuxd-1.0.7/libusbmuxd/libusbmuxd.c:853
  #2  0x7ffa830b013d in internal_connection_send (connection=, data=, len=, sent_bytes=) at 
idevice.c:274
  #3  0x7ffa830b021a in internal_ssl_write (transport=0x2250d60, 
buffer=0x22721f0 "\027\003", length=37) at idevice.c:508
  #4  0x7ffa81ad1508 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.26
  #5  0x7ffa81acd9d9 in _gnutls_send_int () from 
/usr/lib/x86_64-linux-gnu/libgnutls.so.26
  #6  0x7ffa830b066e in idevice_connection_send (connection=, data=, len=4, sent_bytes=0x7fffd341781c) at idevice.c:305
  #7  0x7ffa830b1f65 in internal_plist_send (client=0x224c7e0, 
plist=0x225d380, binary=) at property_list_service.c:143
  #8  0x7ffa830b2e46 in lockdownd_send (client=, 
plist=) at lockdown.c:288
  #9  0x7ffa830b2f01 in lockdownd_stop_session (client=0x2253190, 
session_id=0x225b930 "39F72847-12C5-459B-874B-83345EEDBC17") at lockdown.c:161
  #10 0x7ffa830b39cc in lockdownd_client_free (client=0x2253190) at 
lockdown.c:201
  #11 0x004127a5 in ?? ()
  #12 0x00412864 in ?? ()
  #13 0x7ffa8330c23b in g_timeout_dispatch (source=, 
callback=, user_data=) at 
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3907
  #14 0x7ffa8330aa5d in g_main_dispatch (context=0x221ff30) at 
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:2441
  #15 g_main_context_dispatch (context=0x221ff30) at 
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3011
  #16 0x7ffa8330b258 in g_main_context_iterate (context=0x221ff30, 
block=, dispatch=1, self=) at 
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3089
  #17 0x7ffa8330b792 in g_main_loop_run (loop=0x223d500) at 
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3297
  #18 0x00406a2b in ?? ()
  #19 0x7ffa82b2230d in __libc_start_main (main=0x406730, argc=1, 
ubp_av=0x7fffd3417c68, init=, fini=, 
rtld_fini=, stack_end=0x7fffd3417c58) at libc-start.c:226
  #20 0x00406b71 in ?? ()
  #21 0x7fffd3417c58 in ?? ()
  #22 0x001c in ?? ()
  #23 0x0001 in ?? ()
  #24 0x7fffd3418f46 in ?? ()
  #25 0x in ?? ()

  strace:

  write(2, "usbmuxd_send: Error -1 when send"..., 49) = 49
  sendto(15, "\27\3\0\0 
:\34i\rfEA>$\322+\37\6&\313\310\316\231\204\264;-\315hU=\306"..., 37, 0, NULL, 
0) = -1 EPIPE (Broken pipe)
  --- SIGPIPE (Broken pipe) @ 0 (0) ---
  write(2, "usbmuxd_send: Error -1 when send"..., 49) = 49
  sendto(15, "\27\3\0\0 
:\34i\rfEA>$\322+\37\6&\313\310\316\231\204\264;-\315hU=\306"..., 37, 0, NULL, 
0) = -1 EPIPE (Broken pipe)
  --- SIGPIPE (Broken pipe) @ 0 (0) ---
  write(2, "usbmuxd_send: Error -1 when send"..., 49) = 49
  sendto(15, "\27\3\0\0 
:\34i\rfEA>$\322+\37\6&\313\310\316\231\204\264;-\315hU=\306"..., 37, 0, NULL, 
0) = -1 EPIPE (Broken pipe)
  --- SIGPIPE (Broken pipe) @ 0 (0) ---

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: upower 0.9.13-1
  Uname: Linux 3.3.0-rc3 x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Mar 27 13:22:24 2012
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to oneiric on 2011-09-02 (206 days ago)

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

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

[Touch-packages] [Bug 966568] Re: upowerd is consuming 100% of CPU

[Mike Myers]

This may be the same issue as
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/861642

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

Title:
  upowerd is consuming 100% of CPU

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  It may have started when I plugged in an iPad 2.

  Backtrace from gdb:

  (gdb) bt
  #0  0x7ffa83c3467c in __libc_send (fd=, buf=, n=, flags=) at 
../sysdeps/unix/sysv/linux/x86_64/send.c:33
  #1  0x7ffa816a3d2b in usbmuxd_send (sfd=, data=, len=37, sent_bytes=0x7fffd341761c) at 
/build/buildd/usbmuxd-1.0.7/libusbmuxd/libusbmuxd.c:853
  #2  0x7ffa830b013d in internal_connection_send (connection=, data=, len=, sent_bytes=) at 
idevice.c:274
  #3  0x7ffa830b021a in internal_ssl_write (transport=0x2250d60, 
buffer=0x22721f0 "\027\003", length=37) at idevice.c:508
  #4  0x7ffa81ad1508 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.26
  #5  0x7ffa81acd9d9 in _gnutls_send_int () from 
/usr/lib/x86_64-linux-gnu/libgnutls.so.26
  #6  0x7ffa830b066e in idevice_connection_send (connection=, data=, len=4, sent_bytes=0x7fffd341781c) at idevice.c:305
  #7  0x7ffa830b1f65 in internal_plist_send (client=0x224c7e0, 
plist=0x225d380, binary=) at property_list_service.c:143
  #8  0x7ffa830b2e46 in lockdownd_send (client=, 
plist=) at lockdown.c:288
  #9  0x7ffa830b2f01 in lockdownd_stop_session (client=0x2253190, 
session_id=0x225b930 "39F72847-12C5-459B-874B-83345EEDBC17") at lockdown.c:161
  #10 0x7ffa830b39cc in lockdownd_client_free (client=0x2253190) at 
lockdown.c:201
  #11 0x004127a5 in ?? ()
  #12 0x00412864 in ?? ()
  #13 0x7ffa8330c23b in g_timeout_dispatch (source=, 
callback=, user_data=) at 
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3907
  #14 0x7ffa8330aa5d in g_main_dispatch (context=0x221ff30) at 
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:2441
  #15 g_main_context_dispatch (context=0x221ff30) at 
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3011
  #16 0x7ffa8330b258 in g_main_context_iterate (context=0x221ff30, 
block=, dispatch=1, self=) at 
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3089
  #17 0x7ffa8330b792 in g_main_loop_run (loop=0x223d500) at 
/build/buildd/glib2.0-2.30.0/./glib/gmain.c:3297
  #18 0x00406a2b in ?? ()
  #19 0x7ffa82b2230d in __libc_start_main (main=0x406730, argc=1, 
ubp_av=0x7fffd3417c68, init=, fini=, 
rtld_fini=, stack_end=0x7fffd3417c58) at libc-start.c:226
  #20 0x00406b71 in ?? ()
  #21 0x7fffd3417c58 in ?? ()
  #22 0x001c in ?? ()
  #23 0x0001 in ?? ()
  #24 0x7fffd3418f46 in ?? ()
  #25 0x in ?? ()

  strace:

  write(2, "usbmuxd_send: Error -1 when send"..., 49) = 49
  sendto(15, "\27\3\0\0 
:\34i\rfEA>$\322+\37\6&\313\310\316\231\204\264;-\315hU=\306"..., 37, 0, NULL, 
0) = -1 EPIPE (Broken pipe)
  --- SIGPIPE (Broken pipe) @ 0 (0) ---
  write(2, "usbmuxd_send: Error -1 when send"..., 49) = 49
  sendto(15, "\27\3\0\0 
:\34i\rfEA>$\322+\37\6&\313\310\316\231\204\264;-\315hU=\306"..., 37, 0, NULL, 
0) = -1 EPIPE (Broken pipe)
  --- SIGPIPE (Broken pipe) @ 0 (0) ---
  write(2, "usbmuxd_send: Error -1 when send"..., 49) = 49
  sendto(15, "\27\3\0\0 
:\34i\rfEA>$\322+\37\6&\313\310\316\231\204\264;-\315hU=\306"..., 37, 0, NULL, 
0) = -1 EPIPE (Broken pipe)
  --- SIGPIPE (Broken pipe) @ 0 (0) ---

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: upower 0.9.13-1
  Uname: Linux 3.3.0-rc3 x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Mar 27 13:22:24 2012
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to oneiric on 2011-09-02 (206 days ago)

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

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

[Touch-packages] [Bug 1592817] Re: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0, 0000'

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apt (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  gdebi-gtk crashed with ValueError in update_interface(): could not
  convert string to float: '0,'

Status in apt package in Ubuntu:
  Fix Released
Status in gdebi package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in gdebi source package in Xenial:
  Confirmed

Bug description:
  Errors Bucket
  -
  https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53
  and
  https://errors.ubuntu.com/problem/c349b36522b1d43e2604357f75f0215fdafe1c7a

  Gdebi crashed while installing Google Chrome .deb-fil bur the error
  didn't appear until I logged out and back in again

  ProblemType: CrashDistroRelease: Ubuntu 16.10
  Package: gdebi 0.9.5.7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 15 15:01:11 2016
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2016-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive 
/media/jimmy/Seagate\ Backup\ Plus\ 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb
  ProcEnviron:
   PATH=(custom, no user)
   LANG=da_DK.UTF-8
   LANGUAGE=da
   SHELL=/bin/bash
   TERM=unknown
  PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate 
Backup Plus 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb']SourcePackage: 
gdebi
  Title: gdebi-gtk crashed with ValueError in update_interface(): could not 
convert string to float: '0,'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1638268] Re: certbot-auto claims parse error in apache config, but doesn't tell me which line

[Michael Shuler]

** Package changed: ca-certificates (Ubuntu) => python-certbot (Ubuntu)

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

Title:
  certbot-auto claims parse error in apache config, but doesn't tell me
  which line

Status in python-certbot package in Ubuntu:
  New

Bug description:
  Saving debug log to /var/log/letsencrypt/letsencrypt.log

  ...

  The error was: PluginError(('There has been an error in parsing the
  file (%s): %s', u'/etc/apache2/sites-available/mycrazydomainname.com',
  u'Syntax error'),)

  
  Ok, well, it would be super-helpful to know which line had the syntax error, 
that's a file with hundreds of lines modrewrite rules, tls protocol specifier 
lines, comments... What doesn't it like?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1638268/+subscriptions

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

[Touch-packages] [Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks

[guillaume ramelet]

I confirm the same with yakkey on DELL XPS 13 developer edition (2015)

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename:   yakkety


LANG=C apt-cache policy network-manager
network-manager:
  Installed: 1.2.4-0ubuntu1
  Candidate: 1.2.4-0ubuntu1
  Version table:
 *** 1.2.4-0ubuntu1 500
500 http://fr.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status


as a temporary work around I put a script here:

/etc/pm/sleep.d/99_restart_network_manager

That contains:

#! /bin/sh

case $1 in
 suspend|suspend_hybrid|hibernate)
service network-manager restart
;;
 resume|thaw)
# No need to do anything here
:
;;
esac

As said before, it works only once after a suspend.

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

Title:
  network-manager after suspend showing arrow icon instead of wifi icon
  and showing no wifi networks

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401
  I'm creating my own bug report.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy network-manager
  network-manager:
Installiert:   1.2.2-0ubuntu0.16.04.3
Installationskandidat: 1.2.2-0ubuntu0.16.04.3
Versionstabelle:
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What you expected to happen
  I'm connected by WiFi only, not by a wired connection. I expect to see the 
WiFi icon anytime while being connected to my WiFi network. Also, I expect to 
see all the WiFi networks around me (at least one other network with good 
reception and about 3 with bad reception).

  4) What happened instead
  After waking up the laptop from suspend, there appears the ethernet icon 
(arrow symbols) instead of the WiFi icon.
  Also, in this state there are no other WiFi networks visible in the 
network-manager.
  However, the laptop is still connected with my WiFi and the connection works 
as usual.
  Using "service network-manager restart" in the console I can get the wireless 
icon back and all the other networks around me are visible again.
  This can be reproduced anytime and with 100% "success rate". The problem 
appeared with Ubuntu 16.10 and was persistent since.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 24 20:06:09 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-15 (161 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlo1  proto static  metric 600 
   169.254.0.0/16 dev wlo1  scope link  metric 1000 
   192.168.1.0/24 dev wlo1  proto kernel  scope link  src 192.168.1.244  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlo1wifi  connected/org/freedesktop/NetworkManager/Devices/2  
WiNet 2 162de978-4466-46b0-957b-5f9c141d702a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manag

[Touch-packages] [Bug 1573296] Re: obsolete conffiles not cleaned up on upgrade

[Luke Yelavich]

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

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

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: pulseaudio (Ubuntu Xenial)
 Assignee: (unassigned) => Luke Yelavich (themuso)

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress

Bug description:
  The following files are marked obsolete after the upgrade to 16.04:

   /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
   /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
   /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
   /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete

  
  Those files should be cleaned up and the sysv init script properly 
deregistered.

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

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

[Touch-packages] [Bug 1613001] Re: mouse cursor flashing after adding third monitor through usb 3.0 displaylink monitor

[Christopher M. Penalver]

Michał Skrzypczak, it will help immensely if you filed a new report with Ubuntu 
by ensuring you have the package xdiagnose installed, and that you click the 
Yes button for attaching additional debugging information running the following 
from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  mouse cursor flashing after adding third monitor through usb 3.0
  displaylink monitor

Status in xorg package in Ubuntu:
  Expired

Bug description:
  
  Ubuntu 16.04 LTS, i7-3630QM, Intel HD Graphics 4000

  LVDS1 primary is Samsung NP350 laptop monitor
  HDMI1 is HDMI monitor
  DVI-I-1 is through USB 3.0 displaylink to HDMI/DVI/Eth adapter, 
idVendor=17e9, idProduct=4307, monitor connected via HDMI

  Mouse cursor constantly flashing on HDMI1 (sometimes clicking at empty
  area stops flashing, but mouse/keyboard action in a field with
  editable cursor like a web form triggers flashing), occasionally on
  LVDS1 but never on DVI-I-1

  
  $ xrandr
  Screen 0: minimum 8 x 8, current 5440 x 1080, maximum 32767 x 32767
  LVDS1 connected primary 1600x900+3840+0 (normal left inverted right x axis y 
axis) 380mm x 210mm
 1600x900  60.06*+
 1440x900  59.89  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 800x450   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  HDMI1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
600mm x 340mm
 1920x1080 60.00*+  50.0059.94  
 1920x1080i60.0050.0059.94  
 1680x1050 59.88  
 1280x1024 75.0260.02  
 1440x900  59.90  
 1280x960  60.00  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1440x576  50.00  
 1024x768  75.0870.0760.00  
 1440x480  60.0059.94  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0066.6760.0059.94  
 720x400   70.08  
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 connected 1920x1080+0+0 598mm x 336mm
 1920x1080 60.00*+  50.0059.94  
 1680x1050 59.88  
 1600x900  60.00  
 1280x1024 75.0260.02  
 1280x960  60.00  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 1024x576  59.97  
 832x624   74.55  
 800x600   75.0060.3256.25  
 720x576   50.00  
 848x480   60.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
1920x1080 (0xf7) 148.500MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.50KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  60.00Hz
1920x1080 (0xf8) 148.500MHz +HSync +VSync
  h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
56.25KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  50.00Hz
1920x1080 (0xf9) 148.352MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.43KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  59.94Hz
1680x1050 (0xfd) 119.000MHz +HSync -VSync
  h: width  1680 start 1728 end 1760 total 1840 skew0 clock  
64.67KHz
  v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz
1280x1024 (0xfe) 135.000MHz +HSync +VSync
  h: width  1280 start 1296 end 1440 total 1688 skew0 clock  
79.98KHz
  v: height 1024 start 1025 end 1028 total 1066   clock  75.02Hz
1280x1024 (0xff) 108.000MHz +HSync +VSync
  h: width  1280 start 1328 end 1440 total 1688 skew0 clock  
63.98KHz
  v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz
1280x960 (0x100) 108.000MHz +HSync +VSync
  h: width  1280 start 1376 end 1488 total 1800 skew0 clock  
60.00KHz
  v: height  960 start  961 end  964 total 1000   clock  60.00Hz
1152x864 (0x101) 108.000MHz +HSync +VSync
  h: width  1152 start 1216 end 1344 total 1600 skew0 clock  
67.50KHz
  v: height  864 start  865 end  868 total  900

[Touch-packages] [Bug 1636827] Re: wireless network list disappears

[Christopher M. Penalver]

Juraj, for you personally (not someone else), was there a version of
Ubuntu later than 14.04, but earlier than 16.04 where this didn't occur?

** Tags added: regression-release

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

Title:
  wireless network list disappears

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  On Thinkpad W520, wireless network list disappears occasionally.
  Restarting the network manager service fixes the issue. Please see the
  following bug for more information:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590985

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 26 13:57:59 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-12 (105 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp0s25  ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  
LARICS  3ad4f968-8fd1-4759-a3bc-746cb364628e  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   wlp3s0   wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
FERwlan 3f100dda-2c1b-46d6-83af-064c33b51c5a  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636827/+subscriptions

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

[Touch-packages] [Bug 1637823] Re: keyboard input is not processed in the right order during high CPU load times

[Adolfo Jayme]

I’ve been bit too many times by this :-)

** Changed in: ibus (Ubuntu)
   Status: New => Confirmed

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  keyboard input is not processed in the right order during high CPU
  load times

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  I have noticed several issues with keyboard input processing, that can
  all seemingly be tied to high CPU usage.

  For context, I am using a french keyboard, and also need to type
  Japanese, which has me using IBus and Anthy.

  I think at some point in Ubuntu, the way input was handled changed 
drastically, and ever since I have been dealing with the following issues :
  - Composite keys such as ^ (^ + e => ê) used in French for accents are 
processed in a weird way :
  Suppose I type "Le verbe être est",
  I sometimes end up with "Le verbe treê est" actually appearing when typing 
under high CPU load. (Hinting at the fact that the ^ key stroke processing 
happens asynchronously, and without accounting for the proper and expected 
order of strokes, which is extremely annoying)

  (I mainly see this specific problem in applications such as Chrome,
  Skype for Linux Alpha, Discord, Slack.)

  Before I found a suggestion to set IBUS_ENABLE_SYNC_MODE=1 in my
  session environment, keyboard input order would end up completely
  shuffled. Enforcing sync mode nearly fixed everything except for
  composite keys.

  - When switching between French and Japanese, I have defined a specific 
shortcut to do the switching for me, and I am used to the switching taking 
time. The problem is that switching does not lock any input after that, so that 
it would be processed AFTER the switch was complete.
  When typing "tesuto" I expect the following to be input : てすと
  But I get the following : teすと

  This one, I am thinking is caused by asynchronous input processing for
  the shortcut keys, and the Anthy process taking time to get called
  back from swap memory. I would be perfectly fine with the previous
  behavior, and waiting three seconds, as long as input would be
  processed all at once, in the order I typed it.


  The above two problems mean I have to actually watch at what times I
  am going to need to use accented characters, or to type Japanese, and
  WAIT for the computer to finish switching before resuming typing.

  These literally halve my typing speed because I can't rely on muscle
  memory anymore when typing any language other than English.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ibus 1.5.10-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Oct 30 20:45:04 2016
  InstallationDate: Installed on 2010-01-30 (2464 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to wily on 2016-04-16 (196 days ago)

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

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

[Touch-packages] [Bug 1600576] Re: Screen rolling/rotating horizontally when using specific applications

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Screen rolling/rotating horizontally when using specific applications

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Sometimes the following graphics glitch is triggered where the screen starts 
moving/rotating rapidly. See https://i.imgur.com/u6j5auo.gif (gedit on LXDE).
  This is triggered semi-randomly while using specific apps like Kate, gEdit, 
gVim, leafpad, embedded console inside Dolphin, KDevelop and rarely with 
Konsole.
  Also triggered for a few split-seconds when I move the mouse when in 
fullscreen mode in VLC but stabilises quickly. However, everything is stable 
when I just use Chrome or Firefox, LXTerminal, Clementine and Code::Blocks, 
even for hours.

  Whenever this is triggered, it can sometimes be fixed when I switch to 
desktop or Chrome or a different app while closing the trigger-er app while 
other times, rebooting is the only way. Sometimes (rarely) the screen becomes 
completely black after a while, with key-presses and mouse movements revealing 
the screen for split-seconds which allows me to properly shutdown/restart the 
laptop.
  I've tried to Google the problem with no results, I'm not even sure what to 
search for.

  And I apologize if this isn't the correct place to report. I've
  already tried a couple of places with no replies or help whatsoever.

  Some system details:
  OS: Lubuntu 16.04
  Kernel (uname -r): 4.4.0-28-generic
  Laptop: Lenovo G50-80 with Intel 5500 Integrated graphics chip (Broadwell-U 
Integrated Graphics, inside Core i3-5005U)

  Relevant lspci block:

  00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated 
Graphics (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Lenovo Broadwell-U Integrated Graphics
  Flags: bus master, fast devsel, latency 0, IRQ 48
  Memory at c000 (64-bit, non-prefetchable) [size=16M]
  Memory at b000 (64-bit, prefetchable) [size=256M]
  I/O ports at 4000 [size=64]
  Expansion ROM at  [disabled]
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [d0] Power Management version 2
  Capabilities: [a4] PCI Advanced Features
  Kernel driver in use: i915
  Kernel modules: i915
  Resolution from xrandr --verbose:

  1366x768 (0x47) 72.330MHz -HSync -VSync *current +preferred
  h: width  1366 start 1414 end 1446 total 1526 skew0 clock  
47.40KHz
  v: height  768 start  770 end  775 total  790   clock  60.00Hz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-intel (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Jul 10 15:06:25 2016
  InstallationDate: Installed on 2016-05-28 (43 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-28 (98 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1609135] Re: PPC Corrupt display ATI X800 XT

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  PPC Corrupt display ATI X800 XT

Status in xorg package in Ubuntu:
  Expired

Bug description:
  System: PowerMac 7,2
  Video card: ATI X800 XT
  Display: 1440x900

  With this video card the display is corrupted on approximately 9 out of 10 
attempts to boot. On one boot out of 10 it works. When the display shows 
corruption it is in the form of a distorted checkerboard. The machine 
apparently locks up as the fans eventually come fully on.
  The appended parameters on yaboot are:
  radeon.agpmode=-1 video=offb:off video=radeonfb:off radeon.modeset=1

  This is the same system as in bug #1605413 except I changed out the
  video card.

  This card also does not work when trying to boot Ubuntu-mate 16.10
  Alpha 1

  What I expected to happen:
  The system boots to a normal desktop.

  What happened instead:
  Rarely do I get to a desktop. Usually the display is corrupted and the system 
locks up.

  Ubuntu Mate 16.04
  lsb_release -rd:

  Description: Ubuntu 16.04.1 LTS
  Release: 16.04

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

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

[Touch-packages] [Bug 1615420] Re: Regression: Low screen brightness after standby

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Regression: Low screen brightness after standby

Status in xorg package in Ubuntu:
  Expired

Bug description:
  After updating to Ubuntu 16.04 from 14.04, on my Lenovo T420s, the
  screen is very dim after resuming from standby. Changing the
  brightness by settings or fn keys restores the correct state.

  This is very annoying because it is a repeating regression that
  happens again and again over the last years. Almost every distribution
  upgrade breaks the brightness after standby and took some month or
  even years to have it working correct again.

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

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

[Touch-packages] [Bug 1617338] Re: this cauese my display to freeze and shake every 3seconds or so

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  this cauese my display to freeze and shake every 3seconds or so

Status in xorg package in Ubuntu:
  Expired

Bug description:
  My display is freezing or shaking for a period of every 3 seconds or
  so. I have reinstalled Ubuntu freshly thrice but the same problem
  remains.

  HP 15-d030nr Notebook PC

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Aug 26 19:33:59 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0a) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:2190]
  InstallationDate: Installed on 2016-08-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 001 Device 005: ID 0cf3:3121 Atheros Communications, Inc.
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-93-generic.efi.signed 
root=UUID=e84fe7e4-02c1-4141-a02c-751b41fbb2e2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2190
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 40.17
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd11/29/2013:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn2190:rvr40.17:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097610405F1610180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Aug 26 19:08:38 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8428
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1638666] Re: package libffi6:i386 3.1~rc1+r3.0.13-12ubuntu0.1 failed to install/upgrade: package libffi6:i386 is already installed and configured

[dino99]

*** This bug is a duplicate of bug 1635280 ***
https://bugs.launchpad.net/bugs/1635280

** This bug has been marked a duplicate of bug 1635280
   [ BUG 541595 IS BACK ] package is already installed and configured

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

Title:
  package libffi6:i386 3.1~rc1+r3.0.13-12ubuntu0.1 failed to
  install/upgrade: package libffi6:i386 is already installed and
  configured

Status in libffi package in Ubuntu:
  New

Bug description:
  no worries

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libffi6:i386 3.1~rc1+r3.0.13-12ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  CrashReports:
   600:0:116:283416:2016-11-02 10:59:41.186816692 -0700:2016-11-02 
10:59:42.186816692 -0700:/var/crash/libexpat1:i386.0.crash
   600:0:116:283424:2016-11-02 10:59:41.214816570 -0700:2016-11-02 
10:59:42.214816570 -0700:/var/crash/libffi6:i386.0.crash
  Date: Wed Nov  2 10:59:42 2016
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.9
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.9
  DuplicateSignature: package:libffi6:i386:3.1~rc1+r3.0.13-12ubuntu0.1:package 
libffi6:i386 is already installed and configured
  ErrorMessage: package libffi6:i386 is already installed and configured
  InstallationDate: Installed on 2016-11-02 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: libffi
  Title: package libffi6:i386 3.1~rc1+r3.0.13-12ubuntu0.1 failed to 
install/upgrade: package libffi6:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1638170] Re: Grey cursor in password field is nearly invisible (very thin and low contrast)

[Adolfo Jayme]

** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)

** Project changed: lightdm => unity (Ubuntu)

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

Title:
  Grey cursor in password field is nearly invisible (very thin and low
  contrast)

Status in unity package in Ubuntu:
  New
Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Grey cursor in password field is nearly invisible (very thin and low
  contrast). It also looks inconsistent being much thinner than the text
  "Password".

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

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

[Touch-packages] [Bug 1638767] [NEW] Switching session to Unity8 on login screen is not obviously discoverable

[Daniel van Vugt]

Public bug reported:

Switching session to Unity8 on login screen is not obviously
discoverable.

This might explain why so many users are still asking "where's Unity8?"
even though they're using yakkety. It's just not obvious on the login
screen that the Ubuntu icon is also a button where you change desktop
environments.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: lightdm
 Importance: Undecided
 Status: Incomplete

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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


** Tags: unity8-desktop

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Summary changed:

- Switching session to Unity8 on login screen is not easily discoverable
+ Switching session to Unity8 on login screen is not obviously discoverable

** Description changed:

- Switching session to Unity8 on login screen is not easily discoverable.
+ Switching session to Unity8 on login screen is not obviously
+ discoverable.
  
  This might explain why so many users are still asking "where's Unity8?"
  even though they're using yakkety. It's just not obvious on the login
  screen that the Ubuntu icon is also a button where you change desktop
  environments.

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

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

Title:
  Switching session to Unity8 on login screen is not obviously
  discoverable

Status in Canonical System Image:
  New
Status in Light Display Manager:
  Incomplete
Status in Ubuntu UX:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Switching session to Unity8 on login screen is not obviously
  discoverable.

  This might explain why so many users are still asking "where's
  Unity8?" even though they're using yakkety. It's just not obvious on
  the login screen that the Ubuntu icon is also a button where you
  change desktop environments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1638767/+subscriptions

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

[Touch-packages] [Bug 1638765] [NEW] [PatriotBTSpeaker, playback] make default output

[tony alba]

Public bug reported:

Need to setup blue-tooth speaker every time I reboot. Is there a way to
make it default?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tony   1706 F pulseaudio
CurrentDesktop: Unity
Date: Wed Nov  2 20:50:39 2016
InstallationDate: Installed on 2016-10-14 (19 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: PatriotBTSpeaker
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tony   1706 F pulseaudio
Symptom_Type: No sound at all
Title: [PatriotBTSpeaker, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/24/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K55A.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K55A
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.:bvrK55A.305:bd05/24/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K55A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  [PatriotBTSpeaker, playback] make default output

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Need to setup blue-tooth speaker every time I reboot. Is there a way
  to make it default?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   1706 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov  2 20:50:39 2016
  InstallationDate: Installed on 2016-10-14 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: PatriotBTSpeaker
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   1706 F pulseaudio
  Symptom_Type: No sound at all
  Title: [PatriotBTSpeaker, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  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.:bvrK55A.305:bd05/24/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K55A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1612012] Re: Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

[Daniel van Vugt]

Indeed the cause is again valgrind errors in NestedServer tests. But
should we be reusing the same bug? Just search for "==12777==":

20:13:30 9: [--] 25 tests from NestedServer
20:13:30 9: [ RUN ] NestedServer.nested_platform_connects_and_disconnects
20:13:31 9: [2016-11-02 20:13:31.685261] mirserver: Starting
20:13:31 9: [2016-11-02 20:13:31.689667] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
20:13:31 9: [2016-11-02 20:13:31.733003] mirserver: Using software cursor
20:13:32 9: [2016-11-02 20:13:32.118804] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
20:13:32 9: [2016-11-02 20:13:32.128108] mirserver: Mir version 0.25.0
20:13:32 9: [2016-11-02 20:13:32.211391] mirserver: Starting
20:13:34 9: [2016-11-02 20:13:34.070068] mirserver: Using nested cursor
20:13:34 9: ==12777== Thread 9:
20:13:34 9: ==12777== Invalid read of size 4
20:13:34 9: ==12777== at 0x540688F: 
MirWaitHandle::wait_for_all()::$_0::operator()() const (mir_wait_handle.cpp:53)
20:13:34 9: ==12777== by 0x5406401: void 
std::condition_variable::wait(std::unique_lock&,
 MirWaitHandle::wait_for_all()::$_0) (condition_variable:98)
20:13:34 9: ==12777== by 0x5406376: MirWaitHandle::wait_for_all() 
(mir_wait_handle.cpp:53)
20:13:34 9: ==12777== by 0x54774D9: mir_connection_create_buffer_stream_sync 
(mir_buffer_stream_api.cpp:76)
20:13:34 9: ==12777== by 0x517576D: (anonymous 
namespace)::MirClientHostSurface::set_cursor_image(mir::graphics::CursorImage 
const&) (mir_client_host_connection.cpp:168)
20:13:34 9: ==12777== by 0x5175D95: 
mir::graphics::nested::MirClientHostConnection::set_cursor_image(mir::graphics::CursorImage
 const&) (mir_client_host_connection.cpp:430)


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

Title:
  Valgrind errors in NesterServer.* cause subsequent tests
  (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

Status in Mir:
  Confirmed
Status in Mir 0.24 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Tests always fail together: ServerDisconnect, ServerStartup,
  UnresponsiveClient

  17:27:52 9: [ FAILED ] 5 tests, listed below:
  17:27:52 9: [ FAILED ] ServerDisconnect.is_detected_by_client
  17:27:52 9: [ FAILED ] 
ServerDisconnect.doesnt_stop_client_calling_API_functions
  17:27:52 9: [ FAILED ] ServerStartup.creates_endpoint_on_filesystem
  17:27:52 9: [ FAILED ] 
ServerStartup.after_server_sigkilled_can_start_new_instance
  17:27:52 9: [ FAILED ] UnresponsiveClient.does_not_hang_server

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1772/consoleFull]

  This is happening regularly in CI. These failures occur together.

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

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

[Touch-packages] [Bug 1619183] Re: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instan

[Alberto Salvia Novella]

** Changed in: qt4-x11 (Ubuntu)
   Importance: Undecided => High

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

** Changed in: hundredpapercuts
   Status: New => Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided => High

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

Title:
  package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade:
  intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que
  es distinto de otras instancias del paquetes libqtcore4:i386

Status in One Hundred Papercuts:
  Confirmed
Status in qt4-x11 package in Ubuntu:
  Confirmed

Bug description:
  Trying to install skype with i386 support, breaks.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep  1 10:47:14 2016
  ErrorMessage: intentando sobreescribir el compartido 
`/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes 
libqtcore4:i386
  InstallationDate: Installed on 2016-07-06 (57 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: 
intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es 
distinto de otras instancias del paquetes libqtcore4:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1428490] Re: AppArmor vs unix socket inside LXC containers

[Toby Corkindale]

Hi,
It's been 18 months since I reported this bug.
Sorry for the slow response to your question, but it did come about a year 
after I raised the issue.

This was detected on Ubuntu Server 14.04 LTS.
I am no longer able to tell you which kernel was being run at the time.

I suspect it's still likely to be a problem on the 14.4 LTS, however we
moved to 16.04 LTS this year and haven't heard any more complaints from
our team. We're also mostly using Docker now rather than LXC.

So... problem probably still exists, but I guess no-one really cares any
more.

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

Title:
  AppArmor vs unix socket inside LXC containers

Status in lxc package in Ubuntu:
  New

Bug description:
  I know this seems like an odd bug, but I've spent all day chasing it
  down.

  I was seeing problems with LDAP lookups inside an LXC container, and
  strace on getent lookups was showing that attempts to read from
  /var/run/nslcd/socket were being closed as -1 (EACCESS).

  That file/UNIX socket is owned by nslcd, also running inside the LXC.

  Back on the host machine, setting the LXC config to set lxc.aa_profile
  = unconfined (and restarting the container) then allowed that socket
  to start working freely.

  This seems weird, as there's all sorts of other things using UNIX
  sockets inside containers that still function normally, but I thought
  I'd mention it, especially in case anyone hits this issue.

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

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

[Touch-packages] [Bug 1638755] [NEW] Additional Drivers, "Unknown: Unknown"

[Jason Yundt]

Public bug reported:

After Additional Drivers finishes "Searching for available drivers...",
it lists the name of my CPU as "Unknown: Unknown". Happens every time.
Screen shot attached.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: software-properties-gtk 0.96.24.7
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Nov  2 20:01:10 2016
ExecutablePath: /usr/bin/software-properties-gtk
InstallationDate: Installed on 2016-11-02 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102)
InterpreterPath: /usr/bin/python3.5
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

** Attachment added: "Screenshot from 2016-11-02 20-04-34.png"
   
https://bugs.launchpad.net/bugs/1638755/+attachment/4771467/+files/Screenshot%20from%202016-11-02%2020-04-34.png

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

Title:
  Additional Drivers, "Unknown: Unknown"

Status in software-properties package in Ubuntu:
  New

Bug description:
  After Additional Drivers finishes "Searching for available
  drivers...", it lists the name of my CPU as "Unknown: Unknown".
  Happens every time. Screen shot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov  2 20:01:10 2016
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2016-11-02 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1638755/+subscriptions

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

[Touch-packages] [Bug 1637037] Re: Printer stops mid-job; thereafter, USB mouse fails

[Scott Cowles Jacobs]

*** This bug is a duplicate of bug 1630063 ***
https://bugs.launchpad.net/bugs/1630063

I still have not been able to complete a print job without the USB
devices disconnecting.

Comment #22 of the "Duplicate bug" states:

"I was able to fix the issue by changing the IO_WATCHDOG_DELAY in ohci-
hcd.c from 250 msec to 275 msec. "

Only once has this bug manifested when I was NOT trying to print something, 
so I guess my question is: why does cups somehow generate an excessively long 
IO_WATCHDOG_DELAY
such that it always at some point in a print job trips the bug?

I know nothing about USB, or what IO_WATCHDOG_DELAY is, but I have 8 or
9 devices hooked up with USB, and (with the one exception noted above)
only the printer has tripped this bug.

What is this delay used for, and why is cups' so large so often?

(In other words: the kernel may have a bug in how it handles
IO_WATCHDOG_DELAY, but if cups did not generate a delay that tripped the
bug, there would be no issue for printing. )

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

Title:
  Printer stops mid-job; thereafter, USB mouse fails

Status in cups package in Ubuntu:
  New

Bug description:
  I am not sure, but I believe I have not printed anything since my
  install of Lubuntuy 16.10 last week.

  I printed something from LibreOffice Calc, and it got only partway, and the 
printer stopped printing.  I then noticed that the mouse (USB) had stopped 
working - I thought the batteries had co-incidentally failed, but fresh 
batteries accomplished nothing.
  I had to shut down.

  The next time, feeling that the print function of Calc was faulty, I
  exported the file as .pdf, and printed from Document Viewer (Evince).
  It got just about as far, and stopped, and the mouse failed again.

  The next time, I was printing something from Firefox, and it got most
  of the way through that, but it stopped, and the mouse failed again.

  By now, I had "installed" and activated PointerKeys, and with it, I was 
(slowly and painfully) able to have the terminal do lsusb and cut-n-paste the 
output to leafpad and save.
  Some website suggested one could "reboot" the USB system, but I apparently 
failed to understand or apply the knowledge to success (or the procedure did 
not somehow apply to my current OS).

  Rebooting sometimes (always?) does NOT fix the problem - Shutdown so far has. 
 
  When things are good, there are a lot more items in lsusb than when the mouse 
was not working.

  When the mouse did not work:

  scott@scott-ASUS-M2N68-AM-PLUS:~$ lsusb
  Bus 001 Device 006: ID 7392:7622 Edimax Technology Co., Ltd 
  Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  
  When the mouse works:

  scott@scott-ASUS-M2N68-AM-PLUS:~$ lsusb
  Bus 001 Device 006: ID 7392:7622 Edimax Technology Co., Ltd 
  Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 004: ID 0a12:1004 Cambridge Silicon Radio, Ltd 
  Bus 002 Device 003: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver
  Bus 002 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 002 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270
  Bus 002 Device 002: ID 0a05:7211 Unknown Manufacturer hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  
  Syslog shows some stuff that may show the problem happening:

  Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2798.923885] usb 2-1.4: 
new full-speed USB device number 8 using ohci-pci
  Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.064011] usb 2-1.4: 
New USB device found, idVendor=03f0, idProduct=5511
  Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.064014] usb 2-1.4: 
New USB device strings: Mfr=1, Product=2, SerialNumber=3
  Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.064016] usb 2-1.4: 
Product: Deskjet F300 series
  Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.064017] usb 2-1.4: 
Manufacturer: HP
  Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.064018] usb 2-1.4: 
SerialNumber: CN647B623804KH
  Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS root: loading HP Device 002 008
  Oct 26 16:55:33 scott-ASUS-M2N68-AM-PLUS /hp-config_usb_printer: [2039]: 
error: Failed to create /root/.hplip
  Oct 26 16:55:33 scott-ASUS-M2N68-AM-PLUS /hp-config_usb_printer: 
io/hpmud/musb.c 2183: [2039] hpmud_make_usb_uri() bus=002 dev=008
  Oct 26 16:55:33 scott-ASUS-M2N68-AM-PLUS /hp-config_usb_printer: 
io/hpmud/musb.c 2281: hpmud_make_usb_uri() 
uri=hp:/usb/Deskjet_F300_series?serial=CN647B623804KH bytes_read=49
  Oct 26 16:55:33 scott-ASUS-M2N68-AM-PLUS kernel:

Re: [Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

[Robert Orzanna]

Erio, so this is a workaround?

On Wed, Nov 2, 2016 at 11:39 AM, erio <1380...@bugs.launchpad.net>
wrote:

> Open Xenial 16.04 desktop (with Unity) , install pyqt5 using apt (sudo
> apt install python3-pyqt5). Make a program that has a menu bar, the
> shortcuts are not shown by the side and they don't work.
>
> Uninstall python3-pyqt5, apt install python3-pip. Use pip3 install
> pyqt5, pyqt5 will install and there is no menu bar integration, but now
> shortcuts work.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1380702
>
> Title:
>   No keyboards shortcuts in QT apps
>
> Status in appmenu-qt5:
>   In Progress
> Status in Canonical System Image:
>   In Progress
> Status in sni-qt:
>   New
> Status in qtbase-opensource-src package in Ubuntu:
>   In Progress
>
> Bug description:
>   In some apps built using QT4 & 5, menu shortcuts are greyed out and
>   inoperant. Only alt and FKeys-based shortcuts work. Others, notably
>   ctrl+c for copying, do not.
>
>   This is quite serious ; mail me for more details.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions
>

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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

[Touch-packages] [Bug 1638734] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1638734/+attachment/4771431/+files/ThreadStacktrace.txt

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

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in sd_event_run()

Status in systemd package in Ubuntu:
  New

Bug description:
  Error occurred immediately after boot->login sequence.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 06:19:30 2016
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2016-10-22 (11 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: ASUS All Series
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=9e17c592-c414-4070-b7b9-162980b58673 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
   ?? ()
   __libc_start_main (main=0x563c7c4aabf0, argc=1, argv=0x7ffcdbf8f658, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcdbf8f648) at ../csu/libc-start.c:291
   ?? ()
  Title: systemd-journald crashed with SIGABRT in sd_event_run()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1638734] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1638734/+attachment/4771430/+files/StacktraceSource.txt

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

Title:
  systemd-journald crashed with SIGABRT in sd_event_run()

Status in systemd package in Ubuntu:
  New

Bug description:
  Error occurred immediately after boot->login sequence.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 06:19:30 2016
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2016-10-22 (11 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: ASUS All Series
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=9e17c592-c414-4070-b7b9-162980b58673 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
   ?? ()
   __libc_start_main (main=0x563c7c4aabf0, argc=1, argv=0x7ffcdbf8f658, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcdbf8f648) at ../csu/libc-start.c:291
   ?? ()
  Title: systemd-journald crashed with SIGABRT in sd_event_run()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1638734] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1638734/+attachment/4771429/+files/Stacktrace.txt

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

Title:
  systemd-journald crashed with SIGABRT in sd_event_run()

Status in systemd package in Ubuntu:
  New

Bug description:
  Error occurred immediately after boot->login sequence.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 06:19:30 2016
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2016-10-22 (11 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: ASUS All Series
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=9e17c592-c414-4070-b7b9-162980b58673 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
   ?? ()
   __libc_start_main (main=0x563c7c4aabf0, argc=1, argv=0x7ffcdbf8f658, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcdbf8f648) at ../csu/libc-start.c:291
   ?? ()
  Title: systemd-journald crashed with SIGABRT in sd_event_run()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1638734]

[Apport retracing service]

StacktraceTop:
 sd_event_run (e=0x563c7cd401e0, timeout=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:2651
 main (argc=, argv=) at 
../src/journal/journald.c:101

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

Title:
  systemd-journald crashed with SIGABRT in sd_event_run()

Status in systemd package in Ubuntu:
  New

Bug description:
  Error occurred immediately after boot->login sequence.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 06:19:30 2016
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2016-10-22 (11 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: ASUS All Series
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=9e17c592-c414-4070-b7b9-162980b58673 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
   ?? ()
   __libc_start_main (main=0x563c7c4aabf0, argc=1, argv=0x7ffcdbf8f658, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcdbf8f648) at ../csu/libc-start.c:291
   ?? ()
  Title: systemd-journald crashed with SIGABRT in sd_event_run()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1592497] Re: Gnome Software catalog entry missing for IDLE

[AsciiWolf]

** Tags added: zesty

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

Title:
  Gnome Software catalog entry missing for IDLE

Status in python2.7 package in Ubuntu:
  New

Bug description:
  The IDLE IDE package cannot be installed using the Gnome Software
  application because it's missing the needed metadata.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1592497/+subscriptions

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

[Touch-packages] [Bug 1638734] [NEW] systemd-journald crashed with SIGABRT in sd_event_run()

[Lacyc3]

Public bug reported:

Error occurred immediately after boot->login sequence.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 231-9ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Wed Nov  2 06:19:30 2016
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2016-10-22 (11 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: ASUS All Series
ProcCmdline: /lib/systemd/systemd-journald
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=9e17c592-c414-4070-b7b9-162980b58673 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 sd_event_run () from /lib/systemd/libsystemd-shared-231.so
 ?? ()
 __libc_start_main (main=0x563c7c4aabf0, argc=1, argv=0x7ffcdbf8f658, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcdbf8f648) at ../csu/libc-start.c:291
 ?? ()
Title: systemd-journald crashed with SIGABRT in sd_event_run()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 10/27/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2702
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: amd64 apport-crash package-from-proposed yakkety

** Information type changed from Private to Public

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

Title:
  systemd-journald crashed with SIGABRT in sd_event_run()

Status in systemd package in Ubuntu:
  New

Bug description:
  Error occurred immediately after boot->login sequence.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 06:19:30 2016
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2016-10-22 (11 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: ASUS All Series
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=9e17c592-c414-4070-b7b9-162980b58673 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
   ?? ()
   __libc_start_main (main=0x563c7c4aabf0, argc=1, argv=0x7ffcdbf8f658, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcdbf8f648) at ../csu/libc-start.c:291
   ?? ()
  Title: systemd-journald crashed with SIGABRT in sd_event_run()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly

[areteichi]

I can confirm this occurs on Meizu Pro 5 with OTA-13 as well.

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+subscriptions

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

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Jeremy]

Luke
Using your PPA, manually killing pulse and restarting it doesn't make any 
changes and the only way to use A2DP is the command I put in comment 100

The bug only affects audio devices that support HSP/HFP as I have a
small bluetooth speaker that automatically uses A2DP without fail

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 1410618] Re: MacBook Air 6, 2 TRRS Headset Mic Not Working

[Fábio Ueno]

Hey... Did you guys manage to solve this?

I am facing the same challenge with Macbook Pro 5.5 and ubuntu 16.04.

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

Title:
  MacBook Air 6,2 TRRS Headset Mic Not Working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm running Ubuntu Gnome 14.04 on a new MacBookAir6,2 with the Cirrus
  Logic CS4208 and would love to get the microphone part of the TRRS
  connector working. Mac OS picks up and utilizes the TRRS headset mic
  without issue so I know the hardware is a go.

  With the headset plugged in, running sudo hdajacksensetest -a results
  in:

  Pin 0x05 ( Digital Out, HDMI): present = No
  Pin 0x06 ( Digital Out, HDMI): present = No
  Pin 0x07 ( Digital Out, HDMI): present = No

  AlsaInfo output here:
  http://www.alsa-project.org/db/?f=cabc8cab44d308c8a3898c66d48d9be4fc5ccf83

  I opened up hdajackretask to find four pins:
  Green Headphone
  Pin ID: 0x10
  Headphone

  Internal Speaker
  Pin ID: 0x12
  Internal speaker

  Pink Mic
  Pin ID: 0x18
  Not connected

  Internal Mic
  Pin ID: 0x1c
  Internal mic

  Unplugging and replugging the headset changes the Output device in
  sound settings from Headphones to Speakers so that works, but nothing
  in the input tab ever changes. It always lists two devices: Internal
  Microphone and Microphone. Both of these seem to actually be the
  internal microphone in the mac - either works without the headset
  connected at all.

  So I'm not really sure how to proceed from here, but I'd be happy to
  run whatever diagnostic tests might prove useful and/or even
  contribute code toward a fix - but I just have no idea where to start.
  Is it as simple as just finding the right pin and telling the system
  to use it as a microphone?

  Similar bug report here:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/950494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1410618/+subscriptions

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

[Touch-packages] [Bug 1638708] Re: Hardcoded paths in data/*.desktop.in need Snappy prefixing

[Charles Kerr]

** Description changed:

- Noticed and reported by mterry in https://code.launchpad.net/~mterry
- /indicator-sound/snap-root/+merge/308125:
+ Noticed and reported by mterry in several indicator patches, e.g.
+ :
  
  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  > I think it makes more sense to update the code that reads those
  > files to do the prefixing.

** Summary changed:

- Hardcoded paths in data/*.desktop.in need Snappy prefixing
+ Hardcoded paths in desktop files need to be processed need $SNAP prefixing

** Also affects: indicator-power (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-printers (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-session (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-transfer (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-network (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-messages (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-location (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-datetime (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-bluetooth (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-application (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Noticed and reported by mterry in several indicator patches, e.g.
  :
  
  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  > I think it makes more sense to update the code that reads those
  > files to do the prefixing.
+ 
+ There is also an umbrella ticket for hardcoded paths in the u8 snap:
+ 

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

Title:
  Hardcoded paths in desktop files need to be processed need $SNAP
  prefixing

Status in indicator-application package in Ubuntu:
  New
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-printers package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  New

Bug description:
  Noticed and reported by mterry in several indicator patches, e.g.
  :

  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  > I think it makes more sense to update the code that reads those
  > files to do the prefixing.

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1638708/+subscriptions

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

[Touch-packages] [Bug 1562948] Re: google-earth not working - broken package with Xenial Xerus

[Bug Watch Updater]

** Changed in: lsb (Debian)
   Status: Unknown => Fix Released

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

Title:
  google-earth not working - broken package with Xenial Xerus

Status in googleearth-package package in Ubuntu:
  Confirmed
Status in lsb package in Ubuntu:
  New
Status in lsb package in Debian:
  Fix Released

Bug description:
  With Xubuntu Xenial Xerus 16.04 LTS Beta2 googleearth-package (1.2.2)
  is still not working as reported several times before.
  This time, there is no way to install google-earth with normal administrator 
skills
  at all - as further outlined below.

  As reported for the former LTS Trusty (14.04 LTS) Bug# 1314993,
  the package is still not working and dependencies are not met:

  From Xenial Beta2:
  $ make-googleearth-package --force
  $ sudo dpkg -i googleearth_6.0.3.2197+1.2.0-1_amd64.deb
  Selecting previously unselected package googleearth.
  (Reading database ... 445462 files and directories currently installed.)
  Preparing to unpack googleearth_6.0.3.2197+1.2.0-1_amd64.deb ...
  Unpacking googleearth (6.0.3.2197+1.2.0-1) ...
  dpkg: dependency problems prevent configuration of googleearth:
   googleearth depends on lsb-core; however:
Package lsb-core is not installed.
   googleearth depends on libcurl3:i386; however:
  dpkg: error processing package googleearth (--install):
   dependency problems - leaving unconfigured
  Processing triggers for gnome-menus (3.13.3-6ubuntu3) ...
  Processing triggers for desktop-file-utils (0.22-1ubuntu4) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for shared-mime-info (1.5-2) ...
  Unknown media type in type 'all/all'
  Unknown media type in type 'all/allfiles'
  Errors were encountered while processing:
   googleearth

  As lsb-core is no longer supported by Debian (and thus Ubuntu), this 
dependency
  can not be met and thus also the directly provided Google 32 bit package is 
not installable.
  As reported since years the 64 bit package is also not installable (and 
never[?] was).

  Also the depicted way using Jessie packages 
(lsb-security_4.1+Debian13+nmu1_i386.deb,
  lsb-invalid-mta_4.1+Debian13+nmu1_all.deb and 
lsb-core_4.1+Debian13+nmu1_i386.deb)
  is no longer possible (i.e. with Beta2), as other dependency problems exist.

  This problem may be best addressed by google in providing current 
installation packages
  working on current amd64 systems or by Debian/Ubuntu by providing an 
environment
  where these dependencies are met (this was the former reason for the 
google-earth package).

  Even with 32 bit package provided by Google a stable usage is not possible 
with Werewolf (15.10),
  see e.g. Bug #1559489.
  Thus, additional care by Google may be appropriate.

  Otherwise, this very informative and educative tool is no longer accessible 
for most users
  of the Linux desktop 

  If further pieces of information are needed or something should be
  tested, I am willing to help.

  Best wishes,

  JMB

  ---
  Other pieces of information:
  lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
[current today]
  ~
  sudo dpkg -l | grep earth
  ii  googleearth-package   1.2.2   
   all  utility to automatically build a Debian package of 
Google Earth
  ~
  apt-cache policy googleearth-package
  googleearth-package:
Installed: 1.2.2
Candidate: 1.2.2
Version table:
   *** 1.2.2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://de.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
  100 /var/lib/dpkg/status
  ~~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/googleearth-package/+bug/1562948/+subscriptions

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

[Touch-packages] [Bug 1638710] Re: Hardcoded paths need Snappy prefixing

[Charles Kerr]

*** This bug is a duplicate of bug 1638708 ***
https://bugs.launchpad.net/bugs/1638708

D'oh, user error. This is the same as bug #1638708

** Also affects: indicator-printers (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-power (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: indicator-transfer (Ubuntu)

** No longer affects: indicator-printers (Ubuntu)

** No longer affects: indicator-power (Ubuntu)

** Tags removed: unity8-snap

** This bug has been marked a duplicate of bug 1638708
   Hardcoded paths in desktop files need to be processed need $SNAP prefixing

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

Title:
  Hardcoded paths need Snappy prefixing

Status in indicator-session package in Ubuntu:
  New

Bug description:
  Noticed and reported by mterry in https://code.launchpad.net/~mterry
  /indicator-transfer/snap-root/+merge/308128:

  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  >
  > I'm not sure what the best solution for those is, but presumably
  > it would lie in whichever component consumes the desktop file
  > not this package.

  As mterry points out this is probably not an issue for indicator-
  transfer to fix, this ticket is being filed so that we track the issue
  & see if there's anything that can be done locally or to reassign to
  proper owner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638710/+subscriptions

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

[Touch-packages] [Bug 1638718] [NEW] apport-gtk dialog misses function to copy values

[Karl-Philipp Richter]

Public bug reported:

It'd be really helpful if one was able to copy stacktraces from the
`apport-gtk` dialog. I guess, the function is useful for all other parts
of the report displayed in the dialog as well.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apport-gtk 2.20.3-0ubuntu8
Uname: Linux 4.8.6-040806-generic x86_64
NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
ApportLog:
 ERROR: apport (pid 27227) Wed Nov  2 01:46:06 2016: called for pid 24933, 
signal 11, core limit 0
 ERROR: apport (pid 27227) Wed Nov  2 01:46:06 2016: executable: 
/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitPluginProcess (command line 
"/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitPluginProcess 128 
/usr/lib/mozilla/plugins/flashplugin-alternative.so")
 ERROR: apport (pid 27227) Wed Nov  2 01:46:06 2016: debug: session gdbus call: 
(true,)
 
 ERROR: apport (pid 27227) Wed Nov  2 01:46:09 2016: wrote report 
/var/crash/_usr_lib_x86_64-linux-gnu_webkit2gtk-4.0_WebKitPluginProcess.1000.crash
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Nov  2 22:24:43 2016
InstallationDate: Installed on 2015-12-12 (326 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (16 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  apport-gtk dialog misses function to copy values

Status in apport package in Ubuntu:
  New

Bug description:
  It'd be really helpful if one was able to copy stacktraces from the
  `apport-gtk` dialog. I guess, the function is useful for all other
  parts of the report displayed in the dialog as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apport-gtk 2.20.3-0ubuntu8
  Uname: Linux 4.8.6-040806-generic x86_64
  NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
  ApportLog:
   ERROR: apport (pid 27227) Wed Nov  2 01:46:06 2016: called for pid 24933, 
signal 11, core limit 0
   ERROR: apport (pid 27227) Wed Nov  2 01:46:06 2016: executable: 
/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitPluginProcess (command line 
"/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitPluginProcess 128 
/usr/lib/mozilla/plugins/flashplugin-alternative.so")
   ERROR: apport (pid 27227) Wed Nov  2 01:46:06 2016: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 27227) Wed Nov  2 01:46:09 2016: wrote report 
/var/crash/_usr_lib_x86_64-linux-gnu_webkit2gtk-4.0_WebKitPluginProcess.1000.crash
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov  2 22:24:43 2016
  InstallationDate: Installed on 2015-12-12 (326 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (16 days ago)

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

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

[Touch-packages] [Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up

[patpat]

I stand corrected; 
there's a typo on my patch the correct line should look like:
+ bootp.flags = htons(0x8000);
as mentioned by jvosburgh

Unfortunately this mistake was not previously detected because 
all the net gear I've used on tests and Wireshark completely 
ignored it.


Best,
Patrick

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

Title:
  Delay during PXE Boot, IP-Config gives up

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Trusty:
  Fix Released
Status in klibc source package in Wily:
  Won't Fix
Status in klibc source package in Xenial:
  Fix Released
Status in klibc package in Debian:
  New

Bug description:
  [Impact]
  PXE booting users with live images or other minimal setups using klibc-utils.

  [Test case]
  Attempt to PXE boot using Ubuntu live images; see below for details.

  [Regression potential]
  This forces the yiaddr (client requested/current IP) to be set to 0 when 
sending DHCP messages; currently the messages are DHCPREQUEST and DHCPDISCOVER, 
which should typically only happen when there is no IP set on the device and it 
is otherwise unable to receive unicast (on account of not being configured). 
Should there be a need to send other messages which would require setting the 
yiaddr value to the current configured IP address, a naive change would break. 
The yiaddr variable would need to be adjusted to pull value from a new 
location, or initialized directly by the callers to dhcp_send() where the 
business logic would reside.

  ---

  Attempting to PXE boot both the 12.04.3 and 14.04 Live images.   PXE
  boot works normally (PXE Menu, select desired image, image begins
  loading), then the boot process hangs while IP-Config attempts to get
  an IP address:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 3 secs - giving up

  These lines appear very quickly (5 seconds has NOT elapsed), after
  about a minute, we get this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 4 secs - giving up

  Some time later, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 6 secs - giving up

  Until finally, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 9 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: eth0 guessed broadcast address 172.25.11.31
  IP-Config: eth0 complete (dhcp from 172.25.10.20):
  (snip)

  While watching the DHCP server logs, Ubuntu is either not sending a
  DHCP Discover at times, or is not replying back with a DHCPRequest
  during these sessions, presumably ignoring an response from the DHCP
  server.  From the initial booting of the system via PXE, to when
  Ubuntu finally shows the desktop, almost 12 minutes will have elapsed.

  I am seeing this same behavior on both 12.04.3 and 14.04.  After
  finding a number of similar erros via Google and no real resolution, I
  have opened this bug.

  The system experiencing this issue has multiple ethernet interfaces
  (actual HW, not a VM), some Google found solutions suggest hard coding
  DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't
  acceptable as a system attempting to PXE boot may be using an
  alternate port for the network.

  I have found what looks to be a very similar bug filed for Debian,
  #584583, which also contains a patch for this issue (under Debian).

  I have no problems in PXE booting to various Windows, RedHat, Centos,
  or Fedora OSs.  Ubuntu is the only Live OS that I'm attempting to boot
  at present.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Fri Jun  6 20:22:09 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStat

[Touch-packages] [Bug 1612012] Re: Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

[Cemil Azizoglu]

Just had this happen again :

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2727/consoleFull

** Changed in: mir
   Status: Fix Committed => 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/1612012

Title:
  Valgrind errors in NesterServer.* cause subsequent tests
  (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

Status in Mir:
  Confirmed
Status in Mir 0.24 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Tests always fail together: ServerDisconnect, ServerStartup,
  UnresponsiveClient

  17:27:52 9: [ FAILED ] 5 tests, listed below:
  17:27:52 9: [ FAILED ] ServerDisconnect.is_detected_by_client
  17:27:52 9: [ FAILED ] 
ServerDisconnect.doesnt_stop_client_calling_API_functions
  17:27:52 9: [ FAILED ] ServerStartup.creates_endpoint_on_filesystem
  17:27:52 9: [ FAILED ] 
ServerStartup.after_server_sigkilled_can_start_new_instance
  17:27:52 9: [ FAILED ] UnresponsiveClient.does_not_hang_server

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1772/consoleFull]

  This is happening regularly in CI. These failures occur together.

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

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

[Touch-packages] [Bug 1638398] Re: Theme assets (checkboxes, troughs, etc.) are blurry in hidpi

[Cassidy James Blaede]

Attached is a full-res screenshot on a 4k pixel doubled display.

** Tags added: hidpi

** Attachment added: "widget-factory.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1638398/+attachment/4771379/+files/widget-factory.png

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

Title:
  Theme assets (checkboxes, troughs, etc.) are blurry in hidpi

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Ambiance appears to provide lodpi raster assets, which means all of
  these bits of the theme are not rendered crisply on hidpi displays. It
  would be best to redraw these assets with GtkCSS to enable crisp
  interface scaling, or at least find a way to provide vector or 2x
  assets.

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

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

[Touch-packages] [Bug 1576536] Re: timer messages unnecessarily sent to /dev/kmsg

[Pheeble]

Also, it appears that this bug is present in Debian:
https://lists.debian.org/deity/2016/04/msg00047.html

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

Title:
  timer messages unnecessarily sent to /dev/kmsg

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The random adjustments to the apt timer seem to spam the kernel
  ringbuffer, which is entirely unnecessary:

  [ 5452.648222] systemd[1]: apt-daily.timer: Adding 10h 42min 21.562799s 
random time.
  [ 5454.038740] systemd[1]: apt-daily.timer: Adding 7h 11min 7.994692s random 
time.
  [ 5457.381779] systemd[1]: apt-daily.timer: Adding 10h 43min 34.008994s 
random time.
  [ 5457.495120] systemd[1]: apt-daily.timer: Adding 7h 9min 28.335411s random 
time.
  [ 5457.743417] systemd[1]: apt-daily.timer: Adding 7h 5min 47.291509s random 
time.
  [ 5778.374365] systemd[1]: apt-daily.timer: Adding 8h 26min 267.164ms random 
time.
  [ 5778.495711] systemd[1]: apt-daily.timer: Adding 9h 52min 9.289682s random 
time.
  [ 5778.667351] systemd[1]: apt-daily.timer: Adding 8h 39min 41.199389s random 
time.
  [ 5778.924784] systemd[1]: apt-daily.timer: Adding 2h 38min 40.786228s random 
time.
  [ 5779.035421] systemd[1]: apt-daily.timer: Adding 10h 48min 34.808379s 
random time.
  [ 5779.107951] systemd[1]: apt-daily.timer: Adding 6h 19min 45.904476s random 
time.
  [ 7236.115354] systemd[1]: apt-daily.timer: Adding 5h 12min 18.073639s random 
time.
  [ 7268.716558] systemd[1]: apt-daily.timer: Adding 7h 19min 40.411960s random 
time.
  [ 7269.151388] systemd[1]: apt-daily.timer: Adding 8h 21min 54.857412s random 
time.
  [ 7270.702642] systemd[1]: apt-daily.timer: Adding 8h 33min 10.633964s random 
time.
  [ 7281.835523] systemd[1]: apt-daily.timer: Adding 11h 43min 43.923801s 
random time.
  [ 7339.639840] systemd[1]: apt-daily.timer: Adding 9h 8.911515s random time.
  [ 7340.512389] systemd[1]: apt-daily.timer: Adding 1h 45min 25.722497s random 
time.
  [ 7343.611383] systemd[1]: apt-daily.timer: Adding 22min 8.489125s random 
time.
  [ 7344.186645] systemd[1]: apt-daily.timer: Adding 10h 6min 50.541602s random 
time.
  [ 7346.111888] systemd[1]: apt-daily.timer: Adding 11h 47min 57.661764s 
random time.
  [ 7350.893164] systemd[1]: apt-daily.timer: Adding 3h 10min 23.393765s random 
time.
  [ 7355.747731] systemd[1]: apt-daily.timer: Adding 1h 2min 54.946554s random 
time.
  [ 7355.825972] systemd[1]: apt-daily.timer: Adding 4h 40min 28.148047s random 
time.
  [ 7529.692671] systemd[1]: apt-daily.timer: Adding 10h 20min 39.786553s 
random time.
  [ 7539.109562] systemd[1]: apt-daily.timer: Adding 7h 45min 54.766189s random 
time.
  [ 7539.187368] systemd[1]: apt-daily.timer: Adding 2h 20min 28.098533s random 
time.
  [ 7539.617356] systemd[1]: apt-daily.timer: Adding 10h 36min 4.411352s random 
time.
  [ 7540.960539] systemd[1]: apt-daily.timer: Adding 43min 17.875784s random 
time.
  [ 7541.477412] systemd[1]: apt-daily.timer: Adding 5h 33min 59.201230s random 
time.
  [ 7550.068289] systemd[1]: apt-daily.timer: Adding 6h 41min 2.480405s random 
time.
  [ 7734.981411] systemd[1]: apt-daily.timer: Adding 9h 54min 39.888137s random 
time.
  [ 7735.230060] systemd[1]: apt-daily.timer: Adding 6h 8min 31.925492s random 
time.
  [ 7736.287077] systemd[1]: apt-daily.timer: Adding 4h 56min 30.657866s random 
time.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-07-13 (291 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BXCTO1WW
  Package: systemd 229-4ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-lowlatency.efi.signed 
root=UUID=6fe2ef4e-b82c-468b-a35a-86d8753787d1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  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
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  yakkety
  Uname: Linux 4.4.0-21-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LE

[Touch-packages] [Bug 1576536] Re: timer messages unnecessarily sent to /dev/kmsg

[Pheeble]

This seems to be a problem with any systemd timer that contains a
'RandomizedDelaySec' value in the [Timer] section. Multiple
randomization adjustments to a timer will often occur in quick
succession, sometimes simultaneously, and for no purpose that I can see.

Perhaps systemd timers need a flag to indicate that timer randomization
has already occurred since the relevant service was last run, so don't
do it again.

This is the result of 'journalctl -b | grep "random time"' covering just
the first hour after booting Xubuntu 16.04.1 this morning:

Nov 03 05:02:18 Phil-Desktop systemd[1]: hosts_append.timer: Adding 14.771780s 
random time.
Nov 03 05:02:18 Phil-Desktop systemd[1]: emachine-mount-nfs.timer: Adding 
3.905842s random time.
Nov 03 05:02:18 Phil-Desktop systemd[1]: apt-daily.timer: Adding 11h 10min 
46.989419s random time.
Nov 03 05:02:18 Phil-Desktop systemd[1]: send_boot_notify.timer: Adding 
12.437715s random time.
Nov 03 05:02:18 Phil-Desktop systemd[1]: send_apt_upgrades_list.timer: Adding 
41min 20.509782s random time.
Nov 03 05:02:18 Phil-Desktop systemd[1]: send_journald_log_list.timer: Adding 
3min 48.321721s random time.
Nov 03 05:02:19 Phil-Desktop systemd[1]: send_apt_upgrades_list.timer: Adding 
2min 53.039364s random time.
Nov 03 05:02:19 Phil-Desktop systemd[1]: send_journald_log_list.timer: Adding 
9min 39.120834s random time.
Nov 03 05:02:19 Phil-Desktop systemd[1]: send_boot_notify.timer: Adding 
649.932ms random time.
Nov 03 05:02:19 Phil-Desktop systemd[1]: apt-daily.timer: Adding 10h 36min 
12.532296s random time.
Nov 03 05:02:19 Phil-Desktop systemd[1]: hosts_append.timer: Adding 4.994423s 
random time.
Nov 03 05:03:39 Phil-Desktop systemd[1]: apt-daily.timer: Adding 4h 53min 
16.440349s random time.
Nov 03 05:03:39 Phil-Desktop systemd[1]: apt-daily.timer: Adding 8h 44min 
23.219990s random time.
Nov 03 06:03:45 Phil-Desktop systemd[1]: send_apt_upgrades_list.timer: Adding 
55min 558.055ms random time.
Nov 03 06:03:45 Phil-Desktop systemd[1]: send_apt_upgrades_list.timer: Adding 
25min 6.210969s random time.

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

Title:
  timer messages unnecessarily sent to /dev/kmsg

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The random adjustments to the apt timer seem to spam the kernel
  ringbuffer, which is entirely unnecessary:

  [ 5452.648222] systemd[1]: apt-daily.timer: Adding 10h 42min 21.562799s 
random time.
  [ 5454.038740] systemd[1]: apt-daily.timer: Adding 7h 11min 7.994692s random 
time.
  [ 5457.381779] systemd[1]: apt-daily.timer: Adding 10h 43min 34.008994s 
random time.
  [ 5457.495120] systemd[1]: apt-daily.timer: Adding 7h 9min 28.335411s random 
time.
  [ 5457.743417] systemd[1]: apt-daily.timer: Adding 7h 5min 47.291509s random 
time.
  [ 5778.374365] systemd[1]: apt-daily.timer: Adding 8h 26min 267.164ms random 
time.
  [ 5778.495711] systemd[1]: apt-daily.timer: Adding 9h 52min 9.289682s random 
time.
  [ 5778.667351] systemd[1]: apt-daily.timer: Adding 8h 39min 41.199389s random 
time.
  [ 5778.924784] systemd[1]: apt-daily.timer: Adding 2h 38min 40.786228s random 
time.
  [ 5779.035421] systemd[1]: apt-daily.timer: Adding 10h 48min 34.808379s 
random time.
  [ 5779.107951] systemd[1]: apt-daily.timer: Adding 6h 19min 45.904476s random 
time.
  [ 7236.115354] systemd[1]: apt-daily.timer: Adding 5h 12min 18.073639s random 
time.
  [ 7268.716558] systemd[1]: apt-daily.timer: Adding 7h 19min 40.411960s random 
time.
  [ 7269.151388] systemd[1]: apt-daily.timer: Adding 8h 21min 54.857412s random 
time.
  [ 7270.702642] systemd[1]: apt-daily.timer: Adding 8h 33min 10.633964s random 
time.
  [ 7281.835523] systemd[1]: apt-daily.timer: Adding 11h 43min 43.923801s 
random time.
  [ 7339.639840] systemd[1]: apt-daily.timer: Adding 9h 8.911515s random time.
  [ 7340.512389] systemd[1]: apt-daily.timer: Adding 1h 45min 25.722497s random 
time.
  [ 7343.611383] systemd[1]: apt-daily.timer: Adding 22min 8.489125s random 
time.
  [ 7344.186645] systemd[1]: apt-daily.timer: Adding 10h 6min 50.541602s random 
time.
  [ 7346.111888] systemd[1]: apt-daily.timer: Adding 11h 47min 57.661764s 
random time.
  [ 7350.893164] systemd[1]: apt-daily.timer: Adding 3h 10min 23.393765s random 
time.
  [ 7355.747731] systemd[1]: apt-daily.timer: Adding 1h 2min 54.946554s random 
time.
  [ 7355.825972] systemd[1]: apt-daily.timer: Adding 4h 40min 28.148047s random 
time.
  [ 7529.692671] systemd[1]: apt-daily.timer: Adding 10h 20min 39.786553s 
random time.
  [ 7539.109562] systemd[1]: apt-daily.timer: Adding 7h 45min 54.766189s random 
time.
  [ 7539.187368] systemd[1]: apt-daily.timer: Adding 2h 20min 28.098533s random 
time.
  [ 7539.617356] systemd[1]: apt-daily.timer: Adding 10h 36min 4.411352s random 
time.
  [ 7540.960539] systemd[1]: apt-daily.timer: Adding 43min 17.875784s random 
time

[Touch-packages] [Bug 1638695] [NEW] Python 2.7.12 performance regression

[Major Hayden]

Public bug reported:

I work on the OpenStack-Ansible project and we've noticed that testing
jobs on 16.04 take quite a bit longer to complete than on 14.04.  They
complete within an hour on 14.04 but they normally take 90 minutes or
more on 16.04.  We use the same version of Ansible with both versions of
Ubuntu.

After more digging, I tested python performance (using the 'performance'
module) on 14.04 (2.7.6) and on 16.04 (2.7.12).  There is a significant
performance difference between each version of python.  That is detailed
in a spreadsheet[0].

I began using perf to dig into the differences when running the python
performance module and when using Ansible playbooks.  CPU migrations (as
measured by perf) are doubled in Ubuntu 16.04 when running the same
python workloads.

I tried changing some of the kerne.sched sysctl configurables but they
had very little effect on the results.

I compiled python 2.7.12 from source on 14.04 and found the performance
to be unchanged there.  I'm not entirely sure where the problem might be
now.

We also have a bug open in OpenStack-Ansible[1] that provides additional
detail. Thanks in advance for any help you can provide!

[0] 
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
[1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  I work on the OpenStack-Ansible project and we've noticed that testing
  jobs on 16.04 take quite a bit longer to complete than on 14.04.  They
  complete within an hour on 14.04 but they normally take 90 minutes or
  more on 16.04.  We use the same version of Ansible with both versions
  of Ubuntu.

  After more digging, I tested python performance (using the
  'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12).  There
  is a significant performance difference between each version of
  python.  That is detailed in a spreadsheet[0].

  I began using perf to dig into the differences when running the python
  performance module and when using Ansible playbooks.  CPU migrations
  (as measured by perf) are doubled in Ubuntu 16.04 when running the
  same python workloads.

  I tried changing some of the kerne.sched sysctl configurables but they
  had very little effect on the results.

  I compiled python 2.7.12 from source on 14.04 and found the
  performance to be unchanged there.  I'm not entirely sure where the
  problem might be now.

  We also have a bug open in OpenStack-Ansible[1] that provides
  additional detail. Thanks in advance for any help you can provide!

  [0] 
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
  [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

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

[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: python2.7 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  I work on the OpenStack-Ansible project and we've noticed that testing
  jobs on 16.04 take quite a bit longer to complete than on 14.04.  They
  complete within an hour on 14.04 but they normally take 90 minutes or
  more on 16.04.  We use the same version of Ansible with both versions
  of Ubuntu.

  After more digging, I tested python performance (using the
  'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12).  There
  is a significant performance difference between each version of
  python.  That is detailed in a spreadsheet[0].

  I began using perf to dig into the differences when running the python
  performance module and when using Ansible playbooks.  CPU migrations
  (as measured by perf) are doubled in Ubuntu 16.04 when running the
  same python workloads.

  I tried changing some of the kerne.sched sysctl configurables but they
  had very little effect on the results.

  I compiled python 2.7.12 from source on 14.04 and found the
  performance to be unchanged there.  I'm not entirely sure where the
  problem might be now.

  We also have a bug open in OpenStack-Ansible[1] that provides
  additional detail. Thanks in advance for any help you can provide!

  [0] 
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
  [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

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

[Touch-packages] [Bug 1638666] Re: package libffi6:i386 3.1~rc1+r3.0.13-12ubuntu0.1 failed to install/upgrade: package libffi6:i386 is already installed and configured

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libffi6:i386 3.1~rc1+r3.0.13-12ubuntu0.1 failed to
  install/upgrade: package libffi6:i386 is already installed and
  configured

Status in libffi package in Ubuntu:
  New

Bug description:
  no worries

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libffi6:i386 3.1~rc1+r3.0.13-12ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  CrashReports:
   600:0:116:283416:2016-11-02 10:59:41.186816692 -0700:2016-11-02 
10:59:42.186816692 -0700:/var/crash/libexpat1:i386.0.crash
   600:0:116:283424:2016-11-02 10:59:41.214816570 -0700:2016-11-02 
10:59:42.214816570 -0700:/var/crash/libffi6:i386.0.crash
  Date: Wed Nov  2 10:59:42 2016
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.9
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.9
  DuplicateSignature: package:libffi6:i386:3.1~rc1+r3.0.13-12ubuntu0.1:package 
libffi6:i386 is already installed and configured
  ErrorMessage: package libffi6:i386 is already installed and configured
  InstallationDate: Installed on 2016-11-02 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: libffi
  Title: package libffi6:i386 3.1~rc1+r3.0.13-12ubuntu0.1 failed to 
install/upgrade: package libffi6:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Heimen Stoffels]

I'm also experiencing this issue but I don't have any device connected
(I don't even any iDevice at all!).

-- 
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 1638689] [NEW] package libnss3 2:3.23-0ubuntu0.14.04.1 [modified: usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc

[Jim Lawrence]

Public bug reported:

sudo aptitude upgrade
...
Unpacking libapt-pkg4.12:amd64 (1.0.1ubuntu2.15) over (1.0.1ubuntu2.14) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libnss3_2%3a3.23-0ubuntu0.14.04.1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up libapt-pkg4.12:amd64 (1.0.1ubuntu2.15) ...
Setting up libnspr4:i386 (2:4.12-0ubuntu0.14.04.1) ...
dpkg: dependency problems prevent configuration of libnss3-1d:i386:
 libnss3-1d:i386 depends on libnss3 (= 2:3.23-0ubuntu0.14.04.1); however:
  Version of libnss3:i386 on system is 2:3.16.3-1ubuntu1.

dpkg: error processing package libnss3-1d:i386 (--configure):
 dependency problems - leaving unconfigured
dpkg: error processing package libnss3:amd64 (--configure):
 package libnss3:amd64 2:3.23-0ubuntu0.14.04.1 cannot be configured because 
libnss3:i386 is at a different version (2:3.16.3-1ubuntu1)
dpkg: error processing package libnss3:i386 (--configure):
 package libnss3:i386 2:3.16.3-1ubuntu1 cannot be configured because 
libnss3:amd64 is at a different version (2:3.23-0ubuntu0.14.04.1)
dpkg: dependency problems prevent configuration of libnss3-nssdb:
 libnss3-nssdb depends on libnss3 (= 2:3.23-0ubuntu0.14.04.1); however:
  Package libnss3:amd64 is not configured yet.

dpkg: error processing package libnss3-nssdb (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
Errors were encountered while processing:
 libnss3-1d:i386
 libnss3:amd64
 libnss3:i386
 libnss3-nssdb


Description:Ubuntu 14.04.5 LTS
Release:14.04

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libnss3 2:3.23-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 3.19.0-68.76~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-68-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Wed Nov  2 12:32:54 2016
DuplicateSignature: package:libnss3:2:3.23-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libnss3/changelog.Debian.gz', which is different from other 
instances of package libnss3:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libnss3/changelog.Debian.gz', which is different from other 
instances of package libnss3:i386
InstallationDate: Installed on 2015-09-22 (407 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: nss
Title: package libnss3 2:3.23-0ubuntu0.14.04.1 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libnss3/changelog.Debian.gz', which is 
different from other instances of package libnss3:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check package-conflict trusty

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

Title:
  package libnss3 2:3.23-0ubuntu0.14.04.1 [modified:
  usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libnss3/changelog.Debian.gz', which is different from
  other instances of package libnss3:i386

Status in nss package in Ubuntu:
  New

Bug description:
  sudo aptitude upgrade
  ...
  Unpacking libapt-pkg4.12:amd64 (1.0.1ubuntu2.15) over (1.0.1ubuntu2.14) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libnss3_2%3a3.23-0ubuntu0.14.04.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up libapt-pkg4.12:amd64 (1.0.1ubuntu2.15) ...
  Setting up libnspr4:i386 (2:4.12-0ubuntu0.14.04.1) ...
  dpkg: dependency problems prevent configuration of libnss3-1d:i386:
   libnss3-1d:i386 depends on libnss3 (= 2:3.23-0ubuntu0.14.04.1); however:
Version of libnss3:i386 on system is 2:3.16.3-1ubuntu1.

  dpkg: error processing package libnss3-1d:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: error processing package libnss3:amd64 (--configure):
   package libnss3:amd64 2:3.23-0ubuntu0.14.04.1 cannot be configured because 
libnss3:i386 is at a different version (2:3.16.3-1ubuntu1)
  dpkg: error processing package libnss3:i386 (--configure):
   package libnss3:i386 2:3.16.3-1ubuntu1 cannot be configured because 
libnss3:amd64 is at a different version (2:3.23-0ubuntu0.14.04.1)
  dpkg: dependency problems prevent configuration of libnss3-nssdb:
   libnss3-nssdb depends on libnss3 (= 2:3.23-0ubuntu0.14.04.1); however:
Package libnss3:amd64 is not configured yet.

  dpkg: err

[Touch-packages] [Bug 1591704] Re: bluetoothd crashed with SIGSEGV in __GI__IO_wsetb()

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bluez (Ubuntu)
   Status: New => Confirmed

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

Title:
  bluetoothd crashed with SIGSEGV in __GI__IO_wsetb()

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth crashinfo displayed shortly after login. This happens
  repeatedly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-powerpc-smp 4.4.8
  Uname: Linux 4.4.0-22-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  Date: Sat Jun 11 11:26:29 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-09-16 (269 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha powerpc 
(20150827)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 05ac:0215 Apple, Inc. Internal Keyboard/Trackpad (ISO)
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
   LANG=de_AT.UTF-8
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
  ProcKernelCmdLine: root=UUID=e7580396-741d-4923-8a8a-50db1b938df3 ro 
rootflags=subvol=@ quiet splash
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   __GI__IO_wsetb (f=f@entry=0x204b7ca0 <_IO_stdout_>, b=b@entry=0x0, 
eb=eb@entry=0x0, a=a@entry=0) at wgenops.c:105
   _IO_unbuffer_all () at genops.c:918
   _IO_cleanup () at genops.c:960
   __run_exit_handlers (status=0, listp=, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:95
   __GI_exit (status=) at exit.c:104
  Title: bluetoothd crashed with SIGSEGV in __GI__IO_wsetb()
  UpgradeStatus: Upgraded to xenial on 2016-05-08 (35 days ago)
  UserGroups:
   
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:14:51:95:FF:B4  ACL MTU: 384:8  SCO MTU: 64:8
UP RUNNING 
RX bytes:534 acl:0 sco:0 events:27 errors:0
TX bytes:612 acl:0 sco:0 commands:26 errors:0

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

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

[Touch-packages] [Bug 1635887] Re: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: click (Ubuntu)
   Status: New => Confirmed

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

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

Status in click package in Ubuntu:
  Confirmed

Bug description:
  This bug occurs every time at startup after I have upgraded from Ubuntu 16.04 
LTS to 16.10.
  Computer model: HP Envy 4-1220tx Ultrabook

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: click 0.4.45.1+16.10.20160916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sat Oct 22 11:51:26 2016
  DuplicateSignature:
   package:click:0.4.45.1+16.10.20160916-0ubuntu1
   Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package click (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-25 (58 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: click
  Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (8 days ago)

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

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

[Touch-packages] [Bug 1638675] [NEW] package procps 2:3.3.12-1ubuntu2 failed to install/upgrade: end of file on stdin at conffile prompt

[Radu Andrei Tentea]

Public bug reported:

Not really know of any. Was trying to upgrade 16.04 to 16.10 headless
home media server. Pressed ctrl+c by mistake during install. All hell
broke loose.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: procps 2:3.3.12-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Wed Nov  2 18:37:42 2016
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2013-11-06 (1092 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: procps
Title: package procps 2:3.3.12-1ubuntu2 failed to install/upgrade: end of file 
on stdin at conffile prompt
UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)
mtime.conffile..etc.sysctl.conf: 2014-05-05T12:03:01.086378

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

Title:
  package procps 2:3.3.12-1ubuntu2 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in procps package in Ubuntu:
  New

Bug description:
  Not really know of any. Was trying to upgrade 16.04 to 16.10 headless
  home media server. Pressed ctrl+c by mistake during install. All hell
  broke loose.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: procps 2:3.3.12-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 18:37:42 2016
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2013-11-06 (1092 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: procps
  Title: package procps 2:3.3.12-1ubuntu2 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)
  mtime.conffile..etc.sysctl.conf: 2014-05-05T12:03:01.086378

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

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

[Touch-packages] [Bug 1638663] Re: Segfault on arm64 dragonboard

[Chris Coulson]

** Package changed: oxide-qt (Ubuntu) => oxide

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

Title:
  Segfault on arm64 dragonboard

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  the following is output from the webbrowser-app or webview-demo snaps
  on arm64 dragoonboard with latest core.

  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  [1102/181614:WARNING:audio_manager.cc(314)] Multiple instances of 
AudioManager detected
  [1102/181614:WARNING:audio_manager.cc(275)] Multiple instances of 
AudioManager detected
  [1102/181614:ERROR:layer_tree_host_impl.cc(2250)] Forcing zero-copy tile 
initialization as worker context is missing
  Segmentation fault

  The screen flashes white just before the crash

  Browser from Nov 1 build at 
https://code.launchpad.net/~kgunn72/+snap/ubunutu-browser-snap
  Webbiew from Oct 20 at 
  https://code.launchpad.net/~osomon/+snap/webview-snap-demo/+build/7599

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

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

[Touch-packages] [Bug 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-zesty-2137

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

Title:
  Clicking a date in the new calendar doesn't change the indicator's
  appointment list

Status in Ubuntu UX:
  New
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in qmenumodel package in Ubuntu:
  In Progress
Status in ubuntu-settings-components package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Now that we've got a calendar in indicator-datetime in Unity 8, there
  are a few features from Unity 7 that we should decide if/how we're
  goint to handle in Unity 8.

  * Show Week Numbers
  * Highlight days of the month that include appointments
  * Unity tells indicator-datetime what calendar day has been clicked so that 
the "upcoming appointments" list can be adjusted accordingly

  These are currently implemented as fields in a GAction state
  dictionary and documented in http://bazaar.launchpad.net/~indicator-
  applet-developers/indicator-datetime/trunk.15.10/view/head:/README ...
  however that was all done for Unity 7, and IMO it would make sense to
  improve the unity<->indicator API here so that Unity8 doesn't have to
  deal with key-variant map GAction states.

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

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

[Touch-packages] [Bug 1632804] Re: ROUNDTTT in configure_networking is effectively ignored

[LaMont Jones]

*** This bug is a duplicate of bug 1621507 ***
https://bugs.launchpad.net/bugs/1621507

** This bug has been marked a duplicate of bug 1621507
   initramfs-tools configure_networking() fails to dhcp ipv6 addresses

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

Title:
  ROUNDTTT in configure_networking is effectively ignored

Status in MAAS:
  New
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  With the changes from Bug #1621507, ROUNDTTT is effectively ignored.

  The loop checks only for the existence of /run/net-${DEVICE}.conf, and
  the dhclient scripts ALWAYS (even on failure) create it, it will try
  to get a lease exactly once before bailing out. Ideally, if both ipv4
  and ipv6 are present on the vlan, then both would be configured and
  (as is done) present in the net-$DEV.conf file.  Generally speaking
  (and why we didn't notice this in testing..), dhclient gets a lease on
  the first pass.

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

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

[Touch-packages] [Bug 1638663] [NEW] Segfault on arm64 dragonboard

[Pat McGowan]

Public bug reported:

the following is output from the webbrowser-app or webview-demo snaps on
arm64 dragoonboard with latest core.

Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
[1102/181614:WARNING:audio_manager.cc(314)] Multiple instances of AudioManager 
detected
[1102/181614:WARNING:audio_manager.cc(275)] Multiple instances of AudioManager 
detected
[1102/181614:ERROR:layer_tree_host_impl.cc(2250)] Forcing zero-copy tile 
initialization as worker context is missing
Segmentation fault

The screen flashes white just before the crash

Browser from Nov 1 build at 
https://code.launchpad.net/~kgunn72/+snap/ubunutu-browser-snap
Webbiew from Oct 20 at 
https://code.launchpad.net/~osomon/+snap/webview-snap-demo/+build/7599

** Affects: oxide-qt (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Description changed:

  the following is output from the webbrowser-app or webview-demo snaps on
  arm64 dragoonboard with latest core.
  
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  [1102/181614:WARNING:audio_manager.cc(314)] Multiple instances of 
AudioManager detected
  [1102/181614:WARNING:audio_manager.cc(275)] Multiple instances of 
AudioManager detected
  [1102/181614:ERROR:layer_tree_host_impl.cc(2250)] Forcing zero-copy tile 
initialization as worker context is missing
  Segmentation fault
  
  The screen flashes white just before the crash
+ 
+ Browser from Nov 1 build at 
https://code.launchpad.net/~kgunn72/+snap/ubunutu-browser-snap
+ Webbiew from Oct 20 at 
+ https://code.launchpad.net/~osomon/+snap/webview-snap-demo/+build/7599

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

Title:
  Segfault on arm64 dragonboard

Status in oxide-qt package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  the following is output from the webbrowser-app or webview-demo snaps
  on arm64 dragoonboard with latest core.

  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  [1102/181614:WARNING:audio_manager.cc(314)] Multiple instances of 
AudioManager detected
  [1102/181614:WARNING:audio_manager.cc(275)] Multiple instances of 
AudioManager detected
  [1102/181614:ERROR:layer_tree_host_impl.cc(2250)] Forcing zero-copy tile 
initialization as worker context is missing
  Segmentation fault

  The screen flashes white just before the crash

  Browser from Nov 1 build at 
https://code.launchpad.net/~kgunn72/+snap/ubunutu-browser-snap
  Webbiew from Oct 20 at 
  https://code.launchpad.net/~osomon/+snap/webview-snap-demo/+build/7599

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1638663/+subscriptions

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

[Touch-packages] [Bug 1562948] Re: google-earth not working - broken package with Xenial Xerus

[Graham Inggs]

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

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

** Also affects: lsb (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830481
   Importance: Unknown
   Status: Unknown

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

Title:
  google-earth not working - broken package with Xenial Xerus

Status in googleearth-package package in Ubuntu:
  Confirmed
Status in lsb package in Ubuntu:
  New
Status in lsb package in Debian:
  Unknown

Bug description:
  With Xubuntu Xenial Xerus 16.04 LTS Beta2 googleearth-package (1.2.2)
  is still not working as reported several times before.
  This time, there is no way to install google-earth with normal administrator 
skills
  at all - as further outlined below.

  As reported for the former LTS Trusty (14.04 LTS) Bug# 1314993,
  the package is still not working and dependencies are not met:

  From Xenial Beta2:
  $ make-googleearth-package --force
  $ sudo dpkg -i googleearth_6.0.3.2197+1.2.0-1_amd64.deb
  Selecting previously unselected package googleearth.
  (Reading database ... 445462 files and directories currently installed.)
  Preparing to unpack googleearth_6.0.3.2197+1.2.0-1_amd64.deb ...
  Unpacking googleearth (6.0.3.2197+1.2.0-1) ...
  dpkg: dependency problems prevent configuration of googleearth:
   googleearth depends on lsb-core; however:
Package lsb-core is not installed.
   googleearth depends on libcurl3:i386; however:
  dpkg: error processing package googleearth (--install):
   dependency problems - leaving unconfigured
  Processing triggers for gnome-menus (3.13.3-6ubuntu3) ...
  Processing triggers for desktop-file-utils (0.22-1ubuntu4) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for shared-mime-info (1.5-2) ...
  Unknown media type in type 'all/all'
  Unknown media type in type 'all/allfiles'
  Errors were encountered while processing:
   googleearth

  As lsb-core is no longer supported by Debian (and thus Ubuntu), this 
dependency
  can not be met and thus also the directly provided Google 32 bit package is 
not installable.
  As reported since years the 64 bit package is also not installable (and 
never[?] was).

  Also the depicted way using Jessie packages 
(lsb-security_4.1+Debian13+nmu1_i386.deb,
  lsb-invalid-mta_4.1+Debian13+nmu1_all.deb and 
lsb-core_4.1+Debian13+nmu1_i386.deb)
  is no longer possible (i.e. with Beta2), as other dependency problems exist.

  This problem may be best addressed by google in providing current 
installation packages
  working on current amd64 systems or by Debian/Ubuntu by providing an 
environment
  where these dependencies are met (this was the former reason for the 
google-earth package).

  Even with 32 bit package provided by Google a stable usage is not possible 
with Werewolf (15.10),
  see e.g. Bug #1559489.
  Thus, additional care by Google may be appropriate.

  Otherwise, this very informative and educative tool is no longer accessible 
for most users
  of the Linux desktop 

  If further pieces of information are needed or something should be
  tested, I am willing to help.

  Best wishes,

  JMB

  ---
  Other pieces of information:
  lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
[current today]
  ~
  sudo dpkg -l | grep earth
  ii  googleearth-package   1.2.2   
   all  utility to automatically build a Debian package of 
Google Earth
  ~
  apt-cache policy googleearth-package
  googleearth-package:
Installed: 1.2.2
Candidate: 1.2.2
Version table:
   *** 1.2.2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://de.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
  100 /var/lib/dpkg/status
  ~~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/googleearth-package/+bug/1562948/+subscriptions

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

[Touch-packages] [Bug 1637459] Re: Launching browser on external monitor causes mobile ua-overrides to be loaded

[Olivier Tilloy]

Just tested with an external HDMI monitor connected to my laptop, and I’m 
seeing desktop UA overrides being loaded on both screens, so I guess this is an 
issue with your monitor.
What does xrandr report for the physical dimensions of your external monitor? 
Mine says:

HDMI1 connected primary 1920x1080+0+0 (normal left inverted right x axis
y axis) 510mm x 287mm

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Incomplete

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

Title:
  Launching browser on external monitor causes mobile ua-overrides to be
  loaded

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  Setup:
  I have a laptop that is plugged into an external monitor via HDMI

  What happened:
  1) Open a terminal, move it to the laptop screen and launch the webbrowser-app
  2) Notice in the console that it loads the desktop UA overrides
  3) Close the webbrowser-app and move the terminal to the external monitor
  4) Launch the webbrowser-app in the terminal on the external monitor
  5) Notice in the console that it loads the mobile UA overrides

  What I expected to happen:
  For my screen size to be detected correctly, even if it is an external 
monitor, and then load the correct UA overrides (at step 5 I expected desktop 
UA overrides).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1637459/+subscriptions

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

[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Joel Parke]

I had the same issue with upgrading from 16.04 to 16.10. and I too had
to dismiss MANY identical dialogues about this failure!!  I almost power
cycled... but kept going.. waiting for upgrade to complete PLEASE
fix - or at least don't have an endless cycle of error messages

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome. 
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Touch-packages] [Bug 1592817] Re: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0, 0000'

[Julian Andres Klode]

Let's clean this up.

** Package changed: python-apt (Ubuntu) => apt (Ubuntu)

** Changed in: apt (Ubuntu)
   Status: Triaged => Fix Released

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gdebi (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  gdebi-gtk crashed with ValueError in update_interface(): could not
  convert string to float: '0,'

Status in apt package in Ubuntu:
  Fix Released
Status in gdebi package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  New
Status in gdebi source package in Xenial:
  New

Bug description:
  Errors Bucket
  -
  https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53
  and
  https://errors.ubuntu.com/problem/c349b36522b1d43e2604357f75f0215fdafe1c7a

  Gdebi crashed while installing Google Chrome .deb-fil bur the error
  didn't appear until I logged out and back in again

  ProblemType: CrashDistroRelease: Ubuntu 16.10
  Package: gdebi 0.9.5.7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 15 15:01:11 2016
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2016-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive 
/media/jimmy/Seagate\ Backup\ Plus\ 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb
  ProcEnviron:
   PATH=(custom, no user)
   LANG=da_DK.UTF-8
   LANGUAGE=da
   SHELL=/bin/bash
   TERM=unknown
  PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate 
Backup Plus 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb']SourcePackage: 
gdebi
  Title: gdebi-gtk crashed with ValueError in update_interface(): could not 
convert string to float: '0,'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[José Tomás Atria]

I can confirm that Luke's PPA works with my Jaybird X2 on Kunbutu
Xenial.

A2DP was not selected by default upon connection, but it is possible to
select it manually in the hardware panel in Phonon (Using kde here), and
it works like a charm.

The only funny thing in my setup is that there's an extra entry for a
Jaybird X2 in the audio hardware conf dialog that  shows up as
unavailable. I assume it's from earlier attempts at connecting before
upgrading pulseaudio to Luke's version.

Thanks for the hard work, Luke

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 1638561] Re: unattended-upgrade fails to apply security updates if the update is also in another suite suffix component, such as yakkety-updates

[Seth Arnold]

** Information type changed from Private Security to Public Security

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

Title:
  unattended-upgrade fails to apply security updates if the update is
  also in another suite suffix component, such as yakkety-updates

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  As you can see below, the packages have security updates which are not
  being applied, presumably because the security updates are not only in
  yakkety-security, but also in yakkety-updates. This is a bug and
  leaves systems vulnerable that are expecting unattended-upgrades to
  apply the patches (it fails to do so).

  """
  # apt list --upgradable 2>/dev/null | grep yakkety-security
  liboxideqt-qmlplugin/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  liboxideqtcore0/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  liboxideqtquick0/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 
amd64 [upgradable from: 1.17.9-0ubuntu1]
  oxideqt-codecs/yakkety-updates,yakkety-security 1.18.3-0ubuntu0.16.10.1 amd64 
[upgradable from: 1.17.9-0ubuntu1]
  # unattended-upgrade --dry-run -v  
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=yakkety-security']
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded: 
  
  """

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1638561/+subscriptions

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

[Touch-packages] [Bug 1637459] Re: Launching browser on external monitor causes mobile ua-overrides to be loaded

[Andrew Hayzen]

Note: Even moving the window between the laptop screen and the external
monitor causes the UA overrides to be reloaded.

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

Title:
  Launching browser on external monitor causes mobile ua-overrides to be
  loaded

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Setup:
  I have a laptop that is plugged into an external monitor via HDMI

  What happened:
  1) Open a terminal, move it to the laptop screen and launch the webbrowser-app
  2) Notice in the console that it loads the desktop UA overrides
  3) Close the webbrowser-app and move the terminal to the external monitor
  4) Launch the webbrowser-app in the terminal on the external monitor
  5) Notice in the console that it loads the mobile UA overrides

  What I expected to happen:
  For my screen size to be detected correctly, even if it is an external 
monitor, and then load the correct UA overrides (at step 5 I expected desktop 
UA overrides).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1637459/+subscriptions

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

[Touch-packages] [Bug 1592817] Re: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0, 0000'

[Brian Murray]

Julian K indicated that the fix for 1611010 might end up fixing this and
that he'd look at cherry-picking into into Ubuntu 16.04.

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

Title:
  gdebi-gtk crashed with ValueError in update_interface(): could not
  convert string to float: '0,'

Status in gdebi package in Ubuntu:
  Confirmed
Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  Errors Bucket
  -
  https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53
  and
  https://errors.ubuntu.com/problem/c349b36522b1d43e2604357f75f0215fdafe1c7a

  Gdebi crashed while installing Google Chrome .deb-fil bur the error
  didn't appear until I logged out and back in again

  ProblemType: CrashDistroRelease: Ubuntu 16.10
  Package: gdebi 0.9.5.7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
  Uname: Linux 4.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 15 15:01:11 2016
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2016-06-15 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive 
/media/jimmy/Seagate\ Backup\ Plus\ 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb
  ProcEnviron:
   PATH=(custom, no user)
   LANG=da_DK.UTF-8
   LANGUAGE=da
   SHELL=/bin/bash
   TERM=unknown
  PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate 
Backup Plus 
Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb']SourcePackage: 
gdebi
  Title: gdebi-gtk crashed with ValueError in update_interface(): could not 
convert string to float: '0,'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1634152] Re: Driver video doesn't work properly after Upgrade (16.04 LTS)

[Ubuntu Foundations Team Bug Bot]

The attachment "enable_intel__video_drivers" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1634152

Title:
  Driver video doesn't work properly after Upgrade (16.04 LTS)

Status in xorg package in Ubuntu:
  New

Bug description:
  After the last automatic upgrade (kernel?), the system suggested a restart to 
finalize the installation.
  Immediately after the reboot, the graph login page worked at 640x480. Using 
"xdiagnose", checking (disabling) all, I was able to set the resolution 
1280x1024, but no more capable to manage the dual-screen as before: in the 
"Monitor" configuration page, I see only one "Built-in Display" instead the two 
Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been 
changed.

  My PC is an Acer Veriton X4610G
  CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4
  RAM: 4GiB (128MiB VGA shared)

  I use an UBUNTU 16.04 LTS 64-bit

  Thanks for any feedback!
  Paolo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 17 15:39:54 2016
  DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0492]
  InstallationDate: Installed on 2015-05-15 (521 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp.
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Veriton X4610G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat 
vesafb.invalid=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton X4610G
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton X4610G
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 17 15:32:10 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1638021] Re: [SRU] Update apt/xenial to 1.2.15

[Brian Murray]

Hello Julian, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.15 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apt (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  [SRU] Update apt/xenial to 1.2.15

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  1.2.15 is a somewhat larger bugfix release because I screwed up a bit with 
backporting fixes: 1.2.14 was released in June, and quite a few bugs have been 
fixed since then in the 1.3 series, but I never managed to release a new 1.2.y 
release. See Bug #1595177 for the 1.2.14 details.

  This changes the cache format to fix buffer overflows (the cache
  format is in sync with the 1.3 series and thus has the same version
  number). It also fixes several invalid states in the updating code
  (where we got mismatches before). Then there are several smaller
  bugfixes and more checks for file sanity I cannot really all recall,
  and some translation updates.

  This release also changes the autoremoval algorithm to only protect
  the latest same-source provider of a given package. infinity wanted
  this in for handling virtual ZFS modules provided by the kernel
  causing the kernels not to be autoremoved or something. We have this
  code in Debian testing and unstable since 1.3~pre1 early July and its
  in yakkety, and are reasonably sure it's stable now. This change also
  needs the two refactoring commits for the removal methods and the new
  pretty printers mentioned in the changelog.

  apt (1.2.15) xenial; urgency=medium

    [ Julian Andres Klode ]
    * methods/ftp: Cope with weird PASV responses.
  Thanks to Lukasz Stelmach for the initial patch (Closes: #420940)
    * Fix buffer overflow in debListParser::VersionHash() (Closes: #828812)
    * cache: Bump minor version to 6
    * indextargets: Check that cache could be built before using it
  (Closes: #829651)
    * gpgv: Unlink the correct temp file in error case
    * fileutl: empty file support: Avoid fstat() on -1 fd and check result
    * Ignore SIGINT and SIGQUIT for Pre-Install hooks
    * install-progress: Call the real ::fork() in our fork() method
    * Accept --autoremove as alias for --auto-remove
    * apt-inst: debfile: Pass comp. Name to ExtractTar, not Binary
    * changelog: Respect Dir setting for local changelog getting
    * Fix segfault and out-of-bounds read in Binary fields
    * Merge translations from 1.3~rc3
    * TagFile: Fix off-by-one errors in comment stripping
    * Base256ToNum: Fix uninitialized value
    * VersionHash: Do not skip too long dependency lines
    * Do not read stderr from proxy autodetection scripts

    [ Nicolas Le Cam ]
    * Use the ConditionACPower feature of systemd in the apt-daily service
  (Closes: #827930)

    [ David Kalnischkies ]
    * close server if parsing of header field failed
    * don't do atomic overrides with failed files (Closes: 828908)
    * if reading of autobit state failed, let write fail
    * write auto-bits before calling dpkg & again after if needed
    * factor out Pkg/DepIterator prettyprinters into own header
    * protect only the latest same-source providers from autoremove
    * reinstalling local deb file is no downgrade
    * do not treat same-version local debs as downgrade
    * avoid 416 response teardown binding to null pointer
    * don't change owner/perms/times through file:// symlinks
    * report all instead of first error up the acquire chain
    * keep trying with next if connection to a SRV host failed
    * call flush on the wrapped writebuffered FileFd
    * verify hash of input file in rred
    * use proper warning for automatic pipeline disable
    * rred: truncate result file before writing to it (Closes: #831762)
    * if the FileFd failed already following calls should fail, too
    * pass --force-remove-essential to

[Touch-packages] [Bug 1561142] Re: Unable to print to a Dell E310dw

[Brian Murray]

I upgraded this particular system to 16.10 and it is no longer an issue
for me.

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

Title:
  Unable to print to a Dell E310dw

Status in cups package in Ubuntu:
  New

Bug description:
  I have two systems setup to print to a Dell E310dw connected via
  ethernet.  One of them can print to it fine, the other one cannot.  I
  noticed the following in my cups error log file which might be a
  problem:

  D [23/Mar/2016:10:57:55 -0700] [Job 13] Start rendering...
  D [23/Mar/2016:10:57:55 -0700] [Job 13] Processing page 1...
  D [23/Mar/2016:10:57:55 -0700] [Job 13] Error: /ioerror in --showpage--
  D [23/Mar/2016:10:57:55 -0700] [Job 13] Operand stack:
  D [23/Mar/2016:10:57:55 -0700] [Job 13] (/tmp/gs_Obz7pK)   --nostringval--   
1   true
  D [23/Mar/2016:10:57:55 -0700] [Job 13] Execution stack:
  D [23/Mar/2016:10:57:55 -0700] [Job 13] %interp_exit   .runexec2   
--nostringval--   --nostringval--   --nostringval--   2   %stopped_push   
--nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push 
  1981   1   3   %oparray_pop   1980   1   3   %oparray_pop   1964   1   3   
%oparray_pop   --nostringval--   --nostringval--   --nostringval--   2   1   1  
 --nostringval--   %for_pos_int_continue   --nostringval--   --nostringval--   
1858   2   9   %oparray_pop   --nostringval--   --nostringval--
  D [23/Mar/2016:10:57:55 -0700] [Job 13] Dictionary stack:
  D [23/Mar/2016:10:57:55 -0700] [Job 13] --dict:1207/1684(ro)(G)--   
--dict:1/20(G)--   --dict:83/200(L)--   --dict:83/200(L)--   
--dict:132/256(ro)(G)--   --dict:283/300(ro)(G)--   --dict:28/32(L)--   
--dict:6/8(L)--   --dict:30/40(L)--
  D [23/Mar/2016:10:57:55 -0700] [Job 13] Current allocation mode is local
  D [23/Mar/2016:10:57:55 -0700] [Job 13] Last OS error: Broken pipe
  D [23/Mar/2016:10:57:55 -0700] [Job 13] GPL Ghostscript 9.18: Unrecoverable 
error, exit code 1
  D [23/Mar/2016:10:57:55 -0700] [Job 13] Rendering completed 

  For what its worth both systems are missing icc profiles, so I don't
  think that's the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 23 11:03:14 2016
  InstallationDate: Installed on 2016-01-22 (61 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  Lpstat:
   device for Dell-Printer-E310dw: 
dnssd://Dell%20Printer%20E310dw._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-30055c7c309d
   device for HP_Officejet_5600_series: 
ipps://bizarro.local:631/printers/HP_Officejet_5600_series
  MachineType: LENOVO 20BXCTO1WW
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Dell-Printer-E310dw.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Dell-Printer-E310dw.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1635906] Re: Low graphics mode in multi monitor setup after upgrade to 16.10

[Paolo]

Hi! At last I... SOLVED!!!

Before I saw:

http://askubuntu.com/questions/436374/how-to-get-rid-of-the-gallium-0-4
-on-llvmpipe-llvm-0x300-driver-intel-needed

...then I saw:

https://wiki.ubuntu.com/Kernel/LTSEnablementStack

...later, on a terminal, I've run:

sudo apt-get install --install-recommends linux-generic-lts-xenial
xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-
all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-
lts-xenial

...and, after a restart, my PC returned to work with the correct "Intel®
Sandybridge Desktop" instead of "Gallium 0.4 on llvmpipe..."!

I hope that it can help you.


BR
Paolo

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

Title:
  Low graphics mode in multi monitor setup after upgrade to 16.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  After upgrading from 16.04 to 16.10 my multi monitor setup is unable to reach 
login screen. Computer is Panasonic CF-52 on dock station with two external 
monitors. The error says low graphics mode enabled.Used to work just fine in 
previous distributions. the last error in the log file says: ScreenInit failed 
for driver 0. I have Intel graphics. 

  Workaround found so far: boot laptop out of dock station, then dock it
  and monitors are recognized no problem.

  Troubleshooting done:
  Reintsall Ubuntu from thumb drive - reinstall option: same results
  Reinstall Ubuntu from thumb drive - clean install except for /home drive 
kept: same results
  Run X -configure: same results

  Regards,
  isotope

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Oct 22 18:47:00 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series 
Chipset Integrated Graphics Controller [10f7:8338]
 Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series 
Chipset Integrated Graphics Controller [10f7:8338]
  InstallationDate: Installed on 2016-10-22 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-52GCMBSAE
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=54989005-afb3-4eb2-9813-17ee5bf134c2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.50L20
  dmi.board.name: CF52-2L
  dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.50L20:bd03/27/2009:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-52GCMBSAE:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF52-2L:rvr1:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
  dmi.product.name: CF-52GCMBSAE
  dmi.product.version: 002
  dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Oct 22 17:49:03 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   OutputDP-1DP-2
DP-3  HDMI-1  HDMI-2   

[Touch-packages] [Bug 1634152] Re: Driver video doesn't work properly after Upgrade (16.04 LTS)

[Paolo]

** Attachment added: "enable_intel__video_drivers"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634152/+attachment/4771203/+files/enable_intel__video_drivers

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

Title:
  Driver video doesn't work properly after Upgrade (16.04 LTS)

Status in xorg package in Ubuntu:
  New

Bug description:
  After the last automatic upgrade (kernel?), the system suggested a restart to 
finalize the installation.
  Immediately after the reboot, the graph login page worked at 640x480. Using 
"xdiagnose", checking (disabling) all, I was able to set the resolution 
1280x1024, but no more capable to manage the dual-screen as before: in the 
"Monitor" configuration page, I see only one "Built-in Display" instead the two 
Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been 
changed.

  My PC is an Acer Veriton X4610G
  CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4
  RAM: 4GiB (128MiB VGA shared)

  I use an UBUNTU 16.04 LTS 64-bit

  Thanks for any feedback!
  Paolo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 17 15:39:54 2016
  DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0492]
  InstallationDate: Installed on 2015-05-15 (521 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp.
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Veriton X4610G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat 
vesafb.invalid=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton X4610G
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton X4610G
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 17 15:32:10 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1634152] Re: Driver video doesn't work properly after Upgrade (16.04 LTS)

[Paolo]

** Attachment added: "Intel_video_drivers.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634152/+attachment/4771201/+files/Intel_video_drivers.png

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

Title:
  Driver video doesn't work properly after Upgrade (16.04 LTS)

Status in xorg package in Ubuntu:
  New

Bug description:
  After the last automatic upgrade (kernel?), the system suggested a restart to 
finalize the installation.
  Immediately after the reboot, the graph login page worked at 640x480. Using 
"xdiagnose", checking (disabling) all, I was able to set the resolution 
1280x1024, but no more capable to manage the dual-screen as before: in the 
"Monitor" configuration page, I see only one "Built-in Display" instead the two 
Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been 
changed.

  My PC is an Acer Veriton X4610G
  CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4
  RAM: 4GiB (128MiB VGA shared)

  I use an UBUNTU 16.04 LTS 64-bit

  Thanks for any feedback!
  Paolo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 17 15:39:54 2016
  DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0492]
  InstallationDate: Installed on 2015-05-15 (521 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp.
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Veriton X4610G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat 
vesafb.invalid=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton X4610G
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton X4610G
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 17 15:32:10 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1638608] [NEW] USB sound card not detected

[Miro]

Public bug reported:

I'm trying to use earphone+mic: Koss CS/100 USB which has been working fine 
until a month ago.
All of sudden it doesn't list in the devices. The earphones works on other 
system (windows) fine.

I see this in the dmesg when it's plugged in:

[ 5057.286942] usb 1-7.4: new full-speed USB device number 22 using xhci_hcd
[ 5057.359006] usb 1-7.4: device descriptor read/64, error -32
[ 5057.535048] usb 1-7.4: device descriptor read/64, error -32
[ 5057.711027] usb 1-7.4: new full-speed USB device number 23 using xhci_hcd
[ 5057.783036] usb 1-7.4: device descriptor read/64, error -32
[ 5057.958967] usb 1-7.4: device descriptor read/64, error -32
[ 5058.134906] usb 1-7.4: new full-speed USB device number 24 using xhci_hcd
[ 5058.135027] usb 1-7.4: Device not responding to setup address.
[ 5058.339050] usb 1-7.4: Device not responding to setup address.
[ 5058.542862] usb 1-7.4: device not accepting address 24, error -71
[ 5058.614858] usb 1-7.4: new full-speed USB device number 25 using xhci_hcd
[ 5058.615020] usb 1-7.4: Device not responding to setup address.
[ 5058.818942] usb 1-7.4: Device not responding to setup address.
[ 5059.022808] usb 1-7.4: device not accepting address 25, error -71
[ 5059.022873] usb 1-7-port4: unable to enumerate USB device

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  miro   1801 F pulseaudio
 /dev/snd/controlC1:  miro   1801 F pulseaudio
CurrentDesktop: Unity
Date: Wed Nov  2 16:43:11 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-11 (356 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: USB sound card not detected
UpgradeStatus: Upgraded to xenial on 2016-11-02 (0 days ago)
dmi.bios.date: 09/08/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MM71.88Z.0220.B06.1509081252
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-35C5E08120C7EEAF
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini7,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-35C5E08120C7EEAF
dmi.modalias: 
dmi:bvnAppleInc.:bvrMM71.88Z.0220.B06.1509081252:bd09/08/2015:svnAppleInc.:pnMacmini7,1:pvr1.0:rvnAppleInc.:rnMac-35C5E08120C7EEAF:rvrMacmini7,1:cvnAppleInc.:ct10:cvrMac-35C5E08120C7EEAF:
dmi.product.name: Macmini7,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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

Title:
  USB sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I'm trying to use earphone+mic: Koss CS/100 USB which has been working fine 
until a month ago.
  All of sudden it doesn't list in the devices. The earphones works on other 
system (windows) fine.

  I see this in the dmesg when it's plugged in:

  [ 5057.286942] usb 1-7.4: new full-speed USB device number 22 using xhci_hcd
  [ 5057.359006] usb 1-7.4: device descriptor read/64, error -32
  [ 5057.535048] usb 1-7.4: device descriptor read/64, error -32
  [ 5057.711027] usb 1-7.4: new full-speed USB device number 23 using xhci_hcd
  [ 5057.783036] usb 1-7.4: device descriptor read/64, error -32
  [ 5057.958967] usb 1-7.4: device descriptor read/64, error -32
  [ 5058.134906] usb 1-7.4: new full-speed USB device number 24 using xhci_hcd
  [ 5058.135027] usb 1-7.4: Device not responding to setup address.
  [ 5058.339050] usb 1-7.4: Device not responding to setup address.
  [ 5058.542862] usb 1-7.4: device not accepting address 24, error -71
  [ 5058.614858] usb 1-7.4: new full-speed USB device number 25 using xhci_hcd
  [ 5058.615020] usb 1-7.4: Device not responding to setup address.
  [ 5058.818942] usb 1-7.4: Device not responding to setup address.
  [ 5059.022808] usb 1-7.4: device not accepting address 25, error -71
  [ 5059.022873] usb 1-7-port4: unable to enumerate USB device

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  miro   1801 F pulseaudio
   /dev/snd/controlC1:  miro   1801 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov  2 16:43:11 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-11 (356 days ago)
  InstallationMedia: U

[Touch-packages] [Bug 1634152] Re: Driver video doesn't work properly after Upgrade (16.04 LTS)

[Paolo]

SOLVED!!!

http://askubuntu.com/questions/436374/how-to-get-rid-of-the-gallium-0-4
-on-llvmpipe-llvm-0x300-driver-intel-needed

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

Title:
  Driver video doesn't work properly after Upgrade (16.04 LTS)

Status in xorg package in Ubuntu:
  New

Bug description:
  After the last automatic upgrade (kernel?), the system suggested a restart to 
finalize the installation.
  Immediately after the reboot, the graph login page worked at 640x480. Using 
"xdiagnose", checking (disabling) all, I was able to set the resolution 
1280x1024, but no more capable to manage the dual-screen as before: in the 
"Monitor" configuration page, I see only one "Built-in Display" instead the two 
Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been 
changed.

  My PC is an Acer Veriton X4610G
  CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4
  RAM: 4GiB (128MiB VGA shared)

  I use an UBUNTU 16.04 LTS 64-bit

  Thanks for any feedback!
  Paolo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 17 15:39:54 2016
  DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0492]
  InstallationDate: Installed on 2015-05-15 (521 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp.
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Veriton X4610G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat 
vesafb.invalid=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton X4610G
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton X4610G
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 17 15:32:10 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 40189] Re: autofs needs to be restarted to pick up some shares

[Ing . Radomír Polách]

This still happens to us on 16.04.1 lTS with ldap (+ autofs + nfs).

Why is not fixed?

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

Title:
  autofs needs to be restarted to pick up some shares

Status in autofs package in Ubuntu:
  Invalid
Status in autofs5 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  I am using autofs to access shares on a Windows XP machine from a
  Kubuntu AMD64 machine.  The problems applies in both Breezy and
  Dapper.

  EDIT:  confirmed with similar configuration on Intrepid with a NetApp
  filer hosting NFS.  Server OS removed from summary.

  When I first try to access the mount point via cd or in Konqueror it
  does not exist.  However,  if I then restart autofs
  (/etc/init.d/autofs restart) everythin then works OK.  My config files
  are:

  auto.master

  #
  # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
  #
  # Sample auto.master file
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # For details of the format look at autofs(5).
  #/misc/etc/auto.misc --timeout=60
  #/misc/etc/auto.misc
  #/net /etc/auto.net

  /petunia /etc/petunia.misc --timeout=60

  
  petunia.misc

  #
  # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
  #
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # Details may be found in the autofs(5) manpage

  cd  -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom

  tony  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/tony
  chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/chris
  shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/SharedDocs
  linuxbackups  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/linuxbackups

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

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

[Touch-packages] [Bug 1616517] Re: whoopsie does not send fields from some package management application crashes

[Brian Murray]

Here's a crash report in the Error Tracker w/ AptOrdering which is one
of the fields that was added.

https://errors.ubuntu.com/oops/2533828c-a0b5-11e6-b4ea-fa163ebeb28a

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  whoopsie does not send fields from some package management application
  crashes

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Trusty:
  Fix Released
Status in whoopsie source package in Xenial:
  Fix Committed

Bug description:
  The package hook for update-manager and aptdaemon add information like
  /var/log/apt/term.log and /var/log/apt/history.log that would be
  useful in debugging crashes from those applications.  However, those
  files can be larger than 1 KB so whoopsie does not send them to the
  Error Tracker.  We should be sending those fields along.

  Test Case
  -
  1) launch update-manager
  2) kill -11 the update-manager process
  3) locate the update-manager .crash file and observe DpkgHistoryLog.txt in it
  4) send crash report to Error Tracker (look for .uploaded file)
  5) view crash report in Error Tracker (find OOPS ID by looking at syslog / 
whoopsie status)
  6) observe DpkgHistoryLog.txt not in it

  With the version of the package from -proposed DpkgHistoryLog.txt
  should appear on the OOPS page for the crash that was sent.

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

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

[Touch-packages] [Bug 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

[Jim Hodapp]

Will get to landing the QtMultimedia patch sometime soon.

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

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

Status in Canonical System Image:
  New
Status in gst-plugins-bad0.10 package in Ubuntu:
  In Progress
Status in qtmultimedia-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Hi, as described in QTBUG-50567 [1], qtmultimedia doesn't support opus
  audio codec so for example we cannot record Telegram voice messages (
  bug #1460464 and bug #1375179 ).

  I patched qtmultimedia adding the support for audio/x-opus codec
  through opusdec encoder in qtmultimedia, then I found qtmultimedia
  5.4.1 (shipped with Ubuntu Phone vivid) is built against gstreamer0.10
  and, as gstreamer0.10-plugins-bad packages is not installed by
  default, opusdec encoder is not available.

  I'm working on this bug, I created it to track the progress, in order
  to add opus support I have to:

  1 - create a new gstreamer0.10-opus package containing only the
  opusdec plugin: I don't know whether I have to create a new source
  package containing opusdec sources or only a new .deb package
  (generated from gst-plugins-bad0.10 sources). I'm working on the
  latter as gst-plugins-bad0.10 package requires work in any ways.

  2 - properly patch qtmultimedia source, I'm attaching a 
working-but-needs-cleanup patch. I think some opus declarations in the attached 
patch can be avoided, but I haven't had time to work on it so I'm attaching the 
patch I tested (requires gstreamer0.10-plugins-bad).
  I don't know if qtmultimedia xenial/yakkety versions requires the patch too, 
I haven't checked them yet.

  [1] https://bugreports.qt.io/browse/QTBUG-50567

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630399/+subscriptions

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

[Touch-packages] [Bug 1615209] Re: ip crashes after a few times adding and removing network namespaces

[Robie Basak]

** Changed in: iproute2 (Ubuntu)
   Status: In Progress => Triaged

** Changed in: iproute2 (Ubuntu)
   Importance: Undecided => High

** Tags added: server-next

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

Title:
  ip crashes after a few times adding and removing network namespaces

Status in iproute2 package in Ubuntu:
  Triaged

Bug description:
  # which ip
  /sbin/ip
  # valgrind ip netns add black2
  ==22804== Memcheck, a memory error detector
  ==22804== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==22804== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==22804== Command: ip netns add black2
  ==22804== 
  ==22804== Invalid write of size 1
  ==22804==at 0x4031F43: memcpy (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==22804==by 0x8059C83: ??? (in /bin/ip)
  ==22804==by 0x805AF9A: netns_map_init (in /bin/ip)
  ==22804==by 0x805B01F: do_netns (in /bin/ip)
  ==22804==by 0x804DF67: ??? (in /bin/ip)
  ==22804==by 0x804DA11: main (in /bin/ip)
  ==22804==  Address 0x4227094 is 0 bytes after a block of size 28 alloc'd
  ==22804==at 0x402D17C: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==22804==by 0x8059C5E: ??? (in /bin/ip)
  ==22804==by 0x805AF9A: netns_map_init (in /bin/ip)
  ==22804==by 0x805B01F: do_netns (in /bin/ip)
  ==22804==by 0x804DF67: ??? (in /bin/ip)
  ==22804==by 0x804DA11: main (in /bin/ip)
  ==22804== 
  Cannot create namespace file "/var/run/netns/black2": File exists
  ==22804== 
  ==22804== HEAP SUMMARY:
  ==22804== in use at exit: 28 bytes in 1 blocks
  ==22804==   total heap usage: 2 allocs, 1 frees, 32,824 bytes allocated
  ==22804== 
  ==22804== LEAK SUMMARY:
  ==22804==definitely lost: 0 bytes in 0 blocks
  ==22804==indirectly lost: 0 bytes in 0 blocks
  ==22804==  possibly lost: 0 bytes in 0 blocks
  ==22804==still reachable: 28 bytes in 1 blocks
  ==22804== suppressed: 0 bytes in 0 blocks
  ==22804== Rerun with --leak-check=full to see details of leaked memory
  ==22804== 
  ==22804== For counts of detected and suppressed errors, rerun with: -v
  ==22804== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

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

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

[Touch-packages] [Bug 1309433] Re: account-console crash

[Alberto Mardegan]

** Also affects: webapps-sprint
   Importance: Undecided
   Status: New

** Changed in: webapps-sprint
   Status: New => In Progress

** Changed in: webapps-sprint
   Importance: Undecided => Low

** Changed in: webapps-sprint
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: webapps-sprint
Milestone: None => sprint-27

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

Title:
  account-console crash

Status in Online Accounts: Account plugins:
  In Progress
Status in webapps-sprint:
  In Progress
Status in account-plugins package in Ubuntu:
  In Progress

Bug description:
  jmax@jmax-CKR2 ~% account-console show 1

  (process:4718): accounts-glib-WARNING **: Unable to load account 1
  Traceback (most recent call last):
    File "/usr/bin/account-console", line 36, in show_account
  print >> sys.stderr, 'Account "%s" not found' % args.account
  TypeError: unsupported operand type(s) for >>: 'builtin_function_or_method' 
and '_io.TextIOWrapper'

  and I have to type Ctrl C

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1309433/+subscriptions

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

[Touch-packages] [Bug 1636827] Re: wireless network list disappears

[Juraj]

1) No, it definitely did not occur in 14.04. I believe it's a regression.
2) James Ferguson  noted here 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590985/comments/7) that 
he gets the bug after resuming from suspend. I will update later with more 
specifics, but I consistently get the bug when running Ubuntu for some time (an 
hour, couple of hours?), perhaps doing a suspend. I get the same behaviour like 
James that it's still connected, but network-manager doesn't display the active 
connection nor other connections.
3) Also will update later.

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

Title:
  wireless network list disappears

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  On Thinkpad W520, wireless network list disappears occasionally.
  Restarting the network manager service fixes the issue. Please see the
  following bug for more information:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590985

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 26 13:57:59 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-12 (105 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp0s25  ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  
LARICS  3ad4f968-8fd1-4759-a3bc-746cb364628e  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   wlp3s0   wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
FERwlan 3f100dda-2c1b-46d6-83af-064c33b51c5a  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636827/+subscriptions

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

[Touch-packages] [Bug 1638590] [NEW] package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Héctor Miguel Villa Loyola]

Public bug reported:

no

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Wed Nov  2 03:56:47 2016
DuplicateSignature:
 package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2
 Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
 Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.
 dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-04-04 (211 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: unity-scopes-api
Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)

** Affects: unity-scopes-api (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 unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1638590

Title:
  package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  no

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 03:56:47 2016
  DuplicateSignature:
   package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2
   Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-04 (211 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1638590/+subscriptions

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Scott Moser]

I've just took a read of the code that landed. Over all, the new code is
much more suitable for SRU. I think it still has some issues though.

a.) we use 'grep' and 'cat' extensively in the new code. Most could be
replaced with case statements or other shell builtin such as 'case' and
'read' and avoid subprocesses and their overhead. This is not broken,
but slower boot as a result.

b.) ipconfig would set the 'hostname' in the dhcp request to the value
in the 5th token of ip=. I do not believe that is being done now.

c.) at least 1 dhclient process will end up running after exiting the
initramfs exits, and won't' have access to its open files. I'm not sure
what the behavior will be, but its possible that this process could
decide at re-lease time to take the interface down since it would not
have its lease database around. I say at least due to bug 1633619. If we
ever re-try, I suspect we'll have one for each loop.

Do we know what happens to this uprooted dhclient process?

d.) The ipconfig path that was left on will now have 'sleep's inserted
and will as a result take much longer than necessary if it ever does not
get a lease on the first try.

'b' is definitely a change in behavior. We really need to know what
happens on 'c', and 'd' seems like it should be fixed as it negatively
affects the 'ip=' path.

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Triaged
Status in isc-dhcp source package in Xenial:
  In Progress
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  In Progress
Status in initramfs-tools source package in Yakkety:
  In Progress
Status in isc-dhcp source package in Yakkety:
  In Progress
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  In Progress
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) 

  
  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

[Jorge Niedbalski]

** No longer affects: libnl3 (Ubuntu Precise)

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  libnl can only enable up to 30 VFs even if the PF supports up to 63
  VFs in an Openstack SRIOV configuration.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4.

  When trying to enable a guest with more than 30 VFs attached, the
  following error is returned:

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

  [Test Case]

   1) Edit /etc/default/grub.

  GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63"

   2) Update grub and reboot the machine.

  $ sudo update-grub

   3) Check that the virtual functions are available.

  $ sudo lspci|grep -i eth | grep -i virtual | wc -l
  126

   4) Create a KVM guest.

  $ sudo uvt-kvm create guest1 release=trusty

   5) List the VF devices.

  $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed
  's/\:/\_/g' | sed 's/\./\_/g' > devices.txt

   6) Get the libvirt node device.

  $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list |
  grep $device; done > pci_devices.txt

   7) Generate the XML config for each device.

  $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh
  nodedev-dumpxml $d > devices/$d.xml; done

   8) Save and Run the following script.
  (http://pastebin.ubuntu.com/23374186/)

  $ sudo python generate-interfaces.py |grep address | wc -l

   9) Finally attach the devices to the guest.

  $ sudo for i in $(seq 0 63); do virsh attach-device guest1 
./interfaces/$i.xml --config; done
  Device attached successfully
  [...]

  Device attached successfully
  Device attached successfully

   10) Then destroy/start the guest again, at this point the error is
  reproduced.

  $ sudo virsh destroy guest1
  Domain guest1 destroyed

  $ sudo virsh start guest1

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

  [Regression Potential]

   * None identified.

  [Other Info]

   * Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626

   * A workaround is to install a newer library release.

  $ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  $ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  $ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  $ dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  $ dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  $ dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

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

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

[Touch-packages] [Bug 1638586] [NEW] package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Héctor Miguel Villa Loyola]

Public bug reported:

no se instalo al actualizar version

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Wed Nov  2 03:56:47 2016
DuplicateSignature:
 package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2
 Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
 Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.
 dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-04-04 (211 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: unity-scopes-api
Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)

** Affects: unity-scopes-api (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 unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1638586

Title:
  package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  no se instalo al actualizar version

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 03:56:47 2016
  DuplicateSignature:
   package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2
   Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-04 (211 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1638586/+subscriptions

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

[Touch-packages] [Bug 1638535] Re: liblzo.a (static library) fails to link on 16.10, AMD64 (needs `-fPIC`)

[Brian Murray]

** Tags added: yakkety

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

Title:
  liblzo.a (static library) fails to link on 16.10, AMD64 (needs
  `-fPIC`)

Status in lzo2 package in Ubuntu:
  New

Bug description:
  See this bug report for details:

  https://github.com/opentoonz/opentoonz/issues/866

  When linking with `liblzo.a`, the error:

 Build error liblzo2.a(lzo1x_1.o): relocation R_X86_64_PC32 against
  symbol `memset@@GLIBC_2.2.5' can not be used when making a shared
  object; recompile with -fPIC

  occurs, this wasn't a problem on Ubuntu 16.04.

  To test this: following the build steps here can redo the problem:
  https://github.com/opentoonz/opentoonz/blob/master/doc/how_to_build_linux.md

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

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

[Touch-packages] [Bug 1612299] Re: [MIR] ubuntu-system-settings-online-accounts

[Alberto Mardegan]

** Changed in: webapps-sprint
   Status: Triaged => Fix Released

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

Title:
  [MIR] ubuntu-system-settings-online-accounts

Status in webapps-sprint:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has both unit tests and autopkgtests

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libsystemsettings1, ubuntu-system-settings (bug #1612280)
   * qml-module-ubuntu-onlineaccounts (same source package as this one)
   * libonline-accounts-daemon1, qml-module-ubuntu-onlineaccounts (bug #1613575)
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)

  [Standards compliance]
   * This package uses qmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1612299/+subscriptions

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

[Touch-packages] [Bug 1614108] Re: QStandardPaths::RuntimeLocation returns empty string under pbuilder

[Alberto Mardegan]

** Changed in: webapps-sprint
   Status: In Progress => Fix Released

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

Title:
  QStandardPaths::RuntimeLocation returns empty string under pbuilder

Status in webapps-sprint:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  The unit tests for ubuntu-system-settings-online-accounts are failing
  when run under pbuilder:

  ==
  task-0: * Start testing of UiProxyTest *
  task-0: Config: Using QtTest library 5.5.1, Qt 5.5.1 
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.3.1 
20160519)
  task-0: PASS : UiProxyTest::initTestCase()
  task-0: PASS : UiProxyTest::testInit()
  task-0: QWARN : UiProxyTest::testRequest(success) QStandardPaths: wrong 
ownership on runtime directory /run/user/1001, -2 instead of 1234
  task-0: QWARN : UiProxyTest::testRequest(success) Couldn't setup IPC socket
  task-0: FAIL! : UiProxyTest::testRequest(success) 
'(!remoteProcesses.isEmpty())' returned FALSE. ()
  task-0: Loc: [tst_ui_proxy.cpp(319)]
  ==

  I've debugged the issue, and I've verified that
  QStandardPaths::writableLocation(QStandardPaths::RuntimeLocation) is
  returning an empty string. Although it's documented that in some
  systems that function can return NULL, it would be better if it didn't
  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1614108/+subscriptions

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[MAAS Lander]

** Changed in: maas
   Status: In Progress => Fix Committed

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Triaged
Status in isc-dhcp source package in Xenial:
  In Progress
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  In Progress
Status in initramfs-tools source package in Yakkety:
  In Progress
Status in isc-dhcp source package in Yakkety:
  In Progress
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  In Progress
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) 

  
  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1633619] Re: dhclient -1 exits 0 when no lease found

[Scott Moser]

Steve,
Good sleuthing.

Bug 974284 has good info in it.

This is definitely tricky.
I think we have the following cases to consider and may be at odds.
a.) dhclient -1 should exit failure as documented.
b.) we need a reliable point in boot where all static networking is configured.
c.) Ill timed reboot (or recovery from lab power failure)
a system is configured for dhcp is rebooted while the dhcp server is 
unavailable.
It seems better for this system to keep trying to get an IP address as 
otherwise
the system will be offline forever.  
d.) Any dhcp server downtime and failed lease renewal.
a system is configured for dhcp and initially succeeds, but while re-trying 
a lease
the dhcp server is down for scheduled maintenance.  A failure to release 
here
results in system offline if dhclient takes down the interface.
This is mentioned at 
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/838968/comments/11

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

Title:
  dhclient -1 exits 0 when no lease found

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  I've tried this in containers of xenial, trusty and yakkety.

  i've created a lxc network that does not have dhcp4.

  See https://github.com/lxc/lxd/issues/2481 for some info on how to do
  that.

  Then, I launch an instance:

  $ lxc launch ubuntu-daily:xenial --profile=sm-test-profile2 x1
  % killall dhclient
  % dhclient -r eth0
  % dhclient -1 -v eth0
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/eth0/00:16:3e:b8:e6:70
  Sending on   LPF/eth0/00:16:3e:b8:e6:70
  Sending on   Socket/fallback
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xc08cb53c)

  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0xc08cb53c)
  DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0xc08cb53c)
  ..
  No DHCPOFFERS received.
  No working leases in persistent database - sleeping.

  % echo $?
  0
  % ps axw | grep dhcl
356 ?Ss 0:00 dhclient -1 -v eth0

  
  the man page says of the '-1' option:
     -1 Try to get a lease once.  On  failure  exit  with  code  2.   In
    DHCPv6 this sets the maximum duration of the initial exchange to
    timeout (from dhclient.conf with a default of sixty seconds).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 16:59:45 2016
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633619/+subscriptions

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

[Touch-packages] [Bug 1473762] Re: error running non-shared postrotate script for /var/log/samba/log.nmbd

[Robie Basak]

*** This bug is a duplicate of bug 1385868 ***
https://bugs.launchpad.net/bugs/1385868

This was reported against Vivid in July 2015, and Vivid was EOL in Feb
2016 and never fixed in bug 1385868. So I think this is a duplicate of
bug 1385868 and is now fixed in Wily, Xenial, Yakkety and Zesty. If this
is incorrect, please comment with the release you tested and what
package version of samba you have verified does not work.

** This bug has been marked a duplicate of bug 1385868
   Samba logrotate script uses invalid argument to /etc/init.d/nmdb

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

Title:
  error running non-shared postrotate script for /var/log/samba/log.nmbd

Status in logrotate package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed

Bug description:
  /etc/cron.daily/logrotate is reporting:

  Usage: /etc/init.d/nmbd {start|stop|restart|force-reload|status}
  error: error running non-shared postrotate script for /var/log/samba/log.nmbd 
of '/var/log/samba/log.nmbd '
  run-parts: /etc/cron.daily/logrotate exited with return code 1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: logrotate 3.8.7-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sun Jul 12 20:14:20 2015
  InstallationDate: Installed on 2014-11-20 (234 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: logrotate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1610206] Re: "Web authentication for Google" WebView appears on login

[David Barth]

** Changed in: webapps-sprint
Milestone: sprint-26 => sprint-27

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

Title:
  "Web authentication for Google" WebView appears on login

Status in webapps-sprint:
  In Progress
Status in signon-ui package in Ubuntu:
  Incomplete

Bug description:
  Starting today, when I log in a "Web authentication for Google" web
  view (screenshot attached).

  It's probably because I have to re-authenticate to Google - but the
  web view doesn't tell me what it's asking for, and it is a bit strange
  to just see a dialog on login.

  mardy thinks that it's somehow failing to show the usual notification,
  and falling back to the path which shows the dialog.

  In the attached syslog, pid 7936 is my dbus-daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: signon-ui 0.17+16.04.20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  5 12:14:25 2016
  InstallationDate: Installed on 2012-10-07 (1397 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: signon-ui
  UpgradeStatus: Upgraded to yakkety on 2013-05-07 (1186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1610206/+subscriptions

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

[Touch-packages] [Bug 1614108] Re: QStandardPaths::RuntimeLocation returns empty string under pbuilder

[David Barth]

** Changed in: webapps-sprint
Milestone: sprint-26 => sprint-27

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

Title:
  QStandardPaths::RuntimeLocation returns empty string under pbuilder

Status in webapps-sprint:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  The unit tests for ubuntu-system-settings-online-accounts are failing
  when run under pbuilder:

  ==
  task-0: * Start testing of UiProxyTest *
  task-0: Config: Using QtTest library 5.5.1, Qt 5.5.1 
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.3.1 
20160519)
  task-0: PASS : UiProxyTest::initTestCase()
  task-0: PASS : UiProxyTest::testInit()
  task-0: QWARN : UiProxyTest::testRequest(success) QStandardPaths: wrong 
ownership on runtime directory /run/user/1001, -2 instead of 1234
  task-0: QWARN : UiProxyTest::testRequest(success) Couldn't setup IPC socket
  task-0: FAIL! : UiProxyTest::testRequest(success) 
'(!remoteProcesses.isEmpty())' returned FALSE. ()
  task-0: Loc: [tst_ui_proxy.cpp(319)]
  ==

  I've debugged the issue, and I've verified that
  QStandardPaths::writableLocation(QStandardPaths::RuntimeLocation) is
  returning an empty string. Although it's documented that in some
  systems that function can return NULL, it would be better if it didn't
  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1614108/+subscriptions

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

[Touch-packages] [Bug 1560086] Re: cannot download files with no destination app from webapps

[David Barth]

** Changed in: webapps-sprint
Milestone: sprint-26 => sprint-27

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

Title:
  cannot download files with no destination app from webapps

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in The Webapps-core project:
  New
Status in webapps-sprint:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Using the webbrowser-app I can download any file, and will be prompted
  to open in an app (if apps that support that content-type exist on the
  system) or to download the file in the browser. The same behavior
  should be available webapps but is not.

  Steps to reproduce:
  - Open Gmail webapp
  - Open a message that has an attachment of a file of unsupported type (like a 
.tar, .click, etc)
  - click on the file to download

  Expected results:
  - I should be prompted to open the file in supported app or to download
  - If I choose download the file should be downloaded into ~/Downloads by the 
webbrowser-app

  Actual results:
  - I am told that no apps exist to support this type of file and am not 
allowed to download it

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1560086/+subscriptions

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

[Touch-packages] [Bug 1610206] Re: "Web authentication for Google" WebView appears on login

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/signon-ui/signon-ui-ubuntu-zesty-2135

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

Title:
  "Web authentication for Google" WebView appears on login

Status in webapps-sprint:
  In Progress
Status in signon-ui package in Ubuntu:
  Incomplete

Bug description:
  Starting today, when I log in a "Web authentication for Google" web
  view (screenshot attached).

  It's probably because I have to re-authenticate to Google - but the
  web view doesn't tell me what it's asking for, and it is a bit strange
  to just see a dialog on login.

  mardy thinks that it's somehow failing to show the usual notification,
  and falling back to the path which shows the dialog.

  In the attached syslog, pid 7936 is my dbus-daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: signon-ui 0.17+16.04.20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  5 12:14:25 2016
  InstallationDate: Installed on 2012-10-07 (1397 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: signon-ui
  UpgradeStatus: Upgraded to yakkety on 2013-05-07 (1186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1610206/+subscriptions

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

[Touch-packages] [Bug 1610206] Re: "Web authentication for Google" WebView appears on login

[Alberto Mardegan]

** Also affects: webapps-sprint
   Importance: Undecided
   Status: New

** Changed in: webapps-sprint
Milestone: None => sprint-26

** Changed in: webapps-sprint
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: webapps-sprint
   Status: New => In Progress

** Changed in: webapps-sprint
   Importance: Undecided => Critical

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

Title:
  "Web authentication for Google" WebView appears on login

Status in webapps-sprint:
  In Progress
Status in signon-ui package in Ubuntu:
  Incomplete

Bug description:
  Starting today, when I log in a "Web authentication for Google" web
  view (screenshot attached).

  It's probably because I have to re-authenticate to Google - but the
  web view doesn't tell me what it's asking for, and it is a bit strange
  to just see a dialog on login.

  mardy thinks that it's somehow failing to show the usual notification,
  and falling back to the path which shows the dialog.

  In the attached syslog, pid 7936 is my dbus-daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: signon-ui 0.17+16.04.20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  5 12:14:25 2016
  InstallationDate: Installed on 2012-10-07 (1397 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: signon-ui
  UpgradeStatus: Upgraded to yakkety on 2013-05-07 (1186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1610206/+subscriptions

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

[Touch-packages] [Bug 1636292] Re: package openssh-sftp-server 1:6.6p1-2ubuntu2.8 failed to install/upgrade: package openssh-sftp-server is already installed and configured

[dino99]

*** This bug is a duplicate of bug 1635280 ***
https://bugs.launchpad.net/bugs/1635280

** This bug has been marked a duplicate of bug 1635280
   [ BUG 541595 IS BACK ] package is already installed and configured

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

Title:
  package openssh-sftp-server 1:6.6p1-2ubuntu2.8 failed to
  install/upgrade: package openssh-sftp-server is already installed and
  configured

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  after sudo apt-get install openssh-server

  this crashes.
  Ubuntu 14.04 gnome3 version

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: openssh-sftp-server 1:6.6p1-2ubuntu2.8
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Mon Oct 24 21:10:57 2016
  DuplicateSignature: package:openssh-sftp-server:1:6.6p1-2ubuntu2.8:package 
openssh-sftp-server is already installed and configured
  ErrorMessage: package openssh-sftp-server is already installed and configured
  InstallationDate: Installed on 2016-10-12 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: openssh
  Title: package openssh-sftp-server 1:6.6p1-2ubuntu2.8 failed to 
install/upgrade: package openssh-sftp-server is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1638565] [NEW] HP Envy 34c resolution maxes out at 1920x1200

[Luis Arias]

Public bug reported:

Using get-edid, the best resolution is "Mode 0" below, but this doesn't
show up in the Display systems settings panel.

This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 5
No EDID on bus 7
No EDID on bus 8
No EDID on bus 9
No EDID on bus 10
2 potential busses found: 4 6
Will scan through until the first EDID is found.
Pass a bus number as an option to this program to go only for that one.
256-byte EDID successfully retrieved from i2c bus 4
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
Identifier "HP ENVY 34c"
ModelName "HP ENVY 34c"
VendorName "HWP"
# Monitor Manufactured week 22 of 2015
# EDID version 1.3
# Digital Display
DisplaySize 800 330
Gamma 2.20
Option "DPMS" "true"
Horizsync 27-90
VertRefresh 24-60
# Maximum pixel clock is 250MHz
#Not giving standard mode: 1920x1080, 60Hz
#Not giving standard mode: 1600x900, 60Hz
#Not giving standard mode: 1280x720, 60Hz
#Not giving standard mode: 1920x1200, 60Hz
#Not giving standard mode: 1680x1050, 60Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1600x1200, 60Hz
#Not giving standard mode: 1280x1024, 60Hz

#Extension block found. Parsing...
Modeline"Mode 17" 241.50 2560 2608 2640 2720 1440 1443 1448 
1481 +hsync -vsync 
Modeline"Mode 0" 196.25 3440 3600 3952 4464 1440 1443 1453 1468 
+hsync -vsync 
Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 3" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 
+hsync +vsync
Modeline"Mode 4" 74.250 1280 1390 1420 1650 720 725 730 750 
+hsync +vsync
Modeline"Mode 5" 74.250 1280 1720 1760 1980 720 725 730 750 
+hsync +vsync
Modeline"Mode 6" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 9" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 10" 25.200 640 656 752 800 480 490 492 525 -hsync 
-vsync
Modeline"Mode 11" 74.250 1920 2008 2052 2200 1080 1082 1087 
1125 +hsync +vsync interlace
Modeline"Mode 12" 74.250 1920 2448 2492 2640 1080 1082 1089 
1125 +hsync +vsync interlace
Modeline"Mode 13" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 14" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 15" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 16" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 18" 198.00 2560 2808 2852 3000 1080 1084 1089 
1100 +hsync +vsync 
Modeline"Mode 19" 185.62 2560 3108 3152 3300 1080 1084 1089 
1125 +hsync +vsync 
Modeline"Mode 20" 154.24 1920 1968 2000 2080 1200 1203 1209 
1235 +hsync -vsync 
Option "PreferredMode" "Mode 17"
EndSection

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
Uname: Linux 4.8.0-26-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.98  Mon Sep 19 17:31:03 
PDT 2016
 GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Nov  2 14:22:07 2016
DistUpgraded: 2016-10-29 06:09:22,344 DEBUG icon theme changed, re-reading
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.8.0-26-lowlatency, x86_64: installed
 nvidia-340, 340.98, 4.8.0-26-lowlatency, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05fe]
   Subsystem: Dell GK107M [GeForce GT 750M] [102

[Touch-packages] [Bug 1610206] Re: "Web authentication for Google" WebView appears on login

[Alberto Mardegan]

** Branch linked: lp:~mardy/signon-ui/auth-1610206

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

Title:
  "Web authentication for Google" WebView appears on login

Status in webapps-sprint:
  In Progress
Status in signon-ui package in Ubuntu:
  Incomplete

Bug description:
  Starting today, when I log in a "Web authentication for Google" web
  view (screenshot attached).

  It's probably because I have to re-authenticate to Google - but the
  web view doesn't tell me what it's asking for, and it is a bit strange
  to just see a dialog on login.

  mardy thinks that it's somehow failing to show the usual notification,
  and falling back to the path which shows the dialog.

  In the attached syslog, pid 7936 is my dbus-daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: signon-ui 0.17+16.04.20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  5 12:14:25 2016
  InstallationDate: Installed on 2012-10-07 (1397 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: signon-ui
  UpgradeStatus: Upgraded to yakkety on 2013-05-07 (1186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1610206/+subscriptions

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

[Touch-packages] [Bug 1633479] Please test proposed package

[Chris J Arges]

Hello Scott, or anyone else affected,

Accepted isc-dhcp into yakkety-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.3.3-5ubuntu15.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Precise:
  Fix Committed
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/

   Can't bind to dhcp address: Cannot assign requested address
   Please make sure there is no other dhcp server
   running and that there's no entry for dhcp or
   bootp in /etc/inetd.conf.   Also make sure you
   are not running HP JetAdmin software, which
   includes a bootp server.

   If you think you have received this message due to a bug rather
   than a configuration issue please read the section on submitting
   bugs on either our web page at www.isc.org or in the README file
   before submitting a bug.  These pages explain the proper
   process and the information we find helpful for debugging..
   $ echo $?
   1

  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
   * bug 1633562: 'dhclient -6 -S' does not bring interface up 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+subscriptions

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

[Touch-packages] [Bug 1636292] Re: package openssh-sftp-server 1:6.6p1-2ubuntu2.8 failed to install/upgrade: package openssh-sftp-server is already installed and configured

[Robie Basak]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

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

Title:
  package openssh-sftp-server 1:6.6p1-2ubuntu2.8 failed to
  install/upgrade: package openssh-sftp-server is already installed and
  configured

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  after sudo apt-get install openssh-server

  this crashes.
  Ubuntu 14.04 gnome3 version

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: openssh-sftp-server 1:6.6p1-2ubuntu2.8
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Mon Oct 24 21:10:57 2016
  DuplicateSignature: package:openssh-sftp-server:1:6.6p1-2ubuntu2.8:package 
openssh-sftp-server is already installed and configured
  ErrorMessage: package openssh-sftp-server is already installed and configured
  InstallationDate: Installed on 2016-10-12 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: openssh
  Title: package openssh-sftp-server 1:6.6p1-2ubuntu2.8 failed to 
install/upgrade: package openssh-sftp-server is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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