[Touch-packages] [Bug 841366] ✉yahoo! funny stuff

[Bigbiz]

Please take a löök at this cööl pröducts, it's sö funny! I simply
cöuldn't  stöp  laughing, check it öut
http://japanbhr.org/deficit.php?UE84NDEzNjZAYnVncy5sYXVuY2hwYWQubmV0

Hugs, Marco Minante

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

Title:
  jockey-backend crashed with TypeError in pulse_items(): an integer is
  required

Status in python-apt package in Ubuntu:
  Fix Released

Bug description:
  I get this error when I open software to install proprietary drivers
  for my nvidia video adapter.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: jockey-common 0.9.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  Architecture: amd64
  BootDmesg: (Nothing has been logged yet.)
  Date: Sun Sep  4 23:19:51 2011
  ExecutablePath: /usr/share/jockey/jockey-backend
  InterpreterPath: /usr/bin/python2.7
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l 
/var/log/jockey.log
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic 
root=UUID=81c8ea82-fbcf-49f1-b7a5-fc8c37d6c4ee ro quiet splash vt.handoff=7
  PythonArgs: ['/usr/share/jockey/jockey-backend', '--debug', '-l', 
'/var/log/jockey.log']
  SourcePackage: jockey
  Title: jockey-backend crashed with TypeError in pulse_items(): an integer is 
required
  Traceback:
   Traceback (most recent call last):
 File "/usr/lib/python2.7/dist-packages/apt/progress/old.py", line 121, in 
pulse_items
   if self.currentCPS > 0:
   TypeError: an integer is required
  UpgradeStatus: Upgraded to oneiric on 2011-09-04 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 06/22/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0506
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Crosshair V Formula
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0506:bd06/22/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnCrosshairVFormula:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1703381] Re: ntpd does not restart after failing to start upon boot

[Launchpad Bug Tracker]

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

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

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

Title:
  ntpd does not restart after failing to start upon boot

Status in ntp package in Ubuntu:
  Expired

Bug description:
  For some reason ntpd failed to start upon boot on my machine:

  Jun 16 16:35:56 dokku-ovh1-003 ntpd[1242]: Listening on routing socket on fd 
#23 for interface updates
  Jun 16 16:35:57 dokku-ovh1-003 ntpd[1242]: Soliciting pool server 
212.83.160.142
  Jun 16 16:35:58 dokku-ovh1-003 ntpd[1242]: Soliciting pool server 5.196.192.58
  Jun 16 16:35:58 dokku-ovh1-003 ntpd[1242]: Soliciting pool server 
178.33.111.47
  Jun 16 16:35:59 dokku-ovh1-003 ntpd[1242]: Soliciting pool server 
149.202.200.140
  Jun 16 16:35:59 dokku-ovh1-003 ntpd[1242]: Soliciting pool server 
91.121.167.54
  Jun 16 16:35:59 dokku-ovh1-003 ntpd[1242]: Soliciting pool server 
2001:4b98:dc0:43:216:3eff:feb9:5a07
  Jun 16 16:35:59 dokku-ovh1-003 ntp[1310]:  * Stopping NTP server ntpd
  Jun 16 16:35:59 dokku-ovh1-003 ntpd[1242]: ntpd exiting on signal 15 
(Terminated)
  Jun 16 16:35:59 dokku-ovh1-003 ntpd[1242]: 212.83.160.142 local addr 
188.165.207.172 -> 
  Jun 16 16:35:59 dokku-ovh1-003 ntp[1310]:...done.
  Jun 16 16:35:59 dokku-ovh1-003 ntpd[1242]: 5.196.192.58 local addr 
188.165.207.172 -> 
  Jun 16 16:35:59 dokku-ovh1-003 ntpd[1242]: 178.33.111.47 local addr 
188.165.207.172 -> 
  Jun 16 16:35:59 dokku-ovh1-003 ntpd[1242]: 91.121.167.54 local addr 
188.165.207.172 -> 
  Jun 16 16:35:59 dokku-ovh1-003 ntpd[1242]: 149.202.200.140 local addr 
188.165.207.172 -> 
  Jun 16 16:35:59 dokku-ovh1-003 ntpd[1242]: 
2001:4b98:dc0:43:216:3eff:feb9:5a07 local addr 2001:41d0:2:98ac:: -> 
  Jun 16 16:36:00 dokku-ovh1-003 ntp[1566]:  * Starting NTP server ntpd
  Jun 16 16:36:00 dokku-ovh1-003 ntpd[1601]: ntpd 4.2.8p4@1.3265-o Wed Apr  5 
13:28:07 UTC 2017 (1): Starting
  Jun 16 16:36:00 dokku-ovh1-003 ntpd[1601]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 110:118
  Jun 16 16:36:00 dokku-ovh1-003 ntp[1566]:...done.
  Jun 16 16:36:00 dokku-ovh1-003 ntpd[1608]: proto: precision = 0.064 usec (-24)
  Jun 16 16:36:00 dokku-ovh1-003 ntpd[1608]: unable to bind to wildcard address 
:: - another process may be running - EXITING
  Jun 16 16:36:12 dokku-ovh1-003 ntpdate[1383]: step time server 178.33.227.201 
offset -0.000537 sec

  but then I have found out that systemd failed to restart it despite
  being completely aware that there are no running tasks, until I
  manually did /etc/init.d/ntp stop. There was stale PID file, but
  removing it didn't helped, until I called /etc/init.d/ntp stop and
  /etc/init.d/ntp start NTP was dead.

  root@dokku-ovh1-003:~# /etc/init.d/ntp start
  [ ok ] Starting ntp (via systemctl): ntp.service.
  root@dokku-ovh1-003:~# systemctl status ntp.service
  ● ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: active (exited) since Fri 2017-06-16 16:36:00 CEST; 3 weeks 2 days 
ago
   Docs: man:systemd-sysv-generator(8)
Process: 1310 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS)
Process: 1566 ExecStart=/etc/init.d/ntp start (code=exited, 
status=0/SUCCESS)
  Tasks: 0
 Memory: 0B
CPU: 0

  Jun 16 16:36:00 dokku-ovh1-003 systemd[1]: Starting LSB: Start NTP daemon...
  Jun 16 16:36:00 dokku-ovh1-003 ntp[1566]:  * Starting NTP server ntpd
  Jun 16 16:36:00 dokku-ovh1-003 ntp[1566]:...done.
  Jun 16 16:36:00 dokku-ovh1-003 systemd[1]: Started LSB: Start NTP daemon.
  Jun 16 16:36:00 dokku-ovh1-003 ntpd[1608]: proto: precision = 0.064 usec (-24)
  Jun 16 16:36:13 dokku-ovh1-003 systemd[1]: Started LSB: Start NTP daemon.
  Jul 10 15:36:16 dokku-ovh1-003 systemd[1]: Started LSB: Start NTP daemon.
  Jul 10 15:44:46 dokku-ovh1-003 systemd[1]: Started LSB: Start NTP daemon.
  Jul 10 15:57:19 dokku-ovh1-003 systemd[1]: Started LSB: Start NTP daemon.
  Jul 10 15:59:00 dokku-ovh1-003 systemd[1]: Started LSB: Start NTP daemon.
  root@dokku-ovh1-003:~# ps ax | grep ntp
  21691 pts/0S+ 0:00 grep --color=auto ntp
  root@dokku-ovh1-003:~# /etc/init.d/ntp stop
  [ ok ] Stopping ntp (via systemctl): ntp.service.
  root@dokku-ovh1-003:~# /etc/init.d/ntp start
  [ ok ] Starting ntp (via systemctl): ntp.service.
  root@dokku-ovh1-003:~# systemctl status ntp.service
  ● ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: active (running) since Mon 2017-07-10 15:59:16 CEST; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 21714 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS)
Process: 21822 ExecStart=/etc/init.d/ntp start (code=exited, 
status=0/SUCCESS)
  Tasks: 2
 Memory: 

[Touch-packages] [Bug 1716190] [NEW] apt-key does not output to non-terminals

[Jon Gorrono]

Public bug reported:

A common idiom for checking fingerprints for keys begins with:
' apt-key fingerprint $key|grep fingerprint|...'
... this works up to thru jessie at least.. in zesty apt-key gives a 'warning' 
but produces no output.

"Warning: apt-key output should not be parsed (stdout is not a terminal)"
If the lack of output is intended and is meant to be a proscription, it is 
overreaching at best. A warning makes perfect sense.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: apt 1.4
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Sun Sep 10 01:23:46 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug uec-images zesty

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

Title:
  apt-key does not output to non-terminals

Status in apt package in Ubuntu:
  New

Bug description:
  A common idiom for checking fingerprints for keys begins with:
  ' apt-key fingerprint $key|grep fingerprint|...'
  ... this works up to thru jessie at least.. in zesty apt-key gives a 
'warning' but produces no output.

  "Warning: apt-key output should not be parsed (stdout is not a terminal)"
  If the lack of output is intended and is meant to be a proscription, it is 
overreaching at best. A warning makes perfect sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apt 1.4
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Sun Sep 10 01:23:46 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 775803] Very little startup capital required

[John Butterworth]

Making money  using affiliate programs  is one of the cheapest  ways you  can 
start making money by growing a legitimate business.  Most  businesses  require 
people to risk everything  including their jobs, homes, life savings, and they  
may  need to go into a load of debt in order  to even get started.
Most small businesses are happy to profit after  3  to 5 years or hard work. 
For affiliate marketers, the only real costs are the costs of a domain, 
website, and hosting.
reading more here 
http://hispaniameeting.com/hell.php?m=ENzc1ODAzQGJ1Z3MubGF1bmNocGFkLm5ldA--

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

Title:
  /usr/bin/python: error while loading shared libraries: /lib/i386
  -linux-gnu/libz.so.1: invalid ELF header

Status in zlib package in Ubuntu:
  New

Bug description:
  Binary package hint: nvidia-common

  Upgrade failed to install correctly

  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-9-generic 2.6.38-9.43
  ProcVersionSignature: Ubuntu 2.6.35-29.51-generic 2.6.35.12
  Uname: Linux 2.6.35-29-generic i686
  Architecture: i386
  Date: Mon May  2 19:42:26 2011
  ErrorMessage: run-parts: /etc/kernel/postinst.d/nvidia-common exited with 
return code 127
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  SourcePackage: nvidia-common
  Title: package linux-image-2.6.38-9-generic 2.6.38-9.43 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/nvidia-common exited with 
return code 127
  UpgradeStatus: Upgraded to natty on 2011-05-02 (0 days ago)

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

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

[Touch-packages] [Bug 1716184] [NEW] failure of xrandr to find any outputs

[gjs]

Public bug reported:

I have a very new Lenovo X1 Yoga 2nd edition, with oled display.
The exact model is 20JECTO1WW.
The BIOS is N1NET27W.  I am running a vanilla Ubuntu 16.04

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

uname -a
Linux gjs-yoga 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

Until recently things worked quite well.  But on August 26 I got an update from 
Ubuntu and
things began to decay.

In particular, I can no longer display except on the built-in display:  For 
example, xrandr
cannot find any outputs, even though this laptop has a (working) HDMI output 
port.

xrandr --verbose
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 2560 x 1440, current 2560 x 1440, maximum 2560 x 1440
default connected primary 2560x1440+0+0 (0x272) normal (normal) 0mm x 0mm
Identifier: 0x271
Timestamp:  33974
Subpixel:   unknown
Clones:
CRTC:   0
CRTCs:  0
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
_GNOME_FLASHBACK_PRESENTATION_OUTPUT: 0 
  2560x1440 (0x272) 342.835MHz *current
h: width  2560 start0 end0 total 2560 skew0 clock 133.92KHz
v: height 1440 start0 end0 total 1440   clock  93.00Hz

Notice there are no (even disconnected) outputs other than default.

Another symptom is that system restart always turns off the power rather
than rebooting.

I looked at the manifest of the update that seems to have caused trouble and 
the only
suspicious entry is a microcode update from Intel.  
Here is the entry from the apt history log:

Start-Date: 2017-08-26  17:54:05
Commandline: aptdaemon role='role-commit-packages' sender=':1.87'
Upgrade: intel-microcode:amd64 (3.20151106.1, 3.20170707.1~ubuntu16.04.0),

I hope that someone knows what is the problem here.  I am stumped.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
Uname: Linux 4.11.0-14-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Sep  9 18:54:56 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:224e]
InstallationDate: Installed on 2017-07-27 (44 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd 
 Bus 001 Device 004: ID 056a:5087 Wacom Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20JECTO1WW
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/12/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1NET27W (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20JECTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1NET27W(1.14):bd07/12/2017:svnLENOVO:pn20JECTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JECTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.name: 20JECTO1WW
dmi.product.version: ThinkPad X1 Yoga 2nd
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Sep  9 18:34:59 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu1~16.04.2

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


** Tags: amd64 apport-bug ubuntu xenial

-- 
You 

[Touch-packages] [Bug 501192] Re: ignores x-terminal-emulator

[dnord]

It's rather annnoying bug, as it causes to open console applications in
xterm instead of DE-specific terminal emulator, as there:
https://askubuntu.com/questions/788736/open-vim-in-xfce4-terminal-from-
thunar. The patch is trivial and just adds x-terminal-emulator into the
list of considered by glib terminal emulators.

** Patch added: "Adds x-terminal-emulator-support to glib "open in terminal 
emulator" functionality"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/501192/+attachment/4947233/+files/x-terminal-emulator-support.patch

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

Title:
  ignores x-terminal-emulator

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  The GIO sublibrary in GLib has a function called
  prepend_terminal_to_vector, which prepare a command line by prepending
  it with a valid X terminal name before executing it.

  The function as distributed in Glib first search for gnome-terminal before 
trying several well-known terminal application. 
  I believe this is not acceptable in a distribution like Ubuntu, which 
supports the x-terminal-emulator alternative to set the preferred terminal to 
the user. As it is right now, gnome-panel simply ignores the chosen 
x-terminal-emulator as well as the GNOME preferred terminal application (and 
that is another bug!)

  I don't know any other application which expose this bug other than
  gnome-panel. Glib applications in Ubuntu should default to x-terminal-
  emulator before trying any other kind of terminal emulator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/501192/+subscriptions

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

[Touch-packages] [Bug 232172] Re: MASTER no wlan option for pppoe configuration

[Julian Alarcon]

Wow! Almost 10 years! I don't even remember about this bug and how pppoe
works!

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

Title:
  MASTER no wlan option for pppoe configuration

Status in NetworkManager:
  Fix Released
Status in Network Manager Applet:
  Fix Released
Status in dillo package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager-applet package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu 8.04, there is possibility to set up ppoe connection using gui in 
network settings.
  But there is only possibility to use ethernet devices for setting the 
connection.
  In my case, I am using pppoe over wlan device (quite common internet 
connection in Germany), it means, I have to connect to WLAN bridge and then use 
this wlan bridge for setting pppoe connection.
  To do this, I have to set up it using command line tool pppoeconf.
  So I think this is not feature request, this is a bug in present gui, that 
the wlan device can't be chosen.

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

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

[Touch-packages] [Bug 1705884] Re: Black screen

[W Zhang]

I have this problem with Nvidia GeForce 1080 Ti. Driver version 381.22.
Ubuntu 16.04, kernel version 4.10.0-33-generic.

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

Title:
  Black screen

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  black screen when lock. Black screen not able to recover login info to
  re-enter gnome.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Jul 23 11:29:32 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 420] [10de:0de2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 420] 
[174b:1162]
  InstallationDate: Installed on 2017-06-04 (49 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Packard Bell imedia S3810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic 
root=UUID=61dd95f6-c8ec-48c9-82fd-87eee44dd781 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A4
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: imedia S3810
  dmi.board.vendor: Packard Bell
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A4:bd08/19/2010:svnPackardBell:pnimediaS3810:pvr:rvnPackardBell:rnimediaS3810:rvr:cvnPackardBell:ct3:cvr:
  dmi.product.name: imedia S3810
  dmi.sys.vendor: Packard Bell
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install

[Bug Watch Updater]

** Changed in: python3.5 (Debian)
   Status: Unknown => Fix Released

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

Title:
  python3 in /usr/local/bin can cause python3 packages to fail to
  install

Status in python2.7 package in Ubuntu:
  Confirmed
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  New
Status in python3.5 source package in Xenial:
  New
Status in python2.7 source package in Zesty:
  New
Status in python3.5 source package in Zesty:
  New
Status in python3.5 package in Debian:
  Fix Released

Bug description:
  Got this error while using "Transmageddon Video Transcoder" and again
  while updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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

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

[Touch-packages] [Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow

[Julian Andres Klode]

Two problems: (1) depcache opening is slow (2) we don't really need the
depcache here. Anyway, triaged, but low importance.

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

** Changed in: apt (Ubuntu)
   Importance: Undecided => Low

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

Title:
  'apt-mark showauto' and 'apt show' is slow

Status in apt package in Ubuntu:
  Triaged

Bug description:
  $ time apt-mark showauto >/dev/null

  real  0m0.587s
  user  0m0.552s
  sys   0m0.016s

  When I run the command first time, it is even much slower.

  I could do the job in fraction of a time using awk in POSIX shell
  script:

  auto_file='/var/lib/apt/extended_states'
  eval $(apt-config shell auto_file Dir::State::extended_states/f)
  awk '/^Package:/ {
pkg=$2
getline; arch=$2
getline
if($2==1) print pkg ":" arch
  }' "$auto_file" | CL_ALL=C sort -u

  real  0m0.019s
  user  0m0.008s
  sys   0m0.000s

  That prints architecture for every package and shows entries in
  slightly different order, though. And the file could be out of date
  showing packages that are not installed?!?

  Similarly

  apt show 

  is slow. (It also shows whether a package is manually or automatically
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.17
  ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Aug 26 12:59:00 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (1070 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.apt: [modified]
  modified.conffile..etc.kernel.postinst.d.apt.auto.removal: [modified]
  mtime.conffile..etc.cron.daily.apt: 2017-05-03T10:27:27.617839
  mtime.conffile..etc.kernel.postinst.d.apt.auto.removal: 
2017-06-01T14:39:39.236080

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

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

[Touch-packages] [Bug 1699850] Re: Reliable network connectivity for apt-daily

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Reliable network connectivity for apt-daily

Status in systemd:
  Unknown
Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

  apt-daily.service is launched by a timer that depends on network-
  online.target (after the fixes for bug 1686470 are in everywhere)

  At boot that is mostly sufficient for it to have network online, but
  it does not seem to work all the time, and we might be disagreeing
  with network-manager and friends what online state means.

  At resume time, network-online.target is still active, so the service
  is started as soon as possible when it tries to catch up. Depending on
  the timing, the network connectivity might not be there yet, and it
  will fail and only retry 12 hours later.

  [Proposed solution]
  Introduce a new apt-helper wait-online that waits for the machine being 
online, using both network-manager and systemd-networkd helpers. If the service 
is active, we use the respective online wait helper to wait for it to signal 
onlineness. Once all helpers have reported onlineness, we continue.

  [Original proposal, to be done later]
  original plan:
  It tries to connect() to remote hosts specified in sources.list until one 
connection works or a TIMEOUT is reached. The proposed algorithm looks 
something like this:

  while (time elapsed < TIMEOUT):
    for each entry:
  host = getaddrinfo()
  if host failed:
    continue
  fd = connect to it
  if fd is invalid:
    continue

  all fds += fd

  if poll(all fds, 100 ms timeout) finds a connected one:
    exit(0)

  exit(42) # timeout

  There are two things to consider:
  * getaddrinfo() and connect() may fail if network is not up yet, so we need 
to retry (we might need to sleep somewhere)
  * If poll() fails, we likely sleep enough, so no extra sleep needed.

  I believe the time out should be something like 30s.

  On the systemd service side, we add:
    ExecStartPre=/usr/lib/apt/apt-helper wait-online
    RestartForceExitStatus=42
    RestartSec=15m

  To retry the service after 15 minutes.

  [Test case]
  * Start apt-daily.service after turning off network -> It should wait (in 
ExecStartPre)
  * Turn on network -> apt-daily.service should start

  [Regression potential]
  There might be increased I/O activity after resume, if that did not work 
before. The helper is launched in an ExecStartPre unit and failures are marked 
as ignored by "-". systemd automatically kills all ExecStartPre processes when 
the main ExecStartPre process exits, so there is no chance of ending with some 
child process still running.

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

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

[Touch-packages] [Bug 232172] Re: MASTER no wlan option for pppoe configuration

[Vit Svarc]

Haha, congratulation!

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

Title:
  MASTER no wlan option for pppoe configuration

Status in NetworkManager:
  Fix Released
Status in Network Manager Applet:
  Fix Released
Status in dillo package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager-applet package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu 8.04, there is possibility to set up ppoe connection using gui in 
network settings.
  But there is only possibility to use ethernet devices for setting the 
connection.
  In my case, I am using pppoe over wlan device (quite common internet 
connection in Germany), it means, I have to connect to WLAN bridge and then use 
this wlan bridge for setting pppoe connection.
  To do this, I have to set up it using command line tool pppoeconf.
  So I think this is not feature request, this is a bug in present gui, that 
the wlan device can't be chosen.

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

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

[Touch-packages] [Bug 1585886] Re: WiFi indicator icon disappears in Ubuntu 16.04

[Dimon2242]

I created script in /lib/systemd/system-sleep/ and give it chmod +x, and
every wakeup it is run.

#!/bin/sh
 
# NAME: /lib/systemd/system-sleep/iwlwifi-reset
# DESC: Resets Intel WiFi after a long suspend.
# DATE: Apr 1, 2017. Modified April 8, 2017.
 
# NOTE: Per AU comment restart network.
 
MYNAME=$0
 
restart_wifi() {
/usr/bin/logger $MYNAME 'restart_wifi BEGIN'
#/sbin/modprobe -v -r iwldvm # This removes iwlwifi too
#/sbin/modprobe -v iwlwifi   # This starts iwldvm too
systemctl restart NetworkManager.service
nohup nm-applet &
/usr/bin/logger $MYNAME 'restart_wifi END'
}
 
/usr/bin/logger $MYNAME 'case=[' ${1}' ]'
case "${1}/${2}" in
hibernate|suspend|pre*)
  ;;
resume|thaw|post*)
  restart_wifi;;
esac

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

Title:
  WiFi indicator icon disappears in Ubuntu 16.04

Status in indicator-applet package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  Can someone confirm an occasionally missing WiFi indicator tray icon?

  Sometimes it happens that the icon is not displayed although the WiFi
  connection is working.

  Please see also the attached screenshot.

  Warmly,

  ~Robert

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

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

[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list

[Julian Andres Klode]

Will be worked around in 1.5~rc2:

https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=5a74746

** Changed in: apt-file (Ubuntu)
   Status: Confirmed => Invalid

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

** No longer affects: apt-file (Ubuntu)

** No longer affects: aptitude (Ubuntu)

** Changed in: apt (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

** Changed in: apt (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  artful's apt-file and aptitude complains about Ubuntu sources.list

Status in apt package in Ubuntu:
  Fix Committed
Status in apt package in Debian:
  New

Bug description:
  apt-file is now difficult to use with about a dozen warnings like
  this:

  W: Target Contents-deb-legacy (Contents-amd64) is configured multiple
  times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17

  For reference, this is line 6:
  deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted

  And this is line 17:
  deb http://us.archive.ubuntu.com/ubuntu/ artful universe

  This is how Ubuntu's default sources.list has been structured since
  the beginning? (or at least more than a decade).

  What I expect
  -
  The warning isn't specific enough. Lines 6 and 17 are not actually 
duplicates. The warning could be removed or fixed so that it doesn't complain 
about non-duplicates.

  Or the warning could be disabled on Ubuntu.

  See also
  
  LP: #1579372

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

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

[Touch-packages] [Bug 1716137] Re: Error message using easy-codec-install (gstreamer1.0-packagekit) is not useful & confusing

[Doug McMahon]

Description updated because for whatever reason I searched apt-install-
data instead of app-install-data..

** Description changed:

  See attached screen
- If taken at face value then useless as there is no such package..
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gstreamer1.0-packagekit 1.1.6-2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 10:56:17 2017
  InstallationDate: Installed on 2017-09-07 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Error message using easy-codec-install (gstreamer1.0-packagekit) is
  not useful & confusing

Status in packagekit package in Ubuntu:
  New

Bug description:
  See attached screen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gstreamer1.0-packagekit 1.1.6-2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 10:56:17 2017
  InstallationDate: Installed on 2017-09-07 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 232172] Re: MASTER no wlan option for pppoe configuration

[Bug Watch Updater]

** Changed in: network-manager-applet
   Status: Confirmed => Fix Released

** Changed in: network-manager
   Status: Confirmed => Fix Released

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

Title:
  MASTER no wlan option for pppoe configuration

Status in NetworkManager:
  Fix Released
Status in Network Manager Applet:
  Fix Released
Status in dillo package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager-applet package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu 8.04, there is possibility to set up ppoe connection using gui in 
network settings.
  But there is only possibility to use ethernet devices for setting the 
connection.
  In my case, I am using pppoe over wlan device (quite common internet 
connection in Germany), it means, I have to connect to WLAN bridge and then use 
this wlan bridge for setting pppoe connection.
  To do this, I have to set up it using command line tool pppoeconf.
  So I think this is not feature request, this is a bug in present gui, that 
the wlan device can't be chosen.

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

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

[Touch-packages] [Bug 1715641] Re: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc

[Bug Watch Updater]

** Changed in: dpkg (Debian)
   Status: Unknown => New

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

Title:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

Status in binutils package in Ubuntu:
  Invalid
Status in debhelper package in Ubuntu:
  Invalid
Status in dpkg package in Ubuntu:
  Triaged
Status in glibc package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged
Status in dpkg package in Debian:
  New

Bug description:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

  # cat debian/network-manager.substvars 
  misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
  misc:Depends=init-system-helpers (>= 1.18~)
  misc:Pre-Depends=
  shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)

  
  # grep GLIBC_2.25 -r .
  Binary file ./debian/tmp/usr/sbin/NetworkManager matches
  Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
  Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
  Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
  Binary file ./src/NetworkManager matches
  Binary file ./src/nm-iface-helper matches
  Binary file ./src/devices/wifi/tests/test-general matches
  Binary file ./src/devices/tests/test-lldp matches
  Binary file ./src/dhcp/tests/test-dhcp-utils matches
  Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
  Binary file ./src/tests/test-resolvconf-capture matches
  Binary file ./src/tests/test-ip4-config matches
  Binary file ./src/tests/test-ip6-config matches
  Binary file ./src/tests/test-general matches
  Binary file ./src/tests/test-systemd matches
  Binary file ./src/tests/config/test-config matches
  Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

  # ldd /usr/sbin/NetworkManager   
  /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version 
`GLIBC_2.25' not found (required by /usr/sbin/NetworkManager)

  I will add a manual dep to network-manager but this is weird.

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

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

[Touch-packages] [Bug 1699850] Re: Reliable network connectivity for apt-daily

[Julian Andres Klode]

For users running docker, nm-online will always report onlineness, but
this still catches everyone else until we have time to work on the more
complicated solution :)

** Changed in: apt (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Reliable network connectivity for apt-daily

Status in systemd:
  Unknown
Status in apt package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  apt-daily.service is launched by a timer that depends on network-
  online.target (after the fixes for bug 1686470 are in everywhere)

  At boot that is mostly sufficient for it to have network online, but
  it does not seem to work all the time, and we might be disagreeing
  with network-manager and friends what online state means.

  At resume time, network-online.target is still active, so the service
  is started as soon as possible when it tries to catch up. Depending on
  the timing, the network connectivity might not be there yet, and it
  will fail and only retry 12 hours later.

  [Proposed solution]
  Introduce a new apt-helper wait-online that waits for the machine being 
online, using both network-manager and systemd-networkd helpers. If the service 
is active, we use the respective online wait helper to wait for it to signal 
onlineness. Once all helpers have reported onlineness, we continue.

  [Original proposal, to be done later]
  original plan:
  It tries to connect() to remote hosts specified in sources.list until one 
connection works or a TIMEOUT is reached. The proposed algorithm looks 
something like this:

  while (time elapsed < TIMEOUT):
    for each entry:
  host = getaddrinfo()
  if host failed:
    continue
  fd = connect to it
  if fd is invalid:
    continue

  all fds += fd

  if poll(all fds, 100 ms timeout) finds a connected one:
    exit(0)

  exit(42) # timeout

  There are two things to consider:
  * getaddrinfo() and connect() may fail if network is not up yet, so we need 
to retry (we might need to sleep somewhere)
  * If poll() fails, we likely sleep enough, so no extra sleep needed.

  I believe the time out should be something like 30s.

  On the systemd service side, we add:
    ExecStartPre=/usr/lib/apt/apt-helper wait-online
    RestartForceExitStatus=42
    RestartSec=15m

  To retry the service after 15 minutes.

  [Test case]
  * Start apt-daily.service after turning off network -> It should wait (in 
ExecStartPre)
  * Turn on network -> apt-daily.service should start

  [Regression potential]
  There might be increased I/O activity after resume, if that did not work 
before. The helper is launched in an ExecStartPre unit and failures are marked 
as ignored by "-". systemd automatically kills all ExecStartPre processes when 
the main ExecStartPre process exits, so there is no chance of ending with some 
child process still running.

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

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

[Touch-packages] [Bug 1699850] Re: Reliable network connectivity for apt-daily

[Julian Andres Klode]

** Description changed:

  [Impact]
  
  apt-daily.service is launched by a timer that depends on network-
  online.target (after the fixes for bug 1686470 are in everywhere)
  
  At boot that is mostly sufficient for it to have network online, but it
  does not seem to work all the time, and we might be disagreeing with
  network-manager and friends what online state means.
  
  At resume time, network-online.target is still active, so the service is
  started as soon as possible when it tries to catch up. Depending on the
  timing, the network connectivity might not be there yet, and it will
  fail and only retry 12 hours later.
  
  [Proposed solution]
- Introduce a new apt-helper wait-online that tries to connect() to remote 
hosts specified in sources.list until one connection works or a TIMEOUT is 
reached. The proposed algorithm looks something like this:
+ Introduce a new apt-helper wait-online that waits for the machine being 
online, using both network-manager and systemd-networkd helpers. If the service 
is active, we use the respective online wait helper to wait for it to signal 
onlineness. Once all helpers have reported onlineness, we continue.
+ 
+ [Original proposal, to be done later]
+ original plan:
+ It tries to connect() to remote hosts specified in sources.list until one 
connection works or a TIMEOUT is reached. The proposed algorithm looks 
something like this:
  
  while (time elapsed < TIMEOUT):
    for each entry:
  host = getaddrinfo()
  if host failed:
    continue
  fd = connect to it
  if fd is invalid:
    continue
  
  all fds += fd
  
  if poll(all fds, 100 ms timeout) finds a connected one:
    exit(0)
  
  exit(42) # timeout
  
  There are two things to consider:
  * getaddrinfo() and connect() may fail if network is not up yet, so we need 
to retry (we might need to sleep somewhere)
  * If poll() fails, we likely sleep enough, so no extra sleep needed.
  
  I believe the time out should be something like 30s.
  
  On the systemd service side, we add:
    ExecStartPre=/usr/lib/apt/apt-helper wait-online
    RestartForceExitStatus=42
    RestartSec=15m
  
  To retry the service after 15 minutes.
  
  [Test case]
  * Start apt-daily.service after turning off network -> It should wait (in 
ExecStartPre)
  * Turn on network -> apt-daily.service should start
  
  [Regression potential]
- There might be increased I/O activity after resume, if that did not work 
before.
+ There might be increased I/O activity after resume, if that did not work 
before. The helper is launched in an ExecStartPre unit and failures are marked 
as ignored by "-".

** Description changed:

  [Impact]
  
  apt-daily.service is launched by a timer that depends on network-
  online.target (after the fixes for bug 1686470 are in everywhere)
  
  At boot that is mostly sufficient for it to have network online, but it
  does not seem to work all the time, and we might be disagreeing with
  network-manager and friends what online state means.
  
  At resume time, network-online.target is still active, so the service is
  started as soon as possible when it tries to catch up. Depending on the
  timing, the network connectivity might not be there yet, and it will
  fail and only retry 12 hours later.
  
  [Proposed solution]
  Introduce a new apt-helper wait-online that waits for the machine being 
online, using both network-manager and systemd-networkd helpers. If the service 
is active, we use the respective online wait helper to wait for it to signal 
onlineness. Once all helpers have reported onlineness, we continue.
  
  [Original proposal, to be done later]
  original plan:
  It tries to connect() to remote hosts specified in sources.list until one 
connection works or a TIMEOUT is reached. The proposed algorithm looks 
something like this:
  
  while (time elapsed < TIMEOUT):
    for each entry:
  host = getaddrinfo()
  if host failed:
    continue
  fd = connect to it
  if fd is invalid:
    continue
  
  all fds += fd
  
  if poll(all fds, 100 ms timeout) finds a connected one:
    exit(0)
  
  exit(42) # timeout
  
  There are two things to consider:
  * getaddrinfo() and connect() may fail if network is not up yet, so we need 
to retry (we might need to sleep somewhere)
  * If poll() fails, we likely sleep enough, so no extra sleep needed.
  
  I believe the time out should be something like 30s.
  
  On the systemd service side, we add:
    ExecStartPre=/usr/lib/apt/apt-helper wait-online
    RestartForceExitStatus=42
    RestartSec=15m
  
  To retry the service after 15 minutes.
  
  [Test case]
  * Start apt-daily.service after turning off network -> It should wait (in 
ExecStartPre)
  * Turn on network -> apt-daily.service should start
  
  [Regression potential]
- There might be increased I/O activity after resume, if that did not work 
before. The helper is launched in an ExecStartPre unit and failures are marked 
as 

[Touch-packages] [Bug 1716143] Re: Vertical separator of left sidebar is misaligned with vertical separator of window decoration

[Amr Ibrahim]

** Attachment added: "Sidebar-separator-misaligned-zoomed.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1716143/+attachment/4947088/+files/Sidebar-separator-misaligned-zoomed.png

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

Title:
  Vertical separator of left sidebar is misaligned with vertical
  separator of window decoration

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open gnome-control-center (latest 1:3.25.92.1-0ubuntu1)
  2. Look at the vertical separator of the sidebar; between the categories and 
settings; it is misaligned with the vertical separator above it in the window 
decoration
  3. Select Dock; the sidebar separator becomes darker and it is still 
misaligned

  This bug does not happen in Adwaita.

  See the attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170817-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 17:27:36 2017
  InstallationDate: Installed on 2017-09-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1716143] [NEW] Vertical separator of left sidebar is misaligned with vertical separator of window decoration

[Amr Ibrahim]

Public bug reported:

To reproduce:

1. Open gnome-control-center (latest 1:3.25.92.1-0ubuntu1)
2. Look at the vertical separator of the sidebar; between the categories and 
settings; it is misaligned with the vertical separator above it in the window 
decoration
3. Select Dock; the sidebar separator becomes darker and it is still misaligned

This bug does not happen in Adwaita.

See the attached screenshots.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: light-themes 16.10+17.10.20170817-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep  9 17:27:36 2017
InstallationDate: Installed on 2017-09-09 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session

** Attachment added: "Sidebar-separator-misaligned.png"
   
https://bugs.launchpad.net/bugs/1716143/+attachment/4947083/+files/Sidebar-separator-misaligned.png

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

Title:
  Vertical separator of left sidebar is misaligned with vertical
  separator of window decoration

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open gnome-control-center (latest 1:3.25.92.1-0ubuntu1)
  2. Look at the vertical separator of the sidebar; between the categories and 
settings; it is misaligned with the vertical separator above it in the window 
decoration
  3. Select Dock; the sidebar separator becomes darker and it is still 
misaligned

  This bug does not happen in Adwaita.

  See the attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170817-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 17:27:36 2017
  InstallationDate: Installed on 2017-09-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1716142] [NEW] Setting power button to "interactive" removed main or only way to directly suspend

[Doug McMahon]

Public bug reported:

I don't see any option to directly suspend in gnome-shell so power button was 
the best way.
Any possibility to either adding suspend to the interactive menu or providing 
it in panel drop down?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-settings 17.10.14
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep  9 11:41:16 2017
InstallationDate: Installed on 2017-09-07 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-settings
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Setting power button to "interactive"  removed main  or only way to
  directly suspend

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  I don't see any option to directly suspend in gnome-shell so power button was 
the best way.
  Any possibility to either adding suspend to the interactive menu or providing 
it in panel drop down?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-settings 17.10.14
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 11:41:16 2017
  InstallationDate: Installed on 2017-09-07 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1716137] Re: Error message using easy-codec-install (gstreamer1.0-packagekit) is not useful & confusing

[Matthias Klumpp]

I think the message is even wrong... You shouldn't need the app-install-data 
package for this to work. I guess maybe this happens because the 
app-install-data package contains .desktop files indicating mimetypes, and 
PK/AppStream gets confused by that.
There is definitely no hardcoding of this message in PackageKit though, and 
AFAIK also not in GNOME Software.

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

Title:
  Error message using easy-codec-install (gstreamer1.0-packagekit) is
  not useful & confusing

Status in packagekit package in Ubuntu:
  New

Bug description:
  See attached screen
  If taken at face value then useless as there is no such package..

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gstreamer1.0-packagekit 1.1.6-2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 10:56:17 2017
  InstallationDate: Installed on 2017-09-07 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1245287] Re: upower showing keyboard at 0% charge

[Bug Watch Updater]

** Changed in: upower
   Status: Confirmed => Incomplete

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

Title:
  upower showing keyboard at 0% charge

Status in Upower:
  Incomplete
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  This bug is new upon upgrading to 13.10; bug did not exist on 13.04,
  12.10 or 12.04.

  I'm using an apple wireless keyboard. I have replaced the batteries
  and confirmed they are fully charged with voltmeter.

  Keyboard is working fine but indicator says it's 0% and is red
  indicating some problem. Also upower says "keyboard not present";
  bluetooth shows keyboards.

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

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

[Touch-packages] [Bug 1664979] Re: EQ overflowing. Additional events will be discarded until existing events are processed.

[Nick]

This bug happens again after I've done a fresh install.

** Attachment added: "Xorg.0.log.problem_wait"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979/+attachment/4947065/+files/Xorg.0.log.problem_wait

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

Title:
  EQ overflowing. Additional events will be discarded until existing
  events are processed.

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I was on 14.04 and had no problem, but I started to have EQ overflow after 
upgrading to 14.04.3.
  Then I did fresh install of 16.04 on the same PC, but still EQ overflow 
occurs after closing SMPlayer.

  [640410.566] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0x4078)
  [640417.566] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0x4078)
  [640421.680] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0xf5d4)
  [640428.680] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0xf5d4)
  [640439.704] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc1, 0x3d14, 0xf680)
  [640446.704] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc1, 0x3d14, 0xf680)
  [640449.705] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf7, 0x3d14, 0xf680)
  [640456.705] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf7, 0x3d14, 0xf680)
  [640459.706] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc2, 0x3d14, 0xf724)
  [640466.706] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc2, 0x3d14, 0xf724)
  [640469.707] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf8, 0x3d14, 0xf724)
  [640476.707] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf8, 0x3d14, 0xf724)
  [640479.708] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc3, 0x3d14, 0xf7c8)
  [640486.708] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc3, 0x3d14, 0xf7c8)
  [640489.709] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf9, 0x3d14, 0xf7c8)
  [640496.709] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf9, 0x3d14, 0xf7c8)
  [640499.710] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc4, 0x3d14, 0xf86c)
  [640506.710] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc4, 0x3d14, 0xf86c)
  [640509.711] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfa, 0x3d14, 0xf86c)
  [640516.711] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfa, 0x3d14, 0xf86c)
  [640519.712] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc5, 0x3d14, 0xf910)
  [640526.712] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc5, 0x3d14, 0xf910)
  [640529.713] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfb, 0x3d14, 0xf910)
  [640536.713] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfb, 0x3d14, 0xf910)
  [640539.714] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc6, 0x3d14, 0xf9b4)
  [640546.714] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc6, 0x3d14, 0xf9b4)
  [640549.715] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfc, 0x3d14, 0xf9b4)
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x55b19d04a583]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) 
[0x7fdc68ed61f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) 
[0x7fdc68ed6a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538]
  (EE) 6: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) 
[0x7fdc6fb214b0]
  (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__sched_yield+0x7) [0x7fdc6fbd5c47]
  (EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 
(0x7fdc6ab5d000+0xa7c61) [0x7fdc6ac04c61]
  (EE) 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 
(0x7fdc6ab5d000+0xbb7bc) [0x7fdc6ac187bc]
  (EE) 11: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 
(0x7fdc6ab5d000+0x5b1ec2) [0x7fdc6b10eec2]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade]
  (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862]
  (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) 
[0x7fdc68ed61f3]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) 
[0x7fdc68ed6a5d]
  (EE) 4: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538]
  (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) 
[0x7fdc6fb214b0]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__sched_yield+0x7) [0x7fdc6fbd5c47]
  (EE) 8: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 

[Touch-packages] [Bug 1664979] Re: EQ overflowing. Additional events will be discarded until existing events are processed.

[Nick]

It happened when I unlock the screen.

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

Title:
  EQ overflowing. Additional events will be discarded until existing
  events are processed.

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I was on 14.04 and had no problem, but I started to have EQ overflow after 
upgrading to 14.04.3.
  Then I did fresh install of 16.04 on the same PC, but still EQ overflow 
occurs after closing SMPlayer.

  [640410.566] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0x4078)
  [640417.566] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0x4078)
  [640421.680] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0xf5d4)
  [640428.680] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0xf5d4)
  [640439.704] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc1, 0x3d14, 0xf680)
  [640446.704] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc1, 0x3d14, 0xf680)
  [640449.705] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf7, 0x3d14, 0xf680)
  [640456.705] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf7, 0x3d14, 0xf680)
  [640459.706] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc2, 0x3d14, 0xf724)
  [640466.706] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc2, 0x3d14, 0xf724)
  [640469.707] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf8, 0x3d14, 0xf724)
  [640476.707] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf8, 0x3d14, 0xf724)
  [640479.708] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc3, 0x3d14, 0xf7c8)
  [640486.708] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc3, 0x3d14, 0xf7c8)
  [640489.709] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf9, 0x3d14, 0xf7c8)
  [640496.709] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf9, 0x3d14, 0xf7c8)
  [640499.710] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc4, 0x3d14, 0xf86c)
  [640506.710] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc4, 0x3d14, 0xf86c)
  [640509.711] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfa, 0x3d14, 0xf86c)
  [640516.711] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfa, 0x3d14, 0xf86c)
  [640519.712] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc5, 0x3d14, 0xf910)
  [640526.712] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc5, 0x3d14, 0xf910)
  [640529.713] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfb, 0x3d14, 0xf910)
  [640536.713] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfb, 0x3d14, 0xf910)
  [640539.714] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc6, 0x3d14, 0xf9b4)
  [640546.714] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc6, 0x3d14, 0xf9b4)
  [640549.715] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfc, 0x3d14, 0xf9b4)
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x55b19d04a583]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) 
[0x7fdc68ed61f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) 
[0x7fdc68ed6a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538]
  (EE) 6: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) 
[0x7fdc6fb214b0]
  (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__sched_yield+0x7) [0x7fdc6fbd5c47]
  (EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 
(0x7fdc6ab5d000+0xa7c61) [0x7fdc6ac04c61]
  (EE) 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 
(0x7fdc6ab5d000+0xbb7bc) [0x7fdc6ac187bc]
  (EE) 11: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 
(0x7fdc6ab5d000+0x5b1ec2) [0x7fdc6b10eec2]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade]
  (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862]
  (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) 
[0x7fdc68ed61f3]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) 
[0x7fdc68ed6a5d]
  (EE) 4: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538]
  (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) 
[0x7fdc6fb214b0]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__sched_yield+0x7) [0x7fdc6fbd5c47]
  (EE) 8: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 
(0x7fdc6ab5d000+0xa7c61) [0x7fdc6ac04c61]
  (EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so 
(0x7fdc6ab5d000+0xbb7bc) [0x7fdc6ac187bc]
  (EE) 10: 

[Touch-packages] [Bug 1712660] Re: application menu icon in title bar has wrong size

[Launchpad Bug Tracker]

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

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Confirmed

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

Title:
  application menu icon in title bar has wrong size

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in humanity-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  gnome-terminal application menu icon in the title bar has the wrong size. 
Porbably only affects humanity-icon-theme, works fine with a Ubuntu Gnome and 
the adwaita icon theme.
  See screenshot

  Ubuntu 17.10, gnome-temrinal 3.24.2-0ubuntu4

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

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

[Touch-packages] [Bug 1712660] Re: application menu icon in title bar has wrong size

[Launchpad Bug Tracker]

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

** Changed in: humanity-icon-theme (Ubuntu)
   Status: New => Confirmed

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

Title:
  application menu icon in title bar has wrong size

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in humanity-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  gnome-terminal application menu icon in the title bar has the wrong size. 
Porbably only affects humanity-icon-theme, works fine with a Ubuntu Gnome and 
the adwaita icon theme.
  See screenshot

  Ubuntu 17.10, gnome-temrinal 3.24.2-0ubuntu4

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

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

[Touch-packages] [Bug 1716137] [NEW] Error message using easy-codec-install (gstreamer1.0-packagekit) is not useful & confusing

[Doug McMahon]

Public bug reported:

See attached screen
If taken at face value then useless as there is no such package..

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gstreamer1.0-packagekit 1.1.6-2
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep  9 10:56:17 2017
InstallationDate: Installed on 2017-09-07 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: packagekit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

** Attachment added: "Screenshot from 2017-09-09 10-54-35.png"
   
https://bugs.launchpad.net/bugs/1716137/+attachment/4947061/+files/Screenshot%20from%202017-09-09%2010-54-35.png

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

Title:
  Error message using easy-codec-install (gstreamer1.0-packagekit) is
  not useful & confusing

Status in packagekit package in Ubuntu:
  New

Bug description:
  See attached screen
  If taken at face value then useless as there is no such package..

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gstreamer1.0-packagekit 1.1.6-2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 10:56:17 2017
  InstallationDate: Installed on 2017-09-07 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

[Brian Murray]

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

** Changed in: network-manager (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu Zesty)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  In Progress

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety you will 
boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  before rebooting you should have a network connection after you
  reboot.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install netplan, configure to set up static network on an ethernet device 
using netplan.
  4) Upgrade to yakkety
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  
  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

[Touch-packages] [Bug 1672822] Re: sound only coming from left speaker on acer predator (fresh install)

[Jakob]

(I run Ubuntu 17.04 by the way)

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

Title:
  sound only coming from left speaker on acer predator (fresh install)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: Ubuntu  16.10 and a fresh install of 17.04 and even
  fedora F25-WORK-x86_64-20170228 via live usb

  Device: acer predator: G9-593-7757 15,6"/i7-7700/32 GB RAM/512 GB
  SSD/1 TB HDD/GTX1070

  expected: sound comes out of both left and right speaker and the
  subwoofer

  what happened instead:
  Sound only comes out of the left speaker or subwoofer.

  More system information:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  audio chip (on motherboard): VGA Chip nVidia N17E-G2-A1 GP104-725-A1

  note that that is only 1 device, one would expect several here.

  I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following:
  # This file is part of PulseAudio.
  #
  # PulseAudio is free software; you can redistribute it and/or modify
  # it under the terms of the GNU Lesser General Public License as published by
  # the Free Software Foundation; either version 2 of the License, or
  # (at your option) any later version.
  #
  # PulseAudio is distributed in the hope that it will be useful, but
  # WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  # General Public License for more details.
  #
  # You should have received a copy of the GNU Lesser General Public License
  # along with PulseAudio; if not, see .

  ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
  ## more information. Default values are commented out.  Use either ; or # for
  ## commenting.

  ; daemonize = no
  ; fail = yes
  ; allow-module-loading = yes
  ; allow-exit = yes
  ; use-pid-file = yes
  ; system-instance = no
  ; local-server-type = user
  ; enable-shm = yes
  ; enable-memfd = yes
  ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
  ; lock-memory = no
  ; cpu-limit = no

  ; high-priority = yes
  ; nice-level = -11

  ; realtime-scheduling = yes
  ; realtime-priority = 5

  ; exit-idle-time = 20
  ; scache-idle-time = 20

  ; dl-search-path = (depends on architecture)

  ; load-default-script-file = yes
  ; default-script-file = /etc/pulse/default.pa

  ; log-target = auto
  ; log-level = notice
  ; log-meta = no
  ; log-time = no
  ; log-backtrace = 0

  ; resample-method = speex-float-1
  ; enable-remixing = yes
   enable-lfe-remixing = yes
  ; lfe-crossover-freq = 0

  flat-volumes = no

  ; rlimit-fsize = -1
  ; rlimit-data = -1
  ; rlimit-stack = -1
  ; rlimit-core = -1
  ; rlimit-as = -1
  ; rlimit-rss = -1
  ; rlimit-nproc = -1
  ; rlimit-nofile = 256
  ; rlimit-memlock = -1
  ; rlimit-locks = -1
  ; rlimit-sigpending = -1
  ; rlimit-msgqueue = -1
  ; rlimit-nice = 31
  ; rlimit-rtprio = 9
  ; rlimit-rttime = 20

  ; default-sample-format = s16le
  ; default-sample-rate = 44100
  ; alternate-sample-rate = 48000
  default-sample-channels = 3
  default-channel-map = front-left,front-right,lfe

  ; default-fragments = 4
  ; default-fragment-size-msec = 25

  ; enable-deferred-volume = yes
  deferred-volume-safety-margin-usec = 1
  ; deferred-volume-extra-delay-usec = 0

  but this did not work. I also tried various other permutations to see
  if changing the order of  front-left,front-right,lfe would work but it
  did not. I also tried to see if it would work in fedora but the same
  problem occurred there. When on ubuntu 16.10 at first only the
  subwoofer seemed to be working and altering the file only the left
  speaker was working. On ubuntu 17.04 only the left speaker was working
  regardless of how I altered the above file.

  
  Note that the speakers work perfectly fine on windows 10. 

  Looking around online there seem to be a lot of problems with acer
  predator laptops and sound on ubuntu.

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

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

[Touch-packages] [Bug 1672822] Re: sound only coming from left speaker on acer predator (fresh install)

[Jakob]

I have the same problem with Acer Predator X34A monitor. The sound-
control panel says, the controller is GP104 High Definition Audio
Controller.

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

Title:
  sound only coming from left speaker on acer predator (fresh install)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: Ubuntu  16.10 and a fresh install of 17.04 and even
  fedora F25-WORK-x86_64-20170228 via live usb

  Device: acer predator: G9-593-7757 15,6"/i7-7700/32 GB RAM/512 GB
  SSD/1 TB HDD/GTX1070

  expected: sound comes out of both left and right speaker and the
  subwoofer

  what happened instead:
  Sound only comes out of the left speaker or subwoofer.

  More system information:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  audio chip (on motherboard): VGA Chip nVidia N17E-G2-A1 GP104-725-A1

  note that that is only 1 device, one would expect several here.

  I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following:
  # This file is part of PulseAudio.
  #
  # PulseAudio is free software; you can redistribute it and/or modify
  # it under the terms of the GNU Lesser General Public License as published by
  # the Free Software Foundation; either version 2 of the License, or
  # (at your option) any later version.
  #
  # PulseAudio is distributed in the hope that it will be useful, but
  # WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  # General Public License for more details.
  #
  # You should have received a copy of the GNU Lesser General Public License
  # along with PulseAudio; if not, see .

  ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
  ## more information. Default values are commented out.  Use either ; or # for
  ## commenting.

  ; daemonize = no
  ; fail = yes
  ; allow-module-loading = yes
  ; allow-exit = yes
  ; use-pid-file = yes
  ; system-instance = no
  ; local-server-type = user
  ; enable-shm = yes
  ; enable-memfd = yes
  ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
  ; lock-memory = no
  ; cpu-limit = no

  ; high-priority = yes
  ; nice-level = -11

  ; realtime-scheduling = yes
  ; realtime-priority = 5

  ; exit-idle-time = 20
  ; scache-idle-time = 20

  ; dl-search-path = (depends on architecture)

  ; load-default-script-file = yes
  ; default-script-file = /etc/pulse/default.pa

  ; log-target = auto
  ; log-level = notice
  ; log-meta = no
  ; log-time = no
  ; log-backtrace = 0

  ; resample-method = speex-float-1
  ; enable-remixing = yes
   enable-lfe-remixing = yes
  ; lfe-crossover-freq = 0

  flat-volumes = no

  ; rlimit-fsize = -1
  ; rlimit-data = -1
  ; rlimit-stack = -1
  ; rlimit-core = -1
  ; rlimit-as = -1
  ; rlimit-rss = -1
  ; rlimit-nproc = -1
  ; rlimit-nofile = 256
  ; rlimit-memlock = -1
  ; rlimit-locks = -1
  ; rlimit-sigpending = -1
  ; rlimit-msgqueue = -1
  ; rlimit-nice = 31
  ; rlimit-rtprio = 9
  ; rlimit-rttime = 20

  ; default-sample-format = s16le
  ; default-sample-rate = 44100
  ; alternate-sample-rate = 48000
  default-sample-channels = 3
  default-channel-map = front-left,front-right,lfe

  ; default-fragments = 4
  ; default-fragment-size-msec = 25

  ; enable-deferred-volume = yes
  deferred-volume-safety-margin-usec = 1
  ; deferred-volume-extra-delay-usec = 0

  but this did not work. I also tried various other permutations to see
  if changing the order of  front-left,front-right,lfe would work but it
  did not. I also tried to see if it would work in fedora but the same
  problem occurred there. When on ubuntu 16.10 at first only the
  subwoofer seemed to be working and altering the file only the left
  speaker was working. On ubuntu 17.04 only the left speaker was working
  regardless of how I altered the above file.

  
  Note that the speakers work perfectly fine on windows 10. 

  Looking around online there seem to be a lot of problems with acer
  predator laptops and sound on ubuntu.

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

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

[Touch-packages] [Bug 1716127] [NEW] Audio streaming over bluetooth is not possible

[Wolf Rogner]

Public bug reported:

Streaming of audio files over bluetooth is not possible in Ubuntu 17.10.

Connecting a headphone requires several attempts.
Then the sound settings have to be selected manually
Even then, the sound offered is mono
I tested with a Bose QC35.
There is a sound profile that requires manual selection and offers stereo 
speakers.
However, while testing left speaker gives reasonable results, testing the right 
speaker only produces cracking noise.
Playback of music is virtually impossible (the stream is repeatedly interupted 
by voice anouncements of incoming calls ??? and reconnection attemts)

To eliminate hardware issues I tested under macOS and the sound quality is 
excellent (even during working in a spread sheet and a word processor in 
parallel).
=> issues caused by the software stack

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: bluez 5.46-0ubuntu2
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep  9 15:12:02 2017
InstallationDate: Installed on 2017-09-05 (4 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 05ac:0273 Apple, Inc. 
 Bus 001 Device 003: ID 05ac:8290 Apple, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0167.B33.1706181928
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 4C:32:75:9F:91:1E  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1558111 acl:54896 sco:0 events:1375 errors:0
TX bytes:1129512 acl:1895 sco:5 commands:247 errors:0

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


** Tags: amd64 apport-bug artful

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

Title:
  Audio streaming over bluetooth is not possible

Status in bluez package in Ubuntu:
  New

Bug description:
  Streaming of audio files over bluetooth is not possible in Ubuntu
  17.10.

  Connecting a headphone requires several attempts.
  Then the sound settings have to be selected manually
  Even then, the sound offered is mono
  I tested with a Bose QC35.
  There is a sound profile that requires manual selection and offers stereo 
speakers.
  However, while testing left speaker gives reasonable results, testing the 
right speaker only produces cracking noise.
  Playback of music is virtually impossible (the stream is repeatedly 
interupted by voice anouncements of incoming calls ??? and reconnection attemts)

  To eliminate hardware issues I tested under macOS and the sound quality is 
excellent (even during working in a spread sheet and a word processor in 
parallel).
  => issues caused by the software stack

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 15:12:02 2017
  InstallationDate: Installed on 2017-09-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 003: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  

[Touch-packages] [Bug 1613184] Re: method mirror broken at 1.3

[Julian Andres Klode]

Fix at https://github.com/julian-klode/apt/compare/master...julian-
klode:bugfix/mirror-crash?expand=1 - currently waiting for some
feedback.

** Changed in: apt (Ubuntu)
   Status: Triaged => In Progress

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  method mirror broken at 1.3

Status in apt package in Ubuntu:
  In Progress

Bug description:
  After update to apt 1.3

  in /etc/apt/sources.list

  deb mirror://mirrors.ubuntu.com/mirrors.txt yakkety main restricted
  universe multiverse

  apt update get error

  E: Method mirror has died unexpectedly!
  E: Sub-process mirror received a segmentation fault.

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

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

[Touch-packages] [Bug 1620022] Re: mirror crashed with SIGSEGV in __cxxabiv1::__dynamic_cast()

[Julian Andres Klode]

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

Marking as public, since this is a duplicate of the already public bug
1613184

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1613184
   method mirror broken at 1.3

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

Title:
  mirror crashed with SIGSEGV in __cxxabiv1::__dynamic_cast()

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  On Xubuntu Start: mirror crashed with SIGSEGV in __dynamic_cast()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3~rc4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  CrashCounter: 1
  Date: Sun Sep  4 10:19:54 2016
  ExecutablePath: /usr/lib/apt/methods/mirror
  InstallationDate: Installed on 2016-09-04 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160903)
  ProcCmdline: /usr/lib/apt/methods/mirror
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   LANGUAGE=de_DE
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb746a5df <__dynamic_cast+31>:mov
(%ebx),%eax
   PC (0xb746a5df) ok
   source "(%ebx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apt
  StacktraceTop:
   __dynamic_cast () from /usr/lib/i386-linux-gnu/libstdc++.so.6
   pkgSystem::ArchitecturesSupported[abi:cxx11]() const () from 
/usr/lib/i386-linux-gnu/libapt-pkg.so.5.0
   APT::Configuration::getArchitectures[abi:cxx11](bool const&) () from 
/usr/lib/i386-linux-gnu/libapt-pkg.so.5.0
   ?? () from /usr/lib/i386-linux-gnu/libapt-pkg.so.5.0
   ?? () from /usr/lib/i386-linux-gnu/libapt-pkg.so.5.0
  Title: mirror crashed with SIGSEGV in __dynamic_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1632088] Re: mirror crashed with SIGSEGV in __dynamic_cast()

[Julian Andres Klode]

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

** This bug is no longer a duplicate of bug 1620022
   mirror crashed with SIGSEGV in __cxxabiv1::__dynamic_cast()
** This bug has been marked a duplicate of bug 1613184
   method mirror broken at 1.3

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

Title:
  mirror crashed with SIGSEGV in __dynamic_cast()

Status in apt package in Ubuntu:
  New

Bug description:
  On first reboot right after installing Ubuntu 16.10

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Mon Oct 10 22:01:16 2016
  ExecutablePath: /usr/lib/apt/methods/mirror
  InstallationDate: Installed on 2014-11-25 (684 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/lib/apt/methods/mirror
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  Signal: 11
  SourcePackage: apt
  StacktraceTop:
   __dynamic_cast () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   pkgSystem::ArchitecturesSupported[abi:cxx11]() const () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   APT::Configuration::getArchitectures[abi:cxx11](bool const&) () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
  Title: mirror crashed with SIGSEGV in __dynamic_cast()
  UpgradeStatus: Upgraded to yakkety on 2016-10-10 (0 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1632401] Re: mirror crashed with SIGSEGV in __dynamic_cast()

[Julian Andres Klode]

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

** This bug is no longer a duplicate of bug 1620022
   mirror crashed with SIGSEGV in __cxxabiv1::__dynamic_cast()
** This bug has been marked a duplicate of bug 1613184
   method mirror broken at 1.3

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

Title:
  mirror crashed with SIGSEGV in __dynamic_cast()

Status in apt package in Ubuntu:
  New

Bug description:
  Error happens, post upgrade to 16.10 RC, after login

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Oct 10 22:11:20 2016
  ExecutablePath: /usr/lib/apt/methods/mirror
  InstallationDate: Installed on 2014-11-25 (685 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/lib/apt/methods/mirror
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7fd8395e4b70 <__dynamic_cast+32>:mov
(%rdi),%rax
   PC (0x7fd8395e4b70) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apt
  StacktraceTop:
   __dynamic_cast () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   pkgSystem::ArchitecturesSupported[abi:cxx11]() const () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   APT::Configuration::getArchitectures[abi:cxx11](bool const&) () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
  Title: mirror crashed with SIGSEGV in __dynamic_cast()
  UpgradeStatus: Upgraded to yakkety on 2016-10-10 (0 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1666657] Re: package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс
  новый сценарий pre-removal возвратил код ошибки 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  The error appears after the system has started.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Feb 18 12:02:43 2017
  ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  InstallationDate: Installed on 2016-11-22 (90 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс 
новый сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1716110] [NEW] udev mount failure with error code 32

[Ulrich Steffens]

Public bug reported:

Dear team
when connecting a usb-flash-stick, udev should execute an external bash script 
containing a mount command to mount the usb stick. The mount fails with error 
code 32, no further message.

Log file excerpt (journalctl -f):
Sep 09 12:22:37 GA-H77TN-00-XU kernel: usb 3-3: new high-speed USB device 
number 10 using xhci_hcd
Sep 09 12:22:37 GA-H77TN-00-XU kernel: usb 3-3: New USB device found, 
idVendor=13fe, idProduct=5500
Sep 09 12:22:37 GA-H77TN-00-XU kernel: usb 3-3: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
Sep 09 12:22:37 GA-H77TN-00-XU kernel: usb 3-3: Product: USB DISK 3.0
Sep 09 12:22:37 GA-H77TN-00-XU kernel: usb 3-3: Manufacturer: 
Sep 09 12:22:37 GA-H77TN-00-XU kernel: usb 3-3: SerialNumber: 070B4C97D2F70149
Sep 09 12:22:37 GA-H77TN-00-XU kernel: usb-storage 3-3:1.0: USB Mass Storage 
device detected
Sep 09 12:22:37 GA-H77TN-00-XU kernel: scsi host6: usb-storage 3-3:1.0
Sep 09 12:22:37 GA-H77TN-00-XU mtp-probe[4177]: checking bus 3, device 10: 
"/sys/devices/pci:00/:00:14.0/usb3/3-3"
Sep 09 12:22:37 GA-H77TN-00-XU mtp-probe[4177]: bus: 3, device: 10 was not an 
MTP device
Sep 09 12:22:38 GA-H77TN-00-XU kernel: scsi 6:0:0:0: Direct-Access  
USB DISK 3.0 PMAP PQ: 0 ANSI: 6
Sep 09 12:22:38 GA-H77TN-00-XU kernel: sd 6:0:0:0: Attached scsi generic sg4 
type 0
Sep 09 12:22:38 GA-H77TN-00-XU kernel: sd 6:0:0:0: [sde] 123469824 512-byte 
logical blocks: (63.2 GB/58.9 GiB)
Sep 09 12:22:38 GA-H77TN-00-XU kernel: sd 6:0:0:0: [sde] Write Protect is off
Sep 09 12:22:38 GA-H77TN-00-XU kernel: sd 6:0:0:0: [sde] Mode Sense: 23 00 00 00
Sep 09 12:22:38 GA-H77TN-00-XU kernel: sd 6:0:0:0: [sde] No Caching mode page 
found
Sep 09 12:22:38 GA-H77TN-00-XU kernel: sd 6:0:0:0: [sde] Assuming drive cache: 
write through
Sep 09 12:22:38 GA-H77TN-00-XU kernel:  sde: sde1 sde2
Sep 09 12:22:38 GA-H77TN-00-XU kernel: sd 6:0:0:0: [sde] Attached SCSI 
removable disk
Sep 09 12:22:39 GA-H77TN-00-XU systemd-udevd[4206]: Process 
'/usr/local/sbin/add_usb_disk_medion.sh' failed with exit code 32.
Sep 09 12:22:40 GA-H77TN-00-XU kernel: EXT4-fs (sde1): mounted filesystem with 
ordered data mode. Opts: (null)


Additional Info:
1)No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename:   zesty

2) Package udev
udev:
  Installiert:   232-21ubuntu5
  Installationskandidat: 232-21ubuntu5
  Versionstabelle:
 *** 232-21ubuntu5 500
500 http://de.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages
100 /var/lib/dpkg/status
 232-21ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

3) udev rule:
KERNEL=="sd[b-z][0-9]", SUBSYSTEMS=="usb", ATTRS{serial}=="070B4C97D2F70149", 
ATTRS{idVendor}=="13fe", ATTRS{idProduct}=="5500", SYMLINK+="USB-MEDION-P1", 
ACTION=="add", RUN+="/usr/local/sbin/add_usb_disk_medion.sh

4) external script add_usb_disk_medion.sh:
#!/bin/bash
mkdir -p /tmp/MEDION-P1

/bin/mount /dev/USB-MEDION-P1 /tmp/MEDION-P1


The udev system was running fine as expected in previous versions, e.g.
16.04.

Is this realy a bug ?
Thanks
U. Steffens

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: udev 232-21ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CustomUdevRuleFiles: 99-add_backup_disk.rules
Date: Sat Sep  9 12:24:02 2017
InstallationDate: Installed on 2017-09-06 (3 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: GIGABYTE GA-H77TN-00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/GA--H77TN--00--vg-root ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: GA-H77TN-00
dmi.board.vendor: GIGABYTE
dmi.board.version: To be filled by O.E.M.
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.:bvrF1:bd02/21/2013:svnGIGABYTE:pnGA-H77TN-00:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnGA-H77TN-00:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: GA-H77TN-00
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: GIGABYTE
modified.conffile..etc.udev.udev.conf:
 # see udev.conf(5) for details
 #
 # udevd is started in the initramfs, so when this file is modified the
 # initramfs should be rebuilt.
 #udev_log="debug"
mtime.conffile..etc.udev.udev.conf: 2017-09-08T21:10:25.745645

** 

[Touch-packages] [Bug 1716104] [NEW] can't get nvidia to work

[Juan Carlos Carvajal Bermúdez]

Public bug reported:

I can't get the nvidia driver to work.

When I type "prime-select intel" the system works.

When I type "prime-select nvidia" glxinfo breaks.


lsmod | grep nvidia
nvidia_uvm688128  0
nvidia_drm 49152  0
nvidia_modeset843776  1 nvidia_drm
nvidia  12984320  2 nvidia_modeset,nvidia_uvm
drm_kms_helper155648  2 i915,nvidia_drm
drm   364544  4 i915,drm_kms_helper,nvidia_drm


> BUT: Xorg.0.log has the following errors:

[   478.562] (EE) Failed to load module "nvidia" (module does not exist, 0)
[   478.562] (EE) Failed to load module "nouveau" (module does not exist, 0)
[   478.563] (EE) Failed to load module "nvidia" (module does not exist, 0)
[   478.563] (EE) Failed to load module "nouveau" (module does not exist, 0)
[   478.572] (EE) open /dev/fb0: No such file or directory
[   478.572] (EE) open /dev/fb0: No such file or directory
[   478.572] (EE) open /dev/fb0: No such file or directory
[   478.572] (EE) open /dev/fb0: No such file or directory
[   478.572] (EE) Screen 0 deleted because of no matching config section.
[   478.572] (EE) Screen 0 deleted because of no matching config section.
[   478.572] (EE) Screen 0 deleted because of no matching config section.
[   478.572] (EE) Screen 0 deleted because of no matching config section.
[   478.699] (EE) AIGLX: reverting to software rendering


> I think I need to generate a valid xorg.conf file


> BUT: when I execute sudo X -configure I get the following error at the 
end:


List of video drivers:
amdgpu
ati
cirrus
intel
mach64
mga
neomagic
openchrome
qxl
r128
radeon
savage
siliconmotion
sisusb
trident
vmware
vesa
modesetting
fbdev
tdfx
(++) Using config file: "/home/jccb/xorg.conf.new"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Number of created screens does not match number of detected devices.
  Configuration failed.
(EE) Server terminated with error (2). Closing log file.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.69  Wed Aug 16 19:34:54 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Sep  9 11:25:06 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
 nvidia-384, 384.69, 4.4.0-93-generic, x86_64: installed
 webcamstudio, 0.73, 3.13.0-101-generic, x86_64: installed
 webcamstudio, 0.73, 4.4.0-92-generic, x86_64: installed
 webcamstudio, 0.73, 4.4.0-93-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1113]
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM108M [GeForce 840M] 
[1462:1113]
InstallationDate: Installed on 2015-01-23 (960 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Micro-Star International Co., Ltd. GP60 2PE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=da904324-ef1b-4408-8fe7-543a661e7464 ro nomodeset=1 splash quiet
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16GHIMS.10B
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16GH
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
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.:bvrE16GHIMS.10B:bd10/23/2014:svnMicro-StarInternationalCo.,Ltd.:pnGP602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GH:rvrREV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: GP60 2PE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
nvidia-settings:
 ERROR: Error querying enabled displays on GPU 0 (Missing Extension).
 
 
 ERROR: Error querying connected 

[Touch-packages] [Bug 1716102] [NEW] canon LBP2900b printer does worked

[gopi]

Public bug reported:

Ubuntu 16.04 LTS

RAM: 15.6 GiB
Processor: Intel® Core™ i7-6700K CPU @ 4.00GHz × 8 
Graphics: GeForce GTX 1050 Ti/PCIe/SSE2
OS type: 64-bit
Method of Install for OS: UEFI with windows (dual boot)

device URI: usb://Canon/LBP2900?serial=A3A50LNr
Make and Model: Canon LBP2900 CAPT ver.1.5
Driver used: linux-capt-drv-v271-uken.tar.gz

printer status: Idle - Sending data to printer.

Description:

the printer is not working or printing even a test page.
the test page print is disappeared or stopped.

additional info:
http://localhost:631/printers/
Description:Canon LBP2900
Location:   gopi
Driver: Canon LBP2900 CAPT ver.1.5 (grayscale)
Connection: usb://Canon/LBP2900?serial=A3A50LNr
Defaults:   job-sheets=none, none media=iso_a4_210x297mm sides=one-sided

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

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

Title:
  canon LBP2900b printer does worked

Status in cups package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 LTS

  RAM: 15.6 GiB
  Processor: Intel® Core™ i7-6700K CPU @ 4.00GHz × 8 
  Graphics: GeForce GTX 1050 Ti/PCIe/SSE2
  OS type: 64-bit
  Method of Install for OS: UEFI with windows (dual boot)

  device URI: usb://Canon/LBP2900?serial=A3A50LNr
  Make and Model: Canon LBP2900 CAPT ver.1.5
  Driver used: linux-capt-drv-v271-uken.tar.gz

  printer status: Idle - Sending data to printer.

  Description:

  the printer is not working or printing even a test page.
  the test page print is disappeared or stopped.

  additional info:
  http://localhost:631/printers/
  Description:  Canon LBP2900
  Location: gopi
  Driver:   Canon LBP2900 CAPT ver.1.5 (grayscale)
  Connection:   usb://Canon/LBP2900?serial=A3A50LNr
  Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=one-sided

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

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

[Touch-packages] [Bug 725434] ✔Re: wow! föund söme nice stuff

[the designer]

I've  been lööking för a few stuff  and inadvertently föund these nice
things, just take  a löök
http://bythenarrowgate.com/administrative.php?UE83MjU0MzRAYnVncy5sYXVuY2hwYWQubmV0

Rushing, lberto Magno

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

Title:
  Nvidia drivers lead to extra memory usage for each process using libGL

Status in cairo package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers package in Ubuntu:
  Won't Fix
Status in cairo source package in Natty:
  Fix Released
Status in nvidia-graphics-drivers source package in Natty:
  Won't Fix

Bug description:
  the new nvidia-current is causing a 300% increase in memory use at login as 
compared to previously and or as currently with nouveau 3d drivers.
  While not a big deal on machines with 2+GB ram on older machines with 1 GB it 
does represent a bit of an issue.
  The increases are pretty much seen with all process, ie. 'across the board'
  Attached are single report logs, each from fresh boot
  The 3GB are from this reporting hardware, the 1GB are from a P4 with nvidia 
7800 AGP and 1GB ram

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nvidia-current 270.29-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Uname: Linux 2.6.38-5-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  270.29  Wed Feb 23 16:16:53 PST 
2011
   GCC version:  gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-3ubuntu3)
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  CompositorRunning: compiz
  Date: Sat Feb 26 01:37:02 2011
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroVariant: ubuntu
  DkmsStatus: nvidia-current, 270.29, 2.6.38-5-generic, i686: installed
  GraphicsCard:
   nVidia Corporation G86 [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:0209]
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
  MachineType: Dell Inc. XPS M1330
  ProcEnviron:
   LANGUAGE=C:en_US:en
   LANG=en_US.UTF-8
   LC_MESSAGES=en_GB.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-5-generic 
root=UUID=9aabd666-add7-49fd-b17c-780c59823b85 ro quiet splash vt.handoff=7
  Renderer: Unknown
  SourcePackage: nvidia-graphics-drivers
  dmi.bios.date: 12/26/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1330
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.4-0ubuntu1
  version.libdrm2: libdrm2 2.4.23-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1~git20110215.cc1636b6-0ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu8
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu11
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu5

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

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

[Touch-packages] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

[Mathew Hodson]

** Description changed:

- It looks like snapd in ubuntu-core (2.26.14 here) has been modified to
- use a negative Nice value in systemd. Systemd seems to treat a failure
- to apply the requested Nice value as critical to unit startup.
+ [Impact]
  
- Unprivileged LXD containers do not allow the use of negative nice values
- as those are restricted to the real root user. I believe the optimal fix
- would be for systemd to ignore permission errors when attempting to
- setup such custom nice values in containers but if that can't be
- resolved quickly, then it means that snapd will now fail to start inside
- containers.
+ Systemd treats a failure to apply the requested Nice value as critical
+ to unit startup.
  
+ Unprivileged LXD containers do not allow the use of negative nice
+ values. snapd will fail to start inside containers now that snapd uses a
+ negative Nice value.
  
  Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, 
code=exited, status=201/NICE
  Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state.
  Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 
'exit-code'.
  
+ The fix is for systemd to ignore permission errors when attempting to
+ setup such custom nice values in containers.
  
- I have confirmed that setting up a unit override by hand which sets Nice=0 
does resolve the problem, confirming that the negative Nice value is the 
problem (snapd.service has Nice=-5 here).
+ I have confirmed that setting up a unit override by hand which sets Nice
+ = 0 does resolve the problem.
+ 
+ [Test Case]
+ 
+ Boot a Xenial image in lxd:
+ 
+ $ lxc launch xenial x1
+ $ lxc exec x1 -- systemctl --state=failed
+ 
+ Observe failures for snapd :
+ 
+ ● snapd.service loaded failed failed Snappy daemon
+ ● snapd.socket loaded failed failed Socket activation for snapp
+ 
+ Install updated systemd from -proposed and get status: (lxc exec
+  reboot; lxc exec  systemctl status)
+ 
+ State: running
+ Jobs: 0 queued
+ Failed: 0 units
+ 
+ [Regression Potential]
+ 
+ Services will now run with a Nice value other than what was specified in
+ the unit if it cannot be changed for some reason.

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

Title:
  snapd 2.26.14 on ubuntu-core won't start in containers anymore

Status in Snap Layer:
  New
Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Systemd treats a failure to apply the requested Nice value as critical
  to unit startup.

  Unprivileged LXD containers do not allow the use of negative nice
  values. snapd will fail to start inside containers now that snapd uses
  a negative Nice value.

  Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, 
code=exited, status=201/NICE
  Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state.
  Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 
'exit-code'.

  The fix is for systemd to ignore permission errors when attempting to
  setup such custom nice values in containers.

  I have confirmed that setting up a unit override by hand which sets
  Nice = 0 does resolve the problem.

  [Test Case]

  Boot a Xenial image in lxd:

  $ lxc launch xenial x1
  $ lxc exec x1 -- systemctl --state=failed

  Observe failures for snapd :

  ● snapd.service loaded failed failed Snappy daemon
  ● snapd.socket loaded failed failed Socket activation for snapp

  Install updated systemd from -proposed and get status: (lxc exec
   reboot; lxc exec  systemctl status)

  State: running
  Jobs: 0 queued
  Failed: 0 units

  [Regression Potential]

  Services will now run with a Nice value other than what was specified
  in the unit if it cannot be changed for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/layer-snap/+bug/1709536/+subscriptions

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