[Touch-packages] [Bug 1674058] [NEW] package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Ashanti Monts]

Public bug reported:

I tried to install updates for the system upgrades. It doesn't seem to
be installing properly.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3.2
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Sat Mar 18 23:05:35 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-05-26 (297 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.18
SourcePackage: util-linux
Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  I tried to install updates for the system upgrades. It doesn't seem to
  be installing properly.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sat Mar 18 23:05:35 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-26 (297 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1673491] Re: [Zesty] libnl3 Segmentation fault in sriov environments

[Talat Batheesh]

Thank you, 
The fix is working, i validate it with machine that has sriov environment.
Dimitri, could you please add this fixes to the zesty release ? 

Thanks, 
Talat

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

Title:
  [Zesty] libnl3 Segmentation fault in sriov environments

Status in libnl3 package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  in Ubuntu 17.04 we can't open a virt-manager, we see sefault

  This issue happen when we update from kernel 4.10.0-9-generic to
  4.10.0-11-generic

  root@:~# /usr/sbin/libvirtd
  Segmentation fault (core dumped)   

  root@:~# gdb /usr/sbin/libvirtd ./core 
  GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
  Copyright (C) 2017 Free Software Foundation, Inc.  
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.   
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
  and "show warranty" for details. 
  This GDB was configured as "x86_64-linux-gnu".   
  Type "show configuration" for configuration details. 
  For bug reporting instructions, please see:  
  . 
  Find the GDB manual and other documentation resources online at: 
  .
  For help, type "help".   
  Type "apropos word" to search for commands related to "word"...  
  Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
  [New LWP 4232]
  [New LWP 4216]
  [New LWP 4219]
  [New LWP 4218]
  [New LWP 4231]
  [New LWP 4215]
  [New LWP 4220]
  [New LWP 4224]
  [New LWP 4221]
  [New LWP 4223]
  [New LWP 4222]
  [New LWP 4217]
  [New LWP 4225]
  [New LWP 4227]
  [New LWP 4230]
  [New LWP 4229]
  [New LWP 4228]
  [Thread debugging using libthread_db enabled] 
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/libvirtd'.   
  Program terminated with signal SIGSEGV, Segmentation fault.   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  [Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]  
   
  (gdb) where   
   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  #1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
  #2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #3  0x7f980bfb770b in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #4  0x7f980bfbdc1c in nl_recvmsgs_report () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #5  0x7f980bfbe049 in nl_recvmsgs () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #6  0x7f980bfb6aab in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #7  0x7f980bfb763d in nl_cache_pickup () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #8  0x7f980bfb7871 in nl_cache_refill () from 

[Touch-packages] [Bug 1674072] [NEW] fluidsynth crashed with SIGSEGV in jack_port_get_buffer()

[David Kastrup]

Public bug reported:

Just tried starting it from the command line with a midi file.  Jack
available but not running at the time I tried this.

I cannot vouch whether this was started with or without pasuspender: I
tried both since without pasuspender fluidsynth (or jack) complained
about Pulseaudio hogging the device.  It could have crashed after the
complaint, or it could have crashed independently without such a
complaint.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: fluidsynth 1.1.6-4
ProcVersionSignature: Ubuntu 4.10.0-11.13-lowlatency 4.10.1
Uname: Linux 4.10.0-11-lowlatency x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: i386
CurrentDesktop: MATE
Date: Sun Mar 19 09:28:47 2017
ExecutablePath: /usr/bin/fluidsynth
InstallationDate: Installed on 2011-10-14 (1982 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: fluidsynth /home/username/scores/tabber.midi
SegvAnalysis:
 Segfault happened at: 0xf72d9194 :mov
0xc(%esi),%edx
 PC (0xf72d9194) ok
 source "0xc(%esi)" (0x000c) not located in a known VMA region (needed 
readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: fluidsynth
StacktraceTop:
 jack_port_get_buffer () from /usr/lib/i386-linux-gnu/libjack.so.0
 fluid_jack_driver_process () from /usr/lib/i386-linux-gnu/libfluidsynth.so.1
 ?? () from /usr/lib/i386-linux-gnu/libjack.so.0
 start_thread (arg=0xf6809b40) at pthread_create.c:333
 clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113
Title: fluidsynth crashed with SIGSEGV in jack_port_get_buffer()
UpgradeStatus: Upgraded to zesty on 2017-01-05 (72 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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


** Tags: apport-crash i386 zesty

** 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 fluidsynth in Ubuntu.
https://bugs.launchpad.net/bugs/1674072

Title:
  fluidsynth crashed with SIGSEGV in jack_port_get_buffer()

Status in fluidsynth package in Ubuntu:
  New

Bug description:
  Just tried starting it from the command line with a midi file.  Jack
  available but not running at the time I tried this.

  I cannot vouch whether this was started with or without pasuspender: I
  tried both since without pasuspender fluidsynth (or jack) complained
  about Pulseaudio hogging the device.  It could have crashed after the
  complaint, or it could have crashed independently without such a
  complaint.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: fluidsynth 1.1.6-4
  ProcVersionSignature: Ubuntu 4.10.0-11.13-lowlatency 4.10.1
  Uname: Linux 4.10.0-11-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sun Mar 19 09:28:47 2017
  ExecutablePath: /usr/bin/fluidsynth
  InstallationDate: Installed on 2011-10-14 (1982 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: fluidsynth /home/username/scores/tabber.midi
  SegvAnalysis:
   Segfault happened at: 0xf72d9194 :  mov
0xc(%esi),%edx
   PC (0xf72d9194) ok
   source "0xc(%esi)" (0x000c) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: fluidsynth
  StacktraceTop:
   jack_port_get_buffer () from /usr/lib/i386-linux-gnu/libjack.so.0
   fluid_jack_driver_process () from /usr/lib/i386-linux-gnu/libfluidsynth.so.1
   ?? () from /usr/lib/i386-linux-gnu/libjack.so.0
   start_thread (arg=0xf6809b40) at pthread_create.c:333
   clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113
  Title: fluidsynth crashed with SIGSEGV in jack_port_get_buffer()
  UpgradeStatus: Upgraded to zesty on 2017-01-05 (72 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1673466] Re: Launcher shown on lock screen despite privacy settings

[Launchpad Bug Tracker]

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

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

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

Title:
  Launcher shown on lock screen despite privacy settings

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  With the launcher set to "always shown" in Unity 8, and with privacy
  settings configured to not show the launcher on the lock screen, it
  still shows on the Unity 8 lock screen after the timeout has passed.

  It seems like really the launcher should never be shown on the lock
  screen on any device, and the solution would be to remove this setting
  and always hide the launcher on the lock screen/greeter, as this can
  expose unique information about the user.

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

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

[Touch-packages] [Bug 1674072]

[Apport retracing service]

StacktraceTop:
 jack_port_get_buffer (port=0x0, nframes=1024) at port.c:581
 fluid_jack_driver_process (nframes=1024, arg=0x5706e400) at 
./src/drivers/fluid_jack.c:522
 jack_process_thread_work (arg=0x5706e4d0) at client.c:2214
 start_thread (arg=0xf6809b40) at pthread_create.c:333
 clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113

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

Title:
  fluidsynth crashed with SIGSEGV in jack_port_get_buffer()

Status in fluidsynth package in Ubuntu:
  New

Bug description:
  Just tried starting it from the command line with a midi file.  Jack
  available but not running at the time I tried this.

  I cannot vouch whether this was started with or without pasuspender: I
  tried both since without pasuspender fluidsynth (or jack) complained
  about Pulseaudio hogging the device.  It could have crashed after the
  complaint, or it could have crashed independently without such a
  complaint.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: fluidsynth 1.1.6-4
  ProcVersionSignature: Ubuntu 4.10.0-11.13-lowlatency 4.10.1
  Uname: Linux 4.10.0-11-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sun Mar 19 09:28:47 2017
  ExecutablePath: /usr/bin/fluidsynth
  InstallationDate: Installed on 2011-10-14 (1982 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: fluidsynth /home/username/scores/tabber.midi
  SegvAnalysis:
   Segfault happened at: 0xf72d9194 :  mov
0xc(%esi),%edx
   PC (0xf72d9194) ok
   source "0xc(%esi)" (0x000c) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: fluidsynth
  StacktraceTop:
   jack_port_get_buffer () from /usr/lib/i386-linux-gnu/libjack.so.0
   fluid_jack_driver_process () from /usr/lib/i386-linux-gnu/libfluidsynth.so.1
   ?? () from /usr/lib/i386-linux-gnu/libjack.so.0
   start_thread (arg=0xf6809b40) at pthread_create.c:333
   clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113
  Title: fluidsynth crashed with SIGSEGV in jack_port_get_buffer()
  UpgradeStatus: Upgraded to zesty on 2017-01-05 (72 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1673500] Re: Ctrl+Alt+T does not bring up a terminal

[Lukáš Tinkl]

** Branch linked: lp:~lukas-kde/unity8/terminal-shortcut-lp1673500

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

Title:
  Ctrl+Alt+T does not bring up a terminal

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  I really miss that keyboard shortcut when using unity8.  In unity7,
  that shortcut would bring up a gnome-terminal window (actual command
  configurable in GNOME gsettings somewhere).

  I guess in unity8, it would bring up a ubuntu-terminal-app window (deb
  or snap).

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

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

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

[Apport retracing service]

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

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

Title:
  fluidsynth crashed with SIGSEGV in jack_port_get_buffer()

Status in fluidsynth package in Ubuntu:
  New

Bug description:
  Just tried starting it from the command line with a midi file.  Jack
  available but not running at the time I tried this.

  I cannot vouch whether this was started with or without pasuspender: I
  tried both since without pasuspender fluidsynth (or jack) complained
  about Pulseaudio hogging the device.  It could have crashed after the
  complaint, or it could have crashed independently without such a
  complaint.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: fluidsynth 1.1.6-4
  ProcVersionSignature: Ubuntu 4.10.0-11.13-lowlatency 4.10.1
  Uname: Linux 4.10.0-11-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sun Mar 19 09:28:47 2017
  ExecutablePath: /usr/bin/fluidsynth
  InstallationDate: Installed on 2011-10-14 (1982 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: fluidsynth /home/username/scores/tabber.midi
  SegvAnalysis:
   Segfault happened at: 0xf72d9194 :  mov
0xc(%esi),%edx
   PC (0xf72d9194) ok
   source "0xc(%esi)" (0x000c) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: fluidsynth
  StacktraceTop:
   jack_port_get_buffer () from /usr/lib/i386-linux-gnu/libjack.so.0
   fluid_jack_driver_process () from /usr/lib/i386-linux-gnu/libfluidsynth.so.1
   ?? () from /usr/lib/i386-linux-gnu/libjack.so.0
   start_thread (arg=0xf6809b40) at pthread_create.c:333
   clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113
  Title: fluidsynth crashed with SIGSEGV in jack_port_get_buffer()
  UpgradeStatus: Upgraded to zesty on 2017-01-05 (72 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

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

[Apport retracing service]

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

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

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

** Tags removed: need-i386-retrace

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

Title:
  fluidsynth crashed with SIGSEGV in jack_port_get_buffer()

Status in fluidsynth package in Ubuntu:
  New

Bug description:
  Just tried starting it from the command line with a midi file.  Jack
  available but not running at the time I tried this.

  I cannot vouch whether this was started with or without pasuspender: I
  tried both since without pasuspender fluidsynth (or jack) complained
  about Pulseaudio hogging the device.  It could have crashed after the
  complaint, or it could have crashed independently without such a
  complaint.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: fluidsynth 1.1.6-4
  ProcVersionSignature: Ubuntu 4.10.0-11.13-lowlatency 4.10.1
  Uname: Linux 4.10.0-11-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sun Mar 19 09:28:47 2017
  ExecutablePath: /usr/bin/fluidsynth
  InstallationDate: Installed on 2011-10-14 (1982 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: fluidsynth /home/username/scores/tabber.midi
  SegvAnalysis:
   Segfault happened at: 0xf72d9194 :  mov
0xc(%esi),%edx
   PC (0xf72d9194) ok
   source "0xc(%esi)" (0x000c) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: fluidsynth
  StacktraceTop:
   jack_port_get_buffer () from /usr/lib/i386-linux-gnu/libjack.so.0
   fluid_jack_driver_process () from /usr/lib/i386-linux-gnu/libfluidsynth.so.1
   ?? () from /usr/lib/i386-linux-gnu/libjack.so.0
   start_thread (arg=0xf6809b40) at pthread_create.c:333
   clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113
  Title: fluidsynth crashed with SIGSEGV in jack_port_get_buffer()
  UpgradeStatus: Upgraded to zesty on 2017-01-05 (72 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

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

[Apport retracing service]

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

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

Title:
  fluidsynth crashed with SIGSEGV in jack_port_get_buffer()

Status in fluidsynth package in Ubuntu:
  New

Bug description:
  Just tried starting it from the command line with a midi file.  Jack
  available but not running at the time I tried this.

  I cannot vouch whether this was started with or without pasuspender: I
  tried both since without pasuspender fluidsynth (or jack) complained
  about Pulseaudio hogging the device.  It could have crashed after the
  complaint, or it could have crashed independently without such a
  complaint.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: fluidsynth 1.1.6-4
  ProcVersionSignature: Ubuntu 4.10.0-11.13-lowlatency 4.10.1
  Uname: Linux 4.10.0-11-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sun Mar 19 09:28:47 2017
  ExecutablePath: /usr/bin/fluidsynth
  InstallationDate: Installed on 2011-10-14 (1982 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: fluidsynth /home/username/scores/tabber.midi
  SegvAnalysis:
   Segfault happened at: 0xf72d9194 :  mov
0xc(%esi),%edx
   PC (0xf72d9194) ok
   source "0xc(%esi)" (0x000c) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: fluidsynth
  StacktraceTop:
   jack_port_get_buffer () from /usr/lib/i386-linux-gnu/libjack.so.0
   fluid_jack_driver_process () from /usr/lib/i386-linux-gnu/libfluidsynth.so.1
   ?? () from /usr/lib/i386-linux-gnu/libjack.so.0
   start_thread (arg=0xf6809b40) at pthread_create.c:333
   clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113
  Title: fluidsynth crashed with SIGSEGV in jack_port_get_buffer()
  UpgradeStatus: Upgraded to zesty on 2017-01-05 (72 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1674078] [NEW] PCI/internal sound card not detected

[mippo]

Public bug reported:

hello,

on a PC: HP-x2-Detachable-10-p008
the System Setting, in the Audio section, shows: "Output dummy"

the command: cat /proc/asound/cards

returns: - - - no souncard - - -

(under windows the sound works)


thanks for help

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.10.3-041003-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Sun Mar 19 11:10:11 2017
InstallationDate: Installed on 2017-02-26 (21 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 827C
dmi.board.vendor: HP
dmi.board.version: 93.22
dmi.chassis.type: 32
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd09/30/2016:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.22:cvnHP:ct32:cvrChassisVersion:
dmi.product.name: HP x2 Detachable 10-p0XX
dmi.sys.vendor: HP
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-27T02:14:40.994094

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


** Tags: amd64 apport-bug yakkety

** Description changed:

  hello,
  
  on a PC: HP-x2-Detachable-10-p008
  the System Setting, in the Audio section, shows: "Output dummy"
  
  the command: cat /proc/asound/cards
  
  returns: - - - no souncard - - -
+ 
+ (under windows the sound works)
  
  
  thanks for help
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.10.3-041003-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Mar 19 11:10:11 2017
  InstallationDate: Installed on 2017-02-26 (21 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827C
  dmi.board.vendor: HP
  dmi.board.version: 93.22
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd09/30/2016:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.22:cvnHP:ct32:cvrChassisVersion:
  dmi.product.name: HP x2 Detachable 10-p0XX
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-27T02:14:40.994094

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  hello,

  on a PC: HP-x2-Detachable-10-p008
  the System Setting, in the Audio section, shows: "Output dummy"

  the command: cat /proc/asound/cards

  returns: - - - no souncard - - -

  (under windows the sound works)

  
  thanks for help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.10.3-041003-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Mar 19 11:10:11 2017
  InstallationDate: Installed on 2017-02-26 (21 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827C
  dmi.board.vendor: HP
  dmi.board.version: 93.22
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd09/30/2016:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.22:cvnHP:ct32:cvrChassisVersion:
  dmi.product.name: HP x2 Detachable 10-p0XX
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-27T02:14:40.994094

To manage notifications 

[Touch-packages] [Bug 1673550] Re: Windows not remembering previous size on unity8

[Doug McMahon]

In Desktop mode all apps open in a small square window & have to be resized per 
use, i.e. it doesn't 'remember' window size in a session let alone across 
sessions.
Makes the desktop mode onerous to use..


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

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

Title:
  Windows not remembering previous size on unity8

Status in Canonical System Image:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  running u8 desktop session

  Steps to reproduce:
  - open u-s-s
  - resize the window to 2 column mode
  - close the app with X from window control
  - restart the app

  Expected results:
  - u-s-s should open at the size it was last closed at

  Actutual results:
  - u-s-s window is smaller only showing one column

  This may be related to limiting the max size which we used to have? I
  think we should remove all max sizing restrictions on the app, and
  bring back the maximize button which is not displayed either.

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

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

[Touch-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Igor]

** Summary changed:

- Xorg does not work in rootless mode on nvidia proprietary drivers (GNOME)
+ Xorg does not detect displays in rootless mode on nvidia proprietary drivers 
(GNOME)

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:

[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Stefano]

Can confirm this bug in Ubuntu 17.04 with kernel 4.10.0-13-generic.

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Stefano]

Mär 19 14:50:58 stefano-PC systemd-udevd[458]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event3' (scan code 0x90001, key code 148): Invalid 
argument
Mär 19 14:50:58 stefano-PC systemd-udevd[458]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event3' (scan code 0x90002, key code 152): Invalid 
argument
Mär 19 14:50:58 stefano-PC systemd-udevd[458]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event3' (scan code 0x90003, key code 144): Invalid 
argument
Mär 19 14:50:58 stefano-PC systemd-udevd[458]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event3' (scan code 0x90004, key code 421): Invalid 
argument
Mär 19 14:50:58 stefano-PC systemd-udevd[458]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event3' (scan code 0x90005, key code 423): Invalid 
argument
Mär 19 14:50:58 stefano-PC systemd-udevd[458]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event3' (scan code 0x90006, key code 140): Invalid 
argument
Mär 19 14:50:58 stefano-PC systemd-udevd[458]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event3' (scan code 0x90007, key code 155): Invalid 
argument
Mär 19 14:50:58 stefano-PC systemd-udevd[458]: Error calling EVIOCSKEYCODE on 
device node '/dev/input/event3' (scan code 0x90008, key code 150): Invalid 
argument

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Kai Xu]

Hi everyone,

How can I undo the 8 lines, i.e. make the hda-verb to the default
setting?

Tried it on another ASUS model but doesn't work. Just want undo it.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  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/alsa-driver/+bug/1596381/+subscriptions

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

[Touch-packages] [Bug 1674115] Re: sudo crashed with SIGSEGV in kill()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private Security to Public Security

** Tags removed: need-amd64-retrace

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

Title:
  sudo crashed with SIGSEGV in kill()

Status in sudo package in Ubuntu:
  New

Bug description:
  scanimage -L keeps reporting no SANE scanners found.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: sudo 1.8.19p1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Mar 19 13:25:01 2017
  ExecutablePath: /usr/bin/sudo
  InstallationDate: Installed on 2017-03-18 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: sudo scanimage
  Signal: 11
  SourcePackage: sudo
  StacktraceTop:
   kill () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   __libc_start_main (main=0x5564a3a58a50, argc=2, argv=0x7fff4ef4fa38, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff4ef4fa28) at ../csu/libc-start.c:291
   ?? ()
  Title: sudo crashed with SIGSEGV in kill()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

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

[Arnold Veenhoff]

Public bug reported:

I don't know how to specify. The notification I saw was that the update
could not be fully installed.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-67-generic 4.4.0-67.88
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  arnold 2272 F pulseaudio
 /dev/snd/controlC0:  arnold 2272 F pulseaudio
Date: Sun Mar 19 14:32:22 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=eb6a15f2-248c-421a-a242-0c7484fefd71
MachineType: Acer Aspire 5542
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-67-generic 4.4.0-67.88 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to xenial on 2016-07-29 (232 days ago)
dmi.bios.date: 10/22/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.05
dmi.board.name: JV50TR
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.05:bd10/22/2009:svnAcer:pnAspire5542:pvr0100:rvnAcer:rnJV50TR:rvrRev:cvnAcer:ct10:cvrNone:
dmi.product.name: Aspire 5542
dmi.product.version: 0100
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-package xenial

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I don't know how to specify. The notification I saw was that the
  update could not be fully installed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-67-generic 4.4.0-67.88
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  arnold 2272 F pulseaudio
   /dev/snd/controlC0:  arnold 2272 F pulseaudio
  Date: Sun Mar 19 14:32:22 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=eb6a15f2-248c-421a-a242-0c7484fefd71
  MachineType: Acer Aspire 5542
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-67-generic 4.4.0-67.88 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (232 days ago)
  dmi.bios.date: 10/22/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.05
  dmi.board.name: JV50TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.05:bd10/22/2009:svnAcer:pnAspire5542:pvr0100:rvnAcer:rnJV50TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 5542
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1674112] Re: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: triggers looping, abandoned

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade:
  triggers looping, abandoned

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Mar 19 16:06:04 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-03-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1674112] [NEW] package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: triggers looping, abandoned

[Rene Hoos]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.8
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun Mar 19 16:06:04 2017
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2017-03-19 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade:
  triggers looping, abandoned

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Mar 19 16:06:04 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-03-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1672033] Re: Xorg does not work in rootless mode on nvidia proprietary drivers (GNOME)

[Igor]

Asked on nvidia forum, maybe they'll be able to give some advise:

https://devtalk.nvidia.com/default/topic/1000172/linux/root-less-xorg-
does-not-detect-displays-which-leads-to-segfault-in-mutter/

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go 

[Touch-packages] [Bug 1674103] Re: package linux-image-extra-4.4.0-67-generic 4.4.0-67.88 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I don't know how to specify. The notification I saw was that the
  update could not be fully installed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-67-generic 4.4.0-67.88
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  arnold 2272 F pulseaudio
   /dev/snd/controlC0:  arnold 2272 F pulseaudio
  Date: Sun Mar 19 14:32:22 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=eb6a15f2-248c-421a-a242-0c7484fefd71
  MachineType: Acer Aspire 5542
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-67-generic 4.4.0-67.88 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (232 days ago)
  dmi.bios.date: 10/22/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.05
  dmi.board.name: JV50TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.05:bd10/22/2009:svnAcer:pnAspire5542:pvr0100:rvnAcer:rnJV50TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 5542
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1111882] Re: GnuTLS recv error (-9): A TLS packet with unexpected length was received

[Adam Voss]

My case ended up not being this bug.  I recompiled with OpenSSL
(devopscube.com/gnutls-handshake-failed-aws-codecommit/) and then got
the following error instead:

Writing objects: 100% (1103/1103), 1.09 MiB | 0 bytes/s, done.
Total 1103 (delta 653), reused 1001 (delta 606)
error: RPC failed; curl 56 SSL read: error::lib(0):func(0):reason(0), 
errno 104
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

I am guessing it was because I was pushing so many commits (upstream
changes).  I deleted my fork on GitHub and recreated it so that it would
be up-to-date, then had no problem pushing my changes.

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

Title:
  GnuTLS recv error (-9): A TLS packet with unexpected length was
  received

Status in apt package in Ubuntu:
  Invalid
Status in curl package in Ubuntu:
  Confirmed
Status in git package in Ubuntu:
  Confirmed
Status in gnutls26 package in Ubuntu:
  Confirmed

Bug description:
  On Precise 12.04 whilst attempting:

  GIT_CURL_VERBOSE=1 git clone -v https://git01.codeplex.com/typescript

  the operation fails after the final git pack-file has been received
  and the already-created repository is deleted from the file system.

  ...
  > POST /typescript/git-upload-pack HTTP/1.1
  User-Agent: git/1.8.1.2.433.g9808ce0.dirty
  Host: git01.codeplex.com
  Accept-Encoding: gzip
  Content-Type: application/x-git-upload-pack-request
  Accept: application/x-git-upload-pack-result
  Content-Length: 611

  * upload completely sent off: 611out of 611 bytes
  < HTTP/1.1 200 OK
  < Cache-Control: no-cache, max-age=0, must-revalidate
  < Pragma: no-cache
  < Content-Type: application/x-git-upload-pack-result
  < Expires: Fri, 01 Jan 1980 00:00:00 GMT
  < Server: Microsoft-IIS/7.5
  < X-Powered-By: ASP.NET
  < Date: Thu, 31 Jan 2013 21:43:55 GMT
  < Connection: close
  < 
  remote: Counting objects: 149766, done.
  remote: Compressing objects: 100% (10580/10580), done.
  * GnuTLS recv error (-9): A TLS packet with unexpected length was received.
  * Closing connection #0
  remote: Total 149766 (delta 138201), reused 149559 (delta 138077)
  Receiving objects: 100% (149766/149766), 198.98 MiB | 361 KiB/s, done.
  error: RPC failed; result=56, HTTP code = 200
  Resolving deltas: 100% (138201/138201), done.

  git exits at this point but it deletes the entire cloned ./typescript
  directory.

  I tried building the latest git binary and included an additional
  debug option in "http.c" that allowed me to set the protocol version
  using an environment option:

  CURLOPT_SSLVERSION=1 git clone ...

  where 1 = TLSv1, 2 = SSLv2, 3 = SSLv3.

  I tried each protocol but the result was the same.

  The knock-on bug here is that git ought not to delete what it has
  fetched - in this case more than 250MB of data.

  I did try to build the latest gnutls but it needs a very recent
  version of libnettle which has the "rsa_decrypt_tr" function. I
  stopped at that point since I don't want to get into dependency and
  library version issues.

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

-- 
Mailing list: https://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 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

[Luke Yelavich]

Could you also get a log from PulseAudio as per
https://wiki.ubuntu.com/PulseAudio/Log. Thanks.

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required,
  but nothing I've seen documented seems to help.

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

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

[Touch-packages] [Bug 1674138] [NEW] Xorg fails to load i965_dri.so and swrast_dri.so, undefined symbol _glapi_tls_Dispatch

[Erik Faye-Lund]

Public bug reported:

After a recent update, Xorg fails to start up, and I get the following
error in journalctl when trying to boot:

---8<---
mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) AIGLX 
error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed 
(/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: undefined symbol: 
_glapi_tls_Dispatch)
mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) AIGLX: 
reverting to software rendering
mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) AIGLX 
error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed 
(/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol: 
_glapi_tls_Dispatch)
mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) GLX: 
could not load software renderer
mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (II) GLX: no 
usable GL providers found for screen 0
---8<---

This is with libgl1-mesa-dri version 12.0.6-0ubuntu0.16.04.1. Rolling
back to 11.2.0-1ubuntu2 seems to fix this problem for me (although it
seems to break some other unrelated system-dependencies)

I'm running Ubuntu Gnome 16.04 LTS.

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

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

Title:
  Xorg fails to load i965_dri.so and swrast_dri.so, undefined symbol
  _glapi_tls_Dispatch

Status in mesa package in Ubuntu:
  New

Bug description:
  After a recent update, Xorg fails to start up, and I get the following
  error in journalctl when trying to boot:

  ---8<---
  mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) AIGLX 
error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed 
(/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: undefined symbol: 
_glapi_tls_Dispatch)
  mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) AIGLX: 
reverting to software rendering
  mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) AIGLX 
error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed 
(/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol: 
_glapi_tls_Dispatch)
  mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) GLX: 
could not load software renderer
  mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (II) GLX: no 
usable GL providers found for screen 0
  ---8<---

  This is with libgl1-mesa-dri version 12.0.6-0ubuntu0.16.04.1. Rolling
  back to 11.2.0-1ubuntu2 seems to fix this problem for me (although it
  seems to break some other unrelated system-dependencies)

  I'm running Ubuntu Gnome 16.04 LTS.

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

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

[Touch-packages] [Bug 1674163] [NEW] imposibilidad de instalar una impresora

[Miguel Mateu]

Public bug reported:

Cada vez que intento instalarla marca error del sistema.
No admite otra forma de instalarla

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
BootLog:
 [FAILED] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.7-usb1-1\x2d2).
 See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:1d.7-usb1-1\\x2d2.service"' 
for details.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Mar 19 17:40:15 2017
DistUpgraded: 2016-12-27 18:52:03,292 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation 4 Series Chipset Integrated Graphics 
Controller [1849:2e32]
InstallationDate: Installed on 2016-11-12 (127 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic 
root=UUID=8bc8c59a-fb09-421e-99b0-9f139eff2ea1 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-12-27 (81 days ago)
dmi.bios.date: 07/13/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: G41M-GS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd07/13/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG41M-GS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Mar 19 09:35:30 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 739 
 vendor SAM
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  imposibilidad de instalar una impresora

Status in xorg package in Ubuntu:
  New

Bug description:
  Cada vez que intento instalarla marca error del sistema.
  No admite otra forma de instalarla

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
   [FAILED] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.7-usb1-1\x2d2).
   See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:1d.7-usb1-1\\x2d2.service"' 
for details.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Mar 19 17:40:15 2017
  DistUpgraded: 2016-12-27 18:52:03,292 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 4 Series Chipset Integrated Graphics 
Controller [1849:2e32]
  

Re: [Touch-packages] [Bug 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

[Luke Yelavich]

Please run apport-collect 1673942 in a terminal so we can get some more
information about your hardware.

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required,
  but nothing I've seen documented seems to help.

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

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[s frahm]

Ubuntu 16.04 (ubuntu 4.4.0-64) crashed yet again during upgrade to
4.4.0-66 from this same recurring 5+ year old bug - Pray tell, why can't
Ubuntu just tell me there is not enough room to upgrade the kernel (it
used to) and then perhaps even offer to fix it automagically with some
kind of an automated or scripted version of - $ sudo purge-old-kernels
instead of just crashing my whole enchilada? I simply just don't
understand the Ubuntu cultural or technical limitations that have kept
this from happening. First I have to install Janitor with Ubuntu Tweaks
on 12.04 - 14.04 LTS and delete all but the two latest older versions
and now with 16.04 I must install Byobu Terminal (which thing I like
very much anyway on most linux flavors lately) and manually type - $
sudo purge-old-kernels   5x - each time I attempt an upgrade of a base
install and 4 ea. KVM virtual machines. Oops, I forgot the one on the
hypervisor... CRASH! Arrrggg! Grub / advanced / recover to an older
kernel - $ sudo apt-get install -f   Thanks to the entire community for
such an otherwise wonderful thing that Ubuntu, Lubuntu, etc. is!
(...Hmm, ask the Webmin folks to add a script that does this perhaps?)
Thanks!

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions

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

[Touch-packages] [Bug 1674137] Re: ifdown unknown interface net-tools is broken

[Roger Lawhorn]

** Also affects: net-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ifdown unknown interface net-tools is broken

Status in Linux Mint:
  New
Status in net-tools package in Ubuntu:
  New

Bug description:
  System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena
  Network:   Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller
     driver: alx port: d000 bus-ID: 03:00.0
     IF: enp3s0 state: up speed: 1000 Mbps duplex: full
     Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: 
ath9k bus-ID: 04:00.0
     IF: wlp4s0 state: up

  After mint 18.1 upgrade had various issues.
  After quite a few updates I started having issues with ifdown command.

  I use a script with qemu to setup a bridge (br0) with tap0 and the default 
wired connection enp3s0. The script began giving off unknown interface errors.
  Testing showed that the ifdown command changed behavior after the updates and 
now does this.
  The behavior is not limited to scripting.
  I changed the code from using ifdown to ifconfig enp3s0 down.
  This fails also within the script but with no error.
  It, however, works from a terminal just fine.
  I switched to using the ip command i.e. ip link set enp3s0 down.
  Same result, the interface does not go down, but no error.
  After the script is run and windows 7 boots in qemu I have to open a terminal 
and run the commands manually:
  >ifconfig enp3s0 down
  >ifconfig enp3s0 0.0.0.0 promisc up

  Then all is well.
  These commands will not run from within a script.
  The script is run as such:
  >sudo ./up.sh tap0

  It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge.

  The fact that ifdown no longer recognizes any interfaces seems to
  point to a change in net-tools that has broken something.

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

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

[Touch-packages] [Bug 1674164] [NEW] DVDs with restricted permissions are unreadable for normal user (regression?)

[mikbini]

Public bug reported:

I'm using 16.10. I have a DVD with strange permissions for the root
folder:

michele@cassandra:~$ ls -l /media/michele
total 2
d--x--x--- 3 michele michele 88 gen  1  2004 SONY_DVD_RECORDER_VOLUME

The DVD is readable e.g. on windows but with ubuntu while I can access
it as root:

root@cassandra:~# ls -l /media/michele/SONY_DVD_RECORDER_VOLUME/
total 4
dr-xr-xr-x 2 michele michele 3628 gen  1  2004 VIDEO_TS

I cannot as the non-root user that is logged in when I insert the disk:

michele@cassandra:~$ ls -l /media/michele/SONY_DVD_RECORDER_VOLUME
ls: cannot open directory '/media/michele/SONY_DVD_RECORDER_VOLUME': Permission 
denied

Looking at the mount options it seems to me that this is a regression
for bug #10550. The options used by udisks2 are:

root@cassandra:~# mount |grep SONY
/dev/sr0 on /media/michele/SONY_DVD_RECORDER_VOLUME type udf 
(ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2)

while my understanding from bug #10550 is that I should have also
mode=0777 and dmode=0777

And indeed this works:

root@cassandra:~# mount -t udf -o
ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2,mode=0777,dmode=0777
/dev/sr0 ~michele/z

michele@cassandra:~$ ls -l ~michele/z
total 4
drwxrwxrwx 2 michele michele 3628 gen  1  2004 VIDEO_TS

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

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

Title:
  DVDs with restricted permissions are unreadable for normal user
  (regression?)

Status in util-linux package in Ubuntu:
  New

Bug description:
  I'm using 16.10. I have a DVD with strange permissions for the root
  folder:

  michele@cassandra:~$ ls -l /media/michele
  total 2
  d--x--x--- 3 michele michele 88 gen  1  2004 SONY_DVD_RECORDER_VOLUME

  The DVD is readable e.g. on windows but with ubuntu while I can access
  it as root:

  root@cassandra:~# ls -l /media/michele/SONY_DVD_RECORDER_VOLUME/
  total 4
  dr-xr-xr-x 2 michele michele 3628 gen  1  2004 VIDEO_TS

  I cannot as the non-root user that is logged in when I insert the
  disk:

  michele@cassandra:~$ ls -l /media/michele/SONY_DVD_RECORDER_VOLUME
  ls: cannot open directory '/media/michele/SONY_DVD_RECORDER_VOLUME': 
Permission denied

  Looking at the mount options it seems to me that this is a regression
  for bug #10550. The options used by udisks2 are:

  root@cassandra:~# mount |grep SONY
  /dev/sr0 on /media/michele/SONY_DVD_RECORDER_VOLUME type udf 
(ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2)

  while my understanding from bug #10550 is that I should have also
  mode=0777 and dmode=0777

  And indeed this works:

  root@cassandra:~# mount -t udf -o
  
ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2,mode=0777,dmode=0777
  /dev/sr0 ~michele/z

  michele@cassandra:~$ ls -l ~michele/z
  total 4
  drwxrwxrwx 2 michele michele 3628 gen  1  2004 VIDEO_TS

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

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

[Touch-packages] [Bug 1674138] Re: Xorg fails to load i965_dri.so and swrast_dri.so, undefined symbol _glapi_tls_Dispatch

[Erik Faye-Lund]

Uninstalling the whole desktop and reinstalling made this go away. I
guess I had messed something up.

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

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

Title:
  Xorg fails to load i965_dri.so and swrast_dri.so, undefined symbol
  _glapi_tls_Dispatch

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  After a recent update, Xorg fails to start up, and I get the following
  error in journalctl when trying to boot:

  ---8<---
  mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) AIGLX 
error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed 
(/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: undefined symbol: 
_glapi_tls_Dispatch)
  mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) AIGLX: 
reverting to software rendering
  mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) AIGLX 
error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed 
(/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol: 
_glapi_tls_Dispatch)
  mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) GLX: 
could not load software renderer
  mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (II) GLX: no 
usable GL providers found for screen 0
  ---8<---

  This is with libgl1-mesa-dri version 12.0.6-0ubuntu0.16.04.1. Rolling
  back to 11.2.0-1ubuntu2 seems to fix this problem for me (although it
  seems to break some other unrelated system-dependencies)

  I'm running Ubuntu Gnome 16.04 LTS.

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

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

[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

[Jeremy Bicha]

This bug was fixed in the package zeroinstall-injector - 2.12-3

---
zeroinstall-injector (2.12-3) unstable; urgency=medium

  * Don't recommend python3-aptdaemon.pkcompat. Closes: #848559.

 -- Thomas Leonard   Sun, 19 Mar 2017 09:28:46 +

zeroinstall-injector (2.12-2) unstable; urgency=medium

  * Add missing build dep on tzdata. Closes: #839511.

 -- Thomas Leonard   Sun, 02 Oct 2016 12:53:59 +

zeroinstall-injector (2.12-1) unstable; urgency=medium

  * New upstream release.
  * Add missing build dep. Closes: #837226.

 -- Thomas Leonard   Sun, 25 Sep 2016 07:55:43 +

** Changed in: zeroinstall-injector (Ubuntu)
   Status: New => Fix Released

** No longer affects: zeroinstall-injector (Ubuntu Aa-series)

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  New
Status in mythbuntu-control-centre package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Triaged
Status in aptdaemon source package in aa-series:
  New
Status in apturl source package in aa-series:
  New
Status in dell-recovery source package in aa-series:
  New
Status in gnome-software source package in aa-series:
  New
Status in language-selector source package in aa-series:
  New
Status in lubuntu-software-center source package in aa-series:
  New
Status in mythbuntu-control-centre source package in aa-series:
  New
Status in sessioninstaller source package in aa-series:
  New
Status in software-properties source package in aa-series:
  New
Status in ubiquity source package in aa-series:
  New
Status in ubuntu-mate-meta source package in aa-series:
  New
Status in ubuntu-mate-welcome source package in aa-series:
  New
Status in update-manager source package in aa-series:
  New
Status in update-notifier source package in aa-series:
  New

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

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

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

[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

[Jeremy Bicha]

fails to build :(

** Changed in: zeroinstall-injector (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  New
Status in mythbuntu-control-centre package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Triaged
Status in aptdaemon source package in aa-series:
  New
Status in apturl source package in aa-series:
  New
Status in dell-recovery source package in aa-series:
  New
Status in gnome-software source package in aa-series:
  New
Status in language-selector source package in aa-series:
  New
Status in lubuntu-software-center source package in aa-series:
  New
Status in mythbuntu-control-centre source package in aa-series:
  New
Status in sessioninstaller source package in aa-series:
  New
Status in software-properties source package in aa-series:
  New
Status in ubiquity source package in aa-series:
  New
Status in ubuntu-mate-meta source package in aa-series:
  New
Status in ubuntu-mate-welcome source package in aa-series:
  New
Status in update-manager source package in aa-series:
  New
Status in update-notifier source package in aa-series:
  New

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

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

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

[Touch-packages] [Bug 1674137] Re: ifdown unknown interface net-tools is broken

[Roger Lawhorn]

UPDATE:
To reverify, ifdown command fails always. net-tools is broken after the update.

I have done extensive testing on my scripts adding Y/N questions to verify that 
each command succeeded. They do. 
Therefore, the ip and ifconfig commands do succeed inside of scripts (but not 
ifdown). I was incorrect about that.

What really happens:
At the point where the bridge is made and tap0 and enp3s0 are added to it the 
ipaddr of enp3s0 goes from 0.0.0.0 back to 192.168.1.130 thus breaking the 
bridge.
Both tap0 and enp3s0 must be 0.0.0.0. promiscuous mode, and up inside the 
bridge br0 to work properly.

I am digging deeper on why this happens.
As a temp fix I reset enp3s0 to the correct settings a 2nd time after the 
bridge is made.

Also, after the bridge is removed enp3s0 never performs dhcp to regain its 
original ipaddr.
That is also an issue.

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

Title:
  ifdown unknown interface net-tools is broken

Status in Linux Mint:
  New
Status in net-tools package in Ubuntu:
  New

Bug description:
  System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena
  Network:   Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller
     driver: alx port: d000 bus-ID: 03:00.0
     IF: enp3s0 state: up speed: 1000 Mbps duplex: full
     Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: 
ath9k bus-ID: 04:00.0
     IF: wlp4s0 state: up

  After mint 18.1 upgrade had various issues.
  After quite a few updates I started having issues with ifdown command.

  I use a script with qemu to setup a bridge (br0) with tap0 and the default 
wired connection enp3s0. The script began giving off unknown interface errors.
  Testing showed that the ifdown command changed behavior after the updates and 
now does this.
  The behavior is not limited to scripting.
  I changed the code from using ifdown to ifconfig enp3s0 down.
  This fails also within the script but with no error.
  It, however, works from a terminal just fine.
  I switched to using the ip command i.e. ip link set enp3s0 down.
  Same result, the interface does not go down, but no error.
  After the script is run and windows 7 boots in qemu I have to open a terminal 
and run the commands manually:
  >ifconfig enp3s0 down
  >ifconfig enp3s0 0.0.0.0 promisc up

  Then all is well.
  These commands will not run from within a script.
  The script is run as such:
  >sudo ./up.sh tap0

  It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge.

  The fact that ifdown no longer recognizes any interfaces seems to
  point to a change in net-tools that has broken something.

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

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

[Touch-packages] [Bug 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes

[Yuan-Chen Cheng]

seems not host hw related issue and no oem complain about it per comment log,
remove oem-priority (as tracking) per current status.

** No longer affects: oem-priority/xenial

** No longer affects: oem-priority

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

Title:
  [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy
  LMP Link Management Protocol) PIN codes

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

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

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

[Touch-packages] [Bug 1674137] Re: ifdown unknown interface net-tools is broken

[Roger Lawhorn]

UPDATE: 
Rewrote my scripts to set enp3s0 AFTER the bridge creation and deletion.
Issue with that part over.

ifdown still broken.
Unknown if script issue is related, but those scripts worked fine before the 
updates.
Perhaps more than one update changed how things work.

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

Title:
  ifdown unknown interface net-tools is broken

Status in Linux Mint:
  New
Status in net-tools package in Ubuntu:
  New

Bug description:
  System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena
  Network:   Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller
     driver: alx port: d000 bus-ID: 03:00.0
     IF: enp3s0 state: up speed: 1000 Mbps duplex: full
     Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: 
ath9k bus-ID: 04:00.0
     IF: wlp4s0 state: up

  After mint 18.1 upgrade had various issues.
  After quite a few updates I started having issues with ifdown command.

  I use a script with qemu to setup a bridge (br0) with tap0 and the default 
wired connection enp3s0. The script began giving off unknown interface errors.
  Testing showed that the ifdown command changed behavior after the updates and 
now does this.
  The behavior is not limited to scripting.
  I changed the code from using ifdown to ifconfig enp3s0 down.
  This fails also within the script but with no error.
  It, however, works from a terminal just fine.
  I switched to using the ip command i.e. ip link set enp3s0 down.
  Same result, the interface does not go down, but no error.
  After the script is run and windows 7 boots in qemu I have to open a terminal 
and run the commands manually:
  >ifconfig enp3s0 down
  >ifconfig enp3s0 0.0.0.0 promisc up

  Then all is well.
  These commands will not run from within a script.
  The script is run as such:
  >sudo ./up.sh tap0

  It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge.

  The fact that ifdown no longer recognizes any interfaces seems to
  point to a change in net-tools that has broken something.

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

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

[Touch-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[Kai-Heng Feng]

For those who are affected by the sensitivity issue, this systemd commit
fixes the issue:

commit 579a2ab3d65a2908afef5578af26793e80898d55
Author: Ben Gamari 
Date:   Sat Oct 15 12:11:03 2016 -0400

hwdb: Add sensitivity for Dell Latitude E7470 pointingstick


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

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[Kai-Heng Feng]

@Paul

When the touchpad stuttered, did you see anything like 'overhead' or
'throttled' in dmesg?

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1567168] Re: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de i

[Launchpad Bug Tracker]

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

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

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

Title:
  package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to
  install/upgrade: El paquete está en un estado grave de inconsistencia
  - debe reinstalarlo  antes de intentar su configuración.

Status in krb5 package in Ubuntu:
  Expired

Bug description:
  This error appeared just prior to login. After it, Ubuntu kept working
  fine

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Tue Apr  5 22:54:35 2016
  DuplicateSignature: package:libgssapi-krb5-2:amd64:1.13.2+dfsg-2ubuntu0.1:El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2011-10-15 (1635 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:amd64 1.13.2+dfsg-2ubuntu0.1 failed to 
install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Jarno Suni]

sfrahm, I do you mean Bug #1460396.

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions

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

[Touch-packages] [Bug 1453200] Re: No focusing under low light conditions

[jose sanchez]

ON the Meizu Pro5 the camera does not focus if you are trying to take a
picture with writing the picture comes out good but the text is blurry

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

Title:
  No focusing under low light conditions

Status in Canonical System Image:
  Triaged
Status in camera-app package in Ubuntu:
  Triaged

Bug description:
  Test case.
  - Under low light (but not very low) conditions
  - Open camera app.
  - Tap in settings to disable flash.
  - At a distance of 20 cm, frame a black keyboard.
  - Tap to focus in a key.

  Expected result.
  - Keys are focused.

  Actual result.
  - No focus.

  Also, if it's focused, it will unfocus.  This has been tested in Arale
  with Vivid devel-proposed 207 and krillin with Vivid and stable.

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

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

[Touch-packages] [Bug 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

[john nunnington]

apport information

** Tags added: apport-collected yakkety

** Description changed:

  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.
  
  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.
  
  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.
  
  The pulseaudio log collects initial messages, but nothing else is echoed
  to the log - which could be anything from 3-20 minutes [typically].
  
- I'm more than happy to assist in getting whatever logs are required, but
- nothing I've seen documented seems to help.
+ I'm more than happy to assist in getting whatever logs are required, but 
nothing I've seen documented seems to help.
+ --- 
+ ApportVersion: 2.20.3-0ubuntu8.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC3:  julie 30342 F pulseaudio
+  /dev/snd/controlC1:  julie 30342 F pulseaudio
+  /dev/snd/controlC2:  julie 30342 F pulseaudio
+  /dev/snd/controlC0:  julie 30342 F pulseaudio
+ DistroRelease: Ubuntu 16.10
+ InstallationDate: Installed on 2015-05-19 (670 days ago)
+ InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
+ Package: pulseaudio 1:9.0-2ubuntu2.1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANGUAGE=en_NZ:en
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_NZ.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ Tags:  yakkety
+ Uname: Linux 4.2.0-30-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 11/25/2014
+ dmi.bios.vendor: Award Software International, Inc.
+ dmi.bios.version: F2
+ dmi.board.name: GA-78LMT-USB3 6.0
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
+ dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
+ dmi.product.name: GA-78LMT-USB3 6.0
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.
+ modified.conffile..etc.pulse.daemon.conf: [modified]
+ modified.conffile..etc.pulse.default.pa: [modified]
+ mtime.conffile..etc.pulse.daemon.conf: 2017-03-18T20:58:01.387562
+ mtime.conffile..etc.pulse.default.pa: 2015-12-20T08:49:47.368322

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1673942/+attachment/4840681/+files/AlsaInfo.txt

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required, but 
nothing I've seen documented seems to help.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  julie 30342 F pulseaudio
   /dev/snd/controlC1:  julie 30342 F pulseaudio
   /dev/snd/controlC2:  julie 30342 F pulseaudio
   /dev/snd/controlC0:  julie 30342 F pulseaudio
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-05-19 (670 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: pulseaudio 1:9.0-2ubuntu2.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  yakkety
  Uname: Linux 

[Touch-packages] [Bug 1673942] CurrentDmesg.txt

[john nunnington]

apport information

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

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required, but 
nothing I've seen documented seems to help.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  julie 30342 F pulseaudio
   /dev/snd/controlC1:  julie 30342 F pulseaudio
   /dev/snd/controlC2:  julie 30342 F pulseaudio
   /dev/snd/controlC0:  julie 30342 F pulseaudio
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-05-19 (670 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: pulseaudio 1:9.0-2ubuntu2.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  yakkety
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-03-18T20:58:01.387562
  mtime.conffile..etc.pulse.default.pa: 2015-12-20T08:49:47.368322

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

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

[Touch-packages] [Bug 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

[john nunnington]

pulseaudio log from session that died.

** Attachment added: "pulseverbose.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1673942/+attachment/4840685/+files/pulseverbose.log

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required, but 
nothing I've seen documented seems to help.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  julie 30342 F pulseaudio
   /dev/snd/controlC1:  julie 30342 F pulseaudio
   /dev/snd/controlC2:  julie 30342 F pulseaudio
   /dev/snd/controlC0:  julie 30342 F pulseaudio
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-05-19 (670 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: pulseaudio 1:9.0-2ubuntu2.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  yakkety
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-03-18T20:58:01.387562
  mtime.conffile..etc.pulse.default.pa: 2015-12-20T08:49:47.368322

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

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

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

[john nunnington]

apport information

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

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required, but 
nothing I've seen documented seems to help.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  julie 30342 F pulseaudio
   /dev/snd/controlC1:  julie 30342 F pulseaudio
   /dev/snd/controlC2:  julie 30342 F pulseaudio
   /dev/snd/controlC0:  julie 30342 F pulseaudio
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-05-19 (670 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: pulseaudio 1:9.0-2ubuntu2.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  yakkety
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-03-18T20:58:01.387562
  mtime.conffile..etc.pulse.default.pa: 2015-12-20T08:49:47.368322

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

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

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

[john nunnington]

apport information

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

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required, but 
nothing I've seen documented seems to help.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  julie 30342 F pulseaudio
   /dev/snd/controlC1:  julie 30342 F pulseaudio
   /dev/snd/controlC2:  julie 30342 F pulseaudio
   /dev/snd/controlC0:  julie 30342 F pulseaudio
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-05-19 (670 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: pulseaudio 1:9.0-2ubuntu2.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  yakkety
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-03-18T20:58:01.387562
  mtime.conffile..etc.pulse.default.pa: 2015-12-20T08:49:47.368322

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

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

[Touch-packages] [Bug 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

[john nunnington]

output from 'pacmd list'.

I wasn't looking closely at this, but it looked like the PA daemon fell
over while trying to execute the pacmd verb.

I'm plugged into the motherboard sound output, and typically it is
"stable" from there.

** Attachment added: "pacmd.list.out"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1673942/+attachment/4840686/+files/pacmd.list.out

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required, but 
nothing I've seen documented seems to help.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  julie 30342 F pulseaudio
   /dev/snd/controlC1:  julie 30342 F pulseaudio
   /dev/snd/controlC2:  julie 30342 F pulseaudio
   /dev/snd/controlC0:  julie 30342 F pulseaudio
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-05-19 (670 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: pulseaudio 1:9.0-2ubuntu2.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Tags:  yakkety
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-03-18T20:58:01.387562
  mtime.conffile..etc.pulse.default.pa: 2015-12-20T08:49:47.368322

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

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

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[Samuel Holmes]

Hi,

I was having the same issue, but the fix suggested by Juan Hernandez at
#32 seems to have worked!

I had to install xserver-xorg-core before I could install xserver-xorg-
input-libinput, but it seems to work now!

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  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: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1672960] Re: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size()

[Daniel van Vugt]

** Information type changed from Public to Public Security

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

Title:
  unity-system-compositor crashed with SIGSEGV in invoke() from
  mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message()
  from on_read_size()

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.8.0+17.04.20161206-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/322176398baf670e4e9e5bb140a0aed0bbf0a00e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib

[Daniel van Vugt]

** Information type changed from Public to Public Security

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

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  Triaged
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/. 

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

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

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

[Touch-packages] [Bug 1557634] Re: Unity8/Mir server crashes when given an invalid keymap

[Daniel van Vugt]

** Information type changed from Public to Public Security

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

Title:
  Unity8/Mir server crashes when given an invalid keymap

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/4b8d65fc943d9604a00af4439b24bf85ddc6d1a7

  I foolishly tested unity8's keymap switching with the keymap "zh" (I
  should have used "cn").

  But I noticed that libmirclient crashed when I switched to "zh".
  While this isn't a supported use case, we shouldn't crash.

  Here's a non-debugful stack trace:

  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb614562e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
  #2  0xb6146332 in abort () from /lib/arm-linux-gnueabihf/libc.so.6
  #3  0xb6283120 in __gnu_cxx::__verbose_terminate_handler() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6281950 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #5  0xb62819a6 in std::terminate() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6281bc6 in __cxa_throw ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #7  0xb3d726ec in ?? () from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #8  0xb3d857f2 in 
mir::events::make_event(mir::IntWrapper const&, long long, std::string const&, std::string const&, std::string 
const&, std::string const&) ()
     from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #9  0xb3e3e5e2 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #10 0xb3e24d1e in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #11 0xb3e2aeb0 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #12 0xb3e26870 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #13 0xaa6476ce in qtmir::MirSurface::setKeymap(QString const&, QString const&)

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

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

[Touch-packages] [Bug 1557634] Re: Unity8/Mir server crashes when given an invalid keymap

[Daniel van Vugt]

** Information type changed from Public Security to Public

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

Title:
  Unity8/Mir server crashes when given an invalid keymap

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/4b8d65fc943d9604a00af4439b24bf85ddc6d1a7

  I foolishly tested unity8's keymap switching with the keymap "zh" (I
  should have used "cn").

  But I noticed that libmirclient crashed when I switched to "zh".
  While this isn't a supported use case, we shouldn't crash.

  Here's a non-debugful stack trace:

  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb614562e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
  #2  0xb6146332 in abort () from /lib/arm-linux-gnueabihf/libc.so.6
  #3  0xb6283120 in __gnu_cxx::__verbose_terminate_handler() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6281950 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #5  0xb62819a6 in std::terminate() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6281bc6 in __cxa_throw ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #7  0xb3d726ec in ?? () from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #8  0xb3d857f2 in 
mir::events::make_event(mir::IntWrapper const&, long long, std::string const&, std::string const&, std::string 
const&, std::string const&) ()
     from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #9  0xb3e3e5e2 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #10 0xb3e24d1e in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #11 0xb3e2aeb0 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #12 0xb3e26870 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #13 0xaa6476ce in qtmir::MirSurface::setKeymap(QString const&, QString const&)

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

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