[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Marcos Jacoby]

1007/5000
Truth?
I mean that a library like libcurl4 that is not available separately as it does 
with libcurl3 and that is threaded down the user forcing the removal of lbcurl3 
and all related applications being that you are the developers and not your 
problem?
Are you Microsoft employees by any chance?
Because it's looking alike.
The same arrogant attitude of fucking the customer that I do what I want and 
he'll have to swallow me.
The problem is in curl that forces this break and jeopardizes the whole system.
I even understand using a new library with new functions, leaner and so on, but 
do you need to screw with the whole system or with other applications?
I'm going to have a chat with the Debian people to do the same thing and make 
Ubuntu impractical and give the same excuse.
Then we will see if you are developers or are like Bill Gates, thief of ideas 
of others, putting their own name and blaming the mistakes on others.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Invalid

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

[Touch-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

[Christian Niemeyer]

I suspect libglx0 (transition from libgl1-mesa-glx to libglx0)

Because now we have:
/usr/lib/x86_64-linux-gnu/libGLX.so.0.0.0 (from libglx0 in bionic, new with 
bionic)

instead of:
/usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2.0 (from libgl1-mesa-glx in artful, 
the packages is a transitional dummy package in bionic)


The Xorg.0.log backtrace is showing:

[   210.258] (EE) Backtrace:
[   210.258] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5645df72591d]
[   210.258] (EE) 1: /usr/lib/xorg/Xorg (0x5645df56d000+0x1bc6b9) 
[0x5645df7296b9]
[   210.258] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f00a84af000+0x12890) [0x7f00a84c1890]
[   210.258] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xc7) 
[0x7f00a80fce97]
[   210.258] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x141) 
[0x7f00a80fe801]
[   210.258] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7f00a80be000+0x3039a) 
[0x7f00a80ee39a]
[   210.258] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f00a80be000+0x30412) 
[0x7f00a80ee412]
[   210.258] (EE) 7: /usr/lib/xorg/Xorg (0x5645df56d000+0x3ec17) 
[0x5645df5abc17]
[   210.258] (EE) 8: /usr/lib/xorg/Xorg (0x5645df56d000+0xe26df) 
[0x5645df64f6df]
[   210.258] (EE) 9: /usr/lib/xorg/modules/extensions/libglx.so 
(0x7f00a6473000+0x288d7) [0x7f00a649b8d7]
[   210.258] (EE) 10: /usr/lib/xorg/modules/extensions/libglx.so 
(0x7f00a6473000+0x2f851) [0x7f00a64a2851]
[   210.258] (EE) 11: /usr/lib/xorg/modules/extensions/libglx.so 
(0x7f00a6473000+0x27315) [0x7f00a649a315]
[   210.259] (EE) 12: /usr/lib/xorg/Xorg (InitExtensions+0x3d) [0x5645df63308d]
[   210.259] (EE) 13: /usr/lib/xorg/Xorg (0x5645df56d000+0x56d1f) 
[0x5645df5c3d1f]
[   210.259] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) 
[0x7f00a80dfb97]
[   210.259] (EE) 15: /usr/lib/xorg/Xorg (_start+0x2a) [0x5645df5adbba]
[   210.259] (EE) 
[   210.259] (EE) 
Fatal server error:


However that libglx.so shown in the error log is part of xserver-xorg-
core.


But I suspect it has to do with the changed to vendor neutral libglx
(libglx0, libglvnd0, etc.) That would explain why it is happening with
Bionic and no other versions before for me.


Can someone reproduce this? In your Display Manager switch to a VT (or 
deinstall display manager temporarily) and modify/create a /etc/X11/xorg.conf 
file with

Section "Extensions"
Option "Composite" "Disable"
EndSection


And sudo service lightdm/gdm3 stop and then try to start the Xserver/Xsession 
with startx or xinit.



As this is the first version of Ubuntu which seems to have this problem for

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

Title:
  [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

Status in xorg package in Ubuntu:
  New

Bug description:
  [New bug filed with ubuntu-bug/apport. However there was nothing to
  file against in /var/crashes]

  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco. Disabling the Composite extension prevents
  tearing in (some) games and sometimes is an additional performance
  boost.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [ 35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [ 35.781] X Protocol Version 11, Revision 0
  [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [ 35.787] Build Date: 22 February 2018 08:04:42PM
  [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [ 35.789] Current version of pixman: 0.34.0
  [ 35.792] Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from 

[Touch-packages] [Bug 209447] Re: gnome-keyring-daemon does not honor constrained ssh identities

[Bug Watch Updater]

** Changed in: gnome-keyring
   Status: Confirmed => Fix Released

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

Title:
  gnome-keyring-daemon does not honor constrained ssh identities

Status in GNOME Keyring:
  Fix Released
Status in portable OpenSSH:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  In Progress
Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-keyring

  The ssh-agent honors adding constrained identities -- where such constraints 
may be either:
* Require confirmation each time the agent allows the identity to be used.
* A maximum lifetime for the identity.

  The gnome-keyring-daemon is a replacement for the ssh-agent in Hardy
  Heron, but does not support those constraints.  If the user issues:

ssh-add -c

  or

ssh-add -t 

  The identities will be added without those constraints.

  This is especially important in some uses of the ssh-agent, such as
  ssh-agent forwarding, where the usage of the agent can not be
  considered secure without the confirmation constraint.

  If the gnome-keyring-daemon is intended to replace the ssh-agent in
  Ubuntu, it should support these important security features -- they
  were added with good reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/209447/+subscriptions

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

[Touch-packages] [Bug 1688034] Re: 1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

[Launchpad Bug Tracker]

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

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

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

Title:
  1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04, enrolled with freeipa-client to FreeIPA 4.4.0 (under
  CentOS 7)

  With sudo 1.8.16-0ubuntu1, everything is fine:

  brian.candler@api-dev:~$ sudo -s
  [sudo] password for brian.candler:
  root@api-dev:~#

  After update to 1.8.16-0ubuntu1.3, it no longer works:

  brian.candler@api-dev:~$ sudo -k
  brian.candler@api-dev:~$ sudo -s
  [sudo] password for brian.candler:
  brian.candler is not allowed to run sudo on api-dev.int.example.com.  This 
incident will be reported.

  This is repeatable: downgrade sudo and it works again.

  Seems very likely related to change made as part of #1607666, which
  changes how sudo policies are matched, but has unexpected regression.

  --- Additional info ---

  The sudo policy in IPA is extremely simple. It has a single rule,
  which says:

  - applies to users in groups "system_administrators" and 
"security_administrators"
  - applies to any host
  - applies to any command

  In LDAP under ou=sudoers tree, the groups are flattened out:

  # system administrators on all hosts, sudoers, ipa.example.com
  dn: cn=system administrators on all hosts,ou=sudoers,dc=ipa,dc=example,dc=com
  sudoRunAsGroup: ALL
  objectClass: sudoRole
  objectClass: top
  sudoUser: brian.candler
  sudoUser: ...
  sudoUser: ... list more users
  sudoUser: ...
  sudoRunAsUser: ALL
  sudoCommand: ALL
  sudoHost: ALL
  cn: system administrators on all hosts

  Under cn=sudorules,cn=sudo it refers to the groups rather than the
  individuals:

  # 59ffb10a-9c61-11e6-b5b8-00163efd5284, sudorules, sudo, ipa.example.com
  dn: 
ipaUniqueID=59ffb10a-9c61-11e6-b5b8-00163efd5284,cn=sudorules,cn=sudo,dc=ipa,dc=example,dc=com
  ipaSudoRunAsUserCategory: all
  ipaSudoRunAsGroupCategory: all
  description: admins have full sudo access on any host they can ssh into
  cmdCategory: all
  hostCategory: all
  memberUser: 
cn=system_administrators,cn=groups,cn=accounts,dc=ipa,dc=example,dc=com
  memberUser: 
cn=security_administrators,cn=groups,cn=accounts,dc=ipa,dc=example,dc=com
  objectClass: ipasudorule
  objectClass: ipaassociation
  ipaEnabledFlag: TRUE
  cn: system administrators on all hosts
  ipaUniqueID: 59ffb10a-9c61-11e6-b5b8-00163efd5284

  I have no workaround other than downgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.4.0-1016.25-aws 4.4.59
  Uname: Linux 4.4.0-1016-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed May  3 16:01:23 2017
  Ec2AMI: ami-a8d2d7ce
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/90-cloud-init-users: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1656979] Re: No support for DHE ciphers (TLS)

[Launchpad Bug Tracker]

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

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

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

Title:
  No support for DHE ciphers (TLS)

Status in openldap package in Ubuntu:
  Expired

Bug description:
  Hi,

  Seems the OpenLDAP shipped with Xenial (and prior) built against
  GnuTLS does not support DHE cipher suites.

  | hloeung@ldap-server:~$ apt-cache policy slapd
  | slapd:
  |   Installed: 2.4.42+dfsg-2ubuntu3.1
  |   Candidate: 2.4.42+dfsg-2ubuntu3.1
  |   Version table:
  |  *** 2.4.42+dfsg-2ubuntu3.1 500
  | 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  2.4.42+dfsg-2ubuntu3 500
  | 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Our LDAP server is configured with the following:

  | TLSCertificateFile /etc/ssl/certs/ldap-server.crt
  | TLSCertificateKeyFile /etc/ssl/private/ldap-server.key
  | TLSCACertificateFile /etc/ssl/certs/ldap-server_chain.crt
  | TLSProtocolMin 1.0
  | TLSCipherSuite 
PFS:-VERS-SSL3.0:-DHE-DSS:-ARCFOUR-128:-3DES-CBC:-CAMELLIA-128-GCM:-CAMELLIA-256-GCM:-CAMELLIA-128-CBC:-CAMELLIA-256-CBC:%SERVER_PRECEDENCE
  | TLSDHParamFile /etc/ssl/private/dhparams.pem

  I know TLSDHParamFile isn't used by OpenLDAP when built with GnuTLS,
  but thought I'd try anyways. cipherscan[1] shows the following list of
  cipher suites:

  | prio  ciphersuite  protocols  pfs   
  curves
  | 1 ECDHE-RSA-AES128-GCM-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 2 ECDHE-RSA-AES256-GCM-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 3 ECDHE-RSA-AES128-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 4 ECDHE-RSA-AES128-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 5 ECDHE-RSA-AES256-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 6 ECDHE-RSA-AES256-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1

  Even with TLSCipherSuite config commented out, we see the following
  cipher suites:

  | prio  ciphersuite  protocols  pfs   
  curves
  | 1 ECDHE-RSA-AES256-GCM-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 2 ECDHE-RSA-AES256-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 3 ECDHE-RSA-AES256-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 4 AES256-GCM-SHA384TLSv1.2None  
  None
  | 5 AES256-SHA256TLSv1.2None  
  None
  | 6 AES256-SHA   TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 7 CAMELLIA256-SHA  TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 8 ECDHE-RSA-AES128-GCM-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 9 ECDHE-RSA-AES128-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 10ECDHE-RSA-AES128-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 11AES128-GCM-SHA256TLSv1.2None  
  None
  | 12AES128-SHA256TLSv1.2None  
  None
  | 13AES128-SHA   TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 14CAMELLIA128-SHA  TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 15ECDHE-RSA-DES-CBC3-SHA   TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 16DES-CBC3-SHA TLSv1,TLSv1.1,TLSv1.2  None  
  None

  I think the fix is in the patch below that's released in 2.4.39:

  
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h=622d13a32ec8d623c26a11b60b63e443dc86df99

  
  Thanks,

  Haw

  
  [1]https://github.com/jvehent/cipherscan

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

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

[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers

[Launchpad Bug Tracker]

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

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

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

Title:
  Regression, poor user experience, print dialogs garbled by
  unidentifiable driverless printers

Status in cups package in Ubuntu:
  Expired

Bug description:
  Recently, my print dialogs have started to include network discoverd
  printers in addition to those configured in cups even if the cups-
  browsed service is disabled and the BrowseRemoteProtocols option is
  set to none.

  There does not seem to be any way to disable this behavior apart from
  disabling avahi or its ability to talk to dbus, which causes side
  effects on the system.

  Yet, in some environments this behavior is a definite regression over
  the old one and leads to an extremely poor user experience.

  On some networks:

  - The print dialogs takes 3-10 sec to open which is a huge amount of
  time for an action that is expected to be instantaneous and for which
  there is no visual feedback.

  - The print dialog contains many tens of printer entries, all
  identified by weird hex strings that cannot be related to any useful
  location, that do not help identifying which entry corresponds to
  which printer and that only mess up the list making it hard to find
  the printers that are actually useful.

  For instance, suppose that you work at some office that has recently
  purchased a batch of new printers all the same model. In the print
  dialog you may get many entries like:

  HP_Laserjet_Pro_Mxxxdw_21ACF2

  which only vary in the final hex string. How is one suppose to know
  what is where?

  Please make it possible to disable this driverless printer madness.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libcups2 2.2.4-7ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP 
client-error-bad-request for Create-Printer-Subscriptions (/) from localhost
  CurrentDesktop: KDE
  Date: Fri Dec 15 16:22:07 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1463 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Notebook W740SU
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1752844] Re: Line drawing bug in applications using opengl 1

[Robert Rojas]

** Description changed:

  On Ubuntu 16.04.3, as from the update fixing
- https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594, the line
- rendering in applications using Opengl 1 is incorrect.
+ https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594, antialiased
+ line rendering in applications using Opengl is corrupt. Experienced
+ using Intel GM45.
+ 
+ Steps to reproduce:
+ 1) Create an OpenGL application.
+ 2) Enable GL_LINE_SMOOTH and set line width to any value below 1.5.
+ 3) Draw a line (either by shaders or by glBegin).
  
  Blender and various games by Kenta Cho (tumiki-figthers, torus-trooper,
  parsec47, titanion) are affected.

** Summary changed:

- Line drawing bug in applications using opengl 1
+ Graphical artifacts with antialiased lines in OpenGL

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

Title:
  Graphical artifacts with antialiased lines in OpenGL

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04.3, as from the update fixing
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594,
  antialiased line rendering in applications using Opengl is corrupt.
  Experienced using Intel GM45.

  Steps to reproduce:
  1) Create an OpenGL application.
  2) Enable GL_LINE_SMOOTH and set line width to any value below 1.5.
  3) Draw a line (either by shaders or by glBegin).

  Blender and various games by Kenta Cho (tumiki-figthers, torus-
  trooper, parsec47, titanion) are affected.

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

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

[Touch-packages] [Bug 1753724] Re: nano fails to redo a file insertion

[Launchpad Bug Tracker]

This bug was fixed in the package nano - 2.9.3-2

---
nano (2.9.3-2) unstable; urgency=medium

  * The "#8M" release.
  * Add patch from git master to fix a condition where redo would fail.
Thanks Benno for the heads-up (LP: #1753724).

 -- Jordi Mallach   Tue, 06 Mar 2018 15:46:39 +0100

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

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

Title:
  nano fails to redo a file insertion

Status in nano package in Ubuntu:
  Fix Released

Bug description:
  In Bionic Beaver (and in any nano between 2.8.0 and 2.9.3), trying to
  redo a file insertion can fail with the message: "[ Gone undo line --
  please report a bug ]".

  To reproduce, run 'nano --ignore' and type:  Ctrl+R  /etc/issue
Alt+U  Alt+E

  Attached upstream patch fixes the issue.

  References:
https://savannah.gnu.org/bugs/?53272
http://git.savannah.gnu.org/cgit/nano.git/commit/?id=e9eabdcd
http://lists.gnu.org/archive/html/nano-devel/2018-03/msg00015.html

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

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

[Touch-packages] [Bug 1067386] Re: dm thin facility incomplete - thin-provisioning-tools not packaged

[Karl-Philipp Richter]

5 years later an this is still and issue on 17.10. It's possible to
create complex LVMs setups, e.g. the one described at https://www
.thomas-krenn.com/de/wiki/LVM_Caching_mit_SSDs_einrichten, but then at
the first mount the missing `/usr/sbin/check_cache` binary causes the
mount to fail until `thin-provisioning-tools` is installed.

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

Title:
  dm thin facility incomplete - thin-provisioning-tools not packaged

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  The lvm2 package is built with --with-thin=internal option activated,
  but the supporting userspace activation tools are neither packaged nor
  depended upon correctly.

  The errors reported in Debian at http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=673000#17 also occur on Ubuntu Quantal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: lvm2 2.02.95-4ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 16 14:57:35 2012
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1754686] Re: libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like slack-desktop

[Launchpad Bug Tracker]

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

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

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

Title:
  libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like
  slack-desktop

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Updating the curl package pulls in libcurl4, which for some reason
  forces libcurl3 to be removed. This prevents 3rd party apps that still
  build against libcurl3 from being installed. Isn't there a more
  graceful way to effect the transition from libcurl3 to libcurl4?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcurl4 7.58.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:10:10 2018
  EcryptfsInUse: Yes
  SourcePackage: curl
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)

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

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

[Touch-packages] [Bug 1599401] Re: crash in XTranslateCoordinates from gdk_x11_display_translate_event

[Vlad Orlov]

** Summary changed:

- mate-settings-daemon crashed with signal 5 in _XReply()
+ crash in XTranslateCoordinates from gdk_x11_display_translate_event

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

Title:
  crash in XTranslateCoordinates from gdk_x11_display_translate_event

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  polihron@polihron-K56CA:~$ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: mate-settings-daemon 1.14.0-1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Jul  6 10:50:49 2016
  ExecutablePath: /usr/bin/mate-settings-daemon
  InstallationDate: Installed on 2016-07-01 (4 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160629.1)
  ProcCmdline: /usr/bin/mate-settings-daemon
  Signal: 5
  SourcePackage: mate-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: mate-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

[Daniel Del Pino]

¿Is there a way to resolve this problem in Ubuntu 16.04.4 LTS? Path is
not available for this version.

I had created softlink toward /run/user/1001/gvfs/gvfs... but
Libreoffice fail when open files through that path (i/o error).

I have over 70 users in my company with this problem...

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Trusty:
  Triaged
Status in gtk+3.0 source package in Xenial:
  Triaged
Status in gtk+3.0 source package in Artful:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Touch-packages] [Bug 1594609] Re: /usr/bin/mate-panel:6:g_assertion_message:g_assertion_message_expr:get_icon_fallback:gtk_recent_chooser_menu_create_item:idle_populate_func

[Vlad Orlov]

** Package changed: mate-panel (Ubuntu) => gtk+2.0 (Ubuntu)

** Summary changed:

- 
/usr/bin/mate-panel:6:g_assertion_message:g_assertion_message_expr:get_icon_fallback:gtk_recent_chooser_menu_create_item:idle_populate_func
+ crash due to assertion in get_icon_fallback from 
gtk_recent_chooser_menu_create_item

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

Title:
  crash due to assertion in get_icon_fallback from
  gtk_recent_chooser_menu_create_item

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-panel.  This problem was most recently seen with
  version 1.12.2-1, the problem page at
  https://errors.ubuntu.com/problem/96ae198a578de2353a3cc778896a83a10ab7d131
  contains more details.

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

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

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Brian Murray]

None of the packages which you are having an issue with are ones from
the official Ubuntu archive, subsequently there is nothing we (the
developers of Ubuntu) can do about this. You'll need to take up the
issue with the people who develop these packages.

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

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Invalid

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

[Touch-packages] [Bug 1594609] [NEW] /usr/bin/mate-panel:6:g_assertion_message:g_assertion_message_expr:get_icon_fallback:gtk_recent_chooser_menu_create_item:idle_populate_func

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding mate-panel.  This problem was most recently seen with version
1.12.2-1, the problem page at
https://errors.ubuntu.com/problem/96ae198a578de2353a3cc778896a83a10ab7d131
contains more details.

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


** Tags: vivid wily xenial yakkety
-- 
/usr/bin/mate-panel:6:g_assertion_message:g_assertion_message_expr:get_icon_fallback:gtk_recent_chooser_menu_create_item:idle_populate_func
https://bugs.launchpad.net/bugs/1594609
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+2.0 in Ubuntu.

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

[Touch-packages] [Bug 1754759] [NEW] LAN connection keeps connecting and disconnecting in an infinite loop

[Markus Baumann]

Public bug reported:

With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
- Boot from live-ISO
- Click on network icon in title bar and edit LAN-connection
- Change MTU from Auto to 1492
- Connect LAN cable
=> LAN network keeps connecting and disconnecting in an infinite loop

(No wireless network is configured.)

The error did not occur on Xubuntu 16.04. The same situation occurs with
Xubuntu installed on the SSD. I took the ISO for this bug report, in
order to exclude wrong settings on the installed system.

This is my first bug report - I hope I did not do too much wrong. If
necessary, I can provide more information.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CasperVersion: 1.387
CurrentDesktop: XFCE
Date: Fri Mar  9 20:26:21 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 10.110.120.1 dev enp0s25 proto static metric 100 
 10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
 169.254.0.0/16 dev enp0s25 scope link metric 1000
LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
 Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
nmcli-dev:
 DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
 enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
 wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  -- 
 ----   
   
 lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug artful xubuntu-exp

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

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   

[Touch-packages] [Bug 1753884] Re: session logout after suspend

[Christopher M. Penalver]

Simon, given the gnome-shell crash files generated immediately after,
I'll move this over there for specialists to review.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

Title:
   session logout after suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Only when I have a second monitor plugged in, if I close the lid of my
  laptop, my session gets logged out. What I'm expecting is the lock
  screen comes up.

  Sometimes (but not always) the second monitor will flash the "logged
  out" screen for a second or two before going dim.

  I have "Suspend even if external monitor is plugged in" enabled in
  Tweak Tools.

  WORKAROUND: Suspend via the GUI with the lid open.

  WORKAROUND: Unplug the second monitor before closing the lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Mar  6 18:07:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-02-15 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20AQ009HUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=6f20d80f-81f4-40c1-aafd-95b2c5de55ed ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET78WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ009HUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ009HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ009HUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ009HUS
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-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/gnome-shell/+bug/1753884/+subscriptions

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

[Touch-packages] [Bug 1753136] Re: Gettext package inconsistency

[Gunnar Hjalmarsson]

The translations showed up again after having upgraded to 3.28.0-1.

** Changed in: ubuntu-translations
   Status: New => Fix Released

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

Title:
  Gettext package inconsistency

Status in libgweather:
  Fix Released
Status in Ubuntu Translations:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released

Bug description:
  New translation issue after the switch to meson. It's probably an
  upstream thing, and I have filed an upstream bug report with a patch
  and explained it there.

  Possibly this motivates a new upstream release rather than distro
  patches in Debian/Ubuntu.

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

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

[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed

[AsciiWolf]

Upstream bug report: https://github.com/hughsie/PackageKit/issues/245

** Bug watch added: github.com/hughsie/PackageKit/issues #245
   https://github.com/hughsie/PackageKit/issues/245

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

Title:
  gnome software leaves dependencies installed

Status in GNOME Software:
  Invalid
Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged
Status in packagekit package in Ubuntu:
  New

Bug description:
  Using gnome software (or another PackageKit or aptdaemon based UI) to
  install an application - removal of that package leaves behind
  dependencies

  Installing an application with ubuntu software centre only leaves
  behind config files (seen in synaptic labelled for complete removal).

  After installing and then removing alarm clock with USC -

  sudo apt-get autoremove
  [sudo] password for wolf:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  After cleaning up and then reinstalling with gnome software, followed
  by the removal

  sudo apt-get autoremove
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED
    libappindicator1 libindicator7
  0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade.
  After this operation, 184 kB disk space will be freed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar  3 16:23:45 2016
  InstallationDate: Installed on 2015-10-29 (126 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions

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

[Touch-packages] [Bug 1753884] Re: session logout after suspend

[Simon]

Hey Christopher,

1) When I report the crash files with:

$ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash

I get a pop saying Ubuntu has experienced an error and asks me to
continue to report it. I'm going to assume that this is part of the
process of reporting it and it's working correctly, and not ubuntu-bug
experiencing a bug while I'm reporting it (it's a bit confusing to me).
But it's not clear to me what the next steps are here (even from that
documentation).

2) The crash created after the crash are:

ls -la /var/crash/
total 50516
drwxrwsrwt  2 root  whoopsie 4096 Mar  9 11:12 .
drwxr-xr-x 14 root  root 4096 Aug  1  2017 ..
-rw-r-  1 root  whoopsie   560003 Mar  7 13:16 
_lib_systemd_systemd-udevd.0.crash
-rwxrwxrwx  1 root  whoopsie0 Mar  9 11:11 .lock
-rw-r-  1 simon whoopsie  1585974 Mar  9 11:12 _opt_atom_atom.1000.crash
-rw-r-  1 simon whoopsie 49568222 Mar  9 11:12 
_usr_bin_gnome-shell.1000.crash

The Mar 9 ones are the ones that appeared after I closed my lid, let the
laptop suspend, and start things up again. I don't think the atom crash
file is always there.

3) I'll try upgrading to 17.10 for now, and then 18.04 when it becomes
the new LTS.

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

Title:
   session logout after suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Only when I have a second monitor plugged in, if I close the lid of my
  laptop, my session gets logged out. What I'm expecting is the lock
  screen comes up.

  Sometimes (but not always) the second monitor will flash the "logged
  out" screen for a second or two before going dim.

  I have "Suspend even if external monitor is plugged in" enabled in
  Tweak Tools.

  WORKAROUND: Suspend via the GUI with the lid open.

  WORKAROUND: Unplug the second monitor before closing the lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Mar  6 18:07:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-02-15 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20AQ009HUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=6f20d80f-81f4-40c1-aafd-95b2c5de55ed ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET78WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ009HUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ009HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ009HUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ009HUS
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-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/1753884/+subscriptions

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

[Touch-packages] [Bug 1754744] [NEW] Launching any electron app crashes Xorg

[Kyle Fazzari]

Public bug reported:

If I dare to launch any electron-based app (chrome, spotify, atom,
vscode, etc.) there's roughly an 80% chance that it kills X (bringing me
back to the login screen). This doesn't _always_ happen. Note that I
have a 4k laptop, with a 4k external screen. Things seem to have a
better chance of succeeding if I disconnect the external display before
launching the electron app. Once it launches successfully things seem to
be stable, even after re-connecting the external display.

I SSHd into this machine from another, and connected to X from gdb, then
opened vscode to cause the crash. Here is the backtrace I got from that
session (this is easy to reproduce, happy to provide any requested
info):

root@Pandora:~# gdb /usr/bin/Xorg $(pidof Xorg)
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/usr/bin/Xorg": not in executable format: File format not recognized
Attaching to process 2325
[New LWP 2480]
[New LWP 2481]
[New LWP 2482]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f3302ea95d3 in select () at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) cont
Continuing.

Thread 1 "Xorg" received signal SIGSEGV, Segmentation fault.
0x55f7cbb6f650 in ?? ()
(gdb) bt f
#0  0x55f7cbb6f650 in ?? ()
No symbol table info available.
#1  0x55f7ca8ec6dc in ProcVidModeGetModeLine (client=0x55f7cc218ee0) at 
../../Xext/vidmode.c:255
stuff = 
rep = {type = 1 '\001', pad1 = 0 '\000', sequenceNumber = 254, length = 
5, dotclock = 0, hdisplay = 0, hsyncstart = 0, hsyncend = 0, 
  htotal = 0, hskew = 0, vdisplay = 0, vsyncstart = 0, vsyncend = 0, 
vtotal = 0, pad2 = 0, flags = 0, reserved1 = 0, reserved2 = 0, 
  reserved3 = 0, privsize = 0}
pScreen = 
mode = 0x7ffd64d56e20
dotClock = 32765
#2  0x55f7ca77ad9f in Dispatch () at ../../dix/dispatch.c:430
clientReady = 0x55f7cbf9c780
result = 
client = 0x55f7cc218ee0
nready = 0
icheck = 0x55f7cab7b130 
start_tick = 12090
#3  0x55f7ca77ee13 in dix_main (argc=11, argv=0x7ffd64d57018, 
envp=) at ../../dix/main.c:300
i = 
alwaysCheckForInput = {0, 1}
#4  0x7f3302dcc830 in __libc_start_main (main=0x55f7ca769030 , 
argc=11, argv=0x7ffd64d57018, init=, 
fini=, rtld_fini=, stack_end=0x7ffd64d57008) 
at ../csu/libc-start.c:291
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -792397858051174054, 
94522742050880, 140726295162896, 0, 0, -6839407696988057254, 
-687903866822310}, mask_was_saved = 0}}, priv = {pad = 
{0x0, 0x0, 0xb, 0x55f7ca769030 }, data = {prev = 0x0, 
  cleanup = 0x0, canceltype = 11}}}
not_first_call = 
#5  0x55f7ca769069 in _start ()
No symbol table info available.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Mar  9 12:09:59 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
InstallationDate: Installed on 2016-08-01 (585 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Dell Precision M3800
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=53750055-6616-428b-88f9-c6c555f8c31d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: Dell 

[Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()

[Dale Gulledge]

I don't know whether we've had a regression here, but I started seeing
what looks like this exact same problem this morning.

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

Title:
  systemd-logind spins in cgmanager_ping_sync()

Status in cgmanager package in Ubuntu:
  Invalid
Status in libnih package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  systemd-logind is consuming a high level of cpu on a continual basis:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
 
676 root  20   0   43644   2144   1568 R 100.0  0.0  74:43.77 
systemd-logind

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd-services 204-5ubuntu17
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 09:09:37 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-23 (348 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago)

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

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

[Touch-packages] [Bug 1495170] Re: man apparmor still assumes upstart as init

[Lyn Perrine]

** Tags added: bionic

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

Title:
  man apparmor still assumes upstart as init

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  To reproduce in a terminal or shell run man apparmor. In the section
  Ubunut policy load assumes upstart as in 14.10 and earlier.

  To copy the section from the man page it is

   UBUNTU POLICY LOAD
 Ubuntu systems use upstart(8) instead of a traditional SysV init 
system.  Because upstart is an event-driven init system and understanding that 
policy must be loaded before execution, Ubuntu loads
 policy in two ways:

  1. via upstart jobs for services started during the boot process
  2. via the AppArmor upstart job for any remaining policy

 The AppArmor upstart job is configured to make sure all policy is 
loaded before any user sessions start. When developing policy it is important 
to know how your application is started and if policy
 load should be handled specially.

 The upstart job may be call with or without arguments, like so:

 $ sudo start apparmor
 $ sudo start apparmor ACTION=clear # clear policy cache
 $ sudo start apparmor ACTION=teardown  # unload all policy
 $ sudo start apparmor ACTION=reload# reload policy
 $ sudo start apparmor ACTION=force-reload  # same as 'reload'

 Because the job is an upstart(8) task, use 'start apparmor
  ACTION=teardown' to unload all policy.

 In general, nothing extra has to be done for applications not
  started during boot or those that start after AppArmor's upstart job.

 If the confined application has an Upstart job, adjust the job tUBUNTU 
POLICY LOAD
 Ubuntu systems use upstart(8) instead of a traditional SysV init 
system.  Because upstart is an event-driven init system and understanding that 
policy must be loaded before execution, Ubuntu loads
 policy in two ways:

  1. via upstart jobs for services started during the boot process
  2. via the AppArmor upstart job for any remaining policy

 The AppArmor upstart job is configured to make sure all policy is 
loaded before any user sessions start. When developing policy it is important 
to know how your application is started and if policy
 load should be handled specially.

 The upstart job may be call with or without arguments, like so:

 $ sudo start apparmor
 $ sudo start apparmor ACTION=clear # clear policy cache
 $ sudo start apparmor ACTION=teardown  # unload all policy
 $ sudo start apparmor ACTION=reload# reload policy
 $ sudo start apparmor ACTION=force-reload  # same as 'reload'

 Because the job is an upstart(8) task, use 'start apparmor
  ACTION=teardown' to unload all policy.

 In general, nothing extra has to be done for applications not
  started during boot or those that start after AppArmor's upstart job.

 If the confined application has an Upstart job, adjust the job
  to call /lib/init/apparmor-profile-load with the filename of the
  policy file (relative to /etc/apparmor.d/). For example:

 pre-start script
 /lib/init/apparmor-profile-load usr.bin.foo
 end script

 If the confined application does not have an Upstart job but it starts 
before AppArmor's second stage initscript, then add a symlink from the policy 
file in /etc/apparmor.d to
 /etc/apparmor/init/network-interface-security/. For example:

 $ cd /etc/apparmor/init/network-interface-security/
 $ sudo ln -s /etc/apparmor.d/usr.bin.foo .

 The network-interface-security Upstart job will load all the symlinked 
policy files in /etc/apparmor/init/network-interface-security/ before any 
network interfaces come up. Because network interfaces
 come up very early in the boot process, this will help ensure that 
AppArmor policy is loaded before the confined application starts.

 In addition, AppArmor on Ubuntu stores policy in two places:

  1. /etc/apparmor.d for system policy
  2. /var/lib/apparmor/profiles for click policy
  UBUNTU POLICY LOAD
 Ubuntu systems use upstart(8) instead of a traditional SysV init 
system.  Because upstart is an event-driven init system and understanding that 
policy must be loaded before execution, Ubuntu loads
 policy in two ways:

  1. via upstart jobs for services started during the boot process
  2. via the AppArmor upstart job for any remaining policy

 The AppArmor upstart job is configured to make sure all policy is 
loaded before 

[Touch-packages] [Bug 1627564] Re: crash due to assertion in ensure_surface_for_gicon

[Launchpad Bug Tracker]

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

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

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

Title:
  crash due to assertion in ensure_surface_for_gicon

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  bubble opened up indicating there was a failure during the latest
  update.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Sun Sep 25 20:37:06 2016
  ExecutablePath: /usr/sbin/lightdm-gtk-greeter
  InstallationDate: Installed on 2016-08-04 (52 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
  ProcCmdline: /usr/sbin/lightdm-gtk-greeter
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: lightdm-gtk-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
   [greeter]
   theme-name = Lubuntu-dark-panel
  mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 
2016-08-14T22:33:57.293011

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

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

[Touch-packages] [Bug 1627564] Re: was doing an upgrade and this created a trouble report

[Vlad Orlov]

** Package changed: lightdm-gtk-greeter (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- was doing an upgrade and this created a trouble report
+ crash due to assertion in ensure_surface_for_gicon

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

Title:
  crash due to assertion in ensure_surface_for_gicon

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  bubble opened up indicating there was a failure during the latest
  update.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Sun Sep 25 20:37:06 2016
  ExecutablePath: /usr/sbin/lightdm-gtk-greeter
  InstallationDate: Installed on 2016-08-04 (52 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
  ProcCmdline: /usr/sbin/lightdm-gtk-greeter
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: lightdm-gtk-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
   [greeter]
   theme-name = Lubuntu-dark-panel
  mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 
2016-08-14T22:33:57.293011

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

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

[Touch-packages] [Bug 1678693] Re: mate-notification-daemon crashed with SIGABRT in g_assertion_message()

[Vlad Orlov]

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

** Package changed: mate-notification-daemon (Ubuntu) => gtk+3.0
(Ubuntu)

** This bug has been marked a duplicate of bug 1627564
   crash due to assertion in ensure_surface_for_gicon

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

Title:
  mate-notification-daemon crashed with SIGABRT in g_assertion_message()

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  occurred while installing packages

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-notification-daemon 1.18.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  2 23:04:26 2017
  ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon
  InstallationDate: Installed on 2017-04-01 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_US
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: mate-notification-daemon
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-notification-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1678693] [NEW] mate-notification-daemon crashed with SIGABRT in g_assertion_message()

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

occurred while installing packages

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: mate-notification-daemon 1.18.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Apr  2 23:04:26 2017
ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon
InstallationDate: Installed on 2017-04-01 (1 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANGUAGE=en_US
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: mate-notification-daemon
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: mate-notification-daemon crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: Confirmed


** Tags: amd64 apport-crash zesty
-- 
mate-notification-daemon crashed with SIGABRT in g_assertion_message()
https://bugs.launchpad.net/bugs/1678693
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1627564] [NEW] was doing an upgrade and this created a trouble report

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

bubble opened up indicating there was a failure during the latest
update.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
Uname: Linux 4.4.0-9136-generic i686
ApportVersion: 2.20.3-0ubuntu7
Architecture: i386
Date: Sun Sep 25 20:37:06 2016
ExecutablePath: /usr/sbin/lightdm-gtk-greeter
InstallationDate: Installed on 2016-08-04 (52 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
ProcCmdline: /usr/sbin/lightdm-gtk-greeter
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/false
Signal: 6
SourcePackage: lightdm-gtk-greeter
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
 [greeter]
 theme-name = Lubuntu-dark-panel
mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 2016-08-14T22:33:57.293011

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


** Tags: apport-crash i386 yakkety
-- 
was doing an upgrade and this created a trouble report
https://bugs.launchpad.net/bugs/1627564
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1427638] Re: Extra package box does not expand with its window, rendering its contents unreadable

[L'Africain]

This problem is not present under Ubuntu Mate, I experienced it on
Unity.

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

Title:
  Extra package box does not expand with its window, rendering its
  contents unreadable

Status in gdebi package in Ubuntu:
  Triaged

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 14.10 with lubuntu-desktop
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  0.9.5.4
  3) What you expected to happen
  Look at attached screenshot:
  Window containing focused string "libjpeg62:i386"  should be 
resizable/adjustable to display more than 1 string  (automatically? manually?)
  4) What happened instead
  It's not resizable automatically nor I'm able to resize it to display more 
than 1 string

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

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

[Touch-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

[Eugene Romanenko]

After upgrading artful to bionic (debian way, replaced artful to bionic in 
sources.list) faced this issue.
Solved by installing libegl-mesa0 package.

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Fix Released
Status in mesa-demos package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1754537] Re: Scilab 5.5.2 cannot create Java Main Class on Ubuntu 14.04.

[Timo Aaltonen]

mesa hasn't been updated in trusty, so there's no reason to update
libjogl either

I don't know what broke it, but it wasn't mesa.

** Package changed: mesa (Ubuntu) => scilab (Ubuntu)

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

Title:
  Scilab 5.5.2 cannot create Java Main Class on Ubuntu 14.04.

Status in scilab package in Ubuntu:
  New

Bug description:
  On March 5, after months of working regularly, Scilab 5.5.2 stopped
  working altogether if launched from GUI.

  Trying to launch from terminal, it still did not work but at least
  informed me that it could not create a Java Main Class, and some more
  details:

  Exception in thread "main" java.lang.NullPointerException
at org.scilab.modules.gui.utils.ConfigManager.checkVersion(Unknown 
Source)
at org.scilab.modules.gui.utils.ConfigManager.createUserCopy(Unknown 
Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Packages:
 OpenGL version string: 3.0 Mesa 10.1.3
 Scilab;  5.5.0-2
 libjogl2-ini;  2.1.5-1ubuntu3
 libjogl1-java;  2.1.5-1ubuntu3

  Ubuntu 14.04.5 LTS Release: 14.04

  A related bug is: https://bugs.launchpad.net/mesa/+bug/1742894, which
  has been resolved for Ubuntu Xenial with a new version of
  libjogl2-java. No such fix seems to be available for Trusty, however.

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

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

[Touch-packages] [Bug 1753136] Re: Gettext package inconsistency

[Launchpad Bug Tracker]

This bug was fixed in the package libgweather - 3.28.0-1

---
libgweather (3.28.0-1) experimental; urgency=medium

  * New upstream release (LP: #1753136)
  * Have libgweather-3-dev depend on libgeocode-glib-dev
  * Add workaround for Ubuntu translations issue
  * Update debian/docs to install README.md (Closes: #891540)

 -- Jeremy Bicha   Fri, 09 Mar 2018 06:18:19 -0500

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

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

Title:
  Gettext package inconsistency

Status in libgweather:
  Fix Released
Status in Ubuntu Translations:
  New
Status in libgweather package in Ubuntu:
  Fix Released

Bug description:
  New translation issue after the switch to meson. It's probably an
  upstream thing, and I have filed an upstream bug report with a patch
  and explained it there.

  Possibly this motivates a new upstream release rather than distro
  patches in Debian/Ubuntu.

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

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

[Touch-packages] [Bug 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

[j1n3l0]

If it helps I was trying to install vagrant when this happened. Output
(of a second attempt) below:

$ sudo apt install vagrant
Reading package lists... Done
Building dependency tree   
Reading state information... Done
vagrant is already the newest version (2.0.2+dfsg-2ubuntu2).
0 to upgrade, 0 to newly install, 0 to remove and 5 not to upgrade.
7 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up lvm2 (2.02.176-4.1ubuntu2) ...
update-initramfs: deferring update (trigger activated)
Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked.
invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed.
● lvm2-lvmetad.service - LVM2 metadata daemon
   Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor 
preset: enabled)
   Active: inactive (dead)
 Docs: man:lvmetad(8)

Mar 09 16:06:24 ynap-techub systemd[1]: Started LVM2 metadata daemon.
Mar 09 16:36:08 ynap-techub systemd[1]: Stopping LVM2 metadata daemon...
Mar 09 16:36:08 ynap-techub systemd[1]: Stopped LVM2 metadata daemon.
dpkg: error processing package lvm2 (--configure):
 installed lvm2 package post-installation script subprocess returned error exit 
status 1
dpkg: dependency problems prevent configuration of libguestfs0:amd64:
 libguestfs0:amd64 depends on lvm2; however:
  Package lvm2 is not configured yet.

dpkg: error processing package libguestfs0:amd64 (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates it's a follow-up 
error from a previous failure.
dpkg: dependency problems prevent configuration of 
libguestfs-reiserfs:amd64:
 libguestfs-reiserfs:amd64 depends on libguestfs0 (= 1:1.36.13-1ubuntu3); 
however:
  Package libguestfs0:amd64 is not configured yet.

dpkg: error processing package libguestfs-reiserfs:amd64 (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates it's a follow-up 
error from a previous failure.
dpkg: dependency problems prevent configuration of 
libguestfs-perl:
 libguestfs-perl depends on libguestfs0 (= 1:1.36.13-1ubuntu3); however:
  Package libguestfs0:amd64 is not configured yet.

dpkg: error processing package libguestfs-perl (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports has already been reached
dpkg: 
dependency problems prevent configuration of libguestfs-hfsplus:amd64:
 libguestfs-hfsplus:amd64 depends on libguestfs0 (= 1:1.36.13-1ubuntu3); 
however:
  Package libguestfs0:amd64 is not configured yet.

dpkg: error processing package libguestfs-hfsplus:amd64 (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports has already been reached
dpkg: 
dependency problems prevent configuration of libguestfs-tools:
 libguestfs-tools depends on libguestfs0 (= 1:1.36.13-1ubuntu3); however:
  Package libguestfs0:amd64 is not configured yet.
 libguestfs-tools depends on libguestfs-perl (= 1:1.36.13-1ubuntu3); however:
  Package libguestfs-perl is not configured yet.

dpkg: error processing package libguestfs-tools (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports has already been reached
dpkg: 
dependency problems prevent configuration of libguestfs-xfs:amd64:
 libguestfs-xfs:amd64 depends on libguestfs0 (= 1:1.36.13-1ubuntu3); however:
  Package libguestfs0:amd64 is not configured yet.

dpkg: error processing package libguestfs-xfs:amd64 (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports has already been reached
Processing 
triggers for initramfs-tools (0.130ubuntu3) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-10-generic
Errors were encountered while processing:
 lvm2
 libguestfs0:amd64
 libguestfs-reiserfs:amd64
 libguestfs-perl
 libguestfs-hfsplus:amd64
 libguestfs-tools
 libguestfs-xfs:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I *think* this was from trying to install python-guestfs

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu2
  ProcVersionSignature: Ubuntu 

[Touch-packages] [Bug 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I *think* this was from trying to install python-guestfs

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Wed Jan 31 09:56:36 2018
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-06-28 (217 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: lvm2
  Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-01-30 (0 days ago)

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Stephen M]

This bug is not resolved.  Seeing it under 16.04LTS without dbus-user-
session or flatpak installed.

smm@laptop /var/log
$ sudo apt list --installed |grep dbus-user-session

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

smm@laptop /var/log
$ sudo apt list --installed |grep flatpak

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1754692] Re: Tabs in Settings of Thunderbird not visible

[J.Ar]

The same window with Adwaita-theme is ok.

** Attachment added: "Adwaita Theme"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1754692/+attachment/5074400/+files/Bildschirmfoto%20vom%202018-03-09%2016-49-55.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/1754692

Title:
  Tabs in Settings of Thunderbird not visible

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  I am on Ubuntu 18.04 Bionic right now and noticed a little theme
  missbehavior. (i think)

  >> Open 'Thunderbird'...go into 'Settings'...go to 'Security' (for
  example)

  There the Tabs below (Junk, Password, ...) are not visible.
  There is just text with no background (see screenhot)

  
  Sidenote: The same i noticed on Xubuntu with greybird-theme. But with other 
themes (numix, arc) they are visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.389
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 15:26:35 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1754692/+subscriptions

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

[Touch-packages] [Bug 1754692] [NEW] Tabs in Settings of Thunderbird not visible

[J.Ar]

Public bug reported:

I am on Ubuntu 18.04 Bionic right now and noticed a little theme
missbehavior. (i think)

>> Open 'Thunderbird'...go into 'Settings'...go to 'Security' (for
example)

There the Tabs below (Junk, Password, ...) are not visible.
There is just text with no background (see screenhot)


Sidenote: The same i noticed on Xubuntu with greybird-theme. But with other 
themes (numix, arc) they are visible.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.389
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  9 15:26:35 2018
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Bildschirmfoto vom 2018-03-09 15-30-40.png"
   
https://bugs.launchpad.net/bugs/1754692/+attachment/5074354/+files/Bildschirmfoto%20vom%202018-03-09%2015-30-40.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/1754692

Title:
  Tabs in Settings of Thunderbird not visible

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  I am on Ubuntu 18.04 Bionic right now and noticed a little theme
  missbehavior. (i think)

  >> Open 'Thunderbird'...go into 'Settings'...go to 'Security' (for
  example)

  There the Tabs below (Junk, Password, ...) are not visible.
  There is just text with no background (see screenhot)

  
  Sidenote: The same i noticed on Xubuntu with greybird-theme. But with other 
themes (numix, arc) they are visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.389
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 15:26:35 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1754692/+subscriptions

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

[Touch-packages] [Bug 1754686] [NEW] libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like slack-desktop

[Nathaniel W. Turner]

Public bug reported:

Updating the curl package pulls in libcurl4, which for some reason
forces libcurl3 to be removed. This prevents 3rd party apps that still
build against libcurl3 from being installed. Isn't there a more graceful
way to effect the transition from libcurl3 to libcurl4?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libcurl4 7.58.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar  9 10:10:10 2018
EcryptfsInUse: Yes
SourcePackage: curl
UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)

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


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

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

Title:
  libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like
  slack-desktop

Status in curl package in Ubuntu:
  New

Bug description:
  Updating the curl package pulls in libcurl4, which for some reason
  forces libcurl3 to be removed. This prevents 3rd party apps that still
  build against libcurl3 from being installed. Isn't there a more
  graceful way to effect the transition from libcurl3 to libcurl4?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcurl4 7.58.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:10:10 2018
  EcryptfsInUse: Yes
  SourcePackage: curl
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)

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

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

[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

[Filippo Molesti]

Could we please know when this bug is going to be fixed at last?

If is not uncommon, actually quite common I would say, to have a NVIDIA
graphic card and a more recent version of GCC installed than the one in
the Ubuntu distribution, which is quite old. And then the machine is
broke when the new kernel is installed!

All the fixes in the above risk breaking the machine irreparably. Even
reinstalling Ubuntu from scratch may not work in the long run, if the
bug is not fixed in the new kernel version, because one also need to use
the most recent versions of GCC and thus the problem is bound to
reoccur. And having to keep using kernel 112 also looks quite
unsatisfactorily as a long term solution.

We need the matter to be fixed once and for all.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  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: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To manage notifications about this bug go to:

[Touch-packages] [Bug 1751011] Re: bash crashes in qemu-user environments (bionic)

[nuclearsandwich]

The ROS (http://www.ros.org/) team uses qemu and docker to build native
arm packages on our buildfarm. So this is a pretty significant roadblock
for us as we prepare our next release based on bionic.

Many of our build processes rely on bash scripts, but even if we were to
port all of those away from bash, it's an essential package and building
an image without it is not really tenable. I have packaged bash with the
-no-pie flag restored and that's working for us at the moment, but even
incorporating that into our image baking process is not very clean
(https://github.com/osrf/multiarch-docker-image-generation/pull/21).

If upstream's solution is not preferred. Is there another way to get
bash working under qemu within the release window?

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

Title:
  bash crashes in qemu-user environments (bionic)

Status in bash package in Ubuntu:
  Triaged
Status in bash package in Debian:
  Fix Released

Bug description:
  Attempts to launch bash in an arm64 qemu-user environment in bionic
  results in the following error message:

  bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes
  allocated)

  This causes any qemu/chroot based bootstrapping to fail as many
  packages invoke bash during postinst.

  Version: bash_4.4.18-1ubuntu1_arm64
  Release: 18.04 pre-release

  QEMU: 2.8.0

  This appears to have been reported and fixed in the corresponding
  Debian package (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=889869)

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

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

[Touch-packages] [Bug 1427332] [NEW] nautilus crashed with signal 5 in _XReply()

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

none

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
Date: Mon Mar  2 16:17:00 2015
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
InstallationDate: Installed on 2014-10-24 (129 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=es_UY:es
 PATH=(custom, no user)
 LANG=es_UY.UTF-8
 SHELL=/bin/bash
 TERM=unknown
Signal: 5
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: nautilus crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to vivid on 2015-01-05 (56 days ago)
UserGroups:
 
usr_lib_nautilus:
 brasero3.12.0-0ubuntu2
 evince 3.14.1-0ubuntu5
 file-roller3.14.2-0ubuntu4
 gnome-terminal 3.14.2-0ubuntu2
 nautilus-share 0.7.3-1ubuntu5

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: Confirmed


** Tags: amd64 apport-crash vivid wily yakkety
-- 
nautilus crashed with signal 5 in _XReply()
https://bugs.launchpad.net/bugs/1427332
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1201854] Re: gnome-settings-daemon crashed with signal 5 in _XReply()

[Vlad Orlov]

** Package changed: gnome-settings-daemon (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- gnome-settings-daemon crashed with signal 5 in _XReply()
+ crash in XGetWindowProperty from read_settings from 
gdk_xsettings_manager_window_filter

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

Title:
  crash in XGetWindowProperty from read_settings from
  gdk_xsettings_manager_window_filter

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  This happened immediately after a reboot for updates. Immediately
  after I checked for more updates and there were some, meaning this bug
  might already be fixed. About the updates, I noticed that a few
  'failed to download' but running sudo apt-get upgrade they installed
  fine. I don't know if this is related but it might be. This has
  probably happened several times, but I don't think it's a regular
  pattern. Running 13.10 Alpha. Otherwise seems to be pretty stable so
  far despite the minor bugs.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.6.4-0ubuntu15
  ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Fri Jul 12 23:43:27 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ExecutableTimestamp: 1372327096
  InstallationDate: Installed on 2013-06-14 (28 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcCwd: /home/karatekid
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to saucy on 2013-07-12 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Touch-packages] [Bug 1252904] Re: Move chromium-browser apparmor profile from apparmor package to c-b

[Olivier Tilloy]

** Changed in: apparmor (Ubuntu)
 Assignee: Chad Miller (cmiller) => (unassigned)

** Changed in: chromium-browser (Ubuntu)
 Assignee: Chad Miller (cmiller) => (unassigned)

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

Title:
  Move chromium-browser apparmor profile from apparmor package to c-b

Status in apparmor package in Ubuntu:
  Triaged
Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Chromium-browser should own its own apparmor profile.

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

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

[Touch-packages] [Bug 1201854] [NEW] gnome-settings-daemon crashed with signal 5 in _XReply()

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This happened immediately after a reboot for updates. Immediately after
I checked for more updates and there were some, meaning this bug might
already be fixed. About the updates, I noticed that a few 'failed to
download' but running sudo apt-get upgrade they installed fine. I don't
know if this is related but it might be. This has probably happened
several times, but I don't think it's a regular pattern. Running 13.10
Alpha. Otherwise seems to be pretty stable so far despite the minor
bugs.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-settings-daemon 3.6.4-0ubuntu15
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Fri Jul 12 23:43:27 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ExecutableTimestamp: 1372327096
InstallationDate: Installed on 2013-06-14 (28 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MarkForUpload: True
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCwd: /home/karatekid
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-settings-daemon crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to saucy on 2013-07-12 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: Confirmed


** Tags: amd64 apport-crash saucy
-- 
gnome-settings-daemon crashed with signal 5 in _XReply()
https://bugs.launchpad.net/bugs/1201854
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1744744] [NEW] /usr/bin/mate-settings-daemon:5:XGetWindowProperty:gdk_check_wm_state_changed:gdk_x11_display_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-settings-daemon.  This problem was most recently seen with package version 
1.18.2-1, the problem page at 
https://errors.ubuntu.com/problem/ce324a21097bbf499a8ddc2db96e9a01d4252f07 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic kylin-17.10 yakkety zesty
-- 
/usr/bin/mate-settings-daemon:5:XGetWindowProperty:gdk_check_wm_state_changed:gdk_x11_display_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_translate_event
https://bugs.launchpad.net/bugs/1744744
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1751948] Re: /usr/bin/nautilus:5:XGetWindowProperty:read_settings:gdk_xsettings_manager_window_filter:gdk_event_apply_filters:gdk_event_source_translate_event

[Vlad Orlov]

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

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** This bug has been marked a duplicate of bug 1201854
   crash in XGetWindowProperty from read_settings from 
gdk_xsettings_manager_window_filter

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

Title:
  
/usr/bin/nautilus:5:XGetWindowProperty:read_settings:gdk_xsettings_manager_window_filter:gdk_event_apply_filters:gdk_event_source_translate_event

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.18.5-0ubuntu1~xenial1, the problem page at 
https://errors.ubuntu.com/problem/190c0ee1caee53020969ace002fde3c337a9d748 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1754671] [NEW] Full-tunnel VPN DNS leakage regression

[dwmw2]

*** This bug is a security vulnerability ***

Public security bug reported:

In 16.04 the NetworkManager package used to carry this patch:
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

It fixed the DNS setup so that when I'm on the VPN, I am not sending
unencrypted DNS queries to the (potentially hostile) local nameservers.

This patch disappeared in an update. I think it was present in
1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
It's not a *regression* there though, as they didn't fix it yet (unfortunately!)

** Affects: network-manager (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: regression-update xenial

** Information type changed from Private Security to Public Security

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Touch-packages] [Bug 1670463] Re: crash in XGetWindowProperty from gdk_check_wm_desktop_changed

[Vlad Orlov]

** Summary changed:

- mate-settings-daemon crashed with signal 5 in _XReply()
+ crash in XGetWindowProperty from gdk_check_wm_desktop_changed

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

Title:
  crash in XGetWindowProperty from gdk_check_wm_desktop_changed

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  start up error

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-settings-daemon 1.17.1-0~ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Mon Mar  6 20:29:40 2017
  ExecutablePath: /usr/bin/mate-settings-daemon
  InstallationDate: Installed on 2016-09-09 (177 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/mate-settings-daemon
  Signal: 5
  SourcePackage: mate-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: mate-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to zesty on 2016-10-16 (140 days ago)
  UserGroups: adm audio cdrom dialout dip lpadmin netdev plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Mathieu Trudel-Lapierre]

Confirming this is broken. Dropping the patch 0001-dns-use-DBus-to-make-
dnsmasq-nameserver-changes.patch in network-manager
(1.2.4-0ubuntu0.16.04.1) was done, but it looks like not all the code in
that patch was actually upstream.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

** Tags added: regression-update

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Touch-packages] [Bug 1427332] Re: nautilus crashed with signal 5 in _XReply()

[Vlad Orlov]

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- nautilus crashed with signal 5 in _XReply()
+ crash in XGetWindowProperty from gdk_check_wm_state_changed

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

Title:
  crash in XGetWindowProperty from gdk_check_wm_state_changed

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  Date: Mon Mar  2 16:17:00 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-10-24 (129 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: nautilus
  ProcEnviron:
   LANGUAGE=es_UY:es
   PATH=(custom, no user)
   LANG=es_UY.UTF-8
   SHELL=/bin/bash
   TERM=unknown
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to vivid on 2015-01-05 (56 days ago)
  UserGroups:
   
  usr_lib_nautilus:
   brasero3.12.0-0ubuntu2
   evince 3.14.1-0ubuntu5
   file-roller3.14.2-0ubuntu4
   gnome-terminal 3.14.2-0ubuntu2
   nautilus-share 0.7.3-1ubuntu5

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

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

[Touch-packages] [Bug 1257505] Re: Create Unity Control Center so can remain on old GNOME Control Center version

[Olivier Tilloy]

Not relevant any longer.

** Changed in: chromium-browser (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: chromium-browser (Ubuntu)
 Assignee: Chad Miller (cmiller) => (unassigned)

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

Title:
  Create Unity Control Center so can remain on old GNOME Control Center
  version

Status in Empathy:
  Fix Released
Status in Eye of GNOME:
  Fix Released
Status in GNOME Color Manager:
  Incomplete
Status in GNOME media utilities:
  Expired
Status in gThumb:
  Fix Released
Status in Nautilus:
  Fix Released
Status in Unity:
  Fix Released
Status in activity-log-manager package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Won't Fix
Status in compiz package in Ubuntu:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in empathy package in Ubuntu:
  Fix Released
Status in eog package in Ubuntu:
  Fix Released
Status in gnome-color-manager package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in gnome-media package in Ubuntu:
  Fix Released
Status in gthumb package in Ubuntu:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-session package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in landscape-client package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in ubuntuone-control-panel package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in webaccounts-browser-extension package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu/Unity uses GNOME Control Center as the application to configure
  the Unity session. We've made a lot of changes appropriate for Ubuntu
  and Unity (61 patches) which makes it hard to maintain and creates a
  conflict for Ubuntu GNOME to use the control center. Unity 7 will be
  replaced by Unity 8 in the future which has a new settings interface.

  So we can continue to remain on the current version of GNOME Control
  Center but allow Ubuntu GNOME to continue to update we will create a
  new project lp:unity-control-center which is a copy of GNOME Control
  Center 3.6 but with appropriate renaming so both can be installed.

  A number of packages that refer to gnome-control-center need to be
  updated to refer to unity-control-center (see bug tasks).

  A PPA for testing is https://launchpad.net/~ubuntu-desktop/+archive
  /unity-control-center

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

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

[Touch-packages] [Bug 1464958] Re: chromium-browser does not run in guest account

[Olivier Tilloy]

** Changed in: chromium-browser (Ubuntu)
 Assignee: Chad Miller (cmiller) => (unassigned)

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

Title:
  chromium-browser does not run in guest account

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in google-chrome-beta package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Description:

  In guest account, start chromium browser shows nothing.  Start with
  command line shows error:

  guest-1qFsXl@home:~$ chromium-browser http://www.google.com
  Check failed: NamespaceUtils::DenySetgroups()

  This used to work for months and found failed for few weeks.

  Version:

  Ubuntu 14.04 LTS
  chromium-browser43.0.2357.81-0ubuntu0.14.04.1.1
  linux-image-3.13.0-54-generic3.13.0-54.91
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Desktop-Session:
   'None'
   'None'
   'None'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  Load-Avg-1min: 0.28
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-54-generic 
root=UUID=85a7733c-fbc4-49bf-84ce-02be4c5ba907 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: H97M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd12/15/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2015-01-14T08:39:14.796369

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

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

[Touch-packages] [Bug 1744744] Re: /usr/bin/mate-settings-daemon:5:XGetWindowProperty:gdk_check_wm_state_changed:gdk_x11_display_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_tr

[Vlad Orlov]

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

** Package changed: mate-settings-daemon (Ubuntu) => gtk+3.0 (Ubuntu)

** This bug has been marked a duplicate of bug 1427332
   crash in XGetWindowProperty from gdk_check_wm_state_changed

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

Title:
  /usr/bin/mate-settings-
  
daemon:5:XGetWindowProperty:gdk_check_wm_state_changed:gdk_x11_display_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_translate_event

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-settings-daemon.  This problem was most recently seen with package version 
1.18.2-1, the problem page at 
https://errors.ubuntu.com/problem/ce324a21097bbf499a8ddc2db96e9a01d4252f07 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1751948] [NEW] /usr/bin/nautilus:5:XGetWindowProperty:read_settings:gdk_xsettings_manager_window_filter:gdk_event_apply_filters:gdk_event_source_translate_event

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.18.5-0ubuntu1~xenial1, the problem page at 
https://errors.ubuntu.com/problem/190c0ee1caee53020969ace002fde3c337a9d748 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: kylin-14.10 kylin-15.04 trusty utopic vivid xenial
-- 
/usr/bin/nautilus:5:XGetWindowProperty:read_settings:gdk_xsettings_manager_window_filter:gdk_event_apply_filters:gdk_event_source_translate_event
https://bugs.launchpad.net/bugs/1751948
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1282294] Re: "Cannot open pixbuf loader module file"

[Seth Arnold]

Please note that YOU the dear end user should do NOTHING about this.

The message is entirely useless because the error condition lasts only
seconds. Which is why this error message is so annoying.

Thanks

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

Title:
  "Cannot open pixbuf loader module file"

Status in gdk-pixbuf package in Ubuntu:
  Triaged
Status in gdk-pixbuf package in Debian:
  New

Bug description:
  While doing testing on trusty, I keep finding errors like the
  following in my apt-get -u dist-upgrade output:

  Preparing to unpack 
.../indicator-printers_0.1.7+14.04.20140213-0ubuntu1_amd64.deb ...
  Unpacking indicator-printers (0.1.7+14.04.20140213-0ubuntu1) over 
(0.1.7daily13.03.01-0ubuntu1) ...

  (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.

  (gtk-update-icon-cache-3.0:29672): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...

  (gtk-update-icon-cache-3.0:32198): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.

  
  These errors make it difficult to look for errors that I might have 
introduced in my own packages and if they persist in our final product will 
make users wonder what is broken and why it is broken.

  sarnold@sec-trusty-amd64:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  sarnold@sec-trusty-amd64:~$ dpkg -S gdk-pixbuf-query-loaders
  libgdk-pixbuf2.0-0:amd64: 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
  sarnold@sec-trusty-amd64:~$ apt-cache policy libgdk-pixbuf2.0-0
  libgdk-pixbuf2.0-0:
Installed: 2.30.5-0ubuntu1
Candidate: 2.30.5-0ubuntu1
Version table:
   *** 2.30.5-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  sarnold@sec-trusty-amd64:~$ dpkg -S /usr/bin/gtk-update-icon-cache-3.0
  libgtk-3-bin: /usr/bin/gtk-update-icon-cache-3.0
  sarnold@sec-trusty-amd64:~$ apt-cache policy libgtk-3-bin
  libgtk-3-bin:
Installed: 3.10.7-0ubuntu2
Candidate: 3.10.7-0ubuntu2
Version table:
   *** 3.10.7-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  sarnold@sec-trusty-amd64:~$ 


  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgtk-3-bin 3.10.7-0ubuntu2
  ProcVersionSignature: User Name 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Wed Feb 19 14:38:47 2014
  InstallationDate: Installed on 2014-01-09 (41 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108)
  ProcEnviron:
   TERM=rxvt-unicode
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

[Guilherme G. Piccoli]

Thanks Dan and Brian.

Just tested: after 1h and more than 5500 SSH sessions, no leaks at all were 
observed.
(As a comparison, testing the "old" version 20.26 I got 1.8 MB of leak in half 
an hour!)

Cheers,


Guilherme

** Tags removed: sts-sru-needed verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Below the SRU request form. Please refer to the Original Description
  to a more comprehensive explanation of the problem observed.

  
  [Impact] 

   * systemd-logind tool is leaking memory at each session connected. The 
   issues happens in systemd from Trusty (14.04) only.

   * Three issues observed:
- systemd-logind is leaking entire sessions, i.e, the sessions are not 
  feeed after they're closed. In order to fix that, we proactively add 
  the sessions to systemd garbage collector (gc) when they are closed. 
  Also, part of the fix is to make cgmanager package a dependency. Refer 
  to comment #1 to a more thorough explanation of the issue and the fix.

- a small memory leak was observed in the session creation logic of 
  systemd-logind. The fix for that is the addition of an appropriate 
  free() call. Refer to comment #2 to more details on the issue and fix.

- another small memory leak was observed in the cgmanager glue code of 
  systemd-logind - this code is only present in this specific Ubuntu 
  release of the package, due to necessary compatibility layer with 
  upstart init system. The fix is to properly call free() in 2 
  functions. Refer to comment #3 to a deep exposition of the issue and 
  the fix.

  
  [Test Case]

   * The basic test-case is to run the following loop from a remote machine:
 while true; do ssh  "whoami"; done

   * It's possible to watch the increase in memory consumption from 
 "systemd-logind" process in the target machine. One can use the
 "ps uax" command to verify the RSS of the process, or count its 
 anonymous pages from /proc//smaps.

  
  [Regression Potential] 

   * Since the fixes are small and not intrusive, the potential for 
 regressions are low. More regression considerations on comments #1, #2 
 and #3 for each fix.

   * A potential small regressson is performance-wise, since now we add 
 sessions to garbage collector proactively.

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

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

[Touch-packages] [Bug 1359308] Re: crash due to assertion in gail_focus_notify_when_idle: code should not be reached

[Vlad Orlov]

** Summary changed:

- mate-panel crashed when using window list
+ crash due to assertion in gail_focus_notify_when_idle: code should not be 
reached

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

Title:
  crash due to assertion in gail_focus_notify_when_idle: code should not
  be reached

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  On an Ubuntu MATE utopic amd64 system, mate-panel 1.8.0+dfsg1-2
  crashed when I clicked on an item in the window list (located in the
  bottom panel). The panel reappeared and continued working correctly.
  This happened while apt-get was upgrading packages, but mate-panel was
  not one of the packages being upgraded.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: mate-panel 1.8.0+dfsg1-2
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  Date: Wed Aug 20 13:21:43 2014
  ExecutablePath: /usr/bin/mate-panel
  InstallationDate: Installed on 2014-08-19 (1 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
  ProcCmdline: mate-panel
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1754332] Re: /var/log/journal not created on fresh install of systemd

[Francis Ginther]

** Tags added: id-5aa14c7ee2d7eb378a560dd8

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

Title:
  /var/log/journal not created on fresh install of systemd

Status in systemd package in Ubuntu:
  New

Bug description:
  (Such as during image builds.)

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

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

[Touch-packages] [Bug 1282294] Re: "Cannot open pixbuf loader module file"

[Andreas Mohr]

Not fully successfully fixed via comment #18:

$ sudo gdk-pixbuf-query-loaders | tee 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache 
tee: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission 
denied

Thus should instead do entire execution chain via an admin shell (e.g.: sudo 
-s) proper.
Also prefer using (pasting) the unmodified since original suggestion in 
installation log (due to other potential deviations such as 
architecture-specific i386 vs. x86_64 paths).

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

Title:
  "Cannot open pixbuf loader module file"

Status in gdk-pixbuf package in Ubuntu:
  Triaged
Status in gdk-pixbuf package in Debian:
  New

Bug description:
  While doing testing on trusty, I keep finding errors like the
  following in my apt-get -u dist-upgrade output:

  Preparing to unpack 
.../indicator-printers_0.1.7+14.04.20140213-0ubuntu1_amd64.deb ...
  Unpacking indicator-printers (0.1.7+14.04.20140213-0ubuntu1) over 
(0.1.7daily13.03.01-0ubuntu1) ...

  (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.

  (gtk-update-icon-cache-3.0:29672): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...

  (gtk-update-icon-cache-3.0:32198): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.

  
  These errors make it difficult to look for errors that I might have 
introduced in my own packages and if they persist in our final product will 
make users wonder what is broken and why it is broken.

  sarnold@sec-trusty-amd64:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  sarnold@sec-trusty-amd64:~$ dpkg -S gdk-pixbuf-query-loaders
  libgdk-pixbuf2.0-0:amd64: 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
  sarnold@sec-trusty-amd64:~$ apt-cache policy libgdk-pixbuf2.0-0
  libgdk-pixbuf2.0-0:
Installed: 2.30.5-0ubuntu1
Candidate: 2.30.5-0ubuntu1
Version table:
   *** 2.30.5-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  sarnold@sec-trusty-amd64:~$ dpkg -S /usr/bin/gtk-update-icon-cache-3.0
  libgtk-3-bin: /usr/bin/gtk-update-icon-cache-3.0
  sarnold@sec-trusty-amd64:~$ apt-cache policy libgtk-3-bin
  libgtk-3-bin:
Installed: 3.10.7-0ubuntu2
Candidate: 3.10.7-0ubuntu2
Version table:
   *** 3.10.7-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  sarnold@sec-trusty-amd64:~$ 


  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgtk-3-bin 3.10.7-0ubuntu2
  ProcVersionSignature: User Name 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Wed Feb 19 14:38:47 2014
  InstallationDate: Installed on 2014-01-09 (41 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108)
  ProcEnviron:
   TERM=rxvt-unicode
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1753731] Re: Playing media file over gvfs ceased working

[Sebastien Bacher]

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Playing media file over gvfs ceased working

Status in Gstreamer1.0:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I am trying to play a media file over gvfs with totem which stopped working.
  Also showing the media information of such a remote file in nautilus doesn't 
work anymore.

  My guess was this is a regression of 1.13.1, but using gst-play-1.0
  directly surprisingly works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1753731/+subscriptions

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

[Touch-packages] [Bug 1753731] Re: Playing media file over gvfs ceased working

[Bug Watch Updater]

** Changed in: gstreamer1.0
   Status: Confirmed => Fix Released

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

Title:
  Playing media file over gvfs ceased working

Status in Gstreamer1.0:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Triaged

Bug description:
  I am trying to play a media file over gvfs with totem which stopped working.
  Also showing the media information of such a remote file in nautilus doesn't 
work anymore.

  My guess was this is a regression of 1.13.1, but using gst-play-1.0
  directly surprisingly works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1753731/+subscriptions

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

[Touch-packages] [Bug 666446] Re: NetworkManager VPN should offer an option to use *only* VPN nameservers

[dwmw2]

I don't think this should be considered a 'feature request'. If you have
a full-tunnel VPN, your employer will *expect* all your network traffic
to go via the VPN as if you were dialled directly into the corporate
network. Allowing some of the DNS traffic to "escape" to be seen by
potentially malicious local DNS servers is utterly wrong.

In particular I don't agree this is a 'feature request' for 16.04 because it 
*used* to work there.
You fixed it once with this patch:
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

That patch got dropped in an update, so this isn't just a security
problem but also a regression in 16.04.

cf. https://bugzilla.gnome.org/show_bug.cgi?id=746422
https://bugzilla.redhat.com/show_bug.cgi?id=1553634

** Bug watch added: GNOME Bug Tracker #746422
   https://bugzilla.gnome.org/show_bug.cgi?id=746422

** Bug watch added: Red Hat Bugzilla #1553634
   https://bugzilla.redhat.com/show_bug.cgi?id=1553634

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

Title:
  NetworkManager VPN should offer an option to use *only* VPN
  nameservers

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: network-manager

  If I configure a VPN in NetworkManger, the DNS servers I get via DHCP
  over that VPN connection are *prepended* to /etc/resolv.conf. This is
  good in that they get used first, but it's not quite enough.

  Here's the scenario:

  My two office DNS servers support DNSSEC validation. My ISP at home
  does not.

  When I connect to the VPN and try to resolve a name which fails DNSSEC
  validation (e.g. badsign-a.test.dnssec-tools.org), my office DNS
  servers return SERVFAIL (as per DNSSEC validation behavior). This
  causes libc to fail over to my ISP's DNS server. The result is that
  the domain name resolves, when it should fail.

  If this were a real attack instead of a test scenario, it'd have
  security implications.

  If I could make the VPN *replace* my DNS servers in /etc/resolv.conf,
  everything would work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: network-manager 0.8-0ubuntu3 [modified: 
usr/lib/NetworkManager/nm-crash-logger 
usr/lib/NetworkManager/nm-dhcp-client.action 
usr/lib/NetworkManager/nm-dispatcher.action 
usr/lib/NetworkManager/nm-avahi-autoipd.action]
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic x86_64
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Mon Oct 25 13:32:47 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
  Keyfiles: Error: [Errno 2] No such file or directory
  ProcEnviron: Error: [Errno 13] Permission denied: '/proc/24718/environ'
  SourcePackage: network-manager

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

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

[Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

[Benedict Suarez]

Same with my Ubuntu 16.04

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

Title:
  Bluetooth BCM43142A0 doesn’t work

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
  (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
  displayed in the menu bar, if I open the bluetooth UI and switch on,
  nothing happens and the result of “hcitool dev” is empty.

  I have tried to install the windows driver with ndiswrapper, and the
  bluetooth device seems to be detected as an usb bluetooth device but
  still not working. I then add the device to the bluetooth usb device
  and was able to activate bluetooth in the UI but it does not detect
  any other devices (I’ve tested with a smartphone).

  The driver I have installed can be found in asus page =>
  http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
  Select Windows OS, then “bluetooth” section, take the Broadcom driver
  (should be the first one).

  If you extract this archive, you will find a file named “bcbtums-
  win8x64-brcm.inf” which I installed using the following command:

  ndiswrapper -i bcbtums-win8x64-brcm.inf

  Then, the result of “ndiswrapper -l” is:

  bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

  in usb-devices, I find a device which was not present before
  installation (I might have activated btusb before on this paste):

  T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=2006 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM43142A0
  S:  SerialNumber=B8EE6593D989
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

  then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
  can switch usb on, but no device will be detected and I’ve found this
  in the dmesg:

  [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

  which looks pretty much like a “bluetooth not working” message which I
  don’t understand in details.

  I leave here my full dmesg:

  [0.253889] NetLabel:  domain hash size = 128
  [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
  [0.253901] NetLabel:  unlabeled traffic allowed by default
  [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
  [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
  [0.255995] Switched to clocksource hpet
  [0.260468] AppArmor: AppArmor Filesystem Enabled
  [0.260488] pnp: PnP ACPI init
  [0.260500] ACPI: bus type PNP registered
  [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
  [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
  [0.260642] pnp 00:01: [dma 4]
  [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
  [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
  [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
  [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
  [0.260927] system 00:04: [io  0x] has been reserved
  [0.260928] system 00:04: [io  0x] has been reserved
  [0.260930] system 00:04: [io  0x] has been reserved
  [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
  [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
  [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
  [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
  [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
  [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
  [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
  [0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
  [0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 
(active)
  [0.261059] system 00:07: [io  0x04d0-0x04d1] has been reserved
  [0.261061] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.261089] system 00:08: [io  0x0240-0x0259] has been reserved
  [0.261091] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.261144] pnp 00:09: Plug and Play ACPI device, IDs FLT0101 SYN0a00 
SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)
  [0.261179] pnp 00:0a: Plug and Play ACPI 

[Touch-packages] [Bug 1754628] [NEW] vaapi not working

[EricDHH]

Public bug reported:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7)
Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 
470/480/570/580] (Nitro+ Radeon RX 580 4GB) [1da2:e366]

The graphics run by the amdgpu (not -pro) and is unable to address va-
api acceleration.

eric@athena:~$ vainfo
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva error: dlopen of /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so 
failed: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so: undefined symbol: 
amdgpu_cs_syncobj_import_sync_file
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

While open GL software like the unigine heaven benchmark runs very well.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,grid,imgpng,mousepoll,move,place,regex,resize,session,unitymtgrabhandles,wall,wobbly,animation,expo,ezoom,fade,scale,unityshell,workarounds]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Mar  9 12:16:28 2018
DistUpgraded: 2018-03-09 11:15:52,669 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: amdgpu, 17.50-511655, 4.13.0-36-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
   Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 470/480/570/580] 
(Nitro+ Radeon RX 580 4GB) [1da2:e366]
InstallationDate: Installed on 2018-01-04 (63 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=9782f23b-461f-4cf0-b7d4-9b4e2739964c ro iommu=soft quiet splash 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-03-09 (0 days ago)
dmi.bios.date: 10/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2g
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 970A-UD3P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2g:bd10/07/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Jan 11 18:02:23 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: amdgpu

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


** Tags: amd64 apport-bug bionic reproducible single-occurrence 
third-party-packages ubuntu wayland-session

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

Title:
  vaapi not working

Status in xorg package in Ubuntu:
  New

Bug description:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

  04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7)
Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 
470/480/570/580] (Nitro+ Radeon RX 580 4GB) [1da2:e366]

  The graphics run by the amdgpu (not -pro) and is unable to address va-
 

[Touch-packages] [Bug 532522] Re: Poor metaphor for a "wired network" icon (two arrows pointing up and down)

[Daniel van Vugt]

It appears this is now fixed in Ubuntu 18.04 (using the Gnome icons)

** Changed in: ubuntu-themes (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Poor metaphor for a "wired network" icon (two arrows pointing up and
  down)

Status in Ayatana Design:
  New
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  The icon used to show a wired (ethernet) network in network-manager-
  applet shows two arrows pointing up and down. This icon is typically
  associated to "sync" action on various other places and operating
  systems.

  In user testing of Ubuntu on 2010-12-15, participants identified the
  icon as "flipping between sessions" or "scroll up scroll down."

  Similarly in March 2012, Joe Pirillo: "The up and down is probably
  related to the volume, coz it's right next to the volume."
  

  A more appropriate icon could be something like the ones suggested at
  recent GNOME UX Hackfest, see this blog post
  http://jimmac.musichall.cz/log/?p=946 and/or this image
  http://jimmac.musichall.cz/images/blog/gnome-stencils.png

  See also bug 461427, about the icon showing even when it isn't useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/532522/+subscriptions

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

[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

[mauro]

I tried to remove but if I do also this packeges will e removed

- lubuntu-core
- lubuntu-desktop

So I did apt-get install --reinstal xserver-xorg-video-intel but nothing
has changed.

If I plug in the VGA and open a window I can see that the system see the
monitor anch I can set via the 'monitor setting' what to show where but
the PC input of the TV doesn't highlight and can't connect/show remotely

Please advise if we need to open a new bug with this chipset rather than
continue here.

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1725928] Re: package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files '/lib/udev/hwdb.d/20-sane.hwdb'

[dino99]

** Description changed:

  
  From #3 comment below, to get a workaround, try:
  
+ sudo apt-get -o Dpkg::Options::="--force-overwrite" install --reinstall
+ libsane1:i386 (or your real package name)
  
- sudo apt-get -o Dpkg::Options::="--force-overwrite" install --reinstall 
libsane1:i386 (or your real package name)
+ ***
+ Has been fixed with:
  
+ sane-backends (1.0.27-1~experimental3ubuntu2) bionic; urgency=medium
+ 
+   * debian/rules: Drop timestamps from conflicting multiarch:same files
+ hwdb.d/20-sane.hwdb and rules.d/60-libsane1.rules (closes: #880391)
+ 
+  -- Adam Conrad  Sat, 03 Feb 2018 14:26:39 -0700
  ***
  
  apport error this morning.
  
  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 22 09:37:46 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-edJWJn/5-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb 
(--unpack):
    trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-10-08 (378 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)

** Changed in: sane-backends (Ubuntu)
 Assignee: otec (otecasynove) => (unassigned)

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages
  with differing files  '/lib/udev/hwdb.d/20-sane.hwdb'

Status in sane-backends package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in sane-backends package in Debian:
  New

Bug description:
  
  From #3 comment below, to get a workaround, try:

  sudo apt-get -o Dpkg::Options::="--force-overwrite" install
  --reinstall libsane1:i386 (or your real package name)

  ***
  Has been fixed with:

  sane-backends (1.0.27-1~experimental3ubuntu2) bionic; urgency=medium

* debian/rules: Drop timestamps from conflicting multiarch:same files
  hwdb.d/20-sane.hwdb and rules.d/60-libsane1.rules (closes: #880391)

   -- Adam Conrad  Sat, 03 Feb 2018 14:26:39 -0700
  ***

  apport error this morning.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 22 09:37:46 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-edJWJn/5-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb 
(--unpack):
    trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-10-08 (378 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which 

[Touch-packages] [Bug 537268] Re: Panel icon for "no network" looks like wireless (even when the machine lacks wireless)

[Daniel van Vugt]

The icons have changed since switching to Gnome. Can we therefore
declare this fixed?

** Changed in: ubuntu-themes (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Panel icon for "no network" looks like wireless (even when the machine
  lacks wireless)

Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: ubuntu-mono

  It's in the title : no network icon in panel shouldn't be a wireless
  one when I haven't any wireless networking card.

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912
  CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e
  Date: Thu Mar 11 12:06:46 2010
  DistroRelease: Ubuntu 10.04
  EcryptfsInUse: Yes
  NonfreeKernelModules: nvidia
  Package: ubuntu-mono 0.0.7
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fr_FR:fr:en_GB:en
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SourcePackage: ubuntu-mono
  Uname: Linux 2.6.32-16-generic i686

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

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

[Touch-packages] [Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568

[hakon]

Sound seems to be working again now after upgrading to Ubuntu 17.10!!
Thanks a lot!

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

Title:
  Sound card not recognized on  Dell Vostro 5568

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just reinstalled a fresh Ubuntu 16.10 on my Dell Vostro 5568 laptop.

  The audio controller on the laptop is a Realtek ALC3246 with Waves
  MaxxAudio Pro. The external interface connector is a microphone
  in/stereo headphones/external speakers connector.

  When I select "System Settings->Sound" the output device in the dialog
  window shows as "Dummy Output" and when I press the "Test Sound"
  button no sound is heard from either front left or front right speaker
  ( I have ensured sound is not muted ).

  Note: Before reinstalling, I asked a question on askubuntu,com:

  http://askubuntu.com/q/841759/156688

  So reinstallation of Ubuntu 16.10 did not help on my sound problem.

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

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

[Touch-packages] [Bug 1689862] Re: gnome-shell crashed with SIGSEGV in _int_free() from __GI___libc_free() from g_free() from gweather_location_unref() from gweather_info_set_location_internal()

[Daniel van Vugt]

Fix released (zero crash reports after 17.04)

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Released

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

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

Title:
  gnome-shell crashed with SIGSEGV in _int_free() from
  __GI___libc_free() from g_free() from gweather_location_unref() from
  gweather_info_set_location_internal()

Status in libgweather:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released

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

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

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

[Touch-packages] [Bug 1714308] Re: dns does not work in initramfs after configure_networking

[Scott Moser]

** Merge proposal unlinked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203

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

Title:
  dns does not work in initramfs after configure_networking

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Zesty:
  Confirmed

Bug description:
  in an initramfs built with mkinitramfs-tools that has been booted with
  'ip=' and a dhcp server responded in the dhcp request, you would
  expect dns to work.

  currently it does not.
  at least part of the issue is that libnss_dns.so is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:43:05 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714028: artful network vmtests fail now that ifdown command is removed

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

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

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

[Scott Moser]

** Merge proposal linked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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

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

[Touch-packages] [Bug 1714308] Re: dns does not work in initramfs after configure_networking

[Scott Moser]

** Merge proposal linked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203

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

Title:
  dns does not work in initramfs after configure_networking

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Zesty:
  Confirmed

Bug description:
  in an initramfs built with mkinitramfs-tools that has been booted with
  'ip=' and a dhcp server responded in the dhcp request, you would
  expect dns to work.

  currently it does not.
  at least part of the issue is that libnss_dns.so is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:43:05 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714028: artful network vmtests fail now that ifdown command is removed

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Launchpad Bug Tracker]

** Merge proposal unlinked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Released
Status in klibc package in Debian:
  Confirmed

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU

  ifupdown:
  bug 1629972: networking.service takes down lo on stop

  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)

  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD

  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  [Stable Fix]

  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.

  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

  [Tests for verification]

  Whoever checks the last one off, please mark verification done.

  MAAS test cases:
   X / Y
  [+]/[+] MAAS on IPv6-only network
  [+]/[+] MAAS on IPv4-only network
  [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)

  Non-MAAS test cases:
   X / Y
  [+]/[+] ip="" and ip6 not present
  [+]/[+] ip=:eth0:dhcp and ip6 not present
  [+]/[+] d-i install with iSCSI remote root should complete normally
  [+]/[+] Validate normal boot without remote root
  [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)52-54-00-53-5d-24
  [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

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

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

[Touch-packages] [Bug 1714308] Re: dns does not work in initramfs after configure_networking

[Launchpad Bug Tracker]

** Merge proposal unlinked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203

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

Title:
  dns does not work in initramfs after configure_networking

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Zesty:
  Confirmed

Bug description:
  in an initramfs built with mkinitramfs-tools that has been booted with
  'ip=' and a dhcp server responded in the dhcp request, you would
  expect dns to work.

  currently it does not.
  at least part of the issue is that libnss_dns.so is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:43:05 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714028: artful network vmtests fail now that ifdown command is removed

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Released
Status in klibc package in Debian:
  Confirmed

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU

  ifupdown:
  bug 1629972: networking.service takes down lo on stop

  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)

  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD

  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  [Stable Fix]

  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.

  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

  [Tests for verification]

  Whoever checks the last one off, please mark verification done.

  MAAS test cases:
   X / Y
  [+]/[+] MAAS on IPv6-only network
  [+]/[+] MAAS on IPv4-only network
  [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)

  Non-MAAS test cases:
   X / Y
  [+]/[+] ip="" and ip6 not present
  [+]/[+] ip=:eth0:dhcp and ip6 not present
  [+]/[+] d-i install with iSCSI remote root should complete normally
  [+]/[+] Validate normal boot without remote root
  [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)52-54-00-53-5d-24
  [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)

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

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

[Touch-packages] [Bug 1714308] Re: dns does not work in initramfs after configure_networking

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203

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

Title:
  dns does not work in initramfs after configure_networking

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Zesty:
  Confirmed

Bug description:
  in an initramfs built with mkinitramfs-tools that has been booted with
  'ip=' and a dhcp server responded in the dhcp request, you would
  expect dns to work.

  currently it does not.
  at least part of the issue is that libnss_dns.so is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: User Name 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Aug 31 16:43:05 2017
  Ec2AMI: ami-00e4
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714028: artful network vmtests fail now that ifdown command is removed

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

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

[Touch-packages] [Bug 1754576] [NEW] Cannot adjust color profile of the second (external) monitor

[Benoe]

Public bug reported:

In gnome settings at color management when I try to apply a profile to
my external monitor, the internal monitor's colors are changing. No
change on the external. A week ago it was working correctly.

I can also see some flickering on the internal monitor, when night mode
is on, and the color scheme is changing

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: colord 1.3.3-2build1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  9 08:22:01 2018
InstallationDate: Installed on 2018-02-17 (19 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
SourcePackage: colord
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Cannot adjust color profile of the second (external) monitor

Status in colord package in Ubuntu:
  New

Bug description:
  In gnome settings at color management when I try to apply a profile to
  my external monitor, the internal monitor's colors are changing. No
  change on the external. A week ago it was working correctly.

  I can also see some flickering on the internal monitor, when night
  mode is on, and the color scheme is changing

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: colord 1.3.3-2build1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 08:22:01 2018
  InstallationDate: Installed on 2018-02-17 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: colord
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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