[Touch-packages] [Bug 1947099] [NEW] ipconfig does not honour user-requested timeouts in some cases

2021-10-13 Thread Khaled El Mously
Public bug reported:

In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.

in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again later"
at time equal now + 10 seconds by setting

s->expire = now + 10;


This can happen at any time during the main event loop, which can end up 
extending the user-specified timeout if "now + 10" is greater than "start_time 
+ user-specified-timeout".

I believe a patch like the following is needed to avoid this problem:

--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)

if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+   /* Compensate for already-lost time */
+   gettimeofday(, NULL);
+   if (now.tv_sec + timeout > start + loop_timeout) {
+   timeout = loop_timeout - (now.tv_sec - start);
+   printf("Lowered timeout to match user request = 
(%d s) \n", timeout);
+   }
}

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

** Affects: klibc (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: klibc (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  ipconfig does not honour user-requested timeouts in some cases

Status in klibc package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New

Bug description:
  In some cases, ipconfig can take longer than the user-specified
  timeouts, causing unexpected delays.

  in main.c, in function loop(), the process can go into
  process_timeout_event() (or process_receive_event() ) and if it
  encounters an error situation, will set an attempt to "try again
  later" at time equal now + 10 seconds by setting

  s->expire = now + 10;

  
  This can happen at any time during the main event loop, which can end up 
extending the user-specified timeout if "now + 10" is greater than "start_time 
+ user-specified-timeout".

  I believe a patch like the following is needed to avoid this problem:

  --- a/usr/kinit/ipconfig/main.c
  +++ b/usr/kinit/ipconfig/main.c
  @@ -437,6 +437,13 @@ static int loop(void)

  if (timeout > s->expire - now.tv_sec)
  timeout = s->expire - now.tv_sec;
  +
  +   /* Compensate for already-lost time */
  +   gettimeofday(, NULL);
  +   if (now.tv_sec + timeout > start + loop_timeout) {
  +   timeout = loop_timeout - (now.tv_sec - start);
  +   printf("Lowered timeout to match user request 
= (%d s) \n", timeout);
  +   }
  }

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


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


[Touch-packages] [Bug 537133] Re: mountall issues with NFS root filesystem

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: nfs-utils (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  mountall issues with NFS root filesystem

Status in mountall package in Ubuntu:
  Fix Released
Status in nfs-utils package in Ubuntu:
  Fix Released
Status in portmap package in Ubuntu:
  Fix Released
Status in mountall source package in Lucid:
  Won't Fix
Status in nfs-utils source package in Lucid:
  Won't Fix
Status in portmap source package in Lucid:
  Fix Released
Status in mountall source package in Maverick:
  Won't Fix
Status in nfs-utils source package in Maverick:
  Won't Fix
Status in portmap source package in Maverick:
  Fix Released
Status in mountall source package in Precise:
  Fix Released
Status in nfs-utils source package in Precise:
  Won't Fix
Status in portmap source package in Precise:
  Fix Released
Status in mountall source package in Quantal:
  Fix Released
Status in nfs-utils source package in Quantal:
  Won't Fix
Status in portmap source package in Quantal:
  Fix Released
Status in mountall source package in Raring:
  Fix Released
Status in nfs-utils source package in Raring:
  Won't Fix
Status in portmap source package in Raring:
  Fix Released

Bug description:
  Binary package hint: mountall

  I think I've found two bugs in mountall-2.7 related to nfsroots. This
  report describes both, since working around one exposes the other.

  The first bug is a dependency issue, circular and otherwise. Unless
  the nfsroot is mounted with "nolock", NFS locking depends on
  rpc.statd, which depends on portmap, which depends on the "local-
  filesystems" event (in /etc/init/portmap.conf).  mountall will never
  provide this event because it treats the rootfs as "local" even if
  it's networked, for the sake of daemons that need to wait for the
  rootfs to be remounted rw.

  The problem is that portmap.conf needs access to /etc (ro), /var/run
  (rw) and /lib/init/rw (rw). A dependency on "local-filesystems"
  essentially means / and /tmp. Changing the dependency to "virtual-
  filesystems" would be more correct, but I'm not entirely certain that
  remounting / should depend on any general *-filesystems events.

  It gets messier in statd.conf, which doesn't call out any filesystem
  dependencies, yet requires portmap to be running. It tries to directly
  "start portmap" which fails because the mentioned filesystems aren't
  writable yet. Portmap and statd will start successfully later, but not
  in time to satisfy the rootfs dependency.

  The second bug is when one tries to work around the above problems by
  specifying "nolock" in /etc/fstab for the nfsroot. In this case we
  land in mountall.c at the bottom of run_mount() where the is_remote()
  test causes spawn() to be called with wait=FALSE.  spawn() then calls
  nih_child_add_watch() which is supposed to eventually call back to
  spawn_child_handler(), but it appears to fail to connect:

   spawn: mount -n -a -t nfs -o remount,nolock 16.1.1.2:/export/romano /
   spawn: mount / [272]
   spawn: calling nih_child_add_watch for /
   init: job_process_handler: Ignored event 1 (0) for process 272

  The third line is debugging I added. If spawn_child_handler() had been
  called, we would have seen an additional line:

   mount / [272] exited normally

  I didn't dig into libnih to figure out why this isn't working. Rather
  I changed the test on which wait=FALSE depends, since it seems like
  mountall should be waiting for the rootfs. This works, see attached
  patch, though it only fixes the non-ideal "nolock" case.

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Mar 11 01:18:06 2010
  DistroRelease: Ubuntu 10.04
  Package: mountall 2.7
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
  SourcePackage: mountall
  Uname: Linux 2.6.32-15-generic x86_64

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


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


[Touch-packages] [Bug 998715] Re: Please transition gcr to multi-arch

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: gnome-keyring (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  Please transition gcr to multi-arch

Status in gcr package in Ubuntu:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Invalid
Status in gcr source package in Precise:
  Won't Fix
Status in gnome-keyring source package in Precise:
  Won't Fix
Status in gcr source package in Quantal:
  Won't Fix
Status in gnome-keyring source package in Quantal:
  Invalid
Status in gcr source package in Raring:
  Won't Fix
Status in gnome-keyring source package in Raring:
  Invalid
Status in gcr source package in Saucy:
  Fix Released
Status in gnome-keyring source package in Saucy:
  Invalid
Status in gcr package in Debian:
  Fix Released

Bug description:
  [SRU] The debiffs attached to comments #4 and #5 backport the multi-
  arch changes from Saucy to Raring and Quantal respectively.  See LP:
  #859600 for the Precise version.

  [IMPACT]
  libgcr-3-1:i386 and libgck-1-0:i386 are not installable on an x86_64 system.

  [Test Case]
  Run 'sudo apt-get install libgcr-3-1:i386' and verify that the files are 
installed in the correct location:
  $ ls -l /usr/lib/i386-linux-gnu/libgcr*
  $ ls -l /usr/lib/i386-linux-gnu/libgck*

  [Regression Potential]
  Low, changes only affect packaging.

  
  libgcr-3-1:i386 depends on libgcr-3-common:i386, but this package doesn't 
exists, because libgcr-3-common is architecture independent.
  ===
  $ LANG= sudo apt-get install libgcr-3-1:i386
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgcr-3-1:i386 : Depends: libgcr-3-common:i386 but it is not installable
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libgcr-3-1:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Sun May 13 14:05:01 2012
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=ru_RU.utf8
   LANGUAGE=ru_RU:ru:en_GB:en
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to precise on 2012-05-04 (9 days ago)

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


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


[Touch-packages] [Bug 998715] Re: Please transition gcr to multi-arch

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: gcr (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  Please transition gcr to multi-arch

Status in gcr package in Ubuntu:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Invalid
Status in gcr source package in Precise:
  Won't Fix
Status in gnome-keyring source package in Precise:
  Won't Fix
Status in gcr source package in Quantal:
  Won't Fix
Status in gnome-keyring source package in Quantal:
  Invalid
Status in gcr source package in Raring:
  Won't Fix
Status in gnome-keyring source package in Raring:
  Invalid
Status in gcr source package in Saucy:
  Fix Released
Status in gnome-keyring source package in Saucy:
  Invalid
Status in gcr package in Debian:
  Fix Released

Bug description:
  [SRU] The debiffs attached to comments #4 and #5 backport the multi-
  arch changes from Saucy to Raring and Quantal respectively.  See LP:
  #859600 for the Precise version.

  [IMPACT]
  libgcr-3-1:i386 and libgck-1-0:i386 are not installable on an x86_64 system.

  [Test Case]
  Run 'sudo apt-get install libgcr-3-1:i386' and verify that the files are 
installed in the correct location:
  $ ls -l /usr/lib/i386-linux-gnu/libgcr*
  $ ls -l /usr/lib/i386-linux-gnu/libgck*

  [Regression Potential]
  Low, changes only affect packaging.

  
  libgcr-3-1:i386 depends on libgcr-3-common:i386, but this package doesn't 
exists, because libgcr-3-common is architecture independent.
  ===
  $ LANG= sudo apt-get install libgcr-3-1:i386
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgcr-3-1:i386 : Depends: libgcr-3-common:i386 but it is not installable
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libgcr-3-1:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Sun May 13 14:05:01 2012
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=ru_RU.utf8
   LANGUAGE=ru_RU:ru:en_GB:en
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to precise on 2012-05-04 (9 days ago)

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


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


[Touch-packages] [Bug 992439] Re: libicu48 is not multiarch enabled

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: icu (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  libicu48 is not multiarch enabled

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Precise:
  Won't Fix

Bug description:
  Hello,

  if I try to install the libicu48:i386 package on my amd64 precise
  installation, apt wants to remove a huge list of essential core
  packages, including Unity, Nautilus, LibreOffice, Software-Center,
  etc. . For the exact list of packages to be removed see the attached
  output of apt-get.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libicu48:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  Date: Tue May  1 09:44:45 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120421)
  SourcePackage: icu
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1069570] Re: 1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases databases

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: isc-dhcp (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases
  databases

Status in juju-core:
  Invalid
Status in MAAS:
  Fix Released
Status in MAAS 1.3 series:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in maas package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Precise:
  Won't Fix
Status in maas source package in Precise:
  Fix Released
Status in isc-dhcp source package in Raring:
  Fix Released
Status in maas source package in Raring:
  Won't Fix
Status in isc-dhcp source package in Saucy:
  Fix Released
Status in maas source package in Saucy:
  Fix Released

Bug description:
  [Impact] 
   During my new tests, I tried to create two nodes simultaneously (both via 
DHCP + PXE, not by clicking "+Add node") and I hit this problem:

   Same MAC Address, two different IPs:

  # The format of this file is documented in the dhcpd.leases(5) manual page.
  # This lease file was written by isc-dhcp-4.2.4

  server-duid "\000\001\000\001\030\023\243\007RT\000\360\236\231";

  lease 192.168.50.1 {
    starts 5 2012/10/19 06:31:21;
    ends 5 2012/10/19 18:31:21;
    cltt 5 2012/10/19 06:31:21;
    binding state active;
    next binding state free;
    rewind binding state free;
    hardware ethernet 52:54:00:cd:6b:a2;
    uid "\001RT\000\315k\242";
  }
  lease 192.168.50.2 {
    starts 5 2012/10/19 06:31:43;
    ends 5 2012/10/19 18:31:43;
    cltt 5 2012/10/19 06:31:43;
    binding state active;
    next binding state free;
    rewind binding state free;
    hardware ethernet 52:54:00:cd:6b:a2;
    client-hostname "maas-enlist";
  }
  lease 192.168.50.2 {
    starts 5 2012/10/19 06:31:43;
    ends 5 2012/10/19 18:31:43;
    cltt 5 2012/10/19 06:31:43;
    binding state active;
    next binding state free;
    rewind binding state free;
    hardware ethernet 52:54:00:cd:6b:a2;
    client-hostname "maas-enlist";
  }
  host 192.168.50.1 {
    dynamic;
    hardware ethernet 52:54:00:cd:6b:a2;
    fixed-address 192.168.50.1;
  }
  lease 192.168.50.1 {
    starts 5 2012/10/19 06:31:21;
    ends 5 2012/10/19 06:34:48;
    tstp 5 2012/10/19 06:34:48;
    cltt 5 2012/10/19 06:31:21;
    binding state free;
    hardware ethernet 52:54:00:cd:6b:a2;
    uid "\001RT\000\315k\242";
  }

   1- DHCP gives address 192.168.50.1 to my machine on its first boot;

   2- After some time, I think that after some "reboots / elist /
  don'know for sure or even after commissioning" it; the IP have changed
  to 192.168.50.2 and got registered at DNS (192-168-50-2.test.com) that
  way;

   3- In the end of the day, after allocate it to root and start using
  it (the nodes), the DHCP gives again the IP 192.168.50.1 to my node,
  but DNS still remains with 192.158.50.2...

   ---

   My second node, first starts with 192.168.50.3, got registered with
  192.168.50.4 at DNS (and at MaaS Web GUI) but the DHCP finish with
  192.168.50.3...

  [Test Case]
  In a virtual environment: 
  - Add 2 nodes 
  - PXE boot the instances
  - verify dhcp leases have 1 mac address for 2 different IPs

  After applying latest debdiff alter the following:

 * modify /etc/maas/dhcpd.conf to include 'ignore-client-uids true'

  re-test by adding 2 additional nodes to verify the mac address is
  unique between both nodes.

  [Regression Potential]
  Low, as it adds another optional arguement to disable checking client-uids

  -- snip --

   I'll not try maas-dns again... Too many bugs...   =(

   I think that MaaS needs some kind of "glue" between DHCP and DNS to
  keep it in sync.

  Tks!
  Thiago

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+subscriptions


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


[Touch-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: bluez (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in blueman package in Ubuntu:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in blueman source package in Precise:
  Won't Fix
Status in bluez source package in Precise:
  Won't Fix
Status in gnome-bluetooth source package in Precise:
  Fix Released
Status in blueman source package in Quantal:
  Invalid
Status in bluez source package in Quantal:
  Won't Fix
Status in gnome-bluetooth source package in Quantal:
  Fix Released
Status in blueman source package in Raring:
  Invalid
Status in bluez source package in Raring:
  Won't Fix
Status in gnome-bluetooth source package in Raring:
  Won't Fix
Status in bluez package in Fedora:
  Won't Fix

Bug description:
  [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
  [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
session, watch it automatically re-pair.
  [Regression Potential] Little. The patched piece of XML is only relevant to 
hardware having the same ID.

  When you don't use the mouse for a long enough time, the mouse
  disconnects and won't reconnect. I have to go into bluetooth settings,
  remove it, and re-pair it.

  1)
  ~ % lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

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

  3)
  I expected the mouse to reconnect automatically, or at least after I try to 
reconnect manually through the bluetooth settings.

  4)
  I have to re-pair the mouse in order to use it again. Turning the mouse off 
and on doesn't work either.

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


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


[Touch-packages] [Bug 1187177] Re: iptables calls setsockopt(2) incorrectly, fails when it should not

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: iptables (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  iptables calls setsockopt(2) incorrectly, fails when it should not

Status in iptables package in Ubuntu:
  Fix Released
Status in iptables source package in Lucid:
  Won't Fix
Status in iptables source package in Precise:
  Won't Fix
Status in iptables source package in Quantal:
  Won't Fix
Status in iptables source package in Raring:
  Won't Fix
Status in iptables package in Debian:
  Fix Released

Bug description:
  Since time immemorial, iptables has called setsockopt() and treated any   

  -1 return value as fatal.  Any system call can return EAGAIN or   

  EINPROGRESS (depending on the origins of the API), and good coding

  practice requires checking for that and retrying or otherwise handling

  it.   



  In the case of iptables, if multiple processes are calling iptables   

  concurrently, then it is likely that one of them will fail.  I have seen  

  this with xen, as well as certain firewall configurations where the   

  firewall rules are added as triggered by interfaces being discovered and  

  configured.   



  The attached patch fixes the issue.   

  lamont

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


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


[Touch-packages] [Bug 1212337] Re: [Partial Solved] accounts-daemon crashed with SIGSEGV in dbus_connection_send()

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: accountsservice (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  [Partial Solved] accounts-daemon crashed with SIGSEGV in
  dbus_connection_send()

Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Precise:
  Won't Fix

Bug description:
  Hi. There appeared some problems with 'accountsservice' -- a D-Bus
  interface for user account query and manipulation, that honestly have
  occurred day-to-day.

  ### PROBLEM DESCRIPTION:
  
  A few weeks ago after login as a normal user, 'accountsservice' (used for 
querying and manipulating user account informations) crashed. On the beginning 
it was a random incident. After a few days, 'accountsservice' crashed each time 
after every user logs on. I think, that's all what I can write, to try to 
describe this issue, because everything seems to be okay -- no system freezing 
or slowdowns, no problems after packages update/upgrade etc.

  ### DETAILED INFORMATIONS:
  ==
  * ProblemType: Crash
  * Uname: Linux 3.2.0-51-generic-pae i686
  * Architecture: i386
  * DistroRelease: Ubuntu 12.04 (Xubuntu 12.04 variant)
  * Package: accountsservice 0.6.15-2ubuntu9.6
  * ApportVersion: 2.0.1-0ubuntu17.4
  * NonfreeKernelModules: nvidia
  * Segfault happened at: 0xb76bb7c3:   mov0x10(%eax),%eax
  * Executable Path (ProcCmdline): /usr/lib/accountsservice/accounts-daemon

  Also '/var/log/apport.log' file contain some informations about this
  issue. Everything is in a attached log file.

  ,-[ $ lsb_release -rd ]
  | Description:Ubuntu 12.04.3 LTS
  | Release:12.04
  `-

  ### WHAT HAVE HAD AN IMPACT ON THIS ISSUE?
  ==
  I have no ideas, why it started to happen. Only one thing, which I've done 
for a few weeks before problems with 'accountsservice' was 'conky-all' install. 
Nothing more, nothing less -- no serious administrative tasks were performed 
(except e.g. kernel or programs updates via APT utility or UpdateManager, but 
it seems to be obvious).

  ### APPENDIX:
  =
  I would like to notice, that this issue still occurs, after next point 
Xubuntu update -- from 12.04.2 to 12.04.3 version. So for now, kernel version 
is; 3.2.0-55-generic-pae. Anything related with this bug, when all of this 
started to happen, remains unchanged.
  One more, important, thing to mention is that - in my case - 
'accountsservices' crashed even after a fresh Xubuntu 12.04 install. For more 
info, please see comment #12.

  Best regards.

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


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


[Touch-packages] [Bug 1243473] Re: LD_AUDIT is broken on amd64

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

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

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

Title:
  LD_AUDIT is broken on amd64

Status in eglibc package in Ubuntu:
  Fix Released
Status in eglibc source package in Precise:
  Won't Fix
Status in eglibc source package in Quantal:
  Won't Fix

Bug description:
  [Impact]
  LD_AUDIT is an "auditing interface" for the dynamic linker (ld.so), which 
allows an audit library specified in that environment variable to register 
hooks for loading and unloading objects, resolving relocations, and calling 
functions across dynamic libraries. It is particularly useful as a debugging 
tool; the command "latrace" is based on this functionality. It is also useful 
for making certain runtime changes to how libraries or symbols are resolved, 
similar to LD_PRELOAD but more powerful. See rtld-audit(7) for details.

  In glibc before 2.17 (i.e., Precise and Quantal), on amd64, almost any
  use of LD_AUDIT on amd64 crashes with the following backtrace:

  [1538449.702152] python[13400]: segfault at 60 ip 7fdeaa97e8a3 sp 
7d50bb00 error 4 in ld-2.15.so[7fdeaa97+22000]
  (gdb) bt
  #0  _dl_profile_fixup (l=0x7fdeaab679d8, reloc_arg=3, 
retaddr=140594303358361, regs=0x7d50bbd0, framesizep=0x7d50bf28) at 
../elf/dl-runtime.c:177
  #1  0x7fdeaa9856e8 in _dl_runtime_profile () at 
../sysdeps/x86_64/dl-trampoline.h:49
  ...

  In particular, l->l_reloc_result is NULL, and ld.so proceeds to
  dereference it.

  That code has since been patched upstream with the following comment:
if (l->l_reloc_result == NULL)
  {
/* BZ #14843: ELF_DYNAMIC_RELOCATE is called before l_reloc_result
   is allocated.  We will get here if ELF_DYNAMIC_RELOCATE calls a
   resolver function to resolve an IRELATIVE relocation and that
   resolver calls a function that is not yet resolved (lazy).  For
   example, the resolver in x86-64 libm.so calls __get_cpu_features
   defined in libc.so.  Skip audit and resolve the external function
   in this case.  */

  The referenced upstream bug (which unfortunately doesn't mention that it's 
fixed) is
  http://sourceware.org/bugzilla/show_bug.cgi?id=14843
  The full upstream commit is
  
http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=2e64d2659d3edaebc792ac596a9863f1626e5c25
  and only adds that one if statement and a test case.

  [Test Case]
  Install the latrace package, and try to trace anything that links libm.so (as 
described above) or anything else using the same functionality. `python -c 1` 
is a good test. Note that it segfaults:

  salmon-of-wisdom:/tmp gthomas$ latrace python -c 1

  python finished - killed by signal 11

  The expected result is tracing output. Taken from an schroot with the
  fix applied:

  (precise-amd64)root@salmon-of-wisdom:/tmp# latrace python -c 1
  30242 _dl_get_tls_static_info [/lib64/ld-linux-x86-64.so.2]  
  30242 getrlimit [/lib/x86_64-linux-gnu/libc.so.6]  
  30242 __libc_dl_error_tsd [/lib/x86_64-linux-gnu/libc.so.6]  
  30242 __libc_pthread_init [/lib/x86_64-linux-gnu/libc.so.6]  
  ...

  You can also test this with a simple LD_AUDIT module:

  salmon-of-wisdom:/tmp gthomas$ cat audit.c
  unsigned int la_version(unsigned int version)
  {
  return version;
  }   
  salmon-of-wisdom:/tmp gthomas$ gcc -fPIC -shared -o audit.so audit.c
  salmon-of-wisdom:/tmp gthomas$ LD_AUDIT=/tmp/audit.so python -c 1
  Segmentation fault (core dumped)

  [Regression Potential]
  It seems highly unlikely to me that this patch introduces the possibility of 
regression: it checks for a NULL in a case where ld.so was previously not 
checking and instead dereferencing the NULL pointer, so we were already going 
to crash if we hit the code added by this patch.

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


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


[Touch-packages] [Bug 1199933] Re: apparmor parser in precise does not support block_suspend capability (needed for backported kernels)

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: apparmor (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  apparmor parser in precise does not support block_suspend capability
  (needed for backported kernels)

Status in apparmor package in Ubuntu:
  Fix Released
Status in cups package in Ubuntu:
  Confirmed
Status in apparmor source package in Precise:
  Won't Fix
Status in apparmor source package in Saucy:
  Fix Released

Bug description:
  When running an up-to-date precise system with a 
linux-image-generic-lts-raring HWE kernel (linux 3.8), 
  the precise verion of apparmor will deny all attempts of apparmored apps to 
call the block_suspend system call:

  For example: 
  type=AVC msg=audit(XX.XXX:X): apparmor="DENIED" 
operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=1040 comm="cupsd" 
pid=1040 comm="cupsd" capability=36  capname="block_suspend"

  But it is also impossible to add block_suspend to the apparmor profiles, 
because the AppArmor parser does not know about it:
Setting /usr/sbin/cupsd to enforce mode.
Warning from stdin (line 1): /sbin/apparmor_parser: cannot use or update 
cache, disable, or force-complain via stdin
AppArmor parser error, in stdin line 24: Invalid capability block_suspend.

  This seems to make it impossible to have apparmor  not deny block
  suspend when using an LTS HWE kernel.

  This seems to be related to bug #1052098.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apparmor 2.7.102-0ubuntu3.7
  ProcVersionSignature: Ubuntu 3.8.0-25.37~precise1-generic 3.8.13
  Uname: Linux 3.8.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Wed Jul 10 12:48:24 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  KernLog: Jul 10 12:34:08 gumdrop kernel: [580960.424225] SGI XFS with ACLs, 
security attributes, realtime, large block/inode numbers, no debug enabled
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-3.8.0-25-generic 
root=UUID=981723af-1da9-455d-b776-3a1e8885efde ro rootflags=subvol=@
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  audit.log: Error: [Errno 13] Permission denied: '/var/log/audit/audit.log'

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


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


[Touch-packages] [Bug 1221618] Re: Bluetooth doesn't work after S3/S4 or after turning bluetooth on/off several times by toggle key

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: linux (Ubuntu Precise)
   Status: Incomplete => Won't Fix

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

Title:
  Bluetooth doesn't work after S3/S4 or after turning bluetooth on/off
  several times by toggle key

Status in Bluez Utilities:
  New
Status in OEM Priority Project:
  Invalid
Status in OEM Priority Project precise series:
  Invalid
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Precise:
  Invalid
Status in linux source package in Precise:
  Won't Fix

Bug description:
  After S3/S4 or turning bluetooth on/off several times by toggle key,
  there are many error messages in dmesg. And sometime the bluetooth menu is 
incomplete.
  dmesg:
  [ 1117.356421] init: bluetooth main process (3848) terminated with status 1
  [ 1117.356506] init: bluetooth main process ended, respawning
  [ 1117.399989] init: bluetooth main process (3857) terminated with status 1
  [ 1117.400048] init: bluetooth main process ended, respawning

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


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


[Touch-packages] [Bug 508996] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up IPv6 alias

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: ifupdown (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  'SIOCSIFFLAGS: Cannot assign requested address' when setting up IPv6
  alias

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Precise:
  Won't Fix
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  Binary package hint: ifupdown

  This is very similar to Bug #123773, but is specific to IPv6 and
  should probably be tracked separately.

  I don't have an instance ready to retest on, but this apparently
  worked on Jaunty (9.04) and broke on Karmic (9.10).  I'm actually re-
  using the "/etc/network/interfaces" file that I used successfully
  under Jaunty before upgrading to Karmic.

  Per the IFCONFIG(8) man page, I'm attempting to define an IP alias in
  /etc/network/interfaces:

  auto eth0
  iface eth0 inet static
  address 192.168.1.1
  netmask 255.255.255.0

  auto eth0:0
  iface eth0:0 inet6 static
  address 2001:db8::1
  netmask 64

  (2001:db8::1 is only an example address.)

  Attempting to perform an "ifup eth0:0" results in:

  SIOCSIFFLAGS: Cannot assign requested address
  Failed to bring up eth0:0.

  Unlike Bug #123773, this is not coming from the wireless-tools or
  other event scripts, as disabling them does not change the result.

  The following command is a work-around, and works as a post-up command in 
/etc/network/interfaces:
  ip addr add 2001:db8::1/64 dev eth0

  Defining an IPv4 alias also works correctly using either the alias
  stanza or the "ip addr add" command.

  uname: Linux 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 
x86_64 GNU/Linux
  ifupdown package version is 0.6.8ubuntu21

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


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


[Touch-packages] [Bug 695759] Re: vgimportclone doesn't work

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: lvm2 (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  vgimportclone doesn't work

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Precise:
  Won't Fix

Bug description:
  Binary package hint: lvm2

  Ubuntu Version:
  Ubuntu 10.04.1 LTS (however this also effects 10.10 With latest updates as 
well)

  LVM2 version:
  lvm2:
Installed: 2.02.54-1ubuntu4.1
Candidate: 2.02.54-1ubuntu4.1
Version table:
   *** 2.02.54-1ubuntu4.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
  500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
  100 /var/lib/dpkg/status
   2.02.54-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages

  
  vgimportclone is suppose to import and rename a duplicated volume group on 
the specified PV device.  However, every volumegroup except for the specified 
PV is modified and you still end up with duplicate VG uuid's and names.

  I am using xen with the VM running in PV mode for my testing however
  anything that supports the ability to make a clone of a volume will
  work.

  1.) Create a new disk for the VM
  2.) Partition the disk: fdisk /dev/xvdb 
   type:  n  p  1t  8e  w 

  3.) Create a PV on the new partition: pvcreate /dev/xvdb1
  4.) Create a Volume Group: vgcreate myvol /dev/xvdb1
  5.) Create a Logical Volume on the volume group: lvcreate -L 9G myvol -n vol0
  6.) Format the new disk with ext3: mke2fs -j /dev/myvol/vol0
  7.) Detach the disk from the vm and copy the virtual disk file
  8.) Reattach the disk to the VM
  9.) Attach the copy of the virtual disk file to the VM as well

  At this point you should have two identical copies of the same volume and a 
pvscan should report that /dev/xvdc1 and /dev/xvdb1 have a duplicate PV:
  # pvscan 
  Found duplicate PV eUd4WtLf5v552pWUsT1Wi37gTRs9NSUS: using /dev/xvdc1 not 
/dev/xvdb1
PV /dev/xvdc1   VG myvol lvm2 [10.00 GiB / 1020.00 MiB free]
PV /dev/xvda5   VG localhost   lvm2 [39.53 GiB / 0free]
Total: 2 [49.53 GiB] / in use: 2 [49.53 GiB] / in no VG: 0 [0   ]

  10.) run vgimportclone which is suppose to rename and re-signature the VG and 
PV on the specified PV: vgimportclone /dev/xvdc1
  output from command is below:
WARNING: Activation disabled. No device-mapper interaction will be 
attempted.
Found duplicate PV eUd4WtLf5v552pWUsT1Wi37gTRs9NSUS: using /dev/xvdc1 not 
/dev/xvdb1
Volume group "myvol" successfully changed
Found duplicate PV eUd4WtLf5v552pWUsT1Wi37gTRs9NSUS: using /dev/xvdc1 not 
/dev/xvdb1
Volume group "myvol" successfully renamed to "myvol1"
  Volume Group /dev/xvdc1, exported, skipping.
WARNING: Activation disabled. No device-mapper interaction will be 
attempted.
Found duplicate PV eUd4WtLf5v552pWUsT1Wi37gTRs9NSUS: using /dev/xvdc1 not 
/dev/xvdb1
Volume group "localhost" successfully changed
Found duplicate PV eUd4WtLf5v552pWUsT1Wi37gTRs9NSUS: using /dev/xvdc1 not 
/dev/xvdb1
Volume group "localhost1" successfully renamed to "localhost1"
  Volume Group /dev/xvda5, exported, skipping.
Reading all physical volumes.  This may take a while...
Found duplicate PV eUd4WtLf5v552pWUsT1Wi37gTRs9NSUS: using /dev/xvdc1 not 
/dev/xvdb1
Found volume group "myvol1" using metadata type lvm2
Found volume group "localhost1" using metadata type lvm2

  Actual result:
  The original volume and cloned volume still have the same PV UUID and and 
while it did change the VG name it changed it on *both* VG's.  In addition it 
also renames the VG that the root filesystem  is on which results in a machine 
that is not longer bootable unless fixed. A pvscan after the vgimportclone will 
show:

Found duplicate PV eUd4WtLf5v552pWUsT1Wi37gTRs9NSUS: using /dev/xvdc1 not 
/dev/xvdb1
PV /dev/xvdc1   VG myvol1lvm2 [10.00 GiB / 1020.00 MiB free]
PV /dev/xvda5   VG localhost1   lvm2 [39.53 GiB / 0free]
Total: 2 [49.53 GiB] / in use: 2 [49.53 GiB] / in no VG: 0 [0   ]

  Expected Result:
  The cloned volume (/dev/xvdc1) has its uuid changed for both the PV and VG 
and the VG is renamed to myvol1.  No other Volume Groups are change and a 
pvscan shows:
PV /dev/xvdc1   VG myvol1 lvm2 [10.00 GiB / 1020.00 MiB free]
PV /dev/xvdb1   VG myvol  lvm2 [10.00 GiB / 1020.00 MiB free]
PV /dev/xvda2   VG localhost   lvm2 [39.50 GiB / 0free]
Total: 3 [59.49 GiB] / in use: 3 [59.49 GiB] / in no VG: 0 [0   ]

  In testing running this same procedure against a CentOS 5.5 and Fedora14 vm 
gives the expected results. Output from the commands ran against a fedora 14 VM:
  # pvscan
Found 

[Touch-packages] [Bug 452049] Re: Gnome Places contains filesystems mounted via bind

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: glib2.0 (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Gnome Places contains filesystems mounted via bind

Status in GLib:
  Fix Released
Status in Nautilus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Precise:
  Won't Fix

Bug description:
  Binary package hint: nautilus

  What happens:
  1. mount a folder a to point b with the -bind option in /etc/fstab, for 
example:
   /media/data  /home/username/MyDocuments none 
bind,user=username,group=username   0   0
  2. reboot and then open nautilus
  3. nautilus will show the new mount point in the places sidebar but it will 
give you an error if you click on the mount point:
  Unable to mount MyDocuments
  mount: according to mtab, /media/data is already mounted on 
/home/username/MyDocuments
  mount failed

  What should happen:
  1. nautilus should not show these binded folders since they are well 
accessible through the filesystem
  2. if the mounted folder (e.g. /mount/data) is a block device then it will 
appear in the places sidebar anyway and thus it is not necessary to show the 
mount point again
  3. if the mounted folder is a normal folder from an existing file system then 
its accessible both from the original location and the newly binded location, 
thus the is no need to show it in places again
  4. this is quite annoying

  Additional Information:
  This bug persists in Lucid

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Oct 15 12:04:11 2009
  DistroRelease: Ubuntu 10.04
  Package: nautilus 2.30

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


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


[Touch-packages] [Bug 984785] Re: .goutputstream files polluting $HOME

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: glib2.0 (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  .goutputstream files polluting $HOME

Status in GLib:
  Fix Released
Status in Light Display Manager:
  Fix Released
Status in X.Org X server:
  New
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Invalid
Status in glib2.0 source package in Precise:
  Won't Fix
Status in lightdm source package in Precise:
  Invalid

Bug description:
  .goutputstream files polluting $HOME.
  Which software or operation is creating these and why?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xauth 1:1.0.6-1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia & ati
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 18 13:29:31 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin"
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xauth
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1003856] Re: apparmor denies access to /usr/lib/jvm/java-7-openjdk-amd64/bin/java when using icedtea-7-plugin

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: apparmor (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  apparmor denies access to /usr/lib/jvm/java-7-openjdk-amd64/bin/java
  when using icedtea-7-plugin

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Precise:
  Won't Fix
Status in apparmor source package in Quantal:
  Fix Released

Bug description:
  1.
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  2.
  apparmor:
Installed: 2.7.102-0ubuntu3
Candidate: 2.7.102-0ubuntu3
Version table:
   *** 2.7.102-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  3. Expected result: working icedtea-7-plugin with apparmor and firefox.
  4. When using apparmor with firefox and icedtea-7-plugin access to 
/usr/lib/jvm/java-7-openjdk-amd64/bin/java is denied. Problem is in 
/etc/apparmor.d/abstractions/ubuntu-browsers.d/java:
  ...
/usr/lib/jvm/java-6-openjdk*/jre/lib/*/IcedTeaPlugin.so mr,
/usr/lib/jvm/java-6-openjdk/jre/bin/java cx -> browser_openjdk,
/usr/lib/jvm/java-6-openjdk-{amd64,armel,armhf,i386,powerpc}/jre/bin/java 
cx -> browser_openjdk,
  ...
  /usr/lib/jvm/java-6-openjdk*/jre/bin/java ix,
  /usr/lib/jvm/java-6-openjdk*/jre/lib/i386/client/classes.jsa m,
  ...
  There are hardcoded jvm versions. When changing them to java-7-openjdk* 
problem is fixed.

  Logs:
  May 24 12:27:21 ad2 kernel: [2321420.007034] type=1400 
audit(1337851641.949:5055): apparmor="DENIED" operation="exec" parent=1 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java" pid=29785 comm="firefox" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apparmor 2.7.102-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Thu May 24 12:28:17 2012
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=C
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=bd96e5bc-9915-40e7-b5bf-5e63590d3ea5 ro
  SourcePackage: apparmor
  UpgradeStatus: Upgraded to precise on 2012-04-26 (27 days ago)

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


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


[Touch-packages] [Bug 1056975] Re: libsepol fails to cross-build

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: libsepol (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  libsepol fails to cross-build

Status in libsepol package in Ubuntu:
  Fix Released
Status in libsepol source package in Precise:
  Won't Fix
Status in libsepol source package in Quantal:
  Fix Released
Status in libsepol package in Debian:
  Fix Released

Bug description:
  This package needs a minor fix to cross-build properly. It uses the
  BUILD gcc when crossbuilding, instead of the HOST cc.

  The minor patch attached fixes this by setting CC=$DEB_HOST_GNU_TYPE-
  gcc

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


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


[Touch-packages] [Bug 1074048] Re: When setting up a GRE tunnel through the 'tunnel' method, the mtu parameter is not respected

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: ifupdown (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  When setting up a GRE tunnel through the 'tunnel' method, the mtu
  parameter is not respected

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Precise:
  Won't Fix
Status in ifupdown source package in Quantal:
  Won't Fix

Bug description:
  When setting up the following gre tunnel, the mtu parameter is not
  set.

  auto gtun
  iface gtun inet tunnel
mode gre
address 172.19.6.1
dstaddr 172.19.6.2
netmask 255.255.255.255
endpoint xxx.xxx.xxx.xxx
local yyy.yyy.yyy.yyy
mtu 1396
ttl 255

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: ifupdown 0.7~beta2ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-23.36-virtual 3.2.14
  Uname: Linux 3.2.0-23-virtual x86_64
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  Date: Thu Nov  1 16:13:51 2012
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1061924] Re: Need Antenna quirks for some platforms

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: network-manager (Ubuntu Precise)
   Status: New => Won't Fix

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

Title:
  Need Antenna quirks for some platforms

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  New
Status in udev package in Ubuntu:
  Triaged
Status in network-manager source package in Precise:
  Won't Fix
Status in udev source package in Precise:
  Won't Fix
Status in network-manager source package in Quantal:
  Won't Fix
Status in udev source package in Quantal:
  Won't Fix

Bug description:
  It has recently come to our attention that some laptops, in particular
  the lenovo b470 machines, have only one antenna. Unfortunately, they
  have decided to attach the auxilary antenna in the factory and not the
  main antenna. Udev sounds like the right place to quirk for this.

  Presently we're using an upstart job, the text of which is :

  # LenovoBx70eAtherosAntenna.conf
  #
  # Lenovo B[45]70e systems with Atheros AR9285 wifi only have one
  # antenna, but the ath9k driver defaults to using two antennas (Main
  # for Tx, Aux for Rx).  This job reconfigures the driver to use the
  # main antenna for both Tx and Rx before networking starts.

  description "Fix antenna configuration for Atheros wifi on
  b470e/b570e"

  start on starting networking

  task

  script
  # only required for Lenovo B470e and B570e
  dmidecode --string system-version | grep --quiet --line-regex "Lenovo 
B[45]70e" || exit 0
  
  # only required for Atheros AR9285 devices
  lspci -n | grep --quiet --extended-regexp "^[0-9a-f:.]* 0280: 
168c:002b" || exit 0

  # configure the device to use antenna 1 (Main) for both tx and rx
iw phy0 set antenna 1 1 
  end script

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


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


[Touch-packages] [Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: mountall (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  The disk drive for /tmp is not ready yet or not present

Status in mountall package in Ubuntu:
  Won't Fix
Status in mountall source package in Precise:
  Won't Fix
Status in mountall source package in Quantal:
  Won't Fix
Status in mountall source package in Trusty:
  Fix Released

Bug description:
  I'm using Ubuntu 13.04 dev with mountall 2.46 and on booting I'm
  getting the message "The disk drive for /tmp is not ready yet or not
  present". But it seems that this message doesn't make any troubles.
  I'm able to use /tmp without any problems. Maybe something is trying
  to mount /tmp too early.

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


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


[Touch-packages] [Bug 1107949] Re: printed PDF document (via evince) misses characters/ligatures

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: cairo (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  printed PDF document (via evince) misses characters/ligatures

Status in cairo:
  Fix Released
Status in cairo package in Ubuntu:
  Fix Released
Status in cairo source package in Precise:
  Won't Fix

Bug description:
  The attached test.pdf is not printed correctly with evince. Some characters 
(ff-ligature, alpha) are missing.
  Simply using lpr test.pdf prints just fine.

  I think, it could be the bug reported (and fixed) here:
  https://bugs.freedesktop.org/show_bug.cgi?id=53040

  I am working with the latest packages from Ubuntu 12.04:
  evince 3.6.0-0ubuntu2
  libcairo2 1.12.2-1ubuntu2.2

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


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


[Touch-packages] [Bug 1091702] Re: upower fails to recognize hid devices with new kernels

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: upower (Ubuntu Precise)
   Status: In Progress => Won't Fix

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

Title:
  upower fails to recognize hid devices with new kernels

Status in upower package in Ubuntu:
  Fix Released
Status in upower source package in Precise:
  Won't Fix

Bug description:
  In newer kernels, hiddev* devices now have class "usbmisc", rather
  than "usb" (for reference see http://www.spinics.net/lists/linux-
  usb/msg62276.html ).

  Attached is a patch that fixes this without changing existing behavior
  for older kernels.  The patch commit message contains an example
  attribute-walk on 3.7.0

  SRU INFORMATION:
  Patch: 
http://cgit.freedesktop.org/upower/commit/?id=9f31068707fc79744961cea7258b0eb262effbf1,
 in raring
  Impact: We regularly backport newer kernels to LTS releases, and we do not 
want to cause regressions in power management, especially not if we switch some 
12.04.x point release to a newer kernel by default.
  Regression potential: None, it keeps recognizing the "usb" subsystem, and 
"usbmisc" does not yet exist in Precise final.
  Test case: This needs a device like an USB controlled UPS or a wireless 
mouse/keyboard which reports its battery charge. These should work as before 
with the updated upower, and continue to report their charge in the power 
indicator with newer kernels.

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


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


[Touch-packages] [Bug 1125408] Re: 12.04.2 minimal virtual install is oversized

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: ubuntu-meta (Ubuntu Precise)
   Status: New => Won't Fix

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

Title:
  12.04.2 minimal virtual install is oversized

Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntu-meta source package in Precise:
  Won't Fix

Bug description:
  150MB of kernel modules
  no 'linux-virtual'

  install size is OK.

  see http://testcases.qa.ubuntu.com/Install/ServerMinimalVirtualInstall
  for details on how to reproduce.

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


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


[Touch-packages] [Bug 1067522] Re: openssh-client / ssh does not set IP Type-of-service field

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: openssh (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  openssh-client / ssh does not set IP Type-of-service field

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Precise:
  Won't Fix
Status in openssh package in Debian:
  Fix Released

Bug description:
  The openssh-client bundled with Ubuntu 12.04 fails to set the IP Type of 
Service field to "minimize delay (0x10)" for interactive SSH sessions.   Just 
about any other flavor of Linux/UNIX does this without any trouble.  Even if I 
attempt to force the setting in /etc/ssh/sshd_config:
  IPQoS lowdelay
  The outgoing SSH packets do not have the bit set.

  See this example with tcpdump output:

  [steve.polyack@galvatron ~]$ sudo tcpdump -i eth0 -vvv - -n 'host 2.2.2.2 
&& dst port 22'
  tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 
bytes
  ^Z
  [1]+  Stopped sudo tcpdump -i eth0 -vvv - -n 'host 
2.2.2.2 && dst port 22'
  [steve.polyack@galvatron ~]$ bg
  [1]+ sudo tcpdump -i eth0 -vvv - -n 'host 2.2.2.2 && dst port 22' &
  [steve.polyack@galvatron ~]$ ssh 2.2.2.2
  2012-10-16 17:20:39.113321 IP (tos 0x0, ttl 64, id 58664, offset 0, flags 
[DF], proto TCP (6), length 60)
  1.1.1.1.36127 > 2.2.2.2.22: Flags [S], cksum 0x2dd5 (incorrect -> 
0x200d), seq 3930407303, win 14600, options [mss 1460,sackOK,TS val 1670554799 
ecr 0,nop,wscale 7], length 0
  2012-10-16 17:20:39.298676 IP (tos 0x0, ttl 64, id 58665, offset 0, flags 
[DF], proto TCP (6), length 52)
  1.1.1.1.36127 > 2.2.2.2.22: Flags [.], cksum 0x2dcd (incorrect -> 
0x5cd6), seq 3930407304, ack 1359170341, win 115, options [nop,nop,TS val 
1670554846 ecr 2310866035], length 0
  2012-10-16 17:20:39.329979 IP (tos 0x0, ttl 64, id 58666, offset 0, flags 
[DF], proto TCP (6), length 52)
  1.1.1.1.36127 > 2.2.2.2.22: Flags [.], cksum 0x2dcd (incorrect -> 
0x5c8c), seq 0, ack 40, win 115, options [nop,nop,TS val 1670554853 ecr 
2310866063], length 0
  2012-10-16 17:20:39.330082 IP (tos 0x0, ttl 64, id 58667, offset 0, flags 
[DF], proto TCP (6), length 91)
  1.1.1.1.36127 > 2.2.2.2.22: Flags [P.], cksum 0x2df4 (incorrect -> 
0x9e6b), seq 0:39, ack 40, win 115, options [nop,nop,TS val 1670554853 ecr 
2310866063], length 39
  2012-10-16 17:20:39.759001 IP (tos 0x0, ttl 64, id 58668, offset 0, flags 
[DF], proto TCP (6), length 1324)
  1.1.1.1.36127 > 2.2.2.2.22: Flags [P.], cksum 0x32c5 (incorrect -> 
0x916a), seq 39:1311, ack 776, win 126, options [nop,nop,TS val 1670554961 ecr 
2310866492], length 1272

  The problem persists even after login, once the SSH session is fully
  interactive:

  2012-10-16 17:20:49.626239 IP (tos 0x0, ttl 64, id 58694, offset 0, flags 
[DF], proto TCP (6), length 116)
  1.1.1.1.36127 > 2.2.2.2.22: Flags [P.], cksum 0x2e0d (incorrect -> 
0xb06e), seq 3479:3543, ack 5344, win 226, options [nop,nop,TS val 1670557427 
ecr 2310876270], length 64

  This causes problems in environements where QoS is used and IP ToS is
  obeyed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: openssh-client 1:5.9p1-5ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Tue Oct 16 17:14:19 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:5.9p1-5ubuntu1
  SSHClientVersion: OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
  SourcePackage: openssh
  UpgradeStatus: Upgraded to precise on 2012-07-06 (102 days ago)
  modified.conffile..etc.ssh.ssh.config: [modified]
  mtime.conffile..etc.ssh.ssh.config: 2012-10-05T09:52:10.902327

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


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


[Touch-packages] [Bug 1091473] Re: grep <2.11 is vulnerable to "Arbitrary command execution"

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: grep (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  grep <2.11 is vulnerable to "Arbitrary command execution"

Status in grep package in Ubuntu:
  Fix Released
Status in grep source package in Lucid:
  Won't Fix
Status in grep source package in Oneiric:
  Won't Fix
Status in grep source package in Precise:
  Won't Fix
Status in grep source package in Quantal:
  Fix Released
Status in grep source package in Raring:
  Fix Released
Status in grep source package in Hardy:
  Won't Fix

Bug description:
  grep <2.11 is vulnerable to command execution vulnerability, and it is
  not possible to patch unless you build the source directly from the
  git repo.

  ubuntu 12.04(And everything else, I would assume) uses version 2.10 of
  grep. it is not possible to upgrade without downloading the src and
  building it yourself.


  
  PoC:

  perl -e 'print "x"x(2**31)' | grep x > /dev/null

  This is the grep news form for this:

   * Noteworthy changes in release 2.11 (2012-03-02) [stable]

** Bug fixes

  grep no longer dumps core on lines whose lengths do not fit in 'int'.
  (e.g., lines longer than 2 GiB on a typical 64-bit host).
  Instead, grep either works as expected, or reports an error.
  An error can occur if not enough main memory is available, or if the
  GNU C library's regular expression functions cannot handle such long 
lines.
  [bug present since "the beginning"]


  Solution: Send out a grep update with atleast 2.11 grep from
  http://git.sv.gnu.org/cgit/grep.git


  Full PoC of actually "abusing" this vulnerablility(ls -la within grep)
  can be provided, if 100% needed.

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


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


[Touch-packages] [Bug 1085342] Re: Pulseaudio applications hang (Totem, GNOME Shell etc.)

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: eglibc (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  Pulseaudio applications hang (Totem, GNOME Shell etc.)

Status in GLibC:
  Fix Released
Status in eglibc package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid
Status in eglibc source package in Precise:
  Won't Fix
Status in totem source package in Precise:
  Invalid
Status in eglibc source package in Quantal:
  Won't Fix
Status in totem source package in Quantal:
  Invalid
Status in eglibc package in Debian:
  Fix Released

Bug description:
  At least so here.
  Best way to see would be to use totem for a while, window usually becomes 
unresponsive fairly soon.
  Possible Test case(s):
  Add a couple of music tracks to the playlist, switch from one to the other & 
back again with next & previous buttons. (may cause lockup

  Close Totem(Videos), re-open & add back the same tracks & or try them from 
the "Movie"
   menu dropdown.
  Usually here they won't  play & or be switchable, ect.

  Add a couple of tracks to playlist, click on track names a few times
  to start playback/switch tracks

  Doesn't seem to matter if totem is started normally (no app menu in
  ubuntu session), with the app menu (Exec=env UBUNTU_MENUPROXY=0 totem)
  or from the sound menu

  With the pulseaudio plugin removed & the gst alsa plugin installed
  totem behaves much better though on very rare occasion will become
  unresponsive.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: totem 3.6.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
  Uname: Linux 3.7.0-4-generic x86_64
  ApportVersion: 2.6.3-0ubuntu2
  Architecture: amd64
  Date: Sat Dec  1 01:49:22 2012
  InstallationDate: Installed on 2012-10-23 (38 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1083605] Re: env not changed in acc. with ~/.pam_environment if /home is on nfs

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: pam (Ubuntu Precise)
   Status: Incomplete => Won't Fix

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

Title:
  env not changed in acc. with ~/.pam_environment if /home is on nfs

Status in accountsservice package in Ubuntu:
  Fix Released
Status in pam package in Ubuntu:
  Incomplete
Status in accountsservice source package in Precise:
  Fix Released
Status in pam source package in Precise:
  Won't Fix
Status in accountsservice source package in Quantal:
  Won't Fix
Status in pam source package in Quantal:
  Won't Fix

Bug description:
  When using localization setup from the login screen, the choice
  doesn't work because of a permission error, if the user's home
  directory is mounted with nfs. The problem happens because this is
  done by root, usually not able to write over nfs shares. The problem
  disappears if home directories are exported with no_root_squash
  option. So, something is making access as root, instead as user.

  I'm using Precise.

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


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


[Touch-packages] [Bug 1083161] Re: evince cannot print some PDF files accurately

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: poppler (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  evince cannot print some PDF files accurately

Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Precise:
  Won't Fix

Bug description:
  [Outline]
  Evince cannot print some PDF files accurately.

  Evince 3.4.0
  Ubuntu 12.04 LTS Precise

  [How To Reproduce]
  Open the PDF file by selection of "File"--"Open". Then, see preview by
  selection of "File"--"Print", and clicking "Preview" button.

  [Actual Result]
  Double vertical lines are shown in the preview frame. The main frame shows
  accurate view.

  [Workaround]
  Adobe Reader can print the PDF file accurately.

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


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


[Touch-packages] [Bug 1102042] Re: Open and Save dialogs descends down into sub directory if the selected directory has one sub directory

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: gtk+3.0 (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Open and Save dialogs descends down into sub directory if the selected
  directory has one sub directory

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Won't Fix
Status in gtk+3.0 source package in Quantal:
  Won't Fix
Status in gtk+3.0 source package in Raring:
  Won't Fix

Bug description:
  When selecting a directory that has one sub-directory, the open dialog
  descends down into the sub-directory.

  1. Make this exact folder structure: ~/a-dir/b-dir/ (only one sub-directory 
in a-dir, a-dir can have files)
  2. Open the Open dialog and double-click on the a-dir in your Home folder and 
click Open

  I expect the a-dir to be selected, but b-dir is selected in stead. In
  the attached video you can see the a-dir being open, but the selection
  clearly uses b-dir instead.

  3. Reopen the Open dialog and double-click on the a-dir
  4. Type ./ in the Open dialog’s location field 

  The input in the edit field is automatically changed to
  ./a-dir/b-dir/. The only way I have found to actually select the a-dir
  is to press backspace once after completing step 4.

  
  Similar behavior can be seen in the simplified dialog (e.g. when selecting 
destination for newly opened torrent files in Transmission).

  
  Ubuntu 12.10. Programs affected gedit, transmission, gnome-screenshot, others.

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


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


[Touch-packages] [Bug 1160379] Re: 'Dead circumflex' in Unity keyboard combinations

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: gtk+3.0 (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
   'Dead circumflex' in Unity keyboard combinations

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Precise:
  Won't Fix

Bug description:
  [Impact]

   Unity keyboard shortcuts hint window lists  "Dead circumflex"  for
  "Switches window of current applications" under "Switching" , instead
  of "^" when using german keyboard. This is confusing .

  In English, this is properly mapped to "`" so this appears to have
  lost a translation somewhere. Might be better to map it to "^" in the
  language pack as the German layout has:

  
  - http://de.wikipedia.org/wiki/Zirkumflex
  - http://de.wikipedia.org/wiki/Datei:Laptop_Tastatur.jpg

  [Test Case]

   * Switching to german keyboard 
   * Hold Super key down, until unity shortcuts are seen

  [Regression Potential] 
   
   * I dont see any regression potential 

  [Other Info]
   
  Version affected: 12.04 LTS / unity 5.18.0-0ubuntu1.

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


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


[Touch-packages] [Bug 1258958] Re: apt-mark segfaults when holding an already held package

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: apt (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  apt-mark segfaults when holding an already held package

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Won't Fix

Bug description:
  I'm trying to hold back a package but apt-mark keeps segfaulting.

  # apt-mark hold wine1.7 wine1.7-dbg wine1.7-amd64
  wine1.7 was already set on hold.
  Segmentation fault (core dumped)

  dmesg:
  traps: apt-mark[505732] general protection ip:404d5f sp:7fff0f4a3330 error:0 
in apt-mark[40+a000]

  The hold does seem to be put in place for the first package, but any
  additional packages have to be held one-by-one due to the fault.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apt 0.8.16~exp12ubuntu10.16
  ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sun Dec  8 19:11:03 2013
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1157943] Re: apt-get update fails hash checks on https repositories when file size changes

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

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

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

Title:
  apt-get update fails hash checks on https repositories when file size
  changes

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Won't Fix

Bug description:
  apt uses its own strategy for sending Range: requests on https,
  instead of the libcurl handling. Here's is a scenario where it gets it
  wrong:

  1) apt downloads the file but doesn't put the file in place yet (perhaps it 
got interrupted or something)
  2) the file on the server gets replaced by a smaller file
  3) the next update run wants to download the file, sees a partial read, and 
asks for Range: (len(file)-1)-
  4) the server sees a Range: request for a byte-range past the end of (the 
current version of) the file, considers it invalid, and streams the entire 
file. (This is correct behavior.)
  5) apt assumes the response is the range it expected, and appends it to the 
local staging copy (minus one byte).

  Instead of rolling apt's own attempt to handle ranges in the https
  method, it should just use libcurl's. Attached is a patch which solves
  the problem.

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


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


[Touch-packages] [Bug 1179735] Re: EOG crash - Aborted (core dumped)

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: cairo (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  EOG crash - Aborted (core dumped)

Status in cairo:
  New
Status in cairo package in Ubuntu:
  Fix Released
Status in cairo source package in Precise:
  Won't Fix

Bug description:
  Many times I try to watch large jpg images, my eog crashes. I started
  it in terminal and it seems the exit message is "Aborted (core
  dumped)".

  The images are 5-6-7 MB and I am forced to see them in Shotwell
  because eog is impossible to use. I have no idea what the first line
  means, but it is always there when I start eog.

  eog DSC07456.JPG 
  eog: /build/buildd/cairo-1.12.14/src/cairo-mempool.c:160: get_buddy: 
Assertion `offset + (1 << bits) <= pool->num_blocks' failed.
  Aborted (core dumped)

  
  I run a fresh install of Ubuntu 13.04, all updates to date:
  uname -a
  Linux florin-Satellite-C650 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 
16:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: eog 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue May 14 03:25:52 2013
  InstallationDate: Installed on 2013-04-25 (18 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1166556] Re: CVE-2012-5127

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

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

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

Title:
  CVE-2012-5127

Status in libwebp package in Ubuntu:
  Fix Released
Status in libwebp source package in Oneiric:
  Won't Fix
Status in libwebp source package in Precise:
  Won't Fix
Status in libwebp source package in Quantal:
  Won't Fix
Status in libwebp package in Debian:
  Fix Released

Bug description:
  Integer overflow in Google Chrome before 23.0.1271.64 allows remote
  attackers to cause a denial of service (out-of-bounds read) or
  possibly have unspecified other impact via a crafted WebP image.

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


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


[Touch-packages] [Bug 1291661] Re: PAM misconfiguration for auditd results in audit trail loss

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: audit (Ubuntu Precise)
   Status: Incomplete => Won't Fix

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

Title:
  PAM misconfiguration for auditd results in audit trail loss

Status in audit package in Ubuntu:
  Fix Released
Status in audit source package in Precise:
  Won't Fix
Status in audit source package in Quantal:
  Won't Fix

Bug description:
  The auditd package included in Debian Wheezy and Ubuntu 12.04 LTS (and
  probably other Debian and Ubuntu releases as well) adds
  pam_loginuid.so to the /etc/pam.d/common-session and
  /etc/pam.d/common-session-noninteractive PAM sub-configuration files.
  These sub-configuration files are in turn included by reference in the
  /etc/pam.d/su and /etc/pam.d/sudo files.  This results in
  pam_loginuid.so being included when the user context is switched by
  running su or sudo.

  The man page for pam_loginuid, however, warns us not to do that, as
  this will cause the original user context to be lost in the audit logs
  (emphasis mine):

 The pam_loginuid module sets the loginuid process attribute for the 
process that was authenticated. This is necessary for applications to
 be correctly audited. This PAM module should only be used for entry 
point applications like: login, sshd, gdm, vsftpd, crond and atd. There
 are probably other entry point applications besides these. You should 
not use it for applications like sudo or su as that defeats the
 purpose by changing the loginuid to the account they just switched to.

  The fix, of course, is never to add pam_loginuid.so to any common PAM
  configuration file - or to exclude common-session and common-session-
  noninteractive from /etc/pam.d/su and /etc/pam.d/sudo, replacing it
  with the respective files' constituent lines, but without
  pam_loginuid.so.

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


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


[Touch-packages] [Bug 1192168] Re: zgrep does not correctly pass short options to grep

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: gzip (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  zgrep does not correctly pass short options to grep

Status in gzip package in Ubuntu:
  Fix Released
Status in gzip source package in Precise:
  Won't Fix

Bug description:
  zgrep --help / man zgrep say that “OPTIONs are the same as for
  'grep'.” and “All options specified are passed directly to grep.”,
  respectively. Testing shows that this does not work with the -h
  option:

  -h, --no-filename
Suppress  the  prefixing  of file names on output.  This is the 
default when there is only one file (or
only standard input) to search.

  cadams@platinum:~ $ zgrep -h 11689 /vol/wdl/web-logs/*201306*.gz | head
  
/vol/wdl/web-logs/log.esclf_S.20130531-20130601-20130531-99.99c-0.gz:1.2.3.4
 - - [31/May/2013:08:22:18 +] "GET 
/media/3570/service/dzi/1/22_files/10/1_0.jpg HTTP/1.1" 200 11689 "-" 
"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:21.0) Gecko/20100101 
Firefox/21.0" "-"

  cadams@platinum:~ $ zgrep --no-filename 11689 /vol/wdl/web-logs/*201306*.gz | 
head
  1.2.3.4 - - [31/May/2013:08:22:18 +] "GET 
/media/3570/service/dzi/1/22_files/10/1_0.jpg HTTP/1.1" 200 11689 "-" 
"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:21.0) Gecko/20100101 
Firefox/21.0" "-"

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gzip 1.4-1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-45.70-generic 3.2.44
  Uname: Linux 3.2.0-45-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Tue Jun 18 09:16:30 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gzip
  UpgradeStatus: Upgraded to precise on 2012-11-23 (206 days ago)

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


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


[Touch-packages] [Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: sudo (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

Status in gnome-control-center:
  Confirmed
Status in sudo:
  Unknown
Status in policykit-desktop-privileges package in Ubuntu:
  Opinion
Status in sudo package in Ubuntu:
  Fix Released
Status in policykit-desktop-privileges source package in Precise:
  Opinion
Status in sudo source package in Precise:
  Won't Fix
Status in policykit-desktop-privileges source package in Trusty:
  Opinion
Status in sudo source package in Trusty:
  Triaged
Status in policykit-desktop-privileges source package in Utopic:
  Opinion
Status in sudo source package in Utopic:
  Won't Fix
Status in policykit-desktop-privileges source package in Vivid:
  Opinion
Status in sudo source package in Vivid:
  Won't Fix

Bug description:
  Under unity and cinnamon, it is possible for a user to turn off
  network-syncronized time and then change the time on the system. It is
  also possible to "cat /var/log/auth.log" and find the last time a user
  authenticated with sudo, along with which pty they used. If a user had
  used a terminal and successfully authenticated with sudo anytime in
  the past, and left the sudo file in "/var/lib/sudo//", a
  malicious user could walk up to an unlocked, logged in machine and
  gain sudo without knowing the password for the computer.

  To do this, a user would only need to launch a few terminals, figure
  out which pty they were on via "tty", find the an instance in
  /var/log/auth.log where sudo was used on that PTY, and set the clock
  to that time. Once this is done, they can run (for example) "sudo -s"
  and have a full access terminal.

  1) This has been observed on Ubuntu 13.04, and may work on other versions.
  2) This may have an effect on various window managers, but I confirmed it on 
Unity and Cinnamon
  3) I expected to have to authenticate when I changed the time and date, as I 
do on Gnome and KDE. I also expected to be denied permission to auth.log
  4) I was able to change the system time to whatever I wanted, and view 
auth.log. This was sufficient to access sudo without having to type my password.

  Note: This bug also affects any version of OS X, though the mechanism
  is different. Some versions don't require you to authenticate to
  change the time through the GUI, but some do. No version I've seen
  requires authentication to use the "systemsetup" command, which can
  alter the time from the command line. This may be an overall bug in
  sudo. Why can I bypass security by changing the time?!

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions


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


[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: udisks (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Fix udev rules to consider mmc rpmb partitions

Status in systemd package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Fix Released
Status in udisks package in Ubuntu:
  Triaged
Status in udev source package in Precise:
  Invalid
Status in udisks source package in Precise:
  Won't Fix
Status in systemd source package in Trusty:
  Fix Released
Status in udisks source package in Trusty:
  Triaged

Bug description:
  As per JEDEC 4.5 spec for eMMC devices,
  There is a new partitions as part of eMMC storage devices it self. (Further 
details please refer eMMC spec)

  *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
  with "mmcblkXrpmb" if device expresses it support of RPMB.

  Issues observed:

  issue 1:
  RPMB (Replay Protected Memory Block), A signed access to a Replay Protected 
Memory Block is provided. This function provides means for the system to store 
data to the specific memory area in an authenticated and replay protected 
manner.
  In that case, any read/write access to this partition device will report 
errors.

  issue 2:
  The by-path, line is wrongly mapping to platform-sdhci-tegra.1  -> 
mmcblk2rpmb were as
  it should be platform-sdhci-tegra.1  -> mmcblk2

  ls -l /dev/disk/by-path/
  total 0
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.1 -> 
../../mmcblk2rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.1-part1 -> 
../../mmcblk2p1
  lrwxrwxrwx 1 root root 13 Jan  3  2000 platform-sdhci-tegra.2 -> ../../mmcblk1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.2-part1 -> 
../../mmcblk1p1
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.3 -> 
../../mmcblk0rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part1 -> 
../../mmcblk0p1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part2 -> 
../../mmcblk0p2

  We have locally resolved in our platform in this file 60-persistent-
  storage.rules

  For issue 1: (with this rule)
  # skip block read for partitions of type rpmb
  KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end"

  For issue 2:
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb", 
SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb"
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb", 
SYMLINK+="disk/by-path/$env{ID_PATH}"

  Please consider this issues fix in next udev release .

  
  SRU INFO: This is mostly an issue with running backported kernels on 12.04 
and 14.04. There is no test case which would reproduce this on arbitrary 
hardware, but there are several reporters which are in a position to verify a 
proposed update.

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


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


[Touch-packages] [Bug 789859] Re: add-apt-repository adds invalid deb line if PPA contains a -

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: software-properties (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  add-apt-repository adds invalid deb line if PPA contains a -

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Precise:
  Won't Fix
Status in software-properties package in Debian:
  Invalid

Bug description:
  STEPS TO REPRODUCE:

  1. Add the PPA that contains a minus (-), with add-apt-repository:
  sudo add-apt-repository ppa:deluge-team/ppa
  2. Removing the PPA with ppa-purge:
  sudo ppa-purge ppa:deluge-team/ppa
  3. Again, add the PPA with add-apt-repository:
  sudo add-apt-repository ppa:deluge-team/ppa

  RESULT:
  The file '/etc/apt/sources.list.d/deluge-team-ppa-natty.list' now contains an 
invalid third line that says 'ain':

  rune@runescomp:~/Desktop$ cat 
/etc/apt/sources.list.d/deluge-team-ppa-natty.list
  deb http://ppa.launchpad.net/deluge-team/ppa/ubuntu natty main
  deb-src http://ppa.launchpad.net/deluge-team/ppa/ubuntu natty main
  ain

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: python-software-properties 0.80.9
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  Date: Sun May 29 14:20:37 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_DK:en
   LANG=en_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to natty on 2011-04-28 (30 days ago)

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


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


[Touch-packages] [Bug 760344] Re: gvfsd-http not closing tcp connections

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: libsoup2.4 (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  gvfsd-http not closing tcp connections

Status in libsoup:
  Fix Released
Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Precise:
  Won't Fix
Status in libsoup2.4 source package in Quantal:
  Won't Fix

Bug description:
  Binary package hint: gvfs

  How to recreate the bug...

  Run Rhythmbox, and enable the context pane + album art, and lyrics for
  good measure as well. Close the plugins windows that pops up, click on
  the new icon next to the Ubuntu One Music store and your new window
  should show up. The context pane is great for me, as I love to know
  what I can about the music I listen to. Rhythmbox, through gvfsd-http
  has now fetched all your cool text from last.fm about your artist, but
  it does not close the connection. These connections stay in close_wait
  till you kill the gvfsd-http process.

  this happens any time gvfsd-http is used. 
  netstat -a |grep tcp 

  tcp1  0 farva:47729 10x.terra.com.br:www
CLOSE_WAIT 
  tcp1  0 farva:35961 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:36086 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:42357 10x.terra.com.br:www
CLOSE_WAIT 
  tcp0  0 farva:47836 64.208.5.34:www 
ESTABLISHED
  tcp1  0 farva:42219 10x.terra.com.br:www
CLOSE_WAIT 
  tcp1  0 farva:46945 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:36126 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:59815 64.208.5.24:www 
CLOSE_WAIT 
  tcp0  0 farva:24800 wabothlp0282996.gs:6776 
ESTABLISHED
  tcp1  0 farva:36021 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp0  0 farva:37285 64.208.5.26:www 
ESTABLISHED
  tcp1  0 farva:33204 64.208.5.34:www 
CLOSE_WAIT 
  tcp1  0 farva:36007 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:53431 10x.terra.com.br:www
CLOSE_WAIT 
  tcp1  0 farva:35975 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:59027 5b.29.78ae.static.t:www 
CLOSE_WAIT 
  tcp1  0 farva:47637 10x.terra.com.br:www
CLOSE_WAIT 
  tcp1  0 farva:58324 207.114.197.87:www  
CLOSE_WAIT 
  tcp 5131  0 farva:42165 10x.terra.com.br:wwwCLOSE_WAIT

  gvfsd-htt 1795   josh   18r IPv4  30730  0t0
TCP farva:54963->10x.terra.com.br:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   19u IPv4  38478  0t0
TCP farva:39645->5b.29.78ae.static.theplanet.com:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   22u IPv4  23139  0t0
TCP farva:39074->5b.29.78ae.static.theplanet.com:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   24u IPv4  19766  0t0
TCP farva:42176->10x.terra.com.br:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   25u sock0,6  0t0  
19650 can't identify protocol
  gvfsd-htt 1795   josh   26u IPv4  19607  0t0
TCP farva:35892->5b.29.78ae.static.theplanet.com:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   27u IPv4  20164  0t0
TCP farva:42219->10x.terra.com.br:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   29u IPv4  38494  0t0
TCP farva:51584->10x.terra.com.br:www (CLOSE_WAIT)
  gvfsd-htt 1795   josh   30u sock0,6  0t0  
23195 can't identify protocol
  gvfsd-htt 1795   josh   31u sock0,6  0t0  
20157 can't identify protocol

  I posted a form message about this too 
  http://ubuntuforums.org/showthread.php?p=10646961#post10646961

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


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


[Touch-packages] [Bug 663352] Re: No way to stop/start networking without network management

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: ifupdown (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  No way to stop/start networking without network management

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Precise:
  Won't Fix

Bug description:
  Hi,

  Converted from question to bug, from
  https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/130070

  I want to remove all network management related packages and keep only
  a dhcp client (preferably pump). In plain Debian, I just need to
  properly config /etc/network/interfaces, then

   /etc/init.d/networking restart

  Vola, I'm done. But there is no way in Ubuntu to stop/start
  networking.

  /etc/init.d/networking restart
   * Reconfiguring network interfaces...
  
  Operation failed.
  ^
  ssh stop/waiting
  ssh start/running, process 19500
   [ OK 
]

  At some previous moments, it was working before, and I cannot bring
  the networking to a full stop then start again.

  Reposting comments from other bug reports, because I'm still getting
  the same results in Ubuntu 10.10 Maverick.

  === From https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/430883

  . . . There is no way to stop/start a [networking] service:

  root@quimerix:~# status networking
  networking stop/waiting
  root@quimerix:~# start networking
  networking stop/waiting
  root@quimerix:~# stop networking
  stop: Unknown instance:
  root@quimerix:~# stop networking
  stop: Unknown instance:
  root@quimerix:~# start networking
  networking stop/waiting

  ?

  And the old but working /etc/init.d says

  root@quimerix:~# /etc/init.d/networking start
  Rather than invoking init scripts through /etc/init.d, use the service(8)
  utility, e.g. service networking start

  Since the script you are attempting to invoke has been converted to an
  Upstart job, you may also use the start(8) utility, e.g. start networking
  networking stop/waiting

  So explain me how its supossed that i can restart a [networking]
  service?

  === From https://bugs.launchpad.net/ubuntu/+source/netbase/+bug/492160

  . . . I cannot start my network:

  $sudo service networking restart
  restart: Unknown instance

  $sudo service networking start
  networking stop/waiting

  $sudo /etc/init.d/networking restart

  (ifconfig does not show eth0 interface)

  $ping www.google.com
  ping: unknown host www.google.com

  $sudo ifup eth0
  (ping works)

  Bottom line: No configuration will automatically start the network--I
  have to manually run "ifup" to get the network to start.

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


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


[Touch-packages] [Bug 1083659] Re: modem-manager crashed with SIGSEGV in g_source_remove()

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: modemmanager (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  modem-manager crashed with SIGSEGV in g_source_remove()

Status in ModemManager:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Precise:
  Won't Fix
Status in modemmanager source package in Quantal:
  Won't Fix

Bug description:
  modem-manager crashed with SIGSEGV in g_source_remove()

  How to reproduce:
   1. attach au/huawei DATA07 USB modem.
   2. click "Enable Mobile Broadband" in network-manager indicator
   3. create "au(KDDI) connection" under Japan region with the wizard, then 
connect it.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: modemmanager 0.6.0.0.really-0ubuntu2
  ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
  Uname: Linux 3.7.0-3-generic x86_64
  ApportVersion: 2.6.2-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.329
  Date: Tue Nov 27 16:06:41 2012
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: modemmanager
  UpgradeStatus: No upgrade log present (probably fresh install)

  Upstream fix in MM_06 commit 05a42261795f27c4ecd0cd6503114322c8b8.

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


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


[Touch-packages] [Bug 1115710] Re: Mellanox mlx4_en network driver is not automatically loaded

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: module-init-tools (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Mellanox mlx4_en network driver is not automatically loaded

Status in MAAS:
  Invalid
Status in kmod package in Ubuntu:
  Fix Released
Status in module-init-tools package in Ubuntu:
  Invalid
Status in module-init-tools source package in Precise:
  Won't Fix
Status in module-init-tools source package in Quantal:
  Won't Fix
Status in kmod source package in Raring:
  Fix Released

Bug description:
  The Mellanox Ethernet card module is not being loaded in the ephemeral
  images, which causes enlisting/commissioning to fail to boot the root
  image from ISCSI, given that the interface is not loaded.

  Related bugs:
   * bug 1015339: installer initrd missing kernel modules for Mellanox ConnectX 
HCA Ethernet

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


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


[Touch-packages] [Bug 1103816] Re: package libxml2-dev 2.7.8.dfsg-5.1ubuntu4.3 failed to install/upgrade: './usr/bin/xml2-config' is different from the same file on the system

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: libxml2 (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  package libxml2-dev 2.7.8.dfsg-5.1ubuntu4.3 failed to install/upgrade:
  './usr/bin/xml2-config' is different from the same file on the system

Status in libxml2 package in Ubuntu:
  Fix Released
Status in libxml2 source package in Precise:
  Won't Fix
Status in libxml2 source package in Quantal:
  Fix Released
Status in libxml2 source package in Raring:
  Fix Released

Bug description:
  While trying to install Koha 3.8.6 dependants I encountered the errors
  above

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libxml2-dev 2.7.8.dfsg-5.1ubuntu4.3
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Wed Jan 23 07:46:06 2013
  DuplicateSignature:
   Unpacking libxml2-dev:i386 (from 
.../libxml2-dev_2.7.8.dfsg-5.1ubuntu4.3_i386.deb) ...
   dpkg: error processing 
/var/cache/apt/archives/libxml2-dev_2.7.8.dfsg-5.1ubuntu4.3_i386.deb (--unpack):
'./usr/bin/xml2-config' is different from the same file on the system
  ErrorMessage: './usr/bin/xml2-config' is different from the same file on the 
system
  MarkForUpload: True
  SourcePackage: libxml2
  Title: package libxml2-dev 2.7.8.dfsg-5.1ubuntu4.3 failed to install/upgrade: 
'./usr/bin/xml2-config' is different from the same file on the system
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1169581] Re: desktop LTS 12.04.2 broken cifs support on install

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: initramfs-tools (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  desktop LTS 12.04.2 broken cifs support on install

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Precise:
  Won't Fix
Status in initramfs-tools package in Baltix:
  New

Bug description:
  desktop LTS 12.04/.2 broken cifs support on install

  While initrd.lz includes cifs.ko the modules des_generic.ko and md4.ko
  are missing.

  CIFS is very handy when PXE booting Ubuntu LTS Desktop live from Windows OSs 
as Serva does it here.
  http://vercot.com/~serva/an/NonWindowsPXE3.html

  The inclusion of des_generic.ko  and md4.ko within initrd.lz would
  avoid the need of loading manually made complementary initrd files.

  I hope you guys can add these 2 files for 12.04.3 considering this is an LTS.
  Thanks

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


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


[Touch-packages] [Bug 1194401] Re: unable to boot ubuntu with secure boot enabled and shim package does not exist

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: apport (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  unable to boot ubuntu with secure boot enabled and shim package does
  not exist

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Won't Fix
Status in apport source package in Raring:
  Won't Fix

Bug description:
  after booting to ubuntu with secure boot disabled,i typed "ubuntu-bug shim" 
but this is what i got...
  rahul@rahul-Lenovo-IdeaPad-Y480:~$ ubuntu-bug shim
  ERROR: hook /usr/share/apport/general-hooks/cloud_archive.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/cloud_archive.py", line 18, in 
add_info
  if '~cloud' in packaging.get_version(package) and \
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 123, 
in get_version
  raise ValueError('package %s does not exist' % package)
  ValueError: package shim does not exist
  dpkg-query: no packages found matching shim
  rahul@rahul-Lenovo-IdeaPad-Y480:~$ 
  (process:6311): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: shim (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue Jun 25 14:18:17 2013
  InstallationDate: Installed on 2013-06-26 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: shim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1170832] Re: "Facebook Requires Authorization" when already authorized

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: telepathy-gabble (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  "Facebook Requires Authorization" when already authorized

Status in telepathy-gabble:
  Fix Released
Status in telepathy-gabble package in Ubuntu:
  Fix Released
Status in telepathy-gabble source package in Precise:
  Won't Fix
Status in telepathy-gabble package in Debian:
  Fix Released

Bug description:
  I am running fully updated 13.04 64-bit. I simply cannot get
  empathy/UOA to connect to facebook. When I add the account in UOA
  everything seems to go well, facebook login page loads, it logs in
  successfully, facebook recognizes the session as "safari on linux";
  but upon completing the setup in UOA empathy refuses to connect to it
  and keeps telling me it requires authorization.

  I've Tried the following: Removing the account from UOA
  Ending all active sessions on facebook and deleting the ubuntu app
  rebooting
  adding account in UOA, and allowing the ubuntu app to manage my messages 
etc...

  Didn't help at all. pidgin connects fine on the same computer.

  Sometimes it does let me add it and it works for a while, but
  eventually this issue happens again and leaves me totally unable to
  successfully add a facebook account for quite some time, until it
  randomly decides it wants to work again. Empathy/UOA in 13.04 has been
  unreliable to the point of ridiculousness, the application is
  basically unusable and can't handle the one basic task of an instant
  messaging program, which is connecting to my accounts reliably.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri Apr 19 16:57:50 2013
  InstallationDate: Installed on 2013-04-17 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130416)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-gabble/+bug/1170832/+subscriptions


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


[Touch-packages] [Bug 1215751] Re: package libxml2-dev 2.7.8.dfsg-5.1ubuntu4.6 failed to install/upgrade: './usr/bin/xml2-config' is different from the same file on the system

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: libxml2 (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  package libxml2-dev 2.7.8.dfsg-5.1ubuntu4.6 failed to install/upgrade:
  './usr/bin/xml2-config' is different from the same file on the system

Status in libxml2 package in Ubuntu:
  Confirmed
Status in libxml2 source package in Precise:
  Won't Fix

Bug description:
  Installation of libxml2 using dpkg and dselect. 64-bits Ubuntu 12.04
  LTS.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libxml2-dev 2.7.8.dfsg-5.1ubuntu4.6
  ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
  Uname: Linux 3.2.0-52-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  Date: Fri Aug 23 15:44:09 2013
  DuplicateSignature: 
package:libxml2-dev:2.7.8.dfsg-5.1ubuntu4.6:'./usr/bin/xml2-config' is 
different from the same file on the system
  ErrorMessage: './usr/bin/xml2-config' is different from the same file on the 
system
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  SourcePackage: libxml2
  Title: package libxml2-dev 2.7.8.dfsg-5.1ubuntu4.6 failed to install/upgrade: 
'./usr/bin/xml2-config' is different from the same file on the system
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1233610] Re: boot process hangs very often when NFS shares are used

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: mountall (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  boot process hangs very often when NFS shares are used

Status in mountall package in Ubuntu:
  Fix Released
Status in mountall source package in Precise:
  Won't Fix

Bug description:
  I'm running up-to-date Ubuntu 12.04.3 with the 3.2 kernel. I have a
  FreeNAS box exporting a number of NFS shares. My machine can boot
  once-in-a-while but I have problems on practically every boot, that I
  need to resolve by rebooting and trying again.

  My fstab:

  # /etc/fstab: static file system information.
  proc/proc   procnodev,noexec,nosuid 0   0
  UUID=2f6ca502-9419-4040-a702-2c9dc716dbc5 /   ext4
errors=remount-ro 0   1
  nodev /ramdisk tmpfs defaults 0 0
  silverbox:/mnt/vol1/software /nas/software nfs auto 0 0 # ENROLL
  silverbox:/mnt/vol1/videos /nas/videos nfs auto 0 0 # ENROLL
  silverbox:/mnt/vol4/backup /nas/backup nfs auto 0 0 # ENROLL
  silverbox:/mnt/vol4/home /home nfs auto,exec 0 0 # ENROLL
  silverbox:/mnt/vol4/source /home/zyga/source nfs auto 0 0 # ENROLL
  silverbox:/mnt/vol4/steam /nas/steam nfs auto,bootwait 0 0 # ENROLL
  silverbox:/mnt/vol4/music /nas/music nfs auto,bootwait 0 0 # ENROLL
  silverbox:/mnt/vol4/photos /nas/photos nfs auto,bootwait 0 0 # ENROLL

  The network between the two boxes is working perfectly over gigabit
  wired connection. I can always mount each share explicitly, it only
  causes failures a boot. My local network uses openwrt routers and has
  correct DNS setup for each machine.

  My desktop (the machine affected by this bug) uses network manager
  with DHCP connection but I did try static IP before and it had no
  effect on the failure rate.

  I've added a way to open an emergency tty (patched /etc/init/tty6.conf
  to start on startup) and inspected mountall logs (patched
  mountall.conf to have --debug, not have --verbose, have console log
  and not 'expect daemon'). I'll attach /var/log/mountall.log from a
  successful boot below.

  I have tried to debug this issue with jodh and xnox on #ubuntu-devel
  and got asked to report this and wait for slangasek. I can freely
  reproduce this bug and I can assist in debugging if required.

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


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


[Touch-packages] [Bug 221112] Re: Can't use space bar in search bar when using french alternative keyboard

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: xkeyboard-config (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Can't use space bar in search bar when using french alternative
  keyboard

Status in libgnomekbd :
  Expired
Status in Listen:
  Confirmed
Status in QuodLibet:
  Unknown
Status in Rhythmbox:
  Expired
Status in SciTE:
  New
Status in xkeyboard-config:
  Fix Released
Status in quodlibet package in Ubuntu:
  Invalid
Status in rhythmbox package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Precise:
  Won't Fix

Bug description:
  [Impact]
  In the fr(oss) keymap, both space and Ctrl + space return the same 
XLookupString, which prevents space from being used in some applications.

  This had been fixed in lucid and maverick, but the patch appears to
  have been misplaced during the (rather major) update from 1.8 to 2.1,
  thus the reports of it regressing in comments #135 and #141, as well
  as dupe bug #938671.

  [Development Fix]
  Patch 128_fix_oss_ctrl_space_accelerator.patch fixed this problem in lucid 
and maverick, but was dropped in natty when we updated to upstream 
xkeyboard-config 2.1.  However, the patch was also sent upstream and accepted 
there.  So for quantal a cherrypick of that commit was backported.

  [Stable Fix]
  Since currently quantal is shipping the same xkeyboard-config version as 
precise, we can carry the same patch there as well.

  [Test Case]
  1. Set keyboard to fr(oss).  (Note due to unrelated bug, you need to do this 
in your /etc/defaults/keyboard config file.)
  2. Start rhythmbox
  3. Do a song search
  4. Type in a search term that includes a space character

  Broken Behavior:  Space triggers the play/pause function in rhythmbox
  Fixed Behavior:  A space character is inserted

  [Regression Potential]
  The patch is one we carried in lucid and maverick (when rhythmbox was the 
default music player IIRC), and has been upstream for a while.  So I think it 
is a safe change.

  Actually, I'm surprised there have not been more complaints about it
  lately.  But during the interim we'd switched to banshee so perhaps
  users didn't notice it.

  [Original Report]
  I tried to search for "The Do" in the search bar, but the space bar didn't 
write a space. Instead, it played the currently selected song (space is the 
shortcut for playing/pausing the song). I've just installed the last Hardy 
release candidate.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Apr 23 19:30:12 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/rhythmbox
  NonfreeKernelModules: nvidia
  Package: rhythmbox 0.11.5-0ubuntu6
  PackageArchitecture: i386
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  Uname: Linux 2.6.24-16-generic i686

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


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


[Touch-packages] [Bug 897322] Re: PDF saved forms are not compatible with Adobe Reader

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: poppler (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  PDF saved forms are not compatible with Adobe Reader

Status in Evince:
  Unknown
Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Precise:
  Won't Fix

Bug description:
  When editing and saving the PDF form available at
  http://www.oiq.qc.ca/Documents/DAP/permis/formulaire_inscription_examen_prof-
  fr.pdf, the resulting PDF is not open-able in Adobe Reader X (10.1.1).

  When trying to open the document with Adobe Reader X under Windows 7,
  I get the following error :

  "There was an error opening this document. There was a problem reading
  this document (14)."

  The edited PDF form is attached to this bug.

  $ lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  $ apt-cache policy evince
  evince:
Installed: 2.32.0-0ubuntu12.3
Candidate: 2.32.0-0ubuntu12.3
Version table:
   *** 2.32.0-0ubuntu12.3 0
  500 http://ca.archive.ubuntu.com/ubuntu/ natty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.32.0-0ubuntu12 0
  500 http://ca.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: evince 2.32.0-0ubuntu12.3
  ProcVersionSignature: Ubuntu 2.6.38-13.52-generic 2.6.38.8
  Uname: Linux 2.6.38-13-generic x86_64
  Architecture: amd64
  Date: Mon Nov 28 12:50:22 2011
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature_: Ubuntu 2.6.38-13.52-generic 2.6.38.8
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: dnsmasq (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  NM-controlled dnsmasq prevents other DNS servers from starting

Status in djbdns package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed
Status in pdns-recursor package in Ubuntu:
  Invalid
Status in pdnsd package in Ubuntu:
  Invalid
Status in djbdns source package in Precise:
  Confirmed
Status in dnsmasq source package in Precise:
  Won't Fix
Status in network-manager source package in Precise:
  Won't Fix
Status in pdns-recursor source package in Precise:
  Invalid
Status in pdnsd source package in Precise:
  Invalid

Bug description:
  As described in
  https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-dns-
  resolving, network manager now starts a dnsmasq instance for local DNS
  resolving.

  That breaks the default bind9 and dnsmasq installations, for people that 
actually want to install a DNS server.
  Having to manually comment out "#dns=dnsmasq" in 
/etc/NetworkManager/NetworkManager.conf doesn't sound good, and if it stays 
that way, it should be moved to the bind9 and dnsmasq postinst scripts.

  Please make network-manager smarter so that it checks if bind9 or
  dnsmasq are installed, so that it doesn't start the local resolver in
  that case.

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


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


[Touch-packages] [Bug 941673] Re: performance of accounts-daemon is very poor

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: accountsservice (Ubuntu Precise)
   Status: In Progress => Won't Fix

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

Title:
  performance of accounts-daemon is very poor

Status in accountsservice:
  Unknown
Status in accountsservice package in Ubuntu:
  In Progress
Status in accountsservice source package in Oneiric:
  Won't Fix
Status in accountsservice source package in Precise:
  Won't Fix

Bug description:
  Version 11.10

  
  The performance of accounts-daemon is unacceptable with large password and/or 
group files. We have appoximately 4 users in the passwords file and 16000 
lines in the group file. Having looked at the source, it appears to me the 
problem is that for each user is pulls from the password database (via 
getpwXXX)  its then calls getgroups to return the users list of groups.

  Getgroups must make a complete pass through the group file to determine the 
groups for the user. When initializing this results in
  reading the groups file 4 times.

  I think a better solution is to build a inverted group file map then first 
time getgroups is called by reading the entire group database and building a 
data structure indexed by username where a users group list can by found in a 
single lookup.
  Of couse, an even better solution would be for getgroups to do that itself, 
but that would require much larger code changes.

  I tried installed nscd to see if this would make a difference but no
  dice.

  At the moment, 11.10 is unusable for us because of this problem.

  Hope this is all the info you need.

  Regards, pdg

  p...@uow.edu.au

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


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


[Touch-packages] [Bug 902535] Re: Unable to print with Lexmark S400 series since upgrade to 11.10

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: cups (Ubuntu Precise)
   Status: Incomplete => Won't Fix

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

Title:
  Unable to print with Lexmark S400 series since upgrade to 11.10

Status in cups package in Ubuntu:
  Confirmed
Status in cups source package in Precise:
  Won't Fix

Bug description:
  Following the upgrade from 11.04 to 11.10 my Lexmark S405 now is
  unable to print.

  After removing all previous drivers (i.e. from a clean install of the
  printer), I have two options to proceed:

  If I connect the printer via USB and wait for "auto-detection", the
  system is able to determine that a Lexmark S405 has been added (and
  adds the printer as a "S300-S400-Series". However at the same time I
  get the following error message:

  "Not supported by this backend. 
  The action is not supported by this backend. Please report a bug as this 
should not have happened. Provided postscript-driver not supported"

  The printer is added and does show up in CUPS. The device URI is given
  as:
  "://Lexmark/S300-S400%20Series?serial=90T409817388744=1".
  Previously two packages were also added via the Software Centre (
  "lexmark-legacy-wsu (1.0-1)" and "lexmark-inkjet-legacy-wjre (1.0-1)"
  but my most recent attempt to rectify this fault was following updates
  to fix bug 897309. On this occasion (following the updated
  ghostscript) no software was added via the Software Centre.

  I also have the drivers from Lexmark (the second install option).
  These drivers will install (but if they detect either of the above
  mentioned packages then installation will fail) but, once you are
  prompted to connect the printer via USB the error message highlighted
  above also appears. The results from this approach is that two
  printers are installed...but neither of them work.

  Either method of installing the printer results in the same scenario -
  the printer is listed as "installed", but items in the print queue
  remain there without no response from the printer. A Test Page shows
  the printer as "Processing page 1" before eventually throwing an
  error.

  Incidentally it is possible to scan from the printer (it's an all-in-
  one printer) into Ubuntu, but it seems to be impossible to print out
  from Ubuntu. Also previous work suggested that this may be connected
  to bug 883585. Also, despite CUPS referring to itself as 1.5, the
  intro screen says "what's new in CUPS 1.4". The printer does show up
  in CUPS, but it seems to be impossible to carry out any maintenance on
  the printer within CUPS (but this may be my "newbie-ness" showing
  though).

  
  My first bug report so hope I've included everything!

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


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


[Touch-packages] [Bug 972537] Re: lightdm doesn't allow expired passwords

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: unity-greeter (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  lightdm doesn't allow expired passwords

Status in lightdm package in Ubuntu:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Won't Fix
Status in unity-greeter source package in Precise:
  Won't Fix

Bug description:
  [Impact]
  Kerberos accounts on Ubuntu 12.04.1 can't force password changes via 
unity-greeter.

  [Test Case]
  1. Set up a Kerberos server and client machine (see 
http://bobthegnome.blogspot.co.nz/2012/11/testing-kerberos-in-ubuntu.html)
  2. Log into unity-greeter on client machine
  Expected result:
  Unity Greeter shows appropriate prompts to change password and can log in 
once password changed/
  Observed result:
  Some prompts skipped, password not changed and unable to log in.

  [Regression Potential]
  Potential of breaking other authentication. This has been tested with the 
lightdm regression tests.

  In Ubuntu 12.04, when logging in using the unity greeter in lightdm
  (1.1.9-0ubuntu1) with a user using Kerberos with an expired password,
  the login screen doesn't give the user the appropriate feedback to set
  their new password.  The text console works correctly.  The previous
  LTS used GDM, which behaved correctly.

  The normal prompting for this is:
  Username: cmo-test
  Password:  
  Password expired.  You must change it now.
  Enter new password:  
  Enter it again:  

  Instead, in lightdm, it is:
  Username: cmo-test
  Password: 
  Enter it again: 

  The "Password expired" message is never shown, and "Enter it again" is
  shown in the box instead of "Enter new password".  If you use lighdm-
  gtk-greeter, you get the "password expired" message printed under the
  box, but still have the same prompting, never asking for the new
  password.

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


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


[Touch-packages] [Bug 936186] Re: add-apt-repository crashed with error in get_ppa_info_from_lp(): (23, 'Failed writing body (0 != 1607)')

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: software-properties (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  add-apt-repository crashed with error in get_ppa_info_from_lp(): (23,
  'Failed writing body (0 != 1607)')

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Precise:
  Won't Fix

Bug description:
  Close in start.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.4
  ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
  Uname: Linux 3.2.0-16-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  Date: Sat Feb 18 03:15:16 2012
  DuplicateOf: https://bugs.launchpad.net/bugs/930478
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/add-apt-repository ppa:ricotz/testing
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:ricotz/testing']
  SourcePackage: software-properties
  Title: add-apt-repository crashed with error in get_ppa_info_from_lp(): (23, 
'Failed writing body (0 != 1607)')
  UpgradeStatus: Upgraded to precise on 2012-02-16 (3 days ago)
  UserGroups:

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


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


[Touch-packages] [Bug 959676] Re: cups will not print to USB connected Samsung ML-4500 (with USB -> Parallel adapter)

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: cups (Ubuntu Precise)
   Status: Incomplete => Won't Fix

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

Title:
  cups will not print to USB connected Samsung ML-4500 (with USB ->
  Parallel adapter)

Status in cups package in Ubuntu:
  Expired
Status in cups source package in Precise:
  Won't Fix

Bug description:
  I have a working parallel laser printer: Samsung ML-4500. I have
  connected this to my computer with a usb-to-parallel cable.

  The cable is listed in as:

  $ lsusb -s 005:005
  Bus 005 Device 005: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel 
Port

  Cups recognises the printer model and gnome correctly lists the
  printer in system-config-printer. Any attempt to print to the printer,
  however, results in the printer spinning up it's cooling fans and
  heating the fusing lamp while the "data" led on the front flashes for
  about 5minutes. In the cups admin screen the print job is listed as
  "Sending data to printer." The printer eventually stops whirring and
  shuts back down into standby with the Data led remaining static to
  indicate that the printer is idle. At no point does the printer
  actually begin, or finish, printing anything.

  After plugging the usb cable dmesg reports:

  [ 2952.148182] usb 5-3: new full-speed USB device number 5 using ohci_hcd
  [ 2952.321367] usblp0: USB Bidirectional printer dev 5 if 0 alt 1 proto 2 vid 
0x067B pid 0x2305

  Upon attempting to print to the device dmesg reports:

  [ 2964.457576] usblp0: removed
  [ 2964.479420] usblp0: USB Bidirectional printer dev 5 if 0 alt 1 proto 2 vid 
0x067B pid 0x2305
  [ 2965.505493] usblp0: removed
  [ 2965.537417] usblp0: USB Bidirectional printer dev 5 if 0 alt 1 proto 2 vid 
0x067B pid 0x2305
  [ 2969.733454] usblp0: removed

  (The time period between these two dmesg output snippets shows a print
  attempt directly after plugging the cable. The "usblp0: removed" does
  not appear until the print spool is actively trying to print, and thus
  is not a result of the hotplug event.)

  Now that I have a job in the queue, cups admin screen reports that the
  printer is in the following state:

  ML-4500 Samsung ML-4500 daniel-MS-7693  Samsung ML-4500 Foomatic/gdi
  (recommended)  Processing - "Sending data to printer."

  The printer is idle, however, and does not appear to be receiving any
  communication since the initial attempt at printing the job (which is
  also listed below):

  ML-4500-3   Unknown Withheld1k  Unknown
  processing since Mon 19 Mar 2012 20:05:15 GMT "Sending data to
  printer."

  The time is now 20:24, around twenty minutes since this particular
  test job was started and still no sign of an output. Previous jobs I
  have cancelled to clear the queue.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.2-8
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   W [19/Mar/2012:19:27:50 +] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'ML-4500-Gray..' already 
exists
   W [19/Mar/2012:19:27:50 +] failed to CreateDevice: 
org.freedesktop.ColorManager.AlreadyExists:device id 'cups-ML-4500' already 
exists
   W [19/Mar/2012:19:27:50 +] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
'Photosmart-C4100-series-Gray..' already exists
   W [19/Mar/2012:19:27:50 +] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
'Photosmart-C4100-series-RGB..' already exists
   W [19/Mar/2012:19:27:50 +] failed to CreateDevice: 
org.freedesktop.ColorManager.AlreadyExists:device id 
'cups-Photosmart-C4100-series' already exists
  Date: Mon Mar 19 20:09:47 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  Lpstat: device for ML-4500: usb://Samsung/ML-4500
  MachineType: MSI MS-7693
  Papersize: a4
  PpdFiles: ML-4500: Samsung ML-4500 Foomatic/gdi (recommended)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic 
root=UUID=60ea4233-8504-473c-8911-ce68b72b19b8 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to precise on 2012-03-12 (6 days ago)
  dmi.bios.date: 02/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G46 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 

[Touch-packages] [Bug 978012] Re: Please SRU micro bug fix release of e2fsprogs 1.42.5-1ubuntu2 (main) from Quantal (main)

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: e2fsprogs (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  Please SRU micro bug fix release of e2fsprogs 1.42.5-1ubuntu2 (main)
  from Quantal (main)

Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Precise:
  Won't Fix
Status in e2fsprogs source package in Quantal:
  Fix Released
Status in e2fsprogs package in Baltix:
  In Progress

Bug description:
  == Impact ==
  * fixes multiple file system corruption bugs
  * fixes potential data loss
  * reduces LTS maintenance, due to synchronisation with Wheezy (1.42.4-3) and 
quantal (1.42.4-3ubuntu1)
  * This is not a MicroReleaseUpload, as impact is in line with current SRU 
policies

  == other (questionable) changes ==
  * translations updates
  * API/ABI compatible - symbols file updated to released version numbers (TODO 
check)
  * hardening build flags enabled for -static package
  * for other changes see debian/changelog below and the Release Notes
  http://e2fsprogs.sourceforge.net/e2fsprogs-release.html

  == debian/changelog since last release in Precise ==

  Source: e2fsprogs
  Version: 1.42.4-3ubuntu1~12.04.1
  Distribution: precise-proposed
  Urgency: medium
  Date: Mon, 25 Jun 2012 15:48:41 +0100
  Closes: 646629 646963 654457 663237 665427 665885 674453 674694
  Changes:
   e2fsprogs (1.42.4-3ubuntu1~12.04.1) precise-proposed; urgency=low
   .
     * Upstream micro bug fix point release SRU (LP: #978012)
   - changes included up to and including 1.42.4-3ubuntu1
   .
   e2fsprogs (1.42.4-3ubuntu1) quantal; urgency=low
   .
     * Merge from Debian unstable (LP: #978012), remainging changes:
   - debian/control.in:
   Build-depend on gettext:any instead of on gettext for 
(cross-building)
   Drop build dependency on dc, which hasn't been needed for some time.
   Update maintainer field.
   - debian/rules:
   Block pkg-create-dbgsym from operating on this package.
   Build without dietlibc-dev, which is in universe
   - debian/control:
   Regenerate with ./debian/rules debian/control
   .
   e2fsprogs (1.42.4-3) unstable; urgency=medium
   .
     * Add the -C option to chattr's usage message
     * Fix e2fsprogs so it is blhc (build log hardening check) clean.  This
   fixed e2fsck.static which previously was not getting built with the
   security hardening flags.
   .
   e2fsprogs (1.42.4-2) unstable; urgency=medium
   .
     * Fix FTBFS problem on the hurd and freebsd platforms
   .
   e2fsprogs (1.42.4-1) unstable; urgency=medium
   .
     * New upstream version
     * Fix 64-bit block number bugs in e2fsck, dumpe2fs, and debugfs which
   could corrupt file systems
     * Fixed e2fsck's handling of how errors propagate from the journal to
   the file system superblock
     * Fixed a false positive complaint from e2fsck if all of the extents
   in the last extent block are uninitialized and located after the
   end of the file.
     * dumpe2fs will display the journal's error indicator in the
   superblock if it is set
     * Fixed a  bug which caused e2fsck to incorrectly use O_EXCLUSIVE in
   some corner cases.
     * Fix truncation of extent-mapped inodes in e2fsck and libext2fs
     * Fixed i_blocks accounting in bigalloc file systems.
     * Add support for btrfs's No_COW flag to lsattr and chattr
     * Debugfs interprets the date strings of the form "@ddd" as ddd
   seconds after the epoch
     * Updated/fixed various man pages  (Closes: #674453, #674694)
   .
   e2fsprogs (1.42.3-1) unstable; urgency=low
   .
     * New upstream version
     * Fix bugs on 32-bit systems which could corrupt > 16TB file systems
     * Quiet complaints in e2fsck when the total free blocks or inodes are
   incorrect in the superblock after an system crash, since we don't
   update nor depend on the superblock summaries at each commit boundary
     * Fixed support for (hidden) quota files built into ext4; in
   particular, don't rewrite the quota inode unless the quotas are
   inconsistent
     * Optimized reading and writing bitmaps if direct I/O was enabled
     * Update Czech, Dutch, French, German, Polish, Sweedish, and
   Vietnamese translations
     * Fixed incorrect indentation in tune2fs man page
     * Update debian policy compliance to 3.9.3
   .
   e2fsprogs (1.42.2-2ubuntu1) quantal; urgency=low
   .
     * Merge from Debian unstable (LP: #978012), remainging changes:
   - debian/control.in:
   Build-depend on gettext:any instead of on gettext for 
(cross-building)
   Drop build dependency on dc, which hasn't been needed for some time.
   Update maintainer 

[Touch-packages] [Bug 939126] Re: AppArmor profile does not allow creating of ~/.cache/dconf

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: telepathy-mission-control-5 (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  AppArmor profile does not allow creating of ~/.cache/dconf

Status in telepathy-mission-control-5 package in Ubuntu:
  Fix Released
Status in telepathy-mission-control-5 source package in Precise:
  Won't Fix

Bug description:
  This causes telepathy-gabble (and other CMs) to throw a critical_error
  when creating this directory if it does not exist already.

  To reproduce:
   delete ~/.cache/dconf

  killall telepathy-gabble
  start GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/lib/telepathy/telepathy-gabble 

  this will error when the first account is connected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/939126/+subscriptions


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


[Touch-packages] [Bug 993400] Re: apport asked me to restart an application that had already restarted

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: apport (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  apport asked me to restart an application that had already restarted

Status in apport package in Ubuntu:
  Invalid
Status in apport source package in Precise:
  Won't Fix

Bug description:
  I recently received a compiz crash report notification from apport and
  in the dialog I was asked if I wanted to restart compiz.  Given that I
  was actually seeing the dialog, I was in a desktop environment and
  compiz was already running.  I naturally chose not to restart it and I
  wonder what would have happened had I chosen to.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apport 2.0.1-0ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CheckboxSubmission: 2e6ecd139611830c78226ad04ff4c093
  CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
  CrashReports:
   600:120:134:0:2012-04-24 13:49:18.0 -0700:2012-04-15 
20:02:57.0 
-0700:/var/crash/_usr_lib_ubuntuone-client_ubuntuone-login.1000.uploaded
   664:1000:134:0:2012-04-23 15:49:31.0 -0700:2012-04-23 
15:49:31.0 -0700:/var/crash/apport.1000.upload
   640:1000:134:6005683:2012-05-01 16:01:56.0 -0700:2012-05-01 
16:08:34.0 -0700:/var/crash/_usr_bin_compiz.1000.crash
   600:120:134:0:2012-05-02 09:36:37.0 -0700:2012-04-30 
07:35:12.0 -0700:/var/crash/apport.1000.uploaded
   640:1000:134:2039844:2012-04-23 15:49:27.0 -0700:2012-04-29 
14:29:59.0 -0700:/var/crash/apport.1000.crash
  Date: Wed May  2 09:36:37 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to precise on 2012-01-04 (118 days ago)

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


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


[Touch-packages] [Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: network-manager (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  NM-controlled dnsmasq prevents other DNS servers from starting

Status in djbdns package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed
Status in pdns-recursor package in Ubuntu:
  Invalid
Status in pdnsd package in Ubuntu:
  Invalid
Status in djbdns source package in Precise:
  Confirmed
Status in dnsmasq source package in Precise:
  Won't Fix
Status in network-manager source package in Precise:
  Won't Fix
Status in pdns-recursor source package in Precise:
  Invalid
Status in pdnsd source package in Precise:
  Invalid

Bug description:
  As described in
  https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-dns-
  resolving, network manager now starts a dnsmasq instance for local DNS
  resolving.

  That breaks the default bind9 and dnsmasq installations, for people that 
actually want to install a DNS server.
  Having to manually comment out "#dns=dnsmasq" in 
/etc/NetworkManager/NetworkManager.conf doesn't sound good, and if it stays 
that way, it should be moved to the bind9 and dnsmasq postinst scripts.

  Please make network-manager smarter so that it checks if bind9 or
  dnsmasq are installed, so that it doesn't start the local resolver in
  that case.

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


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


[Touch-packages] [Bug 958382] Re: different softwares hit abort() in gtkfilechooser code

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: gtk+3.0 (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  different softwares hit abort() in gtkfilechooser code

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Precise:
  Won't Fix

Bug description:
  Sorry, don't remember any details.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 21.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic i686
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Sun Mar 18 14:31:46 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcCmdline: gnome-control-center deja-dup
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: deja-dup
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-03-17 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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


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


[Touch-packages] [Bug 987212] Re: Wireless printer "Processing - Unable to locate printer."

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: avahi (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  Wireless printer "Processing - Unable to locate printer."

Status in avahi package in Ubuntu:
  Confirmed
Status in avahi source package in Precise:
  Won't Fix
Status in avahi source package in Quantal:
  Won't Fix
Status in avahi source package in Raring:
  Won't Fix

Bug description:
  Description: Ubuntu 12.04 LTS (Precise Pangolin) Beta 2
  Release: 12.04 Beta 2

  The printer is a Lexmark X734de  printer connected over a wireless
  network that can be found, but will not print. The print job stays in
  the queue forever. Wireless Printer "Processing - Unable to locate
  printer."

  Network/Local Printers found but cannot print - Unable to get printer
  status and says it's "Processing".

  I'm shure we want avoid this for the Ubuntu 12.04 LTS (Precise
  Pangolin) release, when the final has been released. I'm using Ubuntu
  12.04 LTS (Precise Pangolin) Beta 2 with latest update as of today.

  CUPS log: /var/log/cups/error_log

  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-Gray..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-CMYK..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateDevice: 
org.freedesktop.ColorManager.AlreadyExists:device id 'cups-Lexmark-X734de' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-Gray..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-CMYK..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateDevice: 
org.freedesktop.ColorManager.AlreadyExists:device id 'cups-Lexmark-X734de' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-Gray..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-CMYK..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateDevice: 
org.freedesktop.ColorManager.AlreadyExists:device id 'cups-Lexmark-X734de' 
already exists
  E [23/Apr/2012:11:50:58 +0200] [Job 2] Unable to find printer.
  E [23/Apr/2012:11:51:13 +0200] [Job 2] Unable to find printer.
  E [23/Apr/2012:11:51:28 +0200] [Job 2] Unable to find printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: system-config-printer-gnome 1.3.8+20120201-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
  Uname: Linux 3.2.0-20-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  CheckboxSubmission: e28f23d40ba6960d2759044b1acbd380
  CheckboxSystem: c69722ecac764861be52925fa50b4dcc
  Date: Mon Apr 23 11:58:03 2012
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  InterpreterPath: /usr/bin/python2.7
  Lpstat:
   device for Canon-MP190-series: 
usb://Canon/MP190%20series?serial=E14D77=1
   device for Lexmark-X734de: 
dnssd://Lexmark%20X734de._pdl-datastream._tcp.local/
  MachineType: Acer AOA150
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   Lexmark-X734de: Lexmark X734de
   Canon-MP190-series: Canon PIXMA MP190 - CUPS+Gutenprint v5.2.8-pre1
  ProcEnviron:
   LANGUAGE=se_NO:nb_NO:nb:no_NO:no:nn_NO:nn:da:sv:en
   LANG=se_NO
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae 
root=UUID=6448F9C148F991D2 loop=/hostname/disks/root.disk ro quiet splash 
vt.handoff=7
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3305
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3305:bd05/09/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: AOA150
  dmi.product.version: 1
  dmi.sys.vendor: Acer

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


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

[Touch-packages] [Bug 972537] Re: lightdm doesn't allow expired passwords

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: lightdm (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  lightdm doesn't allow expired passwords

Status in lightdm package in Ubuntu:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Won't Fix
Status in unity-greeter source package in Precise:
  Won't Fix

Bug description:
  [Impact]
  Kerberos accounts on Ubuntu 12.04.1 can't force password changes via 
unity-greeter.

  [Test Case]
  1. Set up a Kerberos server and client machine (see 
http://bobthegnome.blogspot.co.nz/2012/11/testing-kerberos-in-ubuntu.html)
  2. Log into unity-greeter on client machine
  Expected result:
  Unity Greeter shows appropriate prompts to change password and can log in 
once password changed/
  Observed result:
  Some prompts skipped, password not changed and unable to log in.

  [Regression Potential]
  Potential of breaking other authentication. This has been tested with the 
lightdm regression tests.

  In Ubuntu 12.04, when logging in using the unity greeter in lightdm
  (1.1.9-0ubuntu1) with a user using Kerberos with an expired password,
  the login screen doesn't give the user the appropriate feedback to set
  their new password.  The text console works correctly.  The previous
  LTS used GDM, which behaved correctly.

  The normal prompting for this is:
  Username: cmo-test
  Password:  
  Password expired.  You must change it now.
  Enter new password:  
  Enter it again:  

  Instead, in lightdm, it is:
  Username: cmo-test
  Password: 
  Enter it again: 

  The "Password expired" message is never shown, and "Enter it again" is
  shown in the box instead of "Enter new password".  If you use lighdm-
  gtk-greeter, you get the "password expired" message printed under the
  box, but still have the same prompting, never asking for the new
  password.

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


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


[Touch-packages] [Bug 998156] Re: GTK Print dialog sends broken custom page size attribute: "PageSize=Custom.Custom.x"

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: gtk+3.0 (Ubuntu Precise)
   Status: In Progress => Won't Fix

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

Title:
  GTK Print dialog sends broken custom page size attribute:
  "PageSize=Custom.Custom.x"

Status in GTK+:
  Fix Released
Status in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Invalid
Status in gimp package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in inkscape package in Ubuntu:
  Invalid
Status in The Precise Pangolin:
  Won't Fix
Status in firefox source package in Precise:
  Invalid
Status in gimp source package in Precise:
  Invalid
Status in gtk+3.0 source package in Precise:
  Won't Fix
Status in inkscape source package in Precise:
  Invalid
Status in The Quantal Quetzal:
  Won't Fix
Status in firefox source package in Quantal:
  Invalid
Status in gimp source package in Quantal:
  Invalid
Status in gtk+3.0 source package in Quantal:
  Fix Released
Status in inkscape source package in Quantal:
  Invalid
Status in gtk+2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  [Fix]

  [Test Case]

  [Regression Potential]

  [Original Report]
  When trying to print a photo, the printer stops with status "rendering 
completed". I have to remove all printing jobs and restart CUPS to be able to 
print again. This error does not occur when printing other documents, i.e. 
simple text.

  I use a HP PhotoSmart b109a connected to a Fritz!Box 7390 wireless
  router ("socket://fritz.box:9100").

  This bug is also present in Debian: http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=664031

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


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


[Touch-packages] [Bug 1028280] Re: sftp remoteserver "ls -l" error

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: openssh (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  sftp remoteserver "ls -l" error

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Precise:
  Won't Fix

Bug description:
  When connected via sftp to remote server, the "ls -l *" returns wrong
  information, other then "ls -l filename".

  Example:
  ---
  $ uname -a
  Linux laptop 2.6.38-15-generic #59-Ubuntu SMP Fri Apr 27 16:04:29 UTC 2012 
i686 i686 i386 GNU/Linux
  $ ssh -v
  OpenSSH_5.8p1 Debian-1ubuntu3, OpenSSL 0.9.8o 01 Jun 2010
  
  $ sftp remoteserver
  sftp> ls -l *tgz
  -rw-r--r--0 1001 0  334258 Jun 10 21:59 ifly.root.tgz
  -rw-r--r--0 1001 0  467990 Jul 24 09:50 ifly_root.tgz
  sftp> ls -l ifly.root.tgz
  -rw-r--r--0 1001 0  467990 Jul 24 09:50 ifly.root.tgz
  sftp> ls -l ifly_root.tgz
  -rw-r--r--0 1001 0  334258 Jun 10 21:59 ifly_root.tgz
  sftp> 
  ---

  The file ifly.root.tgz is really 467990 bytes and Jul 24 09:50, and 
ifly_root.tgz is 334258 bytes and Jun 10 21:59.
  It`s correct.
  But when used "ls -l *tgz" sizes and dates not corresponds to filenames, and 
when  "ls -l *" filenames and file attributes may be mixed in random order: 
directory "/tmp" marked as file "-rw-r--r-", file "index.html" marked as 
directory, etc.
  With other remote servers too.

  When connecting to this and other remote servers from FreeBSD (openssh
  5.4) all works fine.

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


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


[Touch-packages] [Bug 995111] Re: Print failure since upgrade to 12.04

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: cups (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Print failure since upgrade to 12.04

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Precise:
  Won't Fix

Bug description:
  Since upgrade to 12.04 LTS have had difficulty printing which persists even 
after re-installing Oneiric.  I do not think this is a printer malfunction as 
netbook  running Ubuntu 10.04 cups 1.4.3-1ubuntu1.5 prints just fine. Often 
occurring with second jobs when the first page appears with a single line of 
characters at the top and then the printer churns out repeated blank pages 
until stopped by hitting the printer "stop" button. Currently having the 
problem with Ubuntu 11.10 with cups 1.5.0-8 and Ubuntu 12.04 with cups 
1.5.2-9ubuntu1.  Cups Error log does not report an error.  The line of 
characters is not always identical but often similar.  The clearest is
  ERROR:
  undefined
  OFFENDING COMMAND:
  5rCj3Lri1"+f$rI5+n6R8\*imVK6JF'6bb
  STACK:

  More usually
  5rCj3Lri1"+f$rI5+n6R8\*imVK6JF'6bb
   
K6LhR1->%^S_n48hjF.$II@,f_rC4^-LP1_'P3RLc;\M

  Have tried using different driver from bchemnet and in Ubuntu 12.04
  installing cups 1.5.0 from archive but these either have not helped or
  have proved beyond my ability.  I think I need some help

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


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


[Touch-packages] [Bug 998156] Re: GTK Print dialog sends broken custom page size attribute: "PageSize=Custom.Custom.x"

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: Ubuntu Precise
   Status: Triaged => Won't Fix

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

Title:
  GTK Print dialog sends broken custom page size attribute:
  "PageSize=Custom.Custom.x"

Status in GTK+:
  Fix Released
Status in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Invalid
Status in gimp package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in inkscape package in Ubuntu:
  Invalid
Status in The Precise Pangolin:
  Won't Fix
Status in firefox source package in Precise:
  Invalid
Status in gimp source package in Precise:
  Invalid
Status in gtk+3.0 source package in Precise:
  Won't Fix
Status in inkscape source package in Precise:
  Invalid
Status in The Quantal Quetzal:
  Won't Fix
Status in firefox source package in Quantal:
  Invalid
Status in gimp source package in Quantal:
  Invalid
Status in gtk+3.0 source package in Quantal:
  Fix Released
Status in inkscape source package in Quantal:
  Invalid
Status in gtk+2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  [Fix]

  [Test Case]

  [Regression Potential]

  [Original Report]
  When trying to print a photo, the printer stops with status "rendering 
completed". I have to remove all printing jobs and restart CUPS to be able to 
print again. This error does not occur when printing other documents, i.e. 
simple text.

  I use a HP PhotoSmart b109a connected to a Fritz!Box 7390 wireless
  router ("socket://fritz.box:9100").

  This bug is also present in Debian: http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=664031

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


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


[Touch-packages] [Bug 1006898] Re: [SRU] dnsmasq fails at leasing issues when using vlan mode

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: dnsmasq (Ubuntu Precise)
   Status: Incomplete => Won't Fix

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

Title:
  [SRU] dnsmasq fails at leasing issues when using vlan mode

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Precise:
  Won't Fix

Bug description:
  ** Issue **

  There is an issue with the way nova uses dnsmasq in VLAN mode. It starts
  up a single copy of dnsmasq for each vlan on the network host (or on
  every host in multi_host mode). The problem is in the way that dnsmasq
  binds to an ip address and port[2]. Both copies can respond to broadcast
  packet, but unicast packets can only be answered by one of the copies.

  In nova this means that guests from only one project will get responses
  to their unicast dhcp renew requests. Unicast projects from guests in
  other projects get ignored. What happens next is different depending on
  the guest os. Linux generally will send a broadcast packet out after
  the unicast fails, and so the only effect is a small (tens of ms) hiccup
  while interface is reconfigured. It can be much worse than that,
  however. I have seen cases where Windows just gives up and ends up with
  a non-configured interface.

  This bug was first noticed by some users of openstack who rolled their
  own fix. Basically, on linux, if you set the SO_BINDTODEVICE socket
  option, it will allow different daemons to share the port and respond to
  unicast packets, as long as they listen on different interfaces. I
  managed to communicate with Simon Kelley, the maintainer of dnsmasq and
  he has integrated a fix[3] for the issue in the current version[1] of
  dnsmaq.

  [3]
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=9380ba70d67db6b69f817d8e318de5ba1e990b12

  ** Development Fix **

  This has been fixed in quantal with the newer version of dnmasq.

  ** Stable Fix **

  I have backported the patch which fixes this issue, I have attached
  the debdiff and the buildlog.

  ** Test Case **

  1. Install openstack with vlan mode.
  2. Watch instances loose their IP addresses.

  ** Regression Potential **

  Minimal, most installations dont use this type of networking.

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


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


[Touch-packages] [Bug 1020994] Re: Ensure whoopsie sends complete crash files to the error tracker

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: apport (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Ensure whoopsie sends complete crash files to the error tracker

Status in Daisy:
  Invalid
Status in Errors:
  Invalid
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Won't Fix

Bug description:
  [Impact]
  Apport was modifed in bug 989698 to stop showing the information collection 
process if the crash database (launchpad) doesn't accept a type of report.  
Data would be collected in the background and whoopsie would just upload the 
crash.  This led to a situation where whoopsie might upload the .crash file to 
daisy before the information collection was done.  Subsequently, there are 
error reports missing valuable data like the package version and release of 
Ubuntu.

  [Test Case]

  [Regression Potential]

  We do not appear to be getting many crash reports for the current
  development release, according to the API:

  https://errors.ubuntu.com/api/most-common-
  problems/Ubuntu%2012.10/today

  The DistroRelease field is definitely set to "Ubuntu 12.10", so this
  is likely not a problem of it showing up under "Ubuntu 12.10
  (development release)" or "Ubuntu Quantal".

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


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


[Touch-packages] [Bug 1006263] Re: evince prints formulas incorrect

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: cairo (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  evince prints formulas incorrect

Status in GS-GPL:
  Invalid
Status in libcairo:
  Fix Released
Status in cairo package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Invalid
Status in cairo source package in Precise:
  Won't Fix
Status in ghostscript source package in Precise:
  Invalid

Bug description:
  evince does not print mathematical formulas correctly in precise.

  example file: http://ddg.cs.columbia.edu/SIGGRAPH06/DDGCourse2006.pdf
  try to print page 60, look at the formula S(t) in the upper left part, or at 
the S(i_0, i_1, i_2, i_3) in the middle-left. There are all symbols missing: 
"(", ")", "-", ","

  when i print to .ps, evince still shows the file right, but when i
  submit it with "lp" to the printer, the problem is the same as when
  printing directly from evince.

  as a counterexample, when i print the page to .ps from okular and then
  submit it with lp, it gets printed correctly. Printing directly from
  acroread works, too.

  This bug is a regression from lucid, where the same file is printable
  on the same printer with the same drivers from evince.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1006263/+subscriptions


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


[Touch-packages] [Bug 1025670] Re: Segfault (.bss overflow) in PCRE

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: pcre3 (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Segfault (.bss overflow) in PCRE

Status in pcre3 package in Ubuntu:
  Fix Released
Status in pcre3 source package in Precise:
  Won't Fix

Bug description:
  A bug in PCRE was fixed upstream. The issue is a segfault with a
  pattern like /\x{30}/ui, e.g.

  pcregrep -ui '\x{30}' < /dev/null

  There was no bounds checking on access to some UCD character tables,
  and insufficient bounds checking in \x character construction. The fix
  was included in a commit that did a lot of other things:

  http://vcs.pcre.org/viewvc?view=revision=774

  but I have split out the relevant single-line fix for your
  convenience. Patch attached.

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


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


[Touch-packages] [Bug 1045704] Re: should clean pkgcache.bin.* and srcpkgcache.bin.*

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: apt (Ubuntu Precise)
   Status: In Progress => Won't Fix

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

Title:
  should clean pkgcache.bin.* and srcpkgcache.bin.*

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Won't Fix

Bug description:
  TEST CASE:
  1. do sudo touch /var/cache/apt/pkgcache.bin.xxx to simulate atmoic write 
that did not get cleaned up
  2. run sudo apt-get update
  3. verify that the file is still there

  4. install apt from precise-proposed
  5. run sudo apt-get update
  6. verify that the file is now cleaned up

  The issue is reported from a precise system upgraded over time, it
  seems that pkgcache.bin. and srcpkgcache.bin. are left
  over time in  /var/cache/apt/, those should be cleaned

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


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


[Touch-packages] [Bug 1037469] Re: GTK 3.4.2 crashes in GtkEntry gtk_entry_get_icon_pixbuf()

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: gtk+3.0 (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  GTK 3.4.2 crashes in GtkEntry gtk_entry_get_icon_pixbuf()

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Won't Fix

Bug description:
  The java-gnome test suite crashes with the currently shipping Ubuntu
  3.4.2 libgtk-3-0 package. This is a regression. I reported it upstream
  as GNOME #679537 and it was fixed and also applied to the 3.4 branch.
  I'd like to ask if you can see about getting this backported to our
  Precise package of libgtk...

  AfC

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libgtk-3-0 3.4.2-0ubuntu0.4
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Thu Aug 16 18:50:09 2012
  EcryptfsInUse: Yes
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1038573] Re: Unreadable messages displayed during Lucid -> Precise upgrade

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: pango1.0 (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Unreadable messages displayed during Lucid -> Precise upgrade

Status in Pango:
  New
Status in pango1.0 package in Ubuntu:
  Incomplete
Status in pango1.0 source package in Precise:
  Won't Fix

Bug description:
  I'm just testing 10.04.4 -> 12.04.1 upgrades and the upgrade did
  complete successfully but twice during the upgrade I was presented
  with a dialog box that's totally unreadable, and the upgrade process
  does not proceed until I click on the unreadable widget in the lower
  right hand corner of the box. I'm attaching a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: update-manager 1:0.156.14.9
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  Date: Sun Aug 19 00:30:02 2012
  GsettingsChanges:
   com.ubuntu.update-manager first-run false
   com.ubuntu.update-manager launch-time 1345345338
  InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: update-manager
  UpgradeStatus: Upgraded to precise on 2012-08-19 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission 
denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'

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


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


[Touch-packages] [Bug 1049426] Re: Unable to properly convert Orange Spain provider string (from +COPS) to UTF-8

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: modemmanager (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  Unable to properly convert Orange Spain provider string (from +COPS)
  to UTF-8

Status in ModemManager:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Precise:
  Won't Fix

Bug description:
  This appears to be reproducible quite well with Orange in Spain. Bug
  opened on behalf of Chris Hemsing. This is an SRU candidate for
  ModemManager in 12.04 if the patch can be cherry-picked and doesn't
  need to many modifications.

  "
  There is a problem with the charset, which finally leads to a SIGSEGV in
  g_utf8_validate called from parse_operator.

  The modem is a
  Bus 002 Device 003: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800
  HSDPA Modem

  Kernel:
  3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012 x86_64 x86_64
  x86_64 GNU/Linux

  What happens:

  parse_operator gets called

  parse_operator (reply=0x674cc0 "+COPS: 0,0,\"Orange\241\",2",
  cur_charset=MM_MODEM_CHARSET_UCS2) at mm-generic-gsm.c:2856

  after the regexep, correctly

  (gdb) p operator
  $1 = 0x67e2e0 "Orange\241"

  However, "Orange\241" is not UCS2 and therefore

  operator = mm_charset_take_and_convert_to_utf8 (operator,
  MM_MODEM_CHARSET_UCS2);

  returns 0x0 !

  The variable "operator" is not being checked and this leads to a call
  of

  g_utf8_validate (str=0x0 (operator), max_len=-1, end=0x0)

  g_utf8_validate then hits the SIGSEGV.
  "

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


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


[Touch-packages] [Bug 1074777] Re: package libldap-2.4-2 2.4.31-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: openldap (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  package libldap-2.4-2 2.4.31-1ubuntu2 failed to install/upgrade:
  trying to overwrite shared '/etc/ldap/ldap.conf', which is different
  from other instances of package libldap-2.4-2:i386

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Precise:
  Won't Fix
Status in openldap source package in Quantal:
  Won't Fix
Status in openldap package in Debian:
  Fix Released

Bug description:
  !

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: libldap-2.4-2 2.4.31-1ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sat Nov  3 00:07:15 2012
  ErrorMessage: trying to overwrite shared '/etc/ldap/ldap.conf', which is 
different from other instances of package libldap-2.4-2:i386
  InstallationDate: Installed on 2012-10-08 (26 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  SourcePackage: openldap
  Title: package libldap-2.4-2 2.4.31-1ubuntu2 failed to install/upgrade: 
trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other 
instances of package libldap-2.4-2:i386
  UpgradeStatus: Upgraded to quantal on 2012-11-02 (1 days ago)

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


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


[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-10-13 Thread Sergio Durigan Junior
I've also submitted a Merge Request against the Debian clamav package:

https://salsa.debian.org/clamav-team/clamav/-/merge_requests/4

Hopefully it will be accepted & merged into Ubuntu soon. If not, I will
submit an MP to add this change as a delta to our package.

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: blueman (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in blueman package in Ubuntu:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in blueman source package in Precise:
  Won't Fix
Status in bluez source package in Precise:
  Confirmed
Status in gnome-bluetooth source package in Precise:
  Fix Released
Status in blueman source package in Quantal:
  Invalid
Status in bluez source package in Quantal:
  Won't Fix
Status in gnome-bluetooth source package in Quantal:
  Fix Released
Status in blueman source package in Raring:
  Invalid
Status in bluez source package in Raring:
  Won't Fix
Status in gnome-bluetooth source package in Raring:
  Won't Fix
Status in bluez package in Fedora:
  Won't Fix

Bug description:
  [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
  [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
session, watch it automatically re-pair.
  [Regression Potential] Little. The patched piece of XML is only relevant to 
hardware having the same ID.

  When you don't use the mouse for a long enough time, the mouse
  disconnects and won't reconnect. I have to go into bluetooth settings,
  remove it, and re-pair it.

  1)
  ~ % lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

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

  3)
  I expected the mouse to reconnect automatically, or at least after I try to 
reconnect manually through the bluetooth settings.

  4)
  I have to re-pair the mouse in order to use it again. Turning the mouse off 
and on doesn't work either.

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


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


[Touch-packages] [Bug 1158500] Re: auditd fails to add rules when used in precise with -lts-quantal kernel

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: audit (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  auditd fails to add rules when used in precise with -lts-quantal
  kernel

Status in audit package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in audit source package in Precise:
  Won't Fix
Status in linux source package in Precise:
  Invalid

Bug description:
  auditctl fails to add rules when run with the -lts-quantal kernel

  Eample:
  # auditctl -l
  No rules
  # auditctl -a entry,always -F arch=b64 -S execve -k exec
  Error sending add rule data request (Invalid argument)
  #

  Looks like the syscall table needs updating, it works with the 3.2.0
  kernel.

  Tagging this as a security vulnerability because it fails fairly
  quietly and may lead to high security systems not having required
  auditing (like PCI compliant systems), I only noticed by looking in
  /var/log/boot.log.

  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04

  ii  auditd 1.7.18-1ubuntu1
User space tools for security auditing
  ii  linux-image-generic-lts-quantal3.5.0.26.33
Generic Linux kernel image

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


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


[Touch-packages] [Bug 1347246] Re: ifup fails on IPv6 static interface with alias

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: ifupdown (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  ifup fails on IPv6 static interface with alias

Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Precise:
  Won't Fix

Bug description:
  ifup doesn't trim alias portion of interface from sysctl when
  configuring IPv6 static addresses:

  # ifup eth0.4000:ucarp
   * Setting up iSCSI targets
 ...done.
  ssh stop/waiting
  ssh start/running, process 23415
  error: "net.ipv6.conf.eth0/4000:ucarp.autoconf" is an unknown key
  Failed to bring up eth0.4000:ucarp.

  /etc/network/interfaces:

  iface eth0.4000:ucarp inet6 static
address 2001:db8::7006
netmask 64

  Note: I'm running uCARP on the IPv4 address family, and expecting it
  to manage IPv6 address as well via `ifup $IFACE:ucarp` in
  /usr/share/ucarp/vip-up .

  I've tested with /sbin/ifup version 0.7.47.2ubuntu4 copied from a
  Trusty host and it works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: ifupdown 0.7~beta2ubuntu11.1
  ProcVersionSignature: Ubuntu 3.5.0-49.74~precise1-generic 3.5.7.32
  Uname: Linux 3.5.0-49-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Jul 22 22:23:10 2014
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1511545] Re: Implement XDMCP ForwardQuery

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

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

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

Title:
  Implement XDMCP ForwardQuery

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Released
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  LightDM ignores the XDMCP ForwardQuery request.

  [Test Case]
  1. Set up XDMCP so queries are forwarded through a server
  2. Connect to LightDM

  Observed result:
  Connection fails

  Expected result:
  Connection succeeds.

  [Regression Potential]
  Some risk of existing XDMCP queries being broken by the change. Checked with 
regression tests.

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


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


[Touch-packages] [Bug 1512781] Re: CVE-2015-5602 - Unauthorized Privilege Escalation

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: sudo (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  CVE-2015-5602 - Unauthorized Privilege Escalation

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Precise:
  Won't Fix
Status in sudo source package in Trusty:
  Confirmed
Status in sudo source package in Vivid:
  Confirmed
Status in sudo source package in Wily:
  Confirmed
Status in sudo source package in Xenial:
  Fix Released
Status in sudo package in Debian:
  Fix Released

Bug description:
  https://www.exploit-db.com/exploits/37710/

  As descpribed in the link above, sudo versions lower or equal than
  1.8.14 have a security issue: user with root access to a path with
  more than one wildcard can access forbidden files such as /etc/shadow,
  because sudoedit (sudo -e) does not verifiy full path of accessed
  file:

  (quote from link above)

  It seems that sudoedit does not check the full path if a wildcard is used
  twice (e.g. /home/*/*/file.txt), allowing a malicious user to replace the
  file.txt real file with a symbolic link to a different location (e.g.
  /etc/shadow).

  As an expample,

  1. Give user `usr' right to edit some his files:

  usr ALL=(root) NOPASSWD: sudoedit /home/*/*/test.txt

  2. Under usr, create ~/temp directory, and then create a symblink
  ~/temp/test.txt to /etc/shadow

  3. Perform sudoedit ~/temp/test.txt - you will able to access
  /etc/shadow.

  What realease is affected: tested on all supported now Ubuntu
  versions. For personaly me, it's 14.04 LTS.

  What version is affected: as mentioned, all versions <=1.8.14. For
  personally me, it's 1.8.9p5

  What was expected and happend instead: sudoedit should check full real
  path, but it didn't.

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


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


[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

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

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

Title:
  handle interruped read and write calls

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  New
Status in lightdm source package in Xenial:
  New
Status in lightdm source package in Yakkety:
  New
Status in lightdm source package in Zesty:
  Fix Released

Bug description:
  Use SA_RESTART flag to make sure that interrupted calls to read and/or
  write are restarted.

  In my case read is interrupted when reading login1_session_id. Result
  of not handling EINTR error is that login1_session_id is set to NULL
  and console_kit_cookie gets login1 session id.

  Related warnings in lightdm.log:
  [+0.44s] WARNING: Session pid=617: Error reading from session: Interrupted 
system call
  [+0.70s] DEBUG: Activating VT 7
  [+0.70s] DEBUG: Activating ConsoleKit session c1
  [+0.70s] WARNING: Error getting ConsoleKit session: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.ConsoleKit was not provided by any .service files

  And because login1_session_id is null fix for 1637758 bug does not
  work.

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


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


[Touch-packages] [Bug 1827391] Re: Japanese era Reiwa SRU

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: icu (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  Japanese era  Reiwa SRU

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Precise:
  Won't Fix
Status in icu source package in Trusty:
  Confirmed
Status in icu source package in Xenial:
  Confirmed
Status in icu source package in Bionic:
  Confirmed
Status in icu source package in Cosmic:
  Confirmed
Status in icu source package in Disco:
  Won't Fix
Status in icu source package in Eoan:
  Fix Released
Status in icu package in Debian:
  Fix Released

Bug description:
  Japanese era  Reiwa SRU

  $ rmadison icu
  4.8.1.1-3ubuntu0.7 | precise-updates
  52.1-3ubuntu0.8| trusty-updates
  55.1-7ubuntu0.4| xenial-updates
  60.2-3ubuntu3  | bionic
  60.2-6ubuntu1  | cosmic
  63.1-6 | disco
  63.1-6 | eoan

  Note reported abi break / crash of chromium at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933

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


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


[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2021-10-13 Thread Daniel van Vugt
Since this bug is closed, please open new bugs for any ongoing issues.
Just run:

  ubuntu-bug pulseaudio

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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


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


[Touch-packages] [Bug 1397316] Re: GObject signal functions make python apps crash

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: pygobject (Ubuntu Precise)
   Status: Triaged => Won't Fix

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

Title:
  GObject signal functions make python apps crash

Status in pygobject:
  Fix Released
Status in pygobject package in Ubuntu:
  Fix Released
Status in pygobject source package in Precise:
  Won't Fix

Bug description:
  Calling GObject signal functions (signal_handlers_block_matched,
  signal_handlers_unblock_matched and others) in a python app makes it
  crash. This bug has been fixed upstream for some newer versions of
  pygobject, but the older version (3.2.2-1~precise) in Ubuntu 12.04 is
  still affected.

  The test app (which crashes in Ubuntu 12.04) is in the attachment.

  
  Please fix it. Thanks in advance.

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


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


[Touch-packages] [Bug 632382] Re: Console font does not get set

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: console-setup (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  Console font does not get set

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Precise:
  Won't Fix
Status in console-setup source package in Quantal:
  Fix Released

Bug description:
  Binary package hint: console-setup

  Hello,

I upgraded Lucid to Maverick beta yesterday, and since then the
  console font does not get set properly. After talking with Colin
  Watson, and looking at the console-setup udev rule file
  (/lib/udev/rules.d/85-console-setup.rules). I understand that there is
  a possible race with Plymouth. So as suggested by Colin I created the
  attached upstart job (console-font.conf) to workaround the problem,
  and it worked !

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: console-setup 1.34ubuntu15
  ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
  Uname: Linux 2.6.35-19-generic i686
  Architecture: i386
  Date: Tue Sep  7 14:36:00 2010
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en_GB:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup

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


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


[Touch-packages] [Bug 923876] Re: FR: Limit and clean-up kernel images and headers automatically

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: aptitude (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  FR: Limit and clean-up kernel images and headers automatically

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Fix Released
Status in aptitude source package in Precise:
  Won't Fix
Status in apt source package in Quantal:
  Fix Released
Status in aptitude source package in Quantal:
  Won't Fix

Bug description:
  Question #186146 is one among multiple where user unintentionally collects 
multiple kernel images in particular with LTS. There is no hint from relevant 
package management application GUIs which advise to clean up those images. With 
future LTS support of five years the issue presumable will extend.
  Expected.
  After installation of a newer kernel image ask the user if previous kernel 
images should be removed.
  Checkbox: yes - no
  If yes, offer a list of installed kernel images, don't list the one booted. 
Advise to keep at least the last functional one.
  Also remove -headers.

  Perhaps an additional consideration for the blueprint.
  https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-lts-upgrades

  There is a new Quantal blueprint regarding the subject.
  https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-clean-old-kernels

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


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


[Touch-packages] [Bug 702802] Re: event "net-device-up" is triggered too early

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

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

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

Title:
  event "net-device-up" is triggered too early

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Precise:
  Won't Fix

Bug description:
  Binary package hint: ifupdown

  Hello,

  on booting, the event "net-device-up" is triggered too early. The
  event is "sent" to other jobs immediately after the ifup command has
  been executed, but neither ifup nor the calling script
  /etc/network/if-up.d/upstart perform a test if the network connection
  is really working. The result of this behaviour is that a job needing
  network functionality, e.g. mounting NFS filesystems, is possibly
  started before other network machines are reachable and makes the
  computer hang. This happens when the network interface needs some time
  to negotiate the ethernet parameters with the network switch.

  Regards
Christoph

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: ifupdown 0.6.8ubuntu29.2
  ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12
  Uname: Linux 2.6.32-27-generic x86_64
  Architecture: amd64
  Date: Fri Jan 14 10:27:30 2011
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: ifupdown

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


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


[Touch-packages] [Bug 381517] Re: Settings in /etc/kbd/config are not read

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: console-setup (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  Settings in /etc/kbd/config are not read

Status in console-setup package in Ubuntu:
  Confirmed
Status in kbd package in Ubuntu:
  Triaged
Status in console-setup source package in Precise:
  Won't Fix
Status in kbd source package in Precise:
  Triaged

Bug description:
  Binary package hint: kbd

  This concerns kbd 1.14.1-4ubuntu4 in Ubuntu Jaunty.

  I am setting up a text-mode-only server that will normally run
  headless. I want to disable console blanking, so that in the event of
  a kernel panic, I can attach a monitor and read the stack trace. So I
  make the following edits to /etc/kbd/config:

  * Set BLANK_TIME=0
  * Set BLANK_DPMS=on
  * Set POWERDOWN_TIME=0

  And still, the console blanks after about twenty minutes or so (not
  that I timed it). It shouldn't even be necessary to make all three of
  these changes---I believe setting BLANK_TIME=0 alone should do the
  trick---but it underscores the point that console blanking cannot be
  disabled here.

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


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


[Touch-packages] [Bug 981900] Re: glib-networking-services should depend on libproxy1-plugin-webkit

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: glib-networking (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  glib-networking-services should depend on libproxy1-plugin-webkit

Status in glib-networking package in Ubuntu:
  Confirmed
Status in glib-networking source package in Precise:
  Won't Fix
Status in glib-networking source package in Quantal:
  Won't Fix
Status in glib-networking source package in Raring:
  Won't Fix

Bug description:
  Currently, glib-networking-services only contains one binary: glib-
  pacrunner.

  glib-pacrunner runs PAC files using libproxy. However, in libproxy1,
  the pacrunner plugin has been split off into a separate package
  (libproxy1-plugin-webkit). As a result, PAC files which worked in
  previous versions of Ubuntu will no longer work in programs which use
  glib-networking for proxy resolution unless the package is manually
  installed.

  I did not test this against a fresh installation, but it's quite
  likely to be the case as well.

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


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


[Touch-packages] [Bug 983810] Re: libxml2 security update fails to address problem and breaks thread-safety

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: libxml2 (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  libxml2 security update fails to address problem and breaks thread-
  safety

Status in libxml2:
  Fix Released
Status in libxml2 package in Ubuntu:
  Fix Released
Status in libxml2 source package in Lucid:
  Won't Fix
Status in libxml2 source package in Precise:
  Won't Fix
Status in libxml2 source package in Trusty:
  Fix Released
Status in libxml2 package in Debian:
  New

Bug description:
  Using libxml2 2.7.8.dfsg-4ubuntu0.2 from (K)Ubuntu 11.10.

  In an attempt to address oCERT 2011-003, libxml2 now seeds its hash
  table with using rand(). This is broken and lame:

  Firstly, srand() and rand() are not thread-safe, even though libxml2
  is supposed to be thread-safe (when adequately initialized by the
  program). The fix is easy: replace srand() with a variable assignment,
  and replace rand() with rand_r().

  Secondly, using time(NULL) as a seed totally misses the point. It is
  trivial for a potential attacker to guess the value of time(NULL).
  That's the current UTC current time rounded to the second.

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


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


[Touch-packages] [Bug 985634] Re: Wrong translation during the installation process of Ubuntu with choosing Simple Chinese as the installation language

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

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

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

Title:
  Wrong translation during the installation process of Ubuntu  with
  choosing Simple Chinese as the installation language

Status in Ubuntu Translations:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Won't Fix
Status in apt source package in Quantal:
  Fix Released

Bug description:
  ISO version: precise-desktop-amd64.iso
  Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120418.2)
  Installation language: Simple Chinese

  Description:

  Wrong translation during the installation process of Ubuntu 12.04
  desktop version with Simple Chinese chosen as the installation
  language. Please refer to the attached picture

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


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


[Touch-packages] [Bug 997359] Re: nih uses eglibc private symbol __abort_msg

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

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

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

Title:
  nih uses eglibc private symbol __abort_msg

Status in libnih:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in libnih package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Won't Fix
Status in libnih source package in Precise:
  Won't Fix
Status in apport source package in Quantal:
  Won't Fix
Status in libnih source package in Quantal:
  Won't Fix
Status in apport source package in Raring:
  Fix Released
Status in libnih source package in Raring:
  Fix Released

Bug description:
  NIH uses the private eglibc '__abort_msg' symbol to save a string
  explaining why nih_assert() failed. However, __abort_msg is not a
  public symbol which causes problems when libc is upgraded - it
  actually necessitates that for every libc upgrade on, for example,
  Ubuntu systems the following has to happen:

  1) eglibc is upgraded with a version set to ~foo
  2) nih is rebuilt against the eglibc version
  3) nih is upgraded.
  4) the eglibc package is upgraded *again* to drop the ~foo.

  The symbol can be made use of like this:

  $ cat >foo.c
  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 "i686-linux-gnu".
  For bug reporting instructions, please see:
  ...
  Reading symbols from /home/james/src/c/foo...done.
  [New LWP 1597]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
  Core was generated by `foo'.
  Program terminated with signal 6, Aborted.
  #0  0xb770d1b2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
  (gdb) p (char *)__abort_msg
  $1 = 0x93fa098 "nih_make_core.c:46: Assertion failed in main: 0 == 1"
  (gdb)

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


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


[Touch-packages] [Bug 997359] Re: nih uses eglibc private symbol __abort_msg

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

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

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

Title:
  nih uses eglibc private symbol __abort_msg

Status in libnih:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in libnih package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Won't Fix
Status in libnih source package in Precise:
  Won't Fix
Status in apport source package in Quantal:
  Won't Fix
Status in libnih source package in Quantal:
  Won't Fix
Status in apport source package in Raring:
  Fix Released
Status in libnih source package in Raring:
  Fix Released

Bug description:
  NIH uses the private eglibc '__abort_msg' symbol to save a string
  explaining why nih_assert() failed. However, __abort_msg is not a
  public symbol which causes problems when libc is upgraded - it
  actually necessitates that for every libc upgrade on, for example,
  Ubuntu systems the following has to happen:

  1) eglibc is upgraded with a version set to ~foo
  2) nih is rebuilt against the eglibc version
  3) nih is upgraded.
  4) the eglibc package is upgraded *again* to drop the ~foo.

  The symbol can be made use of like this:

  $ cat >foo.c
  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 "i686-linux-gnu".
  For bug reporting instructions, please see:
  ...
  Reading symbols from /home/james/src/c/foo...done.
  [New LWP 1597]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
  Core was generated by `foo'.
  Program terminated with signal 6, Aborted.
  #0  0xb770d1b2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
  (gdb) p (char *)__abort_msg
  $1 = 0x93fa098 "nih_make_core.c:46: Assertion failed in main: 0 == 1"
  (gdb)

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


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


[Touch-packages] [Bug 1007826] Re: crash with AssertionError: file stream must be in binary mode when trying to save report to file

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: apport (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  crash with AssertionError: file stream must be in binary mode when
  trying to save report to file

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Won't Fix

Bug description:
  laney@raleigh> sudo apport-cli nova-common
  [...]
  What would you like to do? Your options are:
S: Send report (4.5 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): k
  Traceback (most recent call last):
File "/usr/bin/apport-cli", line 366, in 
  if not app.run_argv():
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 558, in run_argv
  return self.run_report_bug()
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 399, in 
run_report_bug
  response = self.ui_present_report_details(allowed_to_report)
File "/usr/bin/apport-cli", line 216, in ui_present_report_details
  self.report.write(os.fdopen(fd, 'w'))
File "/usr/lib/python2.7/dist-packages/problem_report.py", line 250, in 
write
  self._assert_bin_mode(file)
File "/usr/lib/python2.7/dist-packages/problem_report.py", line 628, in 
_assert_bin_mode
  assert (type(file) == BytesIO or 'b' in file.mode), 'file stream must be 
in binary mode'
  AssertionError: file stream must be in binary mode

  laney@raleigh> apt-cache policy apport
  apport:
Installed: 2.1.1-0ubuntu2
Candidate: 2.1.1-0ubuntu2
Version table:
   *** 2.1.1-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status

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


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


[Touch-packages] [Bug 1041221] Re: Network Manager gobbles CPU very frequently restarting dnsmasq in IPv6 networks

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: network-manager (Ubuntu Precise)
   Status: New => Won't Fix

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

Title:
  Network Manager gobbles CPU very frequently restarting dnsmasq in IPv6
  networks

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Precise:
  Won't Fix

Bug description:
  Hi,

  this may be related to this bug:
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/958519

  I lost my IPv6 some time ago, after my router was broken. I have now
  my IPv6 connection running again and to set the mininum time between
  router advertisements to 10s to be not affected too strong from the
  mentioned bug. The fix to this bug was simply suppressing error
  messages.

  But I was now curius what is happening at the network of my
  university, which got (at least some parts) IPv6. Here network manager
  eats up to 80% cpu, because it is restarting dnsmasq every second. If
  I disable dnsmasq in /etc/NetworkManager/NetworkManager.conf the cpu
  load drops to 20% to 30%. (syslog attached)

  You should fix this, because this eats the battery of my laptop and
  ubuntu 12.04 will be used a couple of years in which IPv6 will get
  more and more deployed.

  dgf

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Fri Aug 24 15:44:24 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:
   default via 134.169.35.65 dev wlan0  proto static 
   134.169.35.64/26 dev wlan0  proto kernel  scope link  src 134.169.35.124  
metric 2 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-02-14 (191 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.4.0connected   enabled   enabled 
enabledenabled enabled

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


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


[Touch-packages] [Bug 1061924] Re: Need Antenna quirks for some platforms

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release

** Changed in: udev (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  Need Antenna quirks for some platforms

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  New
Status in udev package in Ubuntu:
  Triaged
Status in network-manager source package in Precise:
  New
Status in udev source package in Precise:
  Won't Fix
Status in network-manager source package in Quantal:
  Won't Fix
Status in udev source package in Quantal:
  Won't Fix

Bug description:
  It has recently come to our attention that some laptops, in particular
  the lenovo b470 machines, have only one antenna. Unfortunately, they
  have decided to attach the auxilary antenna in the factory and not the
  main antenna. Udev sounds like the right place to quirk for this.

  Presently we're using an upstart job, the text of which is :

  # LenovoBx70eAtherosAntenna.conf
  #
  # Lenovo B[45]70e systems with Atheros AR9285 wifi only have one
  # antenna, but the ath9k driver defaults to using two antennas (Main
  # for Tx, Aux for Rx).  This job reconfigures the driver to use the
  # main antenna for both Tx and Rx before networking starts.

  description "Fix antenna configuration for Atheros wifi on
  b470e/b570e"

  start on starting networking

  task

  script
  # only required for Lenovo B470e and B570e
  dmidecode --string system-version | grep --quiet --line-regex "Lenovo 
B[45]70e" || exit 0
  
  # only required for Atheros AR9285 devices
  lspci -n | grep --quiet --extended-regexp "^[0-9a-f:.]* 0280: 
168c:002b" || exit 0

  # configure the device to use antenna 1 (Main) for both tx and rx
iw phy0 set antenna 1 1 
  end script

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


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


  1   2   3   >