[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs

2024-02-26 Thread Krister Johansen
Thanks for the update, Matthew.  We're looking forward to getting this
fix from Ubuntu.  My team patched our version the e2fsprogs package from
Focal about a year ago, before we submitted the fix upstream.  Since
that patch, we haven't had any re-occurrences of the problem.  It used
to show up about 4-5 times a day for us. Glad that the fix is working in
your tests as well.

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

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  In Progress
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  In Progress
Status in e2fsprogs source package in Jammy:
  In Progress
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in e2fsprogs source package in Mantic:
  In Progress

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions


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


[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs

2024-02-02 Thread Krister Johansen
Hi Matthew,
Thanks for the update. I'm glad this finally reproduced in your environment.  I 
don't have a great explanation for why it took so much longer there.  I did 
observe that it seemed more likely to occur in us-west-2 during the 9a-5p 
window in the local timezone. The timing may be subtly affected by overall EBS 
utilization.  Just a guess, though.

Thanks again,

-K

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

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  In Progress
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  In Progress
Status in e2fsprogs source package in Jammy:
  In Progress
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in e2fsprogs source package in Mantic:
  In Progress

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions


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


[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs

2024-01-11 Thread Krister Johansen
Hi Matthew,
Thanks for the update.  I went ahead and tested your updated packages on a 
Focal, Jammy, and Noble image in EC2 this evening.  With the latest packages 
installed, I was unable to reproduce the problem on any of the three installs.  
I'm uncertain which builds were inconsistent about triggering the problem for 
you, but it might be worth noting that the version of the package after Focal 
got an additional partial fix for the superblock checksum mismatch.  In those 
cases, it'll re-try the read of the block up to 3 times before returning a 
failure.  In my previous testing, this would increase the amount of time before 
one hits the problem, but not eliminate it entirely.

Thanks again for you help with getting these patches in.  It's much
appreciated!

-K

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

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  In Progress
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  In Progress
Status in e2fsprogs source package in Jammy:
  In Progress
Status in e2fsprogs source package in Lunar:
  In Progress
Status in e2fsprogs source package in Mantic:
  In Progress

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions


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


[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs

2023-12-18 Thread Krister Johansen
@mruffel just wanted to check back to see if the instructions in the
report worked to reproduce the problem for you.  If so, do you have any
estimate when packages with the patch will be made available?  Thanks!

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

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  In Progress
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  In Progress
Status in e2fsprogs source package in Jammy:
  In Progress
Status in e2fsprogs source package in Lunar:
  In Progress
Status in e2fsprogs source package in Mantic:
  In Progress

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions


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


[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs

2023-11-16 Thread Krister Johansen
Hi,
Just wanted to check back to see if the reproducer and fix worked in your 
testing environments.  I was also curious if it were possible to share any 
plans around when an update that contains this fix might be released.  Thanks 
again.

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

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  In Progress
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  In Progress
Status in e2fsprogs source package in Jammy:
  In Progress
Status in e2fsprogs source package in Lunar:
  In Progress
Status in e2fsprogs source package in Mantic:
  In Progress

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions


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


[Touch-packages] [Bug 2036467] Re: superblock checksum mismatch in resize2fs

2023-10-06 Thread Krister Johansen
Thanks for all the responses.  I'm not sure how quickly I'll be able to
get to this either, so I'm hesitant to commit to fixing myself.  That
said, if I can get time to send patches before your team gets to fixing
it, I'll do my best.

To answer the question about how frequently we see this: it was about
4-5 times a day until I applied the patches to our forked version of
e2fsprogs.

A few other things to note about what's going on here.  In 1.45.7,
e2fsprogs added some additional retries to the checksum validation path
on open:

https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=6338a8467564c3a0a12e9fcb08bdd748d736ac2f

I picked up this patch as well, and found that it helped a bit, but I
was still able to reproduce the problem with the reproducer that I
shared.

My team is running on the linux-aws-5.15 HWE kernel that's from jammy
but shipped to focal.  There's a kernel fix that may help with this
problem too, and it has been present since 5.10.  That said, I haven't
tested this on systems that are running 5.4.  (We don't have very many
of these anymore.)

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=05c2c00f3769abb9e323fcaca70d2de0b48af7ba

The 05c2c00f3769 ("ext4: protect superblock modifications with a buffer
lock") may help to ensure that the superblock contents are always
consistent on disk, prior to the DIO read, since the directio path
writes out any dirty cached sb pages prior to issuing the read.

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

Title:
  superblock checksum mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  Confirmed
Status in e2fsprogs source package in Focal:
  New
Status in e2fsprogs source package in Jammy:
  New
Status in e2fsprogs source package in Mantic:
  Confirmed

Bug description:
  Hi,
  We run ext4 on EBS volumes on EC2.  During provisioning, cloud-init will 
occasionally report that resize2fs has failed due to a superblock checksum 
mismatch.  We debugged this internally, and were able to come up with the 
following reproducer:

 #!/usr/bin/bash
 set -euxo pipefail

 while true
 do
 parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
 sleep .5
 mkfs.ext4 /dev/nvme1n1p1
 mount -t ext4 /dev/nvme1n1p1 /mnt
 stress-ng --temp-path /mnt -D 4 &
 STRESS_PID=$!
 sleep 1
 growpart /dev/nvme1n1 1
 resize2fs /dev/nvme1n1p1
 kill $STRESS_PID
 wait $STRESS_PID
 umount /mnt
 wipefs -a /dev/nvme1n1p1
 wipefs -a /dev/nvme1n1
 done

  (This was on a 60gb gp3 volume attached to a c5.4xlarge)

  We were able to find a fix that works and get the patch accepted
  upstream.  The short explanation is that by switching the superblock
  read to direct io, we no longer see the problem.

  The patch is available here, but hasn't been published in a released
  version of e2fsprogs:

  
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  A longer thread with the maintainer is available here:

  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This bug report is to request that Ubuntu backport this patch to the
  versions of e2fsprogs that are in releases that are available in
  images on AWS, preferably Focal and Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions


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


[Touch-packages] [Bug 2036467] [NEW] superblock checksum mismatch in resize2fs

2023-09-18 Thread Krister Johansen
Public bug reported:

Hi,
We run ext4 on EBS volumes on EC2.  During provisioning, cloud-init will 
occasionally report that resize2fs has failed due to a superblock checksum 
mismatch.  We debugged this internally, and were able to come up with the 
following reproducer:

   #!/usr/bin/bash
   set -euxo pipefail

   while true
   do
   parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
   sleep .5
   mkfs.ext4 /dev/nvme1n1p1
   mount -t ext4 /dev/nvme1n1p1 /mnt
   stress-ng --temp-path /mnt -D 4 &
   STRESS_PID=$!
   sleep 1
   growpart /dev/nvme1n1 1
   resize2fs /dev/nvme1n1p1
   kill $STRESS_PID
   wait $STRESS_PID
   umount /mnt
   wipefs -a /dev/nvme1n1p1
   wipefs -a /dev/nvme1n1
   done

(This was on a 60gb gp3 volume attached to a c5.4xlarge)

We were able to find a fix that works and get the patch accepted
upstream.  The short explanation is that by switching the superblock
read to direct io, we no longer see the problem.

The patch is available here, but hasn't been published in a released
version of e2fsprogs:

https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

A longer thread with the maintainer is available here:

https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

This bug report is to request that Ubuntu backport this patch to the
versions of e2fsprogs that are in releases that are available in images
on AWS, preferably Focal and Jammy.

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


** Tags: patch patch-accepted-upstream

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

Title:
  superblock checksum mismatch in resize2fs

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Hi,
  We run ext4 on EBS volumes on EC2.  During provisioning, cloud-init will 
occasionally report that resize2fs has failed due to a superblock checksum 
mismatch.  We debugged this internally, and were able to come up with the 
following reproducer:

 #!/usr/bin/bash
 set -euxo pipefail

 while true
 do
 parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
 sleep .5
 mkfs.ext4 /dev/nvme1n1p1
 mount -t ext4 /dev/nvme1n1p1 /mnt
 stress-ng --temp-path /mnt -D 4 &
 STRESS_PID=$!
 sleep 1
 growpart /dev/nvme1n1 1
 resize2fs /dev/nvme1n1p1
 kill $STRESS_PID
 wait $STRESS_PID
 umount /mnt
 wipefs -a /dev/nvme1n1p1
 wipefs -a /dev/nvme1n1
 done

  (This was on a 60gb gp3 volume attached to a c5.4xlarge)

  We were able to find a fix that works and get the patch accepted
  upstream.  The short explanation is that by switching the superblock
  read to direct io, we no longer see the problem.

  The patch is available here, but hasn't been published in a released
  version of e2fsprogs:

  
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  A longer thread with the maintainer is available here:

  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This bug report is to request that Ubuntu backport this patch to the
  versions of e2fsprogs that are in releases that are available in
  images on AWS, preferably Focal and Jammy.

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


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


[Touch-packages] [Bug 1928932] [NEW] external monitor disabled upon editing file with vim

2021-05-19 Thread Krister Swenson
Public bug reported:

This is the strangest bug I've encountered in my 20+ years of linux use.
See a video of the bug at: 
https://drive.google.com/file/d/1StYD5kbL5pLRBOc6V-TXuE5DgymTdM0R/view?usp=sharing

Using an external monitor I am editing a Snakefile with vim and syntax
highlighting. Under certain condition the monitor will go to sleep.

0. download the Snakefile, vimrc, and the colorscheme that are the attached 
archive
1. move the colorscheme to ~/.vim/colors/
1. `vim -u vimrc Snakefile`
2. delete one of the quotes, and see the external monitor go into sleep mode.

Pertinent points:
- If I disable the custom colorscheme or disable syntax highlighting there is 
no problem.
- If I move the gnome-terminal onto the builtin display, then the external 
monitor reactivates.

I wouldn't normally report this bug because it seems so specific to my
setup. What is alarming is that a vim session in a gnome-terminal, under
certain conditions, can cause the monitor to go to sleep!

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: libwayland-client0 1.18.0-2~exp1.1
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: 
Error executing command as another user: Request dismissed
Date: Wed May 19 12:14:23 2021
DistUpgraded: 2021-04-27 09:44:28,765 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1))
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.11.0-16-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.11.0-17-generic, x86_64: installed
 facetimehd, 0.1, 5.11.0-16-generic, x86_64: installed
 facetimehd, 0.1, 5.11.0-17-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b]
InstallationDate: Installed on 2021-01-19 (119 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: Apple Inc. MacBookAir6,2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=418e02d0-7fe0-4fe3-a1c4-ac2167ada4fe ro quiet splash vt.handoff=7
SourcePackage: wayland
UpgradeStatus: Upgraded to hirsute on 2021-04-27 (22 days ago)
acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
dmi.bios.date: 02/22/2021
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 431.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-7DF21CB3ED6977E5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-7DF21CB3ED6977E5
dmi.modalias: 
dmi:bvnAppleInc.:bvr431.0.0.0.0:bd02/22/2021:br0.1:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
dmi.product.family: MacBook Air
dmi.product.name: MacBookAir6,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute ubuntu wayland-session

** Attachment added: "sleep_bug.tgz"
   
https://bugs.launchpad.net/bugs/1928932/+attachment/5498718/+files/sleep_bug.tgz

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

Title:
  external monitor disabled upon editing file with vim

Status in wayland package in Ubuntu:
  New

Bug description:
  This is the strangest bug I've encountered in my 20+ years of linux use.
  See a video of the bug at: 
https://drive.google.com/file/d/1StYD5kbL5pLRBOc6V-TXuE5DgymTdM0R/view?usp=sharing

  Using an external monitor I am editing a Snakefile with vim and syntax
  highlighting. Under certain condition the 

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

2021-01-13 Thread Krister Swenson
The problem is still present in Ubuntu 20.10 :(

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

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

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

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

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

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

  Internal Speaker
  Pin ID: 0x12
  Internal speaker

  Pink Mic
  Pin ID: 0x18
  Not connected

  Internal Mic
  Pin ID: 0x1c
  Internal mic

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

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

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

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

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


[Touch-packages] [Bug 1880198] Re: Ubuntu as bluetooth speaker - volume on bluetooth client ignored

2020-11-26 Thread Krister Swenson
Thanks Sebastien, I've posted this bug upstream as
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1057

I've also noted some peculiarities with respect to different clients:

- computer: host/sink/server volume remains constant until source/client goes 
to 0, then silent
- Android phone: sink volume constant until the lowest 10% on source, then the 
volume decreases in 4 increments.
- ipad: sink volume constant no matter what the volume on the ipad source.

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1057
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1057

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

Title:
  Ubuntu as bluetooth speaker - volume on bluetooth client ignored

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm using my 20.04 system as a media center. It's got a bluetooth
  adapter plugged into a USB port. I can connect to the system with my
  phone and ipad as an A2DP source and play music.

  The problem is that the volume on the source device is not respected

  When the volume on the source device goes to 0, the sound is muted as
  expected, but any other volume on the source device leads to the same
  volume on the Ubuntu server. The only way to adjust the volume is from
  the server.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kodi   1455 F pulseaudio
   /dev/snd/controlC0:  kodi   1455 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 22 16:42:57 2020
  InstallationDate: Installed on 2015-09-30 (1695 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2404
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Touch-packages] [Bug 1880198] Re: Ubuntu as bluetooth speaker - volume on bluetooth client ignored

2020-11-25 Thread Krister Swenson
Would anyone have an idea as to a workaround, or an idea of how I could
debug this problem?

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

Title:
  Ubuntu as bluetooth speaker - volume on bluetooth client ignored

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm using my 20.04 system as a media center. It's got a bluetooth
  adapter plugged into a USB port. I can connect to the system with my
  phone and ipad as an A2DP source and play music.

  The problem is that the volume on the source device is not respected

  When the volume on the source device goes to 0, the sound is muted as
  expected, but any other volume on the source device leads to the same
  volume on the Ubuntu server. The only way to adjust the volume is from
  the server.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kodi   1455 F pulseaudio
   /dev/snd/controlC0:  kodi   1455 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 22 16:42:57 2020
  InstallationDate: Installed on 2015-09-30 (1695 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2404
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Touch-packages] [Bug 1880198] Re: Ubuntu as bluetooth speaker - volume on bluetooth client ignored

2020-11-25 Thread Krister Swenson
Is this bug filed against the correct package?

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

Title:
  Ubuntu as bluetooth speaker - volume on bluetooth client ignored

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm using my 20.04 system as a media center. It's got a bluetooth
  adapter plugged into a USB port. I can connect to the system with my
  phone and ipad as an A2DP source and play music.

  The problem is that the volume on the source device is not respected

  When the volume on the source device goes to 0, the sound is muted as
  expected, but any other volume on the source device leads to the same
  volume on the Ubuntu server. The only way to adjust the volume is from
  the server.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kodi   1455 F pulseaudio
   /dev/snd/controlC0:  kodi   1455 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 22 16:42:57 2020
  InstallationDate: Installed on 2015-09-30 (1695 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2404
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-29 Thread Krister
I installed 1.22.10-1ubuntu2.1 and turned the hotspot on...
   my clients can use the hotspot normally.

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

** Tags removed: verification-done
** Tags added: verification-needed

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  * Regression potential
  the change is only updating the iptables binary location, there shouldn't be 
any code impact out of having the command working on systems without usrmerge 
when it was not before

  -

  
  I have a machine with a wired network connection and a wifi card. I've been 
using the machine as a wireless router and server in my house. I've attached a 
screenshot of the Wi-Fi network settings. It looks as expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100
   169.254.0.0/16 dev eth0 scope link metric 1000
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:

  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1880198] [NEW] Ubuntu as bluetooth speaker - volume on bluetooth client ignored

2020-05-22 Thread Krister
Public bug reported:

I'm using my 20.04 system as a media center. It's got a bluetooth
adapter plugged into a USB port. I can connect to the system with my
phone and ipad as an A2DP source and play music.

The problem is that the volume on the source device is not respected

When the volume on the source device goes to 0, the sound is muted as
expected, but any other volume on the source device leads to the same
volume on the Ubuntu server. The only way to adjust the volume is from
the server.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  kodi   1455 F pulseaudio
 /dev/snd/controlC0:  kodi   1455 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 22 16:42:57 2020
InstallationDate: Installed on 2015-09-30 (1695 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2404
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H97M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


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

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

Title:
  Ubuntu as bluetooth speaker - volume on bluetooth client ignored

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm using my 20.04 system as a media center. It's got a bluetooth
  adapter plugged into a USB port. I can connect to the system with my
  phone and ipad as an A2DP source and play music.

  The problem is that the volume on the source device is not respected

  When the volume on the source device goes to 0, the sound is muted as
  expected, but any other volume on the source device leads to the same
  volume on the Ubuntu server. The only way to adjust the volume is from
  the server.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kodi   1455 F pulseaudio
   /dev/snd/controlC0:  kodi   1455 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 22 16:42:57 2020
  InstallationDate: Installed on 2015-09-30 (1695 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2404
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Touch-packages] [Bug 1879905] Re: Can no longer connect to Ubuntu WPA hotspot after upgrade to 20.04

2020-05-21 Thread Krister
The upstream report is here:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/2f8a4e90

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #450
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/450

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

Title:
  Can no longer connect to Ubuntu WPA hotspot  after upgrade to 20.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my Ubuntu client to 20.04 and could continue to connect to
  my WPA Hotspot running on an Ubuntu server. Upon update of the server
  to 20.04 I could no longer connect with any of my various client OSs.

  After using the updated network-manager from
  https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1870359, I can now connect to the hotspot from all of my
  machines running many flavors of OS (Windows, MacOS, Android, Ubuntu
  19.10), but I cannot connect from my machine running Ubuntu 20.04.

  If I turn off the encryption on the hotspot or turn on WEP encryption
  (using nm-connection-editor), then I can connect.

  Seeing that my client running 19.10 can connect, I'm not sure if this
  is a problem specif to my particular laptop running 20.04, or if it is
  rather a problem that any client updating to 20.04 will have. I will
  update my other 19.10 machine, that is currently working with the WPA
  hotspot, to help differentiate between these two possibilities.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 10:51:00 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   #dns-nameservers 8.8.8.8 8.8.4.4
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-10-31T09:47:24.831648
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1879905] Re: Can no longer connect to Ubuntu WPA hotspot after upgrade to 20.04

2020-05-21 Thread Krister
Oops..
  the upstream report is here:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/450

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

Title:
  Can no longer connect to Ubuntu WPA hotspot  after upgrade to 20.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my Ubuntu client to 20.04 and could continue to connect to
  my WPA Hotspot running on an Ubuntu server. Upon update of the server
  to 20.04 I could no longer connect with any of my various client OSs.

  After using the updated network-manager from
  https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1870359, I can now connect to the hotspot from all of my
  machines running many flavors of OS (Windows, MacOS, Android, Ubuntu
  19.10), but I cannot connect from my machine running Ubuntu 20.04.

  If I turn off the encryption on the hotspot or turn on WEP encryption
  (using nm-connection-editor), then I can connect.

  Seeing that my client running 19.10 can connect, I'm not sure if this
  is a problem specif to my particular laptop running 20.04, or if it is
  rather a problem that any client updating to 20.04 will have. I will
  update my other 19.10 machine, that is currently working with the WPA
  hotspot, to help differentiate between these two possibilities.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 10:51:00 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   #dns-nameservers 8.8.8.8 8.8.4.4
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-10-31T09:47:24.831648
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1879905] Re: Can no longer connect to Ubuntu WPA hotspot after upgrade to 20.04

2020-05-21 Thread Krister
Here are the relevant lines from jounalctrl:

May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1781] device 
(wlan0): Activation: starting connection 'Julep-WiFi' 
(7a3e625d-dfea-4423-aad6-a868b942407e)
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1796] manager: 
NetworkManager state is now CONNECTED_LOCAL
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1800] device 
(wlan0): supplicant interface state: completed -> disconnected
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1814] device 
(wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 
'managed')
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1822] manager: 
NetworkManager state is now CONNECTING
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1830] device 
(wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 
'managed')
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1836] device 
(wlan0): Activation: (wifi) access point 'Julep-WiFi' has security, but secrets 
are required.
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1836] device 
(wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 
'managed')
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1839] 
sup-iface[0x55942c627b00,wlan0]: wps: type pbc start...
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1904] device 
(wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 
'managed')
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1909] device 
(wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 
'managed')
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1919] device 
(wlan0): Activation: (wifi) connection 'Julep-WiFi' has security, and secrets 
exist.  No new secrets needed.
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1920] Config: 
added 'ssid' value 'Julep-WiFi'
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1920] Config: 
added 'scan_ssid' value '1'
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1920] Config: 
added 'bgscan' value 'simple:30:-70:86400'
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1921] Config: 
added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256'
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1921] Config: 
added 'auth_alg' value 'OPEN'
May 21 14:13:03 praxis NetworkManager[1177]:   [1590063183.1921] Config: 
added 'psk' value ''
May 21 14:13:03 praxis gsd-sharing[3984]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit 
gnome-remote-desktop.service not loaded.
May 21 14:13:03 praxis systemd[1]: Starting resolvconf-pull-resolved.service... 
 
May 21 14:13:03 praxis gnome-shell[239188]: An active wireless connection, in 
infrastructure mode, involves no access point?
May 21 14:13:03 praxis systemd[1]: resolvconf-pull-resolved.service: Succeeded. 
 
May 21 14:13:03 praxis systemd[1]: Finished resolvconf-pull-resolved.service.   
 
May 21 14:13:06 praxis wpa_supplicant[1263]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
May 21 14:13:06 praxis wpa_supplicant[1263]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
May 21 14:13:06 praxis wpa_supplicant[1263]: wlan0: CTRL-EVENT-REGDOM-CHANGE 
init=BEACON_HINT type=UNKNOWN
May 21 14:13:06 praxis wpa_supplicant[1263]: wlan0: Trying to associate with 
98:de:d0:1e:b1:6f (SSID='Julep-WiFi' freq=2412 MHz)
May 21 14:13:06 praxis wpa_supplicant[1263]: wlan0: Association request to the 
driver failed
May 21 14:13:06 praxis kernel: ERROR @wl_set_key_mgmt : 
 
May 21 14:13:06 praxis kernel: invalid cipher group (1027076)   
 
May 21 14:13:06 praxis NetworkManager[1177]:   [1590063186.4696] device 
(wlan0): supplicant interface state: disconnected -> scanning
May 21 14:13:09 praxis kernel: ERROR @wl_set_key_mgmt : 
 
May 21 14:13:09 praxis kernel: invalid cipher group (1027076)   
 
May 21 14:13:09 praxis wpa_supplicant[1263]: wlan0: Trying to associate with 
98:de:d0:1e:b1:6f (SSID='Julep-WiFi' freq=2412 MHz)
May 21 14:13:09 praxis wpa_supplicant[1263]: wlan0: Association request to the 
driver failed
May 21 14:13:09 praxis NetworkManager[1177]:   [1590063189.7244] device 
(wlan0): supplicant interface state: scanning -> disconnected
May 21 14:13:10 praxis NetworkManager[1177]:   [1590063190.2259] device 
(wlan0): supplicant interface state: disconnected -> scanning
May 21 14:13:13 praxis wpa_supplicant[1263]: wlan0: Trying to associate with 
98:de:d0:1e:b1:6f (SSID='Julep-WiFi' freq=2412 MHz)
May 21 14:13:13 praxis wpa_supplicant[1263]: wlan0: Association request to the 
driver failed
May 21 14:13:13 praxis kernel: ERROR @wl_set_key_mgmt : 
 
May 21 14:13:13 praxis kernel: invalid cipher group (1027076)   
 
May 21 14:13:13 praxis NetworkManager[1177]:   

[Touch-packages] [Bug 1879905] [NEW] Can no longer connect to Ubuntu WPA hotspot after upgrade to 20.04

2020-05-21 Thread Krister
Public bug reported:

I upgraded my Ubuntu client to 20.04 and could continue to connect to my
WPA Hotspot running on an Ubuntu server. Upon update of the server to
20.04 I could no longer connect with any of my various client OSs.

After using the updated network-manager from
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359,
I can now connect to the hotspot from all of my machines running many
flavors of OS (Windows, MacOS, Android, Ubuntu 19.10), but I cannot
connect from my machine running Ubuntu 20.04.

If I turn off the encryption on the hotspot or turn on WEP encryption
(using nm-connection-editor), then I can connect.

Seeing that my client running 19.10 can connect, I'm not sure if this is
a problem specif to my particular laptop running 20.04, or if it is
rather a problem that any client updating to 20.04 will have. I will
update my other 19.10 machine, that is currently working with the WPA
hotspot, to help differentiate between these two possibilities.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 21 10:51:00 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
 #dns-nameservers 8.8.8.8 8.8.4.4
IpRoute:
 default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 600 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-10-31T09:47:24.831648
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug focal

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

Title:
  Can no longer connect to Ubuntu WPA hotspot  after upgrade to 20.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my Ubuntu client to 20.04 and could continue to connect to
  my WPA Hotspot running on an Ubuntu server. Upon update of the server
  to 20.04 I could no longer connect with any of my various client OSs.

  After using the updated network-manager from
  https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1870359, I can now connect to the hotspot from all of my
  machines running many flavors of OS (Windows, MacOS, Android, Ubuntu
  19.10), but I cannot connect from my machine running Ubuntu 20.04.

  If I turn off the encryption on the hotspot or turn on WEP encryption
  (using nm-connection-editor), then I can connect.

  Seeing that my client running 19.10 can connect, I'm not sure if this
  is a problem specif to my particular laptop running 20.04, or if it is
  rather a problem that any client updating to 20.04 will have. I will
  update my other 19.10 machine, that is currently working with the WPA
  hotspot, to help differentiate between these two possibilities.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 10:51:00 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   #dns-nameservers 8.8.8.8 8.8.4.4
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-10-31T09:47:24.831648
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: 

[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-21 Thread Krister
@seb128 Which package do you want me to report this against?
ubuntu-bug will not let me do it against network-manager because it is "not an 
official Ubuntu package".

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  * Regression potential
  the change is only updating the iptables binary location, there shouldn't be 
any code impact out of having the command working on systems without usrmerge 
when it was not before

  -

  
  I have a machine with a wired network connection and a wifi card. I've been 
using the machine as a wireless router and server in my house. I've attached a 
screenshot of the Wi-Fi network settings. It looks as expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100
   169.254.0.0/16 dev eth0 scope link metric 1000
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:

  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-20 Thread Krister
The "always gray" issue is indeed solved by clicking out of the wifi
setting and then back in.

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-20 Thread Krister
On the computer with the hotspot, if I make the network open, with no
WPA, then I can connect and use the hotspot with all machines.

If I enable WEP in the hotspot settting (nm-connection-editor), all
machines can still connect and use the hotspot.

If I enbale WPA in the hotspot settings (nm-connection-editor), then my
Ubuntu laptop (another machine) cannot connect to the hotspot, while all
other machines can.

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-20 Thread Krister
With the new packages installed I can now connect and use the hotspot as long 
as the WPA is disabled.
Thanks for the fix!

As soon as I re-enable the WPA, I can no longer connect with my Ubuntu laptop.
I can, however, connect from Android, Windows 10, and MacOS when the WPA in 
enabled.

Is this a different Ubuntu client bug?

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-20 Thread Krister
Another related bug is that the "Turn On WiFi Hotspots..." menu item is
always gray. The only way I can create or modify a hotspot is using the
nm-connection-editor. Is this a bug I should report elsewhere?

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-19 Thread Krister
/usr/sbin/iptables is a symlink to another name with is linked to
another name which is linked to /usr/sbin/xtables-legacy-multi

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-19 Thread Krister
=> which iptables
/usr/sbin/iptables

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-19 Thread Krister
=> iptables --version
iptables v1.8.4 (legacy)

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-18 Thread Krister
1. I removed the network from the Wi-Fi setting and "Turn On Wi-Fi Hotspot..." 
is not grayed out.
2. I opened nm-connection-editor and click the +, then "Wi-Fi", then chose:
  - Mode: Hotspot
  - Device: wlp3s0
  - No security
3. I connect with Ubuntu from another machine. There does appear to be a 
connection (WiFi settings has a check mark next to the network), but there is 
no internet and the icon remains a question mark.

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-18 Thread Krister
** Attachment added: "jrnlctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+attachment/5373391/+files/jrnlctl.txt

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-04-29 Thread Krister
Hello, could someone please help me debug this problem?

This ubuntu 20.04 box is the only viable wifi router in my house!
I'm considering downgrading my system, but would prefer to find the bug.

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1870359] [NEW] My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-04-02 Thread Krister
Public bug reported:

I have a machine with a wired network connection and a wifi card. I've
been using the machine as a wireless router and server in my house. I've
attached a screenshot of the Wi-Fi network settings. It looks as
expected.

Upon updating to 20.04, none of my machines can use the connection. The
linux machine will not connect. The windows machine will connect but
will not have internet.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  2 15:47:02 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-09-30 (1645 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IpRoute:
 default via 192.168.0.1 dev eth0 proto static metric 100 
 169.254.0.0/16 dev eth0 scope link metric 1000 
 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
WifiSyslog:
 
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

** Attachment added: "hotspot.png"
   
https://bugs.launchpad.net/bugs/1870359/+attachment/5344883/+files/hotspot.png

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

2018-04-04 Thread Krister
Gnome-shell will freeze at unexpected times when using the firefox
browser.  The symptoms are the same as when watching videos with totem.
I've switched to chrome without having gnome-shell freeze on me.

Is there something particular about the way firefox 59 (Quantum)
interacts with my graphics hardware?

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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


[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

2018-03-16 Thread Krister
Today the fuzzy screen depicted in the attachment appears spontaneously
while using google maps.  This time with a block around the pointer,
that continued to move with the pointer.

** Attachment added: "IMG_20180316_172748_697.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1752145/+attachment/5081615/+files/IMG_20180316_172748_697.jpg

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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


[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

2018-03-15 Thread Krister
This bug is making it hard to work...
   I just had the system freeze up on me again after less than 5 minutes.
This time, when doing ctrl-alt-F3 I got the strange snow-like screen depicted 
in the attachement and none of the ctrl-alt terminals or GDM (at ctrl-alt-F1) 
showed anything but snow!

** Attachment added: "snowy screen  after freeze and pressing ctrl-alt-F3"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1752145/+attachment/5080321/+files/IMG_20180315_134524_146.jpg

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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


[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

2018-03-15 Thread Krister
More symptoms:

I can kill gnome-shell with "kill -KILL" from a ctrl-alt terminal.
The GDM screen then appears as usual.  Logging in again, however, seems to hang 
on a blank purple screen.

The GDM screen appears normal but moving the mouse over the top-right
corner to activate the menu results in EXTREME lag.  The menu is usable
but doesn't update for dozens of seconds after clicking on it.

Could this be a problem with XWayland?

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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


[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

2018-03-14 Thread Krister
I'm able to interact with the system normally using the ctrl-alt-F3
terminal, although none of the methods listed in
https://askubuntu.com/questions/455301/how-to-restart-gnome-shell-after-
it-became-unresponsive-freeze/496999 properly restart gnome-shell.  It
seems to be related to graphics.

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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


[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

2018-03-14 Thread Krister
I tried using Unity instead of gnome-shell and am experiencing the same 
problem.  Does this mean it's not a problem with mutter?
What is worse, is that this problems seems to crop up every day or so during 
work.  In other words, everything will freeze except for the mouse even if I've 
never watched a video.

Could you please tell me details on how to get the best debug
information for you?

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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


[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

2018-03-05 Thread Krister
I'm sorry for dumping the dmesg output into the thread.  Here it is in a
file.  But it's from after reboot.  Does this have the error messages in
it from the previous session?  Do I have to get a file from /var/log/ ?

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1752145/+attachment/5070185/+files/dmesg.txt

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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


[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

2018-03-05 Thread Krister
Here's dmesg after a freeze of the system when watching a video with
VLC.  The strange snow did not show up this time:

=> dmesg
[0.00] Linux version 4.15.0-10-generic (buildd@lgw01-amd64-036) (gcc 
version 7.3.0 (Ubuntu 7.3.0-3ubuntu1)) #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 
2018 (Ubuntu 4.15.0-10.11-generic 4.15.3)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=7
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0003efff] usable
[0.00] BIOS-e820: [mem 0x0003f000-0x0003] reserved
[0.00] BIOS-e820: [mem 0x0004-0x0009] usable
[0.00] BIOS-e820: [mem 0x0010-0xc93bcfff] usable
[0.00] BIOS-e820: [mem 0xc93bd000-0xc9f5cfff] reserved
[0.00] BIOS-e820: [mem 0xc9f5d000-0xc9fc3fff] ACPI data
[0.00] BIOS-e820: [mem 0xc9fc4000-0xcac90fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xcac91000-0xcb10efff] reserved
[0.00] BIOS-e820: [mem 0xcb10f000-0xcb172fff] type 20
[0.00] BIOS-e820: [mem 0xcb173000-0xcb173fff] usable
[0.00] BIOS-e820: [mem 0xcb174000-0xcb181fff] reserved
[0.00] BIOS-e820: [mem 0xcb182000-0xccff] usable
[0.00] BIOS-e820: [mem 0xcd00-0xcdff] reserved
[0.00] BIOS-e820: [mem 0xd000-0xdfff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00082fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.40 by American Megatrends
[0.00] efi:  ACPI=0xc9f72000  ACPI 2.0=0xc9f72000  SMBIOS=0xf 
[0.00] secureboot: Secure boot could not be determined (mode 0)
[0.00] random: fast init done
[0.00] SMBIOS 2.8 present.
[0.00] DMI: Dell Inc. Precision Tower 7810/0KJCC5, BIOS A20 07/26/2017
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x83 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-D write-protect
[0.00]   E-F uncachable
[0.00] MTRR variable ranges enabled:
[0.00]   0 base E000 mask 3FFFE000 uncachable
[0.00]   1 base D000 mask 3000 uncachable
[0.00]   2 base 0300 mask 3F80 uncachable
[0.00]   3 base CE00 mask 3E00 uncachable
[0.00]   4 base E000 mask 3000 write-through
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.00] e820: last_pfn = 0xcd000 max_arch_pfn = 0x4
[0.00] Scanning 1 areas for low memory corruption
[0.00] Base memory trampoline at [(ptrval)] 99000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x60c93e000, 0x60c93efff] PGTABLE
[0.00] BRK [0x60c93f000, 0x60c93] PGTABLE
[0.00] BRK [0x60c94, 0x60c940fff] PGTABLE
[0.00] BRK [0x60c941000, 0x60c941fff] PGTABLE
[0.00] BRK [0x60c942000, 0x60c942fff] PGTABLE
[0.00] BRK [0x60c943000, 0x60c943fff] PGTABLE
[0.00] BRK [0x60c944000, 0x60c944fff] PGTABLE
[0.00] BRK [0x60c945000, 0x60c945fff] PGTABLE
[0.00] RAMDISK: [mem 0x31b2d000-0x34d8dfff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0xC9F72000 24 (v02 DELL  )
[0.00] ACPI: XSDT 0xC9F72098 B4 (v01 DELL   CBX3 
01072009 AMI  00010013)
[0.00] ACPI: FACP 0xC9F9DEC8 00010C (v05 DELL   CBX3 
01072009 AMI  00010013)
[0.00] ACPI: DSDT 0xC9F721E0 02BCE1 (v02 DELL   

[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

2018-03-05 Thread Krister
=> lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
DMI2 (rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2
00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 1 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 1 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 2 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.2 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.3 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:05.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D Map/VTd_Misc/System Management (rev 01)
00:05.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D IIO Hot Plug (rev 01)
00:05.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D IIO RAS/Control Status/Global Errors (rev 01)
00:05.4 PIC: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC 
(rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC
00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR 
(rev 05)
Subsystem: Dell C610/X99 series chipset SPSR
00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset USB xHCI Host Controller
Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI 
Controller #1 (rev 05)
Subsystem: Dell C610/X99 series chipset MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
00:16.2 IDE interface: Intel Corporation C610/X99 series chipset IDE-r 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset IDE-r Controller
Kernel driver in use: ata_generic
Kernel modules: pata_acpi
00:16.3 Serial controller: Intel Corporation C610/X99 series chipset KT 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset KT Controller
Kernel driver in use: serial
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 
05)
Subsystem: Dell Ethernet Connection I217-LM
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced 
Host Controller #2 (rev 05)
Subsystem: Dell C610/X99 series chipset USB Enhanced Host Controller
Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset HD Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root 
Port #1 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root 
Port #2 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root 
Port #3 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced 
Host Controller #1 (rev 05)
Subsystem: Dell C610/X99 series chipset USB Enhanced Host Controller
Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller 
(rev 05)
Subsystem: Dell C610/X99 series chipset LPC Controller
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA 
Controller [AHCI mode] (rev 05)
Subsystem: Dell C610/X99 series chipset 6-Port SATA Controller [AHCI 
mode]
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation C610/X99 series chipset SMBus Controller (rev 
05)
Subsystem: Dell C610/X99 series 

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2017-03-06 Thread Krister Trangius
I updated to kernel 4.10.1 but still no success. I also tried the
solutions mentioned above, but with no success :(

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

Title:
  [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
  while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a strange behavior with a headphone jack on my
  laptop.

  I have an external audio speaker connected to it. When I disconnect the 
speaker and reconnect it again it stops working.
  Even more, laptop audio stops working too. And after the reboot, I don't even 
see any of the audio devices.

  I've googled a lot and tried different fixes from forums with no luck.
  After a while, I've accidentally discovered that putting the laptop to
  the sleep mode and rebooting system after brings audio back to live.
  Even more, if speakers were attached during this sleep-reboot
  procedure, they are starting to work as well.

  However, after the next reboot speakers are not working again. And if
  I will plug them out and in - problem with completely missing audio
  returns.

  P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
  hibernation made me believe that it's somehow related. But after
  uninstalling this package nothing really changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   kop3224 F...m pulseaudio
   /dev/snd/controlC0:  kop3224 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 12:17:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after 
a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2017-03-06 Thread Krister Trangius
I have the same issue. None of the solutions described above works for
me (suspend/resume, Vart van Deenen's solution, "sudo alsa force-reload"
or anything else). The settings in control center/sound detects that the
headphones are plugged in, but sound comes out of them.

Sound from speakers work fine, also headphones with USB DAC/amplifier
works.

Laptop Dell XPS 9550
Unbuntu Gnome 16.10
BIOS 1.2.19

uname -a
Linux elefant 4.8.0-39-generic #42-Ubuntu SMP Mon Feb 20 11:47:27 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
  while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a strange behavior with a headphone jack on my
  laptop.

  I have an external audio speaker connected to it. When I disconnect the 
speaker and reconnect it again it stops working.
  Even more, laptop audio stops working too. And after the reboot, I don't even 
see any of the audio devices.

  I've googled a lot and tried different fixes from forums with no luck.
  After a while, I've accidentally discovered that putting the laptop to
  the sleep mode and rebooting system after brings audio back to live.
  Even more, if speakers were attached during this sleep-reboot
  procedure, they are starting to work as well.

  However, after the next reboot speakers are not working again. And if
  I will plug them out and in - problem with completely missing audio
  returns.

  P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
  hibernation made me believe that it's somehow related. But after
  uninstalling this package nothing really changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   kop3224 F...m pulseaudio
   /dev/snd/controlC0:  kop3224 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 12:17:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after 
a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2016-11-29 Thread Krister
@mulletinc:  Thank you!
Comment #18 solved the problem for me.

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2016-10-24 Thread Krister
*** This bug is a duplicate of bug 1342123 ***
https://bugs.launchpad.net/bugs/1342123

In "Online Accounts" settings, I removed my Google account completely.
This has not fixed the problem with indicator-datetime-service using all
of my memory and swap.

Please remove the duplicate marking.

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2016-10-18 Thread Krister
*** This bug is a duplicate of bug 1342123 ***
https://bugs.launchpad.net/bugs/1342123

I found the correct Setting manager (the other one was for Unity8?) and
have tried to reproduce the behavior described by Jonathan.  Disabling
the "Evolution Data Server" entry for my calendar does not fix the
problem.  All 8G of memory and 8G of swap gets devoured in under 10
seconds.

I think that marking this a duplicate of bug #1342123 is a mistake for
two reasons:

1. bug #1342123 is a bug for mobile system (the corresponding bug for
the desktop is bug #1589605)

2. they are talking about rather modest amounts of memory usage like
100MB, not 16G.

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2016-10-17 Thread Krister
This occurs on both my desktop and laptop.

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2016-10-17 Thread Krister
@brierjon:  I don't see the same thing that you do in 16.10 (see attachment).
I am missing a Google account setting.


** Attachment added: "Scronlineaccounts.png"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+attachment/4762383/+files/Scronlineaccounts.png

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2016-10-17 Thread Krister
This is urgent, as it renders and upgraded system completely useless.

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


[Touch-packages] [Bug 1634059] [NEW] indicator-datetime-service devours memory rendering system useless

2016-10-17 Thread Krister
*** This bug is a duplicate of bug 1633319 ***
https://bugs.launchpad.net/bugs/1633319

Public bug reported:

Upon upgrading to 16.10, yakkety yak, I cannot load Unity because the
indicator-datetime-service devours memory at an incredible pace before
being automatically killed, and restarting to devour all over again!

The workaround I found is to open a virtual terminal  and
then log into unity while quickly switching back to the the F1 terminal.
I then repeatedly do "killall -KILL indicator-datetime-service" until it
stops coming back.

This is a major bug in that it renders the entire system unusable.  It
happened on both my laptop and my desktop after upgrade to 16.10.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 17 11:02:54 2016
InstallationDate: Installed on 2014-10-13 (735 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
SourcePackage: indicator-datetime
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (2 days ago)

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


** Tags: amd64 apport-bug yakkety

** This bug has been marked a duplicate of bug 1633319
   memory leak in indicator-datetime

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

Title:
  indicator-datetime-service devours memory rendering system useless

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Upon upgrading to 16.10, yakkety yak, I cannot load Unity because the
  indicator-datetime-service devours memory at an incredible pace before
  being automatically killed, and restarting to devour all over again!

  The workaround I found is to open a virtual terminal 
  and then log into unity while quickly switching back to the the F1
  terminal.  I then repeatedly do "killall -KILL indicator-datetime-
  service" until it stops coming back.

  This is a major bug in that it renders the entire system unusable.  It
  happened on both my laptop and my desktop after upgrade to 16.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 17 11:02:54 2016
  InstallationDate: Installed on 2014-10-13 (735 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (2 days ago)

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

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


[Touch-packages] [Bug 1596513] Re: "save to" dialogue no longer has recent folders list

2016-06-28 Thread Krister
gedit DOES have the issue.

Gimp, Inscape, LibreOffice do NOT.

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

Title:
  "save to" dialogue no longer has recent folders list

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  In 16.04 the recent files/folders category when saving a file has
  disappeared.

  This feature saved many clicks for me (as long as the distraction of
  thinking about my file heirarchy).

  A common use case is the following:

  1. Create a presentation with Libre Office in a new directory call 
"newpresentation".
  2. Search for an image on the internet to include in the presentation.
  3. click "save as".

  Now, one has to traverse the entire path to the folder in which the 
presentation is saved.
  Before, with the recent files/folders tab I was able to just choose 
"newpresentation" from the list...
 this type of thing is very common for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160526.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jun 27 13:52:02 2016
  DistUpgraded: 2016-04-26 18:48:25,435 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[1028:0577]
  InstallationDate: Installed on 2014-10-13 (623 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  MachineType: Dell Inc. OptiPlex 7010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=33ba6095-36ce-4b66-ba92-ad16532a4e50 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (61 days ago)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0773VG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  upstart.unity7.log:
   WARN  2016-06-27 13:11:38 unity.iconloader IconLoader.cpp:264 Unable to load 
icon . GThemedIcon application-x-homebank application-x-generic at size 64
   WARN  2016-06-27 13:51:54 unity.iconloader IconLoader.cpp:264 Unable to load 
icon . GThemedIcon application-x-homebank application-x-generic at size 64
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jun 27 11:40:26 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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


[Touch-packages] [Bug 1596513] Re: "save to" dialogue no longer has recent folders list

2016-06-28 Thread Krister
The use case I point to is actually the Firefox "save to" dialogue.

Now that I look at it...
  this seems to be a problem with firefox.  The other applications do include 
the recent files dialogue.

Sorry for the false alarm.

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

** Changed in: ubuntu
   Status: Incomplete => Invalid

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

Title:
  "save to" dialogue no longer has recent folders list

Status in Ubuntu:
  Invalid

Bug description:
  In 16.04 the recent files/folders category when saving a file has
  disappeared.

  This feature saved many clicks for me (as long as the distraction of
  thinking about my file heirarchy).

  A common use case is the following:

  1. Create a presentation with Libre Office in a new directory call 
"newpresentation".
  2. Search for an image on the internet to include in the presentation.
  3. click "save as".

  Now, one has to traverse the entire path to the folder in which the 
presentation is saved.
  Before, with the recent files/folders tab I was able to just choose 
"newpresentation" from the list...
 this type of thing is very common for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160526.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jun 27 13:52:02 2016
  DistUpgraded: 2016-04-26 18:48:25,435 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[1028:0577]
  InstallationDate: Installed on 2014-10-13 (623 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  MachineType: Dell Inc. OptiPlex 7010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=33ba6095-36ce-4b66-ba92-ad16532a4e50 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (61 days ago)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0773VG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  upstart.unity7.log:
   WARN  2016-06-27 13:11:38 unity.iconloader IconLoader.cpp:264 Unable to load 
icon . GThemedIcon application-x-homebank application-x-generic at size 64
   WARN  2016-06-27 13:51:54 unity.iconloader IconLoader.cpp:264 Unable to load 
icon . GThemedIcon application-x-homebank application-x-generic at size 64
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jun 27 11:40:26 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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


[Touch-packages] [Bug 1532440] [NEW] touchpad setting missing when using a wireless keyboard with touchpad

2016-01-09 Thread Krister
Public bug reported:

1. Plug in a wireless keyboard with a built-in trackpad (I have the logitech 
K400 Plus).
2. open dconf-editor
3. go to org > gnome > settings-daemon > peripherals
4. see that there is no "touchpad" entry

My laptop has a touchpad entry that allows me to adjust touchpad-specific 
parameters.
I would expect these to show up with the wireless keyboard/touchpad.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: dconf-cli 0.24.0-2
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jan  9 14:41:02 2016
InstallationDate: Installed on 2015-09-30 (100 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
JournalErrors:
 No journal files were found.
 -- No entries --
SourcePackage: d-conf
UpgradeStatus: Upgraded to wily on 2015-11-01 (68 days ago)

** Affects: d-conf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  touchpad setting missing when using a wireless keyboard with touchpad

Status in d-conf package in Ubuntu:
  New

Bug description:
  1. Plug in a wireless keyboard with a built-in trackpad (I have the logitech 
K400 Plus).
  2. open dconf-editor
  3. go to org > gnome > settings-daemon > peripherals
  4. see that there is no "touchpad" entry

  My laptop has a touchpad entry that allows me to adjust touchpad-specific 
parameters.
  I would expect these to show up with the wireless keyboard/touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: dconf-cli 0.24.0-2
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan  9 14:41:02 2016
  InstallationDate: Installed on 2015-09-30 (100 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  JournalErrors:
   No journal files were found.
   -- No entries --
  SourcePackage: d-conf
  UpgradeStatus: Upgraded to wily on 2015-11-01 (68 days ago)

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

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


[Touch-packages] [Bug 1449654] [NEW] windows can be resized from wrong workspace

2015-04-28 Thread Krister
Public bug reported:

1. Setup multiple workspaces.
2. Create a window and move it so that the right side of the window is at the 
right edge of the workspace (but not past the right edge).
3. Move right one workspace.

See that you can grab the window from the workspace to the left and
resize it into the current workspace.

I shouldn't be able to grab a window from another workspace.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity 7.3.2+15.04.20150420-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Tue Apr 28 18:20:44 2015
InstallationDate: Installed on 2014-10-13 (197 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923)
SourcePackage: unity
UpgradeStatus: Upgraded to vivid on 2015-04-25 (3 days ago)

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


** Tags: amd64 apport-bug third-party-packages vivid

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

Title:
  windows can be resized from wrong workspace

Status in unity package in Ubuntu:
  New

Bug description:
  1. Setup multiple workspaces.
  2. Create a window and move it so that the right side of the window is at the 
right edge of the workspace (but not past the right edge).
  3. Move right one workspace.

  See that you can grab the window from the workspace to the left and
  resize it into the current workspace.

  I shouldn't be able to grab a window from another workspace.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 28 18:20:44 2015
  InstallationDate: Installed on 2014-10-13 (197 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (3 days ago)

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

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


[Touch-packages] [Bug 1311724] Re: Macbook Air resumes immidiately after suspend

2014-10-27 Thread Krister
This seems to work all the time when the computer is unplugged...
  when plugged in, it seems to work most of the time.

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

Title:
  Macbook Air resumes immidiately after suspend

Status in “pm-utils” package in Ubuntu:
  Confirmed

Bug description:
  Computer model : Apple Macbook Air 6,2 (Mid 2013)
  BIOS version   : MBA61.88Z.0099.B04 (dmidecode -s bios-version), Oct. 2013 
version
  OS installed   : Ubuntu 14.04, single boot

  Problem description:
   
  When closing lid on computer machine suspends. Within 8 to 10 seconds the 
machine resumes again with lid still closed. Imidiately opening an closing lid 
makes suspends the computer and it keeps suspended until lid is opened again.

  This behaviour is the same when entering a sudo pm-suspend from the
  terminal. Machine suspends. But resumes after 8 to 10 seconds.
  Immidiately doing a second sudo pm-suspend, suspends the machine and
  keeps it suspended.

  There is one case where the behaviour described above is different.
  That is in the situation where machine is put into suspend for the
  first time after a complete reboot. In this case the machine suspends
  correctly and stays suspended as expected.

  The problem is consistent and can be reproduced as desribed any number
  of times.

  Disabling wi-fi (using the Broadcom 802.11 Linux STA proprietary
  driver) doesn't alter the behaviour described above.

  
  cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  P0P2S3*disabled
  EC  S3*disabled
  HDEFS3*disabled  pci::00:1b.0
  RP01S3*disabled  pci::00:1c.0
  RP02S3*disabled  pci::00:1c.1
  RP03S3*disabled  pci::00:1c.2
  ARPTS4*disabled  pci::03:00.0
  RP05S3*disabled  pci::00:1c.4
  RP06S3*disabled  pci::00:1c.5
  SPITS3*disabled
  XHC1S3*enabled   pci::00:14.0
  ADP1S3*disabled  platform:ACPI0003:00
  LID0S3*enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 23 17:03:05 2014
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64+mac 
(20140417)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1311724] Re: Macbook Air resumes immidiately after suspend

2014-10-17 Thread Krister
The workaround in #4 works for me as long as I do (as root):
 echo medium_power  /sys/class/scsi_host/host0/link_power_management_policy

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

Title:
  Macbook Air resumes immidiately after suspend

Status in “pm-utils” package in Ubuntu:
  Confirmed

Bug description:
  Computer model : Apple Macbook Air 6,2 (Mid 2013)
  BIOS version   : MBA61.88Z.0099.B04 (dmidecode -s bios-version), Oct. 2013 
version
  OS installed   : Ubuntu 14.04, single boot

  Problem description:
   
  When closing lid on computer machine suspends. Within 8 to 10 seconds the 
machine resumes again with lid still closed. Imidiately opening an closing lid 
makes suspends the computer and it keeps suspended until lid is opened again.

  This behaviour is the same when entering a sudo pm-suspend from the
  terminal. Machine suspends. But resumes after 8 to 10 seconds.
  Immidiately doing a second sudo pm-suspend, suspends the machine and
  keeps it suspended.

  There is one case where the behaviour described above is different.
  That is in the situation where machine is put into suspend for the
  first time after a complete reboot. In this case the machine suspends
  correctly and stays suspended as expected.

  The problem is consistent and can be reproduced as desribed any number
  of times.

  Disabling wi-fi (using the Broadcom 802.11 Linux STA proprietary
  driver) doesn't alter the behaviour described above.

  
  cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  P0P2S3*disabled
  EC  S3*disabled
  HDEFS3*disabled  pci::00:1b.0
  RP01S3*disabled  pci::00:1c.0
  RP02S3*disabled  pci::00:1c.1
  RP03S3*disabled  pci::00:1c.2
  ARPTS4*disabled  pci::03:00.0
  RP05S3*disabled  pci::00:1c.4
  RP06S3*disabled  pci::00:1c.5
  SPITS3*disabled
  XHC1S3*enabled   pci::00:14.0
  ADP1S3*disabled  platform:ACPI0003:00
  LID0S3*enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 23 17:03:05 2014
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64+mac 
(20140417)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1311724] Re: Macbook Air resumes immidiately after suspend

2014-10-17 Thread Krister
Careful though, this does not work every time...  just most of the time.

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

Title:
  Macbook Air resumes immidiately after suspend

Status in “pm-utils” package in Ubuntu:
  Confirmed

Bug description:
  Computer model : Apple Macbook Air 6,2 (Mid 2013)
  BIOS version   : MBA61.88Z.0099.B04 (dmidecode -s bios-version), Oct. 2013 
version
  OS installed   : Ubuntu 14.04, single boot

  Problem description:
   
  When closing lid on computer machine suspends. Within 8 to 10 seconds the 
machine resumes again with lid still closed. Imidiately opening an closing lid 
makes suspends the computer and it keeps suspended until lid is opened again.

  This behaviour is the same when entering a sudo pm-suspend from the
  terminal. Machine suspends. But resumes after 8 to 10 seconds.
  Immidiately doing a second sudo pm-suspend, suspends the machine and
  keeps it suspended.

  There is one case where the behaviour described above is different.
  That is in the situation where machine is put into suspend for the
  first time after a complete reboot. In this case the machine suspends
  correctly and stays suspended as expected.

  The problem is consistent and can be reproduced as desribed any number
  of times.

  Disabling wi-fi (using the Broadcom 802.11 Linux STA proprietary
  driver) doesn't alter the behaviour described above.

  
  cat /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  P0P2S3*disabled
  EC  S3*disabled
  HDEFS3*disabled  pci::00:1b.0
  RP01S3*disabled  pci::00:1c.0
  RP02S3*disabled  pci::00:1c.1
  RP03S3*disabled  pci::00:1c.2
  ARPTS4*disabled  pci::03:00.0
  RP05S3*disabled  pci::00:1c.4
  RP06S3*disabled  pci::00:1c.5
  SPITS3*disabled
  XHC1S3*enabled   pci::00:14.0
  ADP1S3*disabled  platform:ACPI0003:00
  LID0S3*enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 23 17:03:05 2014
  InstallationDate: Installed on 2014-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64+mac 
(20140417)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1382690] [NEW] firefox does not get focus when opened by hotkey

2014-10-17 Thread Krister
Public bug reported:

open firefox using the hotkey set for the web browser in the keyboard
setting.

see that the window opens but it is not on top.
one must click on it to use it.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8
Uname: Linux 3.13.0-38-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Oct 17 17:49:04 2014
DistUpgraded: 2014-04-23 16:28:40,889 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:011b]
InstallationDate: Installed on 2013-10-25 (357 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64+mac 
(20131016.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05ac:0291 Apple, Inc. 
 Bus 001 Device 006: ID 05ac:828f Apple, Inc. 
 Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookAir6,2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38-generic 
root=UUID=079cbe6b-6488-4e57-85d3-c3e3e2fcbe40 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-23 (177 days ago)
XorgConf:
 Section Device
 Identifier  Intel Graphics
 Driver  intel
 Option  Backlight mba6x_backlight
 EndSection
dmi.bios.date: 09/27/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA61.88Z.0099.B04.1309271229
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-7DF21CB3ED6977E5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-7DF21CB3ED6977E5
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B04.1309271229:bd09/27/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
dmi.product.name: MacBookAir6,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Oct 17 17:11:53 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   40159 
 vendor APP
xserver.version: 2:1.15.1-0ubuntu2.1

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


** Tags: amd64 apport-bug compiz-0.9 package-from-proposed trusty ubuntu

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

Title:
  firefox does not get focus when opened by hotkey

Status in “unity” package in Ubuntu:
  New

Bug description:
  open firefox using the hotkey set for the web browser in the keyboard
  setting.

  see that the window opens but it is not on top.
  one must click on it to use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8
  Uname: Linux 3.13.0-38-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct 17 17:49:04 2014
  DistUpgraded: 2014-04-23 16:28:40,889 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] 
(rev 09) (prog-if 00 [VGA controller])
 

[Touch-packages] [Bug 1342609] [NEW] altspace on windowless desktop opens window accessibility menu

2014-07-16 Thread Krister
Public bug reported:

1. Go to a desktop with now windows open.
2. Press altspace.
3. See that the window accessibility menu opens.

Clicking on entries in this menu causes problems with Unity.
For example if you click on Move Workspace Left, then many graphical issues 
arrise.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.1+14.04.20140513-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed Jul 16 11:11:27 2014
InstallationDate: Installed on 2013-10-03 (285 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-23 (83 days ago)

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  altspace on windowless desktop opens window accessibility menu

Status in “unity” package in Ubuntu:
  New

Bug description:
  1. Go to a desktop with now windows open.
  2. Press altspace.
  3. See that the window accessibility menu opens.

  Clicking on entries in this menu causes problems with Unity.
  For example if you click on Move Workspace Left, then many graphical issues 
arrise.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Jul 16 11:11:27 2014
  InstallationDate: Installed on 2013-10-03 (285 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (83 days ago)

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

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