[Touch-packages] [Bug 2061383] [NEW] [noble] Add ManageForeignNextHops feature to fix NextHop deletions

[Justin Lamp]

Public bug reported:

Hi,

I was wondering if it was possible to integrate the new
ManageForeignNextHops feature via a backport into Ubuntu 24.04.

Without this feature/bugfix we have problems with systemd-networkd
deleting the Nexthops of FRR on a restart of Switch failure. This is
especially problematic with our EVPN setup. For more information please
have a look into the following issue:

https://github.com/systemd/systemd/issues/29034
https://github.com/systemd/systemd/commit/0977039bdc9e857cdb0dfe1d96d0de0d94d02155

Best regards,
Justin Lamp

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


** Tags: systemd-networkd

** Tags added: systemd-networkd

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

Title:
   [noble] Add ManageForeignNextHops feature to fix NextHop deletions

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  I was wondering if it was possible to integrate the new
  ManageForeignNextHops feature via a backport into Ubuntu 24.04.

  Without this feature/bugfix we have problems with systemd-networkd
  deleting the Nexthops of FRR on a restart of Switch failure. This is
  especially problematic with our EVPN setup. For more information
  please have a look into the following issue:

  https://github.com/systemd/systemd/issues/29034
  
https://github.com/systemd/systemd/commit/0977039bdc9e857cdb0dfe1d96d0de0d94d02155

  Best regards,
  Justin Lamp

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


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

[Touch-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

[Justin Kelley]

What's the resolution here? I've tried every incantation of fixes and
patches. I'm currently running 6.9-rc but even that doesn't resolve the
problem. Latest installs of sof-firmwre, updating alsa tools...nothing

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

[Touch-packages] [Bug 2049697] [NEW] GPU not being detected when I try to run any game

[Justin Klassen]

Public bug reported:

I ran ran apport-bug xorg and it took me here. Trying to figure out an
issue where any time I open a game, it crashes and gives the error
message "GPU not detected". From everything I've tried it seems like the
computer has no problem detecting the GPU and it seems to be working
fine, but games are still not working. Any help is appreciated!

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 17 18:34:19 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:0122]
InstallationDate: Installed on 2023-10-25 (84 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: Apple Inc. iMac14,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2020
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 146.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-031B6874CF7F642A
dmi.board.vendor: Apple Inc.
dmi.board.version: iMac14,1
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-031B6874CF7F642A
dmi.modalias: 
dmi:bvnAppleInc.:bvr146.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pniMac14,1:pvr1.0:rvnAppleInc.:rnMac-031B6874CF7F642A:rvriMac14,1:cvnAppleInc.:ct13:cvrMac-031B6874CF7F642A:skuSystemSKU#:
dmi.product.family: iMac
dmi.product.name: iMac14,1
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.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  GPU not being detected when I try to run any game

Status in xorg package in Ubuntu:
  New

Bug description:
  I ran ran apport-bug xorg and it took me here. Trying to figure out an
  issue where any time I open a game, it crashes and gives the error
  message "GPU not detected". From everything I've tried it seems like
  the computer has no problem detecting the GPU and it seems to be
  working fine, but games are still not working. Any help is
  appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 18:34:19 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:0122]
  InstallationDate: Installed on 2023-10-25 (84 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Apple Inc. iMac14,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 146.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-031B6874CF7F642A
  dmi.board.vendor: Apple Inc.
  dmi.board.version: 

[Touch-packages] [Bug 2048091] [NEW] IP Neighbor cannot force delete in batch mode

[Justin Lamp]

Public bug reported:

Hey there,

we encountered an error where the ip command in batch mode will fail
when trying to delete neighbor entries that aren't there anymore even
though the `-force` option is active.

$ ip -force -b /dev/stdin <https://lkml.kernel.org/netdev/1426645592-4002-1-git-send-email-ro...@cumulusnetworks.com/

https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/ip/ipneigh.c#n213

Unfortunately this feature is very important to us, as we need to make
sure that the entries are gone for good and need the speed of the batch
mode to process the updates.

Thanks and best regards,
Justin Lamp

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

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

Title:
  IP Neighbor cannot force delete in batch mode

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Hey there,

  we encountered an error where the ip command in batch mode will fail
  when trying to delete neighbor entries that aren't there anymore even
  though the `-force` option is active.

  $ ip -force -b /dev/stdin <https://lkml.kernel.org/netdev/1426645592-4002-1-git-send-email-ro...@cumulusnetworks.com/

  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/ip/ipneigh.c#n213

  Unfortunately this feature is very important to us, as we need to make
  sure that the entries are gone for good and need the speed of the
  batch mode to process the updates.

  Thanks and best regards,
  Justin Lamp

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


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

[Touch-packages] [Bug 2040318] [NEW] GPU not found

[Justin Klassen]

Public bug reported:

Trying to workout an issue where my GPU is not being detected, ran
apport-bug xorg and it took me here

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.26.1-0ubuntu2.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 24 13:33:03 2023
DistUpgraded: 2023-10-21 10:19:12,691 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: lunar
DistroVariant: ubuntu
DkmsStatus:
 broadcom-sta/6.30.223.271, 6.2.0-34-generic, x86_64: installed
 broadcom-sta/6.30.223.271, 6.2.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:0122]
InstallationDate: Installed on 2023-04-29 (178 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 006: ID 05ac:828d Apple, Inc. Bluetooth USB Host Controller
 Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
 Bus 001 Device 002: ID 05ac:8511 Apple, Inc. FaceTime HD Camera (Built-in)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. iMac14,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=25be08ed-269b-48f4-b449-432add52d238 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to lunar on 2023-10-21 (3 days ago)
dmi.bios.date: 06/10/2020
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 146.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-031B6874CF7F642A
dmi.board.vendor: Apple Inc.
dmi.board.version: iMac14,1
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-031B6874CF7F642A
dmi.modalias: 
dmi:bvnAppleInc.:bvr146.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pniMac14,1:pvr1.0:rvnAppleInc.:rnMac-031B6874CF7F642A:rvriMac14,1:cvnAppleInc.:ct13:cvrMac-031B6874CF7F642A:skuSystemSKU#:
dmi.product.family: iMac
dmi.product.name: iMac14,1
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.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.0.20230712.1-2073~22.04
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug lunar third-party-packages ubuntu wayland-session

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

Title:
  GPU not found

Status in xorg package in Ubuntu:
  New

Bug description:
  Trying to workout an issue where my GPU is not being detected, ran
  apport-bug xorg and it took me here

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:33:03 2023
  DistUpgraded: 2023-10-21 10:19:12,691 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  DkmsStatus:
   broadcom-sta/6.30.223.271, 6.2.0-34-generic, x86_64: installed
   broadcom-sta/6.30.223.271, 6.2.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:0122]
  InstallationDate: Installed on 2023-04-29 (178 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05ac:828d Apple, Inc. Bluetooth USB Host Controller
   Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 002: ID 

[Touch-packages] [Bug 2011574] Re: rsyslogd: /dev/console permission errors

[Justin Abrahms]

Also noting that `sudo useradd syslog tty` did fix the underlying issue.

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

Title:
  rsyslogd: /dev/console permission errors

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  See: https://bugs.launchpad.net/bugs/1890177

  I am opening a new ticket because I believe there may have been a
  regression. I am using rsyslog8.2112.0-2ubuntu2.2 and I still
  see this issue.

  /etc/rsyslog.d/90-google.conf:
  # Google Compute Engine default console logging.
  #
  # daemon: logging from Google provided daemons.
  # kern: logging information in case of an unexpected crash during boot.
  #
  daemon,kern.* /dev/console

  Logs are filled with:
  rsyslogd: action 'action-8-builtin:omfile' suspended (module 
'builtin:omfile'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 ]
  rsyslogd: action 'action-8-builtin:omfile' resumed (module 'builtin:omfile') 
[v8.2112.0 try https://www.rsyslog.com/e/2359 ]

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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

[Touch-packages] [Bug 2011574] Re: rsyslogd: /dev/console permission errors

[Justin Abrahms]

** Patch added: 
"0001-Grant-the-syslog-user-access-to-the-tty-group-so-it-.patch"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2011574/+attachment/5687233/+files/0001-Grant-the-syslog-user-access-to-the-tty-group-so-it-.patch

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

Title:
  rsyslogd: /dev/console permission errors

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  See: https://bugs.launchpad.net/bugs/1890177

  I am opening a new ticket because I believe there may have been a
  regression. I am using rsyslog8.2112.0-2ubuntu2.2 and I still
  see this issue.

  /etc/rsyslog.d/90-google.conf:
  # Google Compute Engine default console logging.
  #
  # daemon: logging from Google provided daemons.
  # kern: logging information in case of an unexpected crash during boot.
  #
  daemon,kern.* /dev/console

  Logs are filled with:
  rsyslogd: action 'action-8-builtin:omfile' suspended (module 
'builtin:omfile'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 ]
  rsyslogd: action 'action-8-builtin:omfile' resumed (module 'builtin:omfile') 
[v8.2112.0 try https://www.rsyslog.com/e/2359 ]

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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

[Touch-packages] [Bug 2011574] Re: rsyslogd: /dev/console permission errors

[Justin Abrahms]

Here to confirm that I am also experiencing this bug.

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

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

Title:
  rsyslogd: /dev/console permission errors

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  See: https://bugs.launchpad.net/bugs/1890177

  I am opening a new ticket because I believe there may have been a
  regression. I am using rsyslog8.2112.0-2ubuntu2.2 and I still
  see this issue.

  /etc/rsyslog.d/90-google.conf:
  # Google Compute Engine default console logging.
  #
  # daemon: logging from Google provided daemons.
  # kern: logging information in case of an unexpected crash during boot.
  #
  daemon,kern.* /dev/console

  Logs are filled with:
  rsyslogd: action 'action-8-builtin:omfile' suspended (module 
'builtin:omfile'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 ]
  rsyslogd: action 'action-8-builtin:omfile' resumed (module 'builtin:omfile') 
[v8.2112.0 try https://www.rsyslog.com/e/2359 ]

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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

[Touch-packages] [Bug 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible

[Tsun Justin Ko]

Hello, we are also experiencing this problem and would like to see it
resolved.

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

Title:
  Missing all modules for usb nics in initrd which makes PXE boot
  impossible

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Confirmed
Status in initramfs-tools source package in Hirsute:
  Confirmed
Status in initramfs-tools source package in Impish:
  Won't Fix
Status in initramfs-tools source package in Jammy:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  initrd taken from the live iso for PXE boot does not contain USB NIC
  drivers which makes PXE installation/netboot impossible via usb.

  This is the case on 20.04 server iso (both hwe and normal
  kernel/initrd) and desktop iso.

  "kernel/drivers/net/usb" is empty and needs to be included in the
  initramfs build.

  As most modern thin laptops lack physical rj45 ethernet this is a big
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18
  Uname: Linux 5.8.0-64-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 15 16:47:45 2021
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago)

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


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

[Touch-packages] [Bug 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC

[Justin]

Thank you, this solution fixes the bug for me as well.

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

Title:
  NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Situation:

  My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a
  privacy perspective, for readability reasons and for network
  management policies, DHCPv6 should *always* be preferred over SLAAC
  addresses when available. And according to RFC 6724, the smaller /128
  scope of the DHCPv6 address should be chosen over the larger /64 scope
  of the SLAAC address.

  NetworkManager has always been able to adhere to that by simply
  setting ip6.privacy=0 for the connection (in nm-connection-editor
  *not* selecting "Prefer temporary address" for IPv6 privacy
  extensions). Then it would use the DHCPv6 address as the source for
  all outgoing traffic.

  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world and be echoed
  back.

  Regression:

  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection.

  Constantly removing the SLAAC addresses with `ip addr del` or
  disabling SLAAC RA's on the router are now the only ways to stop
  NetworkManager from preferring SLAAC over DHCPv6. None of the local
  options in NetworkManager 1.36.6 are able to restore the previous,
  desired and correct way of working: the SLAAC address should never be
  used as the preferred address if a DHCPv6 lease is given.

  Looking at the changelog of NetworkManager 1.36.6, multiple things
  regarding IP address order and temporary addresses have been changed
  in that release, any of them (or a combination) introducing this bug:

  * Fix a bug in synchronization of IP addresses with kernel that could lead to 
a wrong address order.
  * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag 
is set.
  * Ensure temporary IPv6 addresses are removed on disconnect and reapply.

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  Steps to reproduce:

  1. Connect to a network where the router sends "A" and "M" bits in the
  RA's and has a DHCPv6 server running (e.g. any OpenWrt router).

  2. When running `ip -6 a`, the list now sorts SLAAC addresses above
  DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not
  the case. (The Linux kernel uses the address highest in the list as
  preferred.)

  3. When running something like `curl ifconfig.co`, the SLAAC address
  is being returned, which makes sense as that is now preferred by the
  kernel. (But it shouldn't be.)

  Desired behaviour:

  NetworkManager should always sort DHCPv6 addresses above SLAAC
  addresses, as is the case for all versions prior to 1.36.6 and also
  corrected again in 1.38.0. In case static addresses are manually set,
  those should take first priority, with DHCPv6 second and
  SLAAC/autoconf last.

  Implications:

  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in
  all kinds of firewalls to allow me to access servers for my work. Now
  that the "wrong" address is being preferred for outgoing traffic (a
  SLAAC address that I have no influence on and cannot centrally
  configure), I am being locked out of the servers in question unless I
  forcefully remove the addresses or disable SLAAC on my router, so my
  outgoing traffic is being routed through the DHCPv6 address again.

  Note that "just disabling SLAAC RA's on the router" is not something
  everybody can do, as it requires root access to the device. Moreover,
  it would break IPv6 connectivity entirely for devices that don't
  support DHCPv6 (read: Android).

  Conclusion:

  So this update introduces a very breaking change in IPv6 source
  address selection to an LTS release, while LTS releases should be
  stable.

  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should. As that version is also used in Ubuntu kinetic, most likely
  this bug is not present there.

  Looking at the changelog of 1.38.0:

  * Fix bug setting priority for IP addresses.
  * Static IPv6 addresses from "ipv6.addresses" are now preferred over 
addresses from DHCPv6, which are preferred over addresses from autoconf. This 
affects IPv6 source address selection, if the rules from RFC 6724, section 5 
don't give a exhaustive match.

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS

  It looks like Ubuntu just 

[Touch-packages] [Bug 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC

[Justin]

@seb128 I am also affected by this bug and privacy-wise every other
Ubuntu 22.04 user as well, but I didn´t respond, trusting the process
that this bug would be fixed. So I am supporting your efforts getting an
upstream fix shortly or alternatively reverting the change that created
the regression.

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

Title:
  NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC

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

Bug description:
  Situation:

  My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a
  privacy perspective, for readability reasons and for network
  management policies, DHCPv6 should *always* be preferred over SLAAC
  addresses when available. And according to RFC 6724, the smaller /128
  scope of the DHCPv6 address should be chosen over the larger /64 scope
  of the SLAAC address.

  NetworkManager has always been able to adhere to that by simply
  setting ip6.privacy=0 for the connection (in nm-connection-editor
  *not* selecting "Prefer temporary address" for IPv6 privacy
  extensions). Then it would use the DHCPv6 address as the source for
  all outgoing traffic.

  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world and be echoed
  back.

  Regression:

  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection.

  Constantly removing the SLAAC addresses with `ip addr del` or
  disabling SLAAC RA's on the router are now the only ways to stop
  NetworkManager from preferring SLAAC over DHCPv6. None of the local
  options in NetworkManager 1.36.6 are able to restore the previous,
  desired and correct way of working: the SLAAC address should never be
  used as the preferred address if a DHCPv6 lease is given.

  Looking at the changelog of NetworkManager 1.36.6, multiple things
  regarding IP address order and temporary addresses have been changed
  in that release, any of them (or a combination) introducing this bug:

  * Fix a bug in synchronization of IP addresses with kernel that could lead to 
a wrong address order.
  * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag 
is set.
  * Ensure temporary IPv6 addresses are removed on disconnect and reapply.

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  Steps to reproduce:

  1. Connect to a network where the router sends "A" and "M" bits in the
  RA's and has a DHCPv6 server running (e.g. any OpenWrt router).

  2. When running `ip -6 a`, the list now sorts SLAAC addresses above
  DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not
  the case. (The Linux kernel uses the address highest in the list as
  preferred.)

  3. When running something like `curl ifconfig.co`, the SLAAC address
  is being returned, which makes sense as that is now preferred by the
  kernel. (But it shouldn't be.)

  Desired behaviour:

  NetworkManager should always sort DHCPv6 addresses above SLAAC
  addresses, as is the case for all versions prior to 1.36.6 and also
  corrected again in 1.38.0. In case static addresses are manually set,
  those should take first priority, with DHCPv6 second and
  SLAAC/autoconf last.

  Implications:

  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in
  all kinds of firewalls to allow me to access servers for my work. Now
  that the "wrong" address is being preferred for outgoing traffic (a
  SLAAC address that I have no influence on and cannot centrally
  configure), I am being locked out of the servers in question unless I
  forcefully remove the addresses or disable SLAAC on my router, so my
  outgoing traffic is being routed through the DHCPv6 address again.

  Note that "just disabling SLAAC RA's on the router" is not something
  everybody can do, as it requires root access to the device. Moreover,
  it would break IPv6 connectivity entirely for devices that don't
  support DHCPv6 (read: Android).

  Conclusion:

  So this update introduces a very breaking change in IPv6 source
  address selection to an LTS release, while LTS releases should be
  stable.

  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should. As that version is also used in Ubuntu kinetic, most likely
  this bug is not present there.

  Looking at the changelog of 1.38.0:

  * Fix bug setting priority for IP addresses.
  * Static IPv6 addresses from "ipv6.addresses" are now preferred over 
addresses from DHCPv6, which are preferred over addresses from 

[Touch-packages] [Bug 1933276] [NEW] trash

[Justin Case]

Public bug reported:

system locks when trash can is emptied.  Doesn't empty.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
Uname: Linux 3.13.0-170-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.29
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
Date: Tue Jun 22 18:16:17 2021
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Device [104d:9035]
   Subsystem: Sony Corporation Device [104d:9035]
InstallationDate: Installed on 2014-12-20 (2376 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Sony Corporation VGN-FW170J
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic 
root=UUID=97ba2d83-7962-452a-82d3-a77935bf95bf ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0270Y0
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0270Y0:bd10/07/2009:svnSonyCorporation:pnVGN-FW170J:pvrC600HH56:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-FW170J
dmi.product.version: C600HH56
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11
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.7
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Jun 22 09:16:31 2021
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.11

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


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

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

Title:
  trash

Status in xorg package in Ubuntu:
  New

Bug description:
  system locks when trash can is emptied.  Doesn't empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  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
  Date: Tue Jun 22 18:16:17 2021
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Device [104d:9035]
 Subsystem: Sony Corporation Device [104d:9035]
  InstallationDate: Installed on 2014-12-20 (2376 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Sony Corporation VGN-FW170J
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic 
root=UUID=97ba2d83-7962-452a-82d3-a77935bf95bf ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0270Y0
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: 

[Touch-packages] [Bug 875660]

[Justin Zobel]

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you
can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status
to resolved.

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

Title:
  PA and knotify startup race leads to wrong device selection

Status in Phonon:
  Unknown
Status in kde-runtime package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  This appears to be a regression in Oneiric.
  I'm running Kubuntu with pulseaudio.
  I have on my motherboard intel hda analog audio and my graphics card (an ATI) 
had an HDMI out; by default I like the audio to come out of the analog output 
that is the only one connected.

  Sometimes logging into KDE I find that it's decided to switch to the
  HDMI as the default; today I caught it and did an lsof /dev/snd/* and
  found:

  knotify4  2276   dg  memCHR  116,3  6691 /dev/snd/pcmC0D0p
  knotify4  2276   dg   20r   CHR 116,33  0t0 9995 /dev/snd/timer
  knotify4  2276   dg   21u   CHR  116,3  0t0 6691 /dev/snd/pcmC0D0p
  pulseaudi 2893   dg   24u   CHR  116,9  0t0 6698 /dev/snd/controlC1   


  
  pulseaudi 2893   dg   31u   CHR  116,6  0t0 6694 /dev/snd/controlC0   


  
  pulseaudi 2893   dg   38u   CHR  116,6  0t0 6694 /dev/snd/controlC0   


  

  So knotify4 has hogged the analog output, and hence pa can't get in.

  So I kill knotify4, and do a pactl exit to restart pa - but pa then
  still lists the HDMI as the default output in paman, and I can't see a
  way to get it back to default without restarting everything.

  I'm also going to subscribe this bug to kde-runtime; I'm not sure who
  is supposed to manage the race between pa startup and anything else,
  and I'm not sure if it's a kubuntu special or KDE in general.

  Dave

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: pulseaudio 1:1.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dg 4889 F pulseaudio
   /dev/snd/controlC0:  dg 4889 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbcf8000 irq 47'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,18490397,0010'
 Controls  : 37
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 48'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  CheckboxSubmission: f2d10bd9f943a85b486a282e7840a570
  CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948
  Date: Sun Oct 16 12:31:37 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to oneiric on 2011-09-24 (21 days ago)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: P55M Pro
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/10/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1896632] [NEW] package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: »installiertes lvm2-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück

[Justin Pietsch]

Public bug reported:

I ve no idea what happend or why.

The system reports me a bug, I thought I would send the information.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.07-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Sep 21 22:17:26 2020
DpkgHistoryLog:
 Start-Date: 2020-09-21  22:17:25
 Commandline: apt-get autoremove
 Requested-By: pietsch (1000)
ErrorMessage: »installiertes lvm2-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: lvm2
Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: »installiertes 
lvm2-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 
zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package lvm2 2.03.07-1ubuntu1 failed to install/upgrade:
  »installiertes lvm2-Skript des Paketes post-installation«-Unterprozess
  gab den Fehlerwert 1 zurück

Status in lvm2 package in Ubuntu:
  New

Bug description:
  I ve no idea what happend or why.

  The system reports me a bug, I thought I would send the information.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Sep 21 22:17:26 2020
  DpkgHistoryLog:
   Start-Date: 2020-09-21  22:17:25
   Commandline: apt-get autoremove
   Requested-By: pietsch (1000)
  ErrorMessage: »installiertes lvm2-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: lvm2
  Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: 
»installiertes lvm2-Skript des Paketes post-installation«-Unterprozess gab den 
Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1833174] Re: Shadowing the vim-window results in vim-gtk3 crash

[Justin Huff]

This is apparently fixed upstream, but I haven't had a chance to verify.

https://github.com/vim/vim/issues/4835

** Bug watch added: github.com/vim/vim/issues #4835
   https://github.com/vim/vim/issues/4835

** Also affects: vim via
   https://github.com/vim/vim/issues/4835
   Importance: Unknown
   Status: Unknown

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

Title:
   Shadowing the vim-window results in vim-gtk3 crash

Status in vim:
  Unknown
Status in vim package in Ubuntu:
  Confirmed

Bug description:
  With XFCE when I try to "shadow" the vim-gtk3 window (just to show only the 
title bar) it results in a vim crash and the window just disappears without any 
core dump neither .swp files on.
  The only message I get on the terminal is

  BadMatch (invalid parameter attributes)
  Vim: Got X error
  Vim: Finished.

  This behaviour started from Xubuntu 18.04.
  The vim-gtk package is not suffering from this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: vim-gtk3 2:8.1.0320-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun 18 09:10:38 2019
  InstallationDate: Installed on 2019-04-23 (55 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1833174] Re: Shadowing the vim-window results in vim-gtk3 crash

[Justin Huff]

Still happens on xubuntu 20.04. Unfortunately, vim-gtk2 isn't around
anymore, so the workaround is invalid.

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

Title:
   Shadowing the vim-window results in vim-gtk3 crash

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  With XFCE when I try to "shadow" the vim-gtk3 window (just to show only the 
title bar) it results in a vim crash and the window just disappears without any 
core dump neither .swp files on.
  The only message I get on the terminal is

  BadMatch (invalid parameter attributes)
  Vim: Got X error
  Vim: Finished.

  This behaviour started from Xubuntu 18.04.
  The vim-gtk package is not suffering from this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: vim-gtk3 2:8.1.0320-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun 18 09:10:38 2019
  InstallationDate: Installed on 2019-04-23 (55 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1877932] Re: Bluetooth not connecting to last paired device when enabling bluetooth

[Justin Joseph]

Hi,
It is not connecting at Bluetooth level. Once I manage to get it connected,
all works like charm.

On Mon, May 11, 2020, 2:30 PM Sebastien Bacher 
wrote:

> Thank you for your bug report. Is it not connecting to the device at the
> bluetooth level or is connecting but not routing the sound to the
> headset?
>
> ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu)
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1877932
>
> Title:
>   Bluetooth not connecting to last paired device when enabling bluetooth
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>
>   I am using a Dell Lattitude E7470 laptop. I am trying to connect a
> Bluetooth headset (Anker).
>   I am seeing this issue with the latest upgrade to the Ubuntu 20.04 LTS
> version. I have a Bluetooth headset which is paired with the machine. Given
> the Bluetooth is enabled in the Ubuntu machine and I switch on my Bluetooth
> headset, the ubuntu machine does not automatically connect to this device
> anymore. It used to do it very easily with 18.04,19.04 and 19.10 ubuntu
> version.
>   I have to do a variety of steps to get it connected:
>   * turn off and on the headset.
>   * turn off and on the laptop bluetooth.
>   * try manully connecting to the device from the setting menu multiple
> times.
>   * Sometimes it detects and get connected automatically as it should.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
>   Uname: Linux 5.4.0-29-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  justin 2220 F pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun May 10 19:42:46 2020
>   InstallationDate: Installed on 2019-02-21 (444 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   PackageArchitecture: all
>   ProcEnviron:
>LANGUAGE=en_GB:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_GB.UTF-8
>SHELL=/usr/bin/zsh
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: Bluetooth sound card not detected
>   UpgradeStatus: Upgraded to focal on 2020-04-27 (13 days ago)
>   dmi.bios.date: 10/08/2019
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.22.8
>   dmi.board.name: 0T6HHJ
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.22.8:bd10/08/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.family: Latitude
>   dmi.product.name: Latitude E7470
>   dmi.product.sku: 06DC
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877932/+subscriptions
>

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

Title:
  Bluetooth not connecting to last paired device when enabling bluetooth

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  
  I am using a Dell Lattitude E7470 laptop. I am trying to connect a Bluetooth 
headset (Anker). 
  I am seeing this issue with the latest upgrade to the Ubuntu 20.04 LTS 
version. I have a Bluetooth headset which is paired with the machine. Given the 
Bluetooth is enabled in the Ubuntu machine and I switch on my Bluetooth 
headset, the ubuntu machine does not automatically connect to this device 
anymore. It used to do it very easily with 18.04,19.04 and 19.10 ubuntu version.
  I have to do a variety of steps to get it connected:
  * turn off and on the headset.
  * turn off and on the laptop bluetooth.
  * try manully connecting to the device from the setting menu multiple times.
  * Sometimes it detects and get connected automatically as it should.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  justin 2220 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 19:42:46 2020
  InstallationDate: Installed on 2019-02-21 (444 d

[Touch-packages] [Bug 1822587] Re: wifi service stops occasionally.

[Justin Hall]

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

This behaviour has become noticeably worse since the recent updates the
last couple days (26 April 2020 today).

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

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Touch-packages] [Bug 1822587] Re: wifi service stops occasionally.

[Justin Hall]

Sometime after my original logging of the bug, the intermittent service
failure stopped. Unfortunately I did not keep track of which update the
problem disappeared after.

For months the service was rock-solid without any failures, until the
update yesterday and since then I've had to restart the service three
times, very much the same as when I originally logged the bug, either by
restarting the service through the console if that works, or switching
my laptop into and out of airplane mode which then works if the first
option failed.

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

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Touch-packages] [Bug 1822587] Re: wifi service stops occasionally.

[Justin Hall]

This issue has started recurring again after the Ubuntu update I
installed yesterday (18/Feb/2020).

Sometime after my original logging of the bug, the intermittent service
failure stopped. Unfortunately I did not keep track of which update the
problem disappeared after.

For months the service was rock-solid without any failures, until the
update yesterday and since then I've had to restart the service three
times, very much the same as when I originally logged the bug, either by
restarting the service through the console if that works, or switching
my laptop into and out of airplane mode which then works if the first
option failed.

Not sure if I should attach more info and what? Thanks

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

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Touch-packages] [Bug 1832074] [NEW] base-files '/etc/update-motd.d/50-motd-news' reports system use to Ubuntu

[Justin Fletcher]

Public bug reported:

System information::

root@here $ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04

root@here$ dpkg -l base-files | tail -1
ii  base-files 10.1ubuntu2.4 amd64Debian base system miscellaneous 
files


What I expect to happen::

Logins to my machine should not be communicated to anyone else, and
should not provide anyone else of information about my machine.


What does happen::

Logins to my machine report that a login occurred, and provide details
about the installed system, to Ubuntu.


Report::

I've just upgraded fromt Trusty to Bionic, and found that on login I get
a message telling me something about Ubuntu's Kubernetes. I don't want
advertising presented to me when I log in to MY system, so I began to
investigate where this is happening - assuming that /etc/update-
motd.d/10-help-text or 00-header had been updated during the upgrade and
recreated with this content.

Instead, I discover that there is another script that has been added -
/etc/update-motd.d/50-motd-news - which adds this junk text to the
login. Not only that, but the script comminucates with Ubuntu, to fetch
that information. Not only that, but it provides information about the
system that is running as part of the request.

During the upgrade, I was not asked about whether it was ok for the
system to call home every time I login (or every 12 hours, whichever is
sooner, but at least a minute after you boot), and it absolutely would
not be my expectation that this be the default. When I log in to my
machine, I do not expect that the event would be reported to any off-
site system, and I suspect that most other users would be surprised if
not horrified to find that the fact that a system is in use was being
reported to Ubuntu.

The service can be disabled by changing a setting in /etc/defaults/motd-
news from ENABLED=1 to ENABLED=0, but this almost certainly should be
defaulting to 0 - tracking disabled by default, not tracking enabled by
default.

For example, on my system this provides a user agent containing:

```
curl/7.58.0-2ubuntu3.7 Ubuntu/18.04.2/LTS GNU/Linux/4.15.0-50-generic/x86_64 
Intel(R)/Xeon(R)/CPU/X5675/@/3.07GHz uptime/580915.35/4598709.84
```

This means that every time the user logs in (or after 12 hours from the
prior log in, whichever is longer) Ubuntu receives:

* The IP address of a system that is in use (which might be behind NAT, but 
it's still a report).
* The Distribution version details.
* The Kernel version details
* The CPU type
* The uptime

Knowing where a machine is, that it is active, exactly what type of
system it is an how often it is restarted, would be an awesome dataset
for any attacker to obtain - ideally (for them) it tells them the
location of systems that are alive, how they might be attacked - from
the distribution version, the kernel and the CPU information, you can
determine a set of vulnerabilities to attack - and the uptime, which
will indicate how likely the system is to be patched.

The only thing that might be worse might be to include a cookie-jar on
the curl command, which would allow tracking of individual systems,
rather than aggregating them behind NAT using the IP (although it's
still possible that the data reported in the user agent may be able to
make that information individually usable). That said, the root user
could (unintentionally) enable a cookie jar in their .curlrc and thus
enable individual system tracking without realising.

Whilst there may be legitimate reasons for reporting this information
(say for reporting to the user that their system has updates available
or that the system is vulnerable!), an advertising tool which reports
the system's information regularly back to home does not seem
appropriate for a 'base-files' package.

The surprise at having my logins recorded on a remote site pales in
comparison to the horror of recording a database of systems that might
be abused.

The Privacy and potential Security concerns of this feature hugely
outweigh any perceived benefit to the user, and I believe that the right
course of action is to remove this script entirely from the
distribution. At the very least the script's operation should default to
being disabled.

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: privacy

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

Title:
  base-files '/etc/update-motd.d/50-motd-news' reports system use to
  Ubuntu

Status in base-files package in Ubuntu:
  New

Bug description:
  System information::

  root@here $ lsb_release -rd
  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  root@here$ dpkg -l base-files | tail -1
  ii  base-files 10.1ubuntu2.4 amd64Debian base system 
miscellaneous files

  
  What I expect to happen::

  Logins to my machine should not be 

[Touch-packages] [Bug 1822587] [NEW] wifi service stops occasionally.

[Justin Hall]

Public bug reported:

wifi service stops occasionally: ('?' in the top right icon). an old bug
that disappeared a few updates back, back now after yesterday's update.
'service network-manager restart' gets it working again. annoying as i
thought it gone.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: network-manager 1.12.4-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 14:50:50 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-07-30 (975 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   CONNECTIONCON-UUID  CON-PATH 
  
 wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
 enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
 lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN 
 running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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


** Tags: amd64 apport-bug cosmic

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

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  New

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   --

[Touch-packages] [Bug 1819300] [NEW] package tzdata 2018i-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Justin]

Public bug reported:

cant upload packages

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tzdata 2018i-0ubuntu0.16.04
ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Sat Mar  9 19:41:21 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2019-03-10 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29ubuntu0.1
SourcePackage: tzdata
Title: package tzdata 2018i-0ubuntu0.16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2019-03-10 (0 days ago)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package tzdata 2018i-0ubuntu0.16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in tzdata package in Ubuntu:
  New

Bug description:
  cant upload packages

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tzdata 2018i-0ubuntu0.16.04
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sat Mar  9 19:41:21 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2019-03-10 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: tzdata
  Title: package tzdata 2018i-0ubuntu0.16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-03-10 (0 days ago)

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

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

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Justin Bull]

Hi Daniel,

I reported the bug
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1814551 which had
its status changed to Confirmed yesterday.

Thanks for getting back to me.

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in ibus source package in Cosmic:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/391

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1814551] Re: Ubuntu 18.10's ibus package breaks password fields in Firefox Beta (65, 66 via PPA)

[Justin Bull]

Apologies, I meant to state in step one that the input method system is
iBus.

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

Title:
  Ubuntu 18.10's ibus package breaks password fields in Firefox Beta
  (65, 66 via PPA)

Status in ibus package in Ubuntu:
  New

Bug description:
  Essentially
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 but
  reproducible in Cosmic even with the patched gnome-shell installed via
  APT.

  SYSTEM INFO
  =

  * Ubuntu 18.10 Cosmic with latest updates
  * proc/version_signature: Ubuntu 4.18.0-14.15-generic 4.18.20
  * uname: Linux justin-ubuntu 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 
09:01:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  * gnome-shell 3.30.1-2ubuntu1.18.10.2
  * ibus 1.5.19-1ubuntu1
  * Both Firefox 65 and 66 (66.0~b4+build1-0ubuntu0.18.04.1 per official PPA)

  
  STEPS TO REPRODUCE
  =

  1. Ensure keyboard input method system is 
  1. Download Firefox Beta channel via their official PPA: 
https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next
  2. Download and install the 1Password X firefox extentsion: 
https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/
  3. Open the extension window by either pressing the shortcut Ctrl+. or 
clicking the 1Password icon in the Firefox UI
  4. Enter in the password in the input and press enter.

  Expected: The vault unlocks or displays a "this is a wrong password"

  Actual: The UI appears to "refresh" and nothing occurs.

  WORKAROUND/VALIDATION
  =

  Like the original bug, switching the keyboard input method to XIM from
  iBus resolves the issue suggesting to me that the symptoms I am
  experiencing are caused by the root issue previously filed, fixed, and
  deployed.

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

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

[Touch-packages] [Bug 1814551] [NEW] Ubuntu 18.10's ibus package breaks password fields in Firefox Beta (65, 66 via PPA)

[Justin Bull]

Public bug reported:

Essentially https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304
but reproducible in Cosmic even with the patched gnome-shell installed
via APT.

SYSTEM INFO
=

* Ubuntu 18.10 Cosmic with latest updates
* proc/version_signature: Ubuntu 4.18.0-14.15-generic 4.18.20
* uname: Linux justin-ubuntu 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 
09:01:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
* gnome-shell 3.30.1-2ubuntu1.18.10.2
* ibus 1.5.19-1ubuntu1
* Both Firefox 65 and 66 (66.0~b4+build1-0ubuntu0.18.04.1 per official PPA)


STEPS TO REPRODUCE
=

1. Ensure keyboard input method system is 
1. Download Firefox Beta channel via their official PPA: 
https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next
2. Download and install the 1Password X firefox extentsion: 
https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/
3. Open the extension window by either pressing the shortcut Ctrl+. or clicking 
the 1Password icon in the Firefox UI
4. Enter in the password in the input and press enter.

Expected: The vault unlocks or displays a "this is a wrong password"

Actual: The UI appears to "refresh" and nothing occurs.

WORKAROUND/VALIDATION
=

Like the original bug, switching the keyboard input method to XIM from
iBus resolves the issue suggesting to me that the symptoms I am
experiencing are caused by the root issue previously filed, fixed, and
deployed.

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

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

Title:
  Ubuntu 18.10's ibus package breaks password fields in Firefox Beta
  (65, 66 via PPA)

Status in ibus package in Ubuntu:
  New

Bug description:
  Essentially
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 but
  reproducible in Cosmic even with the patched gnome-shell installed via
  APT.

  SYSTEM INFO
  =

  * Ubuntu 18.10 Cosmic with latest updates
  * proc/version_signature: Ubuntu 4.18.0-14.15-generic 4.18.20
  * uname: Linux justin-ubuntu 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 
09:01:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  * gnome-shell 3.30.1-2ubuntu1.18.10.2
  * ibus 1.5.19-1ubuntu1
  * Both Firefox 65 and 66 (66.0~b4+build1-0ubuntu0.18.04.1 per official PPA)

  
  STEPS TO REPRODUCE
  =

  1. Ensure keyboard input method system is 
  1. Download Firefox Beta channel via their official PPA: 
https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next
  2. Download and install the 1Password X firefox extentsion: 
https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/
  3. Open the extension window by either pressing the shortcut Ctrl+. or 
clicking the 1Password icon in the Firefox UI
  4. Enter in the password in the input and press enter.

  Expected: The vault unlocks or displays a "this is a wrong password"

  Actual: The UI appears to "refresh" and nothing occurs.

  WORKAROUND/VALIDATION
  =

  Like the original bug, switching the keyboard input method to XIM from
  iBus resolves the issue suggesting to me that the symptoms I am
  experiencing are caused by the root issue previously filed, fixed, and
  deployed.

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

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

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Justin Bull]

I'm afraid this bug is still reproducible with:

* Ubuntu 18.10 Cosmic with latest updates
* gnome-shell 3.30.1-2ubuntu1.18.10.2
* Both Firefox 65 and 66 (66.0~b4+build1-0ubuntu0.18.04.1 per official PPA)

In the spirit of cutting down on noise I didn't want to file a new
ticket. Should this be reopened or am I misunderstanding something.

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in ibus source package in Cosmic:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/391

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1806463] Re: Unattended-Upgrade::InstallOnShutdown "true" not working

[Justin V]

After reading the NEWS file, it seems that it is necessary for the dbus
signal to be sent first, at which point the upgrade begins.  Next, the
SIGTERM is received, but the upgrade has already started.  So, "shutdown
-r now" will not trigger an upgrade.

I'll need some time to be able to experiment with a reboot.  I was doing
"shutdown -r now".  Also, I am using xfce, so maybe it is not sending a
signal (either).

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

Title:
  Unattended-Upgrade::InstallOnShutdown "true" not working

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Cosmic, unattended-upgrades 1.5ubuntu3.18.10.0

  Trying to get install-on-shutdown working.  Added << Unattended-
  Upgrade::InstallOnShutdown "true"; >> to apt.conf.

  It appears that the logic for install-on-shutdown is in /usr/share
  /unattended-upgrades/unattended-upgrade-shutdown.  The logic for run-
  on-shutdown is in UnattendedUpgradesShutdown.try_iter_on_shutdown,
  which is only called by iter "if not
  self.stop_signal_received.is_set()".  However, since --wait-for-signal
  is true, it waits for a signal, then the iter says "signal recieved,
  so skip upgrade":

  1. apt.conf: Unattended-Upgrade::InstallOnShutdown "true" (though, unused)
  2. unattended-upgrades.service: .../unattended-upgrade-shutdown 
--wait-for-signal
  3. UnattendedUpgradesShutdown.run: signal_handler is installed; wait.
  4. UUS.run.signal_handler: stop_signal_received.set(); start_iterations()
  5. UUS.start_iterations: scheduler timer to call self.iter
  6. UUS.iter: not self.stop_signal_received.is_set() is always False
  7. UUS.try_iter_on_shutdown is never called

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

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

[Touch-packages] [Bug 1806463] Re: Unattended-Upgrade::InstallOnShutdown "true" not working

[Justin V]

BTW, in Debian stretch, the service runs the script via a "stop-script",
so the shutdown script is not called with --wait-for-signal, since it is
run at service-down which means it does not need to wait.  In that case,
it would seem that the signal would not be set, and the install-on-
shutdown logic would be triggered.

Don't know if stretch is ahead or behind or forked from cosmic.

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

Title:
  Unattended-Upgrade::InstallOnShutdown "true" not working

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Cosmic, unattended-upgrades 1.5ubuntu3.18.10.0

  Trying to get install-on-shutdown working.  Added << Unattended-
  Upgrade::InstallOnShutdown "true"; >> to apt.conf.

  It appears that the logic for install-on-shutdown is in /usr/share
  /unattended-upgrades/unattended-upgrade-shutdown.  The logic for run-
  on-shutdown is in UnattendedUpgradesShutdown.try_iter_on_shutdown,
  which is only called by iter "if not
  self.stop_signal_received.is_set()".  However, since --wait-for-signal
  is true, it waits for a signal, then the iter says "signal recieved,
  so skip upgrade":

  1. apt.conf: Unattended-Upgrade::InstallOnShutdown "true" (though, unused)
  2. unattended-upgrades.service: .../unattended-upgrade-shutdown 
--wait-for-signal
  3. UnattendedUpgradesShutdown.run: signal_handler is installed; wait.
  4. UUS.run.signal_handler: stop_signal_received.set(); start_iterations()
  5. UUS.start_iterations: scheduler timer to call self.iter
  6. UUS.iter: not self.stop_signal_received.is_set() is always False
  7. UUS.try_iter_on_shutdown is never called

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

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

[Touch-packages] [Bug 1806463] [NEW] Unattended-Upgrade::InstallOnShutdown "true" not working

[Justin V]

Public bug reported:

Cosmic, unattended-upgrades 1.5ubuntu3.18.10.0

Trying to get install-on-shutdown working.  Added << Unattended-
Upgrade::InstallOnShutdown "true"; >> to apt.conf.

It appears that the logic for install-on-shutdown is in /usr/share
/unattended-upgrades/unattended-upgrade-shutdown.  The logic for run-on-
shutdown is in UnattendedUpgradesShutdown.try_iter_on_shutdown, which is
only called by iter "if not self.stop_signal_received.is_set()".
However, since --wait-for-signal is true, it waits for a signal, then
the iter says "signal recieved, so skip upgrade":

1. apt.conf: Unattended-Upgrade::InstallOnShutdown "true" (though, unused)
2. unattended-upgrades.service: .../unattended-upgrade-shutdown 
--wait-for-signal
3. UnattendedUpgradesShutdown.run: signal_handler is installed; wait.
4. UUS.run.signal_handler: stop_signal_received.set(); start_iterations()
5. UUS.start_iterations: scheduler timer to call self.iter
6. UUS.iter: not self.stop_signal_received.is_set() is always False
7. UUS.try_iter_on_shutdown is never called

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Unattended-Upgrade::InstallOnShutdown "true" not working

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Cosmic, unattended-upgrades 1.5ubuntu3.18.10.0

  Trying to get install-on-shutdown working.  Added << Unattended-
  Upgrade::InstallOnShutdown "true"; >> to apt.conf.

  It appears that the logic for install-on-shutdown is in /usr/share
  /unattended-upgrades/unattended-upgrade-shutdown.  The logic for run-
  on-shutdown is in UnattendedUpgradesShutdown.try_iter_on_shutdown,
  which is only called by iter "if not
  self.stop_signal_received.is_set()".  However, since --wait-for-signal
  is true, it waits for a signal, then the iter says "signal recieved,
  so skip upgrade":

  1. apt.conf: Unattended-Upgrade::InstallOnShutdown "true" (though, unused)
  2. unattended-upgrades.service: .../unattended-upgrade-shutdown 
--wait-for-signal
  3. UnattendedUpgradesShutdown.run: signal_handler is installed; wait.
  4. UUS.run.signal_handler: stop_signal_received.set(); start_iterations()
  5. UUS.start_iterations: scheduler timer to call self.iter
  6. UUS.iter: not self.stop_signal_received.is_set() is always False
  7. UUS.try_iter_on_shutdown is never called

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

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

[Touch-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working

[Justin]

Hello I have the same issue. I tried for a couple days to fix it without
any results. I have the latest drivers installed
(https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS). I then tried to set
all configurations to default and ran alsa-info. The ouput is located at
the following url and in the attached text document. I hope this is
helpful.

http://www.alsa-
project.org/db/?f=79aa0cb7023e375b7255e6789c7bd19c26a70d4f


thankyou

** Attachment added: "My Sound card information"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+attachment/5192618/+files/alsa_info.txt

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

Title:
  [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal
  microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04
  on it. Everything works except the internal microphone. I have also
  tested with an external microphone and this didn't work either.

  I have worked my way through all the suggested solutions I could find,
  including trying to reconfigure the pins using hdajacketask. In
  pavucontrol I have options for Internal Microphone and Microphone
  (unplugged) but the internal mic only captures static noise.

  The latest HD-Audio Codec-Specific Models has configurations for
  alc255-acer and alc256 for some other models, but setting options snd-
  hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve
  the issue with any of these.

  Some info -

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-
  LP HD Audio (rev 21)

  
  cat /proc/asound/cards:

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf1a8000 irq 127

  
  dmesg | grep snd:

  [3.944593] snd_hda_core: loading out-of-tree module taints kernel.
  [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0)
  [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0)
  [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, 
version 0.201808050301~ubuntu18.04.1
  [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.013068] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [4.013069] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  info on node 12 from cat /proc/asound/card*/codec\#*:

  Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
Control: name="Internal Mic Boost Volume", index=0, device=0
  ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals:  [0x02 0x02]
Pincap 0x0020: IN
Pin Default 0x4000: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0x0, Sequence = 0x0
Pin-ctls: 0x20: IN
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0

  Let me know if you need any other information.

  James

  ---

  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

[Justin Jia]

I still have this problem, Anybody running the latest pulseaudio on
Raspberry Pi or CM3? I'm using pulseaudio 12.2 with bluez 5.50.

After I connected to a Bluetooth speaker. When play something, it's
really choppy and skipping a lot. The debug message shows:

D: [bluetooth] module-bluez5-device.c: Skipping 43083 us (= 7600 bytes)
in audio stream

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  When the connection drops temporarily, using A2DP, a noticeable latency is 
introduced, and the audio goes out of sync.

  [Test Case]
  1) Enable the -proposed repository, and install the new pulseaudio

  2) Restart your computer, connect it to a bluetooth device (e.g. a
  headset or a speaker), play one or more videos either locally or
  online, and see if you can still reproduce the problem.

  [Regression Potential]
  Low, as the changes are upstream, and, if anything, it should also fix a 
memory leak.

  Furthermore, the changes only affect the bluez5-device module, in
  pulseaudio, and they make the buffer updating logic more conscious of
  how things can change when the connection drops. This is unlikely to
  affect anything else in pulseaudio.

  
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working 
properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[Justin Bennett]

I just started noticing this issue on my machine today. Ubuntu 18.04. I
also had nameserver 127.0.0.1 in /etc/resolv.conf. Changed to
127.0.0.53, per diepes' comment and CPU calmed down for me as well.

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  

[Touch-packages] [Bug 1781294] [NEW] no sound but system recognizes integrated sound card on laptop

[Justin Luther]

Public bug reported:

This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
the troubleshooting steps here:

https://help.ubuntu.com/community/SoundTroubleshooting

and have included some output of those diagnostic steps below:


$ sudo aplay -l
aplay: device_list:270: no soundcards found...

$ find /lib/modules/`uname -r` | grep snd
/lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
/lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
/lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
/lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
/lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
/lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
/lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
/lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
/lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
/lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
/lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
...and lots more

$ lspci -v | grep -A7 -i "audio"
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 131
Memory at dc228000 (64-bit, non-prefetchable) [size=16K]
Memory at dc20 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

Sound settings still only list dummy output.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 11 18:44:06 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2017-05-11 (426 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago)
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.name: 01KT0M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  no sound but system recognizes integrated sound card on laptop

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
  the troubleshooting steps here:

  https://help.ubuntu.com/community/SoundTroubleshooting

  and have included some output of those diagnostic steps below:

  
  $ sudo aplay -l
  aplay: device_list:270: no soundcards found...

  $ find /lib/modules/`uname -r` | grep snd
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
  ...and lots more

  $ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, 

[Touch-packages] [Bug 1778386] Re: If SSH host keys are missing, they should automatically regenerate at boot time

[Justin St. Marie]

Is there a recommended method for regenerating the keys without having
to touch the console on every virtual machine?

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

Title:
  If SSH host keys are missing, they should automatically regenerate at
  boot time

Status in openssh package in Ubuntu:
  Won't Fix

Bug description:
  When SSH host keys are missing, they should be automatically
  regenerated at boot time so SSH functions.  This is particularly
  useful if cloning VM's or using a VM template.

  I have modified the following using CentOS 7's .service file.

  /lib/systemd/system/ssh-keygen.service :

  [Unit]
  Description=OpenSSH Server Key Generation
  ConditionFileNotEmpty=|!/etc/ssh/ssh_host_rsa_key
  ConditionFileNotEmpty=|!/etc/ssh/ssh_host_ecdsa_key
  ConditionFileNotEmpty=|!/etc/ssh/ssh_host_ed25519_key
  PartOf=ssh.service sshd.socket

  [Service]
  ExecStart=/usr/sbin/dpkg-reconfigure openssh-server
  Type=oneshot
  RemainAfterExit=yes

  And added the following to ssh.service.

  /lib/systemd/system/ssh.service :
  [Unit]
  ...
  After=network.target ssh-keygen.service
  ...
  Wants=ssh-keygen.service
  ...

  I have tested this and it is working.

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

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

[Touch-packages] [Bug 1773279] [NEW] systemd-journalctl crashing from pthread_sigmask

[Justin Wood (Callek)]

Public bug reported:

I found related askubuntu thread https://askubuntu.com/questions/1039119
/systemd-journald-crashed-with-sigabrt-in-pthread-sigmask with no
answers yet.

I too have a Lenovo X1 Carbon Gen 6

On resume I seem to have the same issue:

Stack:
 #0 pthread_sigmask (how=2, newmask=, oldmask=0x0) at 
../sysdeps/unix/sysv/linux/pthread_sigmask.c:50
   local_newmask = {__val = {8392704,  }}
   result = 0
   __mask = 
   __word = 
   __mask = 
   __word = 
#1 0x0007f8f2f6dce49 in journal_file_set_offline () from 
/lib/systemd/libsystemd-shared-237.so

systemd version is 237-3ubuntu10 for amd64 on Bionic

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

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

Title:
  systemd-journalctl crashing from pthread_sigmask

Status in systemd package in Ubuntu:
  New

Bug description:
  I found related askubuntu thread
  https://askubuntu.com/questions/1039119/systemd-journald-crashed-with-
  sigabrt-in-pthread-sigmask with no answers yet.

  I too have a Lenovo X1 Carbon Gen 6

  On resume I seem to have the same issue:

  Stack:
   #0 pthread_sigmask (how=2, newmask=, oldmask=0x0) at 
../sysdeps/unix/sysv/linux/pthread_sigmask.c:50
 local_newmask = {__val = {8392704,  }}
 result = 0
 __mask = 
 __word = 
 __mask = 
 __word = 
  #1 0x0007f8f2f6dce49 in journal_file_set_offline () from 
/lib/systemd/libsystemd-shared-237.so

  systemd version is 237-3ubuntu10 for amd64 on Bionic

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

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

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

[Justin]

I have this problem on a Dell XPS 15 laptop touchpad running Linux Mint
18.3 based upon Ubuntu 16.04. This actually defaults to libinput, and
that's where I first encountered the issue. So I tried synaptic to see
if it would go away (it did not), which led me to this bug. So for me it
happens with both drivers, it's just worse under synaptic. With
libinput, it doesn't jump as far across the screen. But it does jump,
under the scenario described in #52 -- you're moving the mouse with one
finger to where you want to click, and you click with the other finger.
But at that moment the pointer jumps in the direction of the other
pointer (for right-handed people clicking with their pointer finger,
this is to the bottom left).

Sadly, these are touchpads without dedicated buttons, but being used by
users who are used to having and using dedicated buttons. In either
case, it's quite frustrating. And it does not occur under windows, so it
isn't a hardware-only issue.

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

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

Status in xorg package in Ubuntu:
  Confirmed

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

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

  Thanks,
  MZ

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

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

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

[Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

[Justin Beitz]

Issue remains for me as well 18.04 - 3.28.1

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Justin Nichols]

I do not understand how this did not hold up the release of Ubuntu
18.04.  Many apps now conflict because of this issue.

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

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

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

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

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

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

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

[Touch-packages] [Bug 1766119] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Justin Paul Johnson]

Public bug reported:

installing ubuntu 18.04 says to  me that the ca-certificates cant be
installed

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
Date: Sun Apr 22 13:29:09 2018
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2017-12-01 (142 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  installing ubuntu 18.04 says to  me that the ca-certificates cant be
  installed

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Sun Apr 22 13:29:09 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-12-01 (142 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1368411] Re: Cannot insert IPV6 rule before IPV4 rules

[Justin Coffman]

Over three years, actually. Coming up on four. Wow.

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

Title:
  Cannot insert IPV6 rule before IPV4 rules

Status in ufw:
  New
Status in ufw package in Ubuntu:
  Confirmed

Bug description:
  I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when 
IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered  6 to 10,  the 
following command:
  [code]
  ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  errors with "ERROR: Invalid position '1'".

  However, the command
  [code]
  ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  succeeds.

  In my case, this poses a problem, since I am trying to insert rules
  from a script against brute force attacks. The script needs to insert
  blocking rules before a number of other rules that open up some ports
  (since the order of rules is important in ufw). However since the
  number of IPV4 rules will be changing all the time, the position of
  the first available number for an IPV6 address is hard to determine.

  Proposed solution: either allow IPV6 rules to precede IPV4 rules, or
  implement a keyword defining the first available position; e.g. "ufw
  insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1".

  BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu
  12.04.5 LTS,

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

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

[Touch-packages] [Bug 1368411] Re: Cannot insert IPV6 rule before IPV4 rules

[Justin Coffman]

Given the growing prevalence of IPv6 connectivity, this is a huge
problem for this package. This bug has been open for nearly three years.
Why is this still here?

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

Title:
  Cannot insert IPV6 rule before IPV4 rules

Status in ufw:
  New
Status in ufw package in Ubuntu:
  Confirmed

Bug description:
  I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when 
IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered  6 to 10,  the 
following command:
  [code]
  ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  errors with "ERROR: Invalid position '1'".

  However, the command
  [code]
  ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1
  [/code]
  succeeds.

  In my case, this poses a problem, since I am trying to insert rules
  from a script against brute force attacks. The script needs to insert
  blocking rules before a number of other rules that open up some ports
  (since the order of rules is important in ufw). However since the
  number of IPV4 rules will be changing all the time, the position of
  the first available number for an IPV6 address is hard to determine.

  Proposed solution: either allow IPV6 rules to precede IPV4 rules, or
  implement a keyword defining the first available position; e.g. "ufw
  insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1".

  BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu
  12.04.5 LTS,

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

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

[Touch-packages] [Bug 1753115] Re: add-apt-repository documentation does not mention --no-updates option

[Justin Luth]

related to 1559482 add-apt-repository manpage does not mention new -u
option

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

Title:
  add-apt-repository documentation does not mention --no-updates option

Status in software-properties package in Ubuntu:
  New

Bug description:
  The default has changed so that --updates is the default.  The man
  page should be updated to reflect that and to document the -n --no-
  updates option for 18.04

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

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

[Touch-packages] [Bug 1753115] [NEW] add-apt-repository documentation does not mention --no-updates option

[Justin Luth]

Public bug reported:

The default has changed so that --updates is the default.  The man page
should be updated to reflect that and to document the -n --no-updates
option for 18.04

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic

** Tags added: bionic

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

Title:
  add-apt-repository documentation does not mention --no-updates option

Status in software-properties package in Ubuntu:
  New

Bug description:
  The default has changed so that --updates is the default.  The man
  page should be updated to reflect that and to document the -n --no-
  updates option for 18.04

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

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

[Touch-packages] [Bug 1750638] Re: Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite WICD working and native kernel support

[Justin]

Marked as confirmed based on several other reports on the internet:

https://askubuntu.com/questions/929027/qualcomm-atheros-qca6174-802
-11ac-wireless-network-adapter-168c003e-rev-32

https://ubuntuforums.org/showthread.php?t=2323812

etc

Fun update:
Bluetooth from the same card works perfectly fine once airplane mode is 
disabled.

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

Title:
   Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite
  WICD working and native kernel support

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This fails in a similar manner from 16.04 to 18.04, in both gnome and
  unity where applicable. Details of failure in 18.04:

  System always boots in airplane mode, no matter what. When you disable
  it and go to turn the wifi on in system settings, it hangs while doing
  so, but sometimes works and shows wifi, though it usually doesn't. I
  can't reproduce the cause of success of failure, but the wifi settings
  menu does immediately stop updating new networks after this point no
  matter what. The wifi menu in the top right never works at all.

  How I know it's not a hardware issue:
  It works in windows
  It works in WICD
  People say it works in other distros
  It shows up under lshw -C network as expected

  How I know it's not a firmware issue:
  It works in other distros
  It works in WICD

  How I know it's not a driver issue:
  It's natively supported in the kernel after an open source driver that worked 
for everyone was merged (which no one could get properly with Ubuntu's network 
manager)
  It shows up under lshw -C network as expected
  It works with WICD

  This is the default wifi card for a ton of new Lenovo laptops, so this
  is actually a serious issue.

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

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

[Touch-packages] [Bug 1750638] [NEW] Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite WICD working and native kernel support

[Justin]

Public bug reported:

This fails in a similar manner from 16.04 to 18.04, in both gnome and
unity where applicable. Details of failure in 18.04:

System always boots in airplane mode, no matter what. When you disable
it and go to turn the wifi on in system settings, it hangs while doing
so, but sometimes works and shows wifi, though it usually doesn't. I
can't reproduce the cause of success of failure, but the wifi settings
menu does immediately stop updating new networks after this point no
matter what. The wifi menu in the top right never works at all.

How I know it's not a hardware issue:
It works in windows
It works in WICD
People say it works in other distros
It shows up under lshw -C network as expected

How I know it's not a firmware issue:
It works in other distros
It works in WICD

How I know it's not a driver issue:
It's natively supported in the kernel after an open source driver that worked 
for everyone was merged (which no one could get properly with Ubuntu's network 
manager)
It shows up under lshw -C network as expected
It works with WICD

This is the default wifi card for a ton of new Lenovo laptops, so this
is actually a serious issue.

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

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

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

Title:
   Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite
  WICD working and native kernel support

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This fails in a similar manner from 16.04 to 18.04, in both gnome and
  unity where applicable. Details of failure in 18.04:

  System always boots in airplane mode, no matter what. When you disable
  it and go to turn the wifi on in system settings, it hangs while doing
  so, but sometimes works and shows wifi, though it usually doesn't. I
  can't reproduce the cause of success of failure, but the wifi settings
  menu does immediately stop updating new networks after this point no
  matter what. The wifi menu in the top right never works at all.

  How I know it's not a hardware issue:
  It works in windows
  It works in WICD
  People say it works in other distros
  It shows up under lshw -C network as expected

  How I know it's not a firmware issue:
  It works in other distros
  It works in WICD

  How I know it's not a driver issue:
  It's natively supported in the kernel after an open source driver that worked 
for everyone was merged (which no one could get properly with Ubuntu's network 
manager)
  It shows up under lshw -C network as expected
  It works with WICD

  This is the default wifi card for a ton of new Lenovo laptops, so this
  is actually a serious issue.

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

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

[Touch-packages] [Bug 1605911] Re: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other in

[Justin Case]

I note that running the following and restarting Ubuntu 16.04 LTS will
fix the problem, having *just* installed the Chrome (63.0.3239.132)
browser and immediately getting the panic regarding libunity9:

```
$ sudo apt-get install --reinstall libunity9
```

Presumably Chrome is the problem here. It likely overwrites the stable
version.

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

Title:
  package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  I don't know what's going on.  All I know is that I'm trying to
  install some programs to Ubuntu and it isn't working.  I tried the
  apt-get install -f to no avail.  I'm trying to install the Chrome
  browser from Google and Tetravex plus some updates and they won't
  install.   I'm new to Ubuntu and wanted to try it out as an
  alternative to Windows.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+16.04.20160701-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Jul 23 13:35:07 2016
  DuplicateSignature:
   package:libunity9:7.1.4+16.04.20160701-0ubuntu1
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libunity
  Title: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1732447] [NEW] rename no longer included in perl package, but still linked

[Justin Luth]

Public bug reported:

typing "rename" in a terminal responds with...
 
The program 'rename' can be found in the following packages:
 * perl
 * rename
Ask your administrator to install one of them

...but perl is already installed.  Internet reports suggest this has
started in 17.10.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: perl 5.26.0-8ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
Date: Wed Nov 15 16:24:29 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LC_PAPER=en_GB.UTF-8
SourcePackage: perl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  rename no longer included in perl package, but still linked

Status in perl package in Ubuntu:
  New

Bug description:
  typing "rename" in a terminal responds with...
   
  The program 'rename' can be found in the following packages:
   * perl
   * rename
  Ask your administrator to install one of them

  ...but perl is already installed.  Internet reports suggest this has
  started in 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: perl 5.26.0-8ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Wed Nov 15 16:24:29 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   LC_PAPER=en_GB.UTF-8
  SourcePackage: perl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1553669] Re: Annoying "call from" message

[Justin Abrahms]

Can reproduce the same with 16.04.3 and Bose QC35 headphones.

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

Title:
  Annoying "call from" message

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

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

[Touch-packages] [Bug 1711882] [NEW] package gir1.2-accounts-1.0:amd64 1.21+16.04.20160222-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Justin Goldsmith]

Public bug reported:

Error occurred while installing Unity on Ubuntu Mate 16.04.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gir1.2-accounts-1.0:amd64 1.21+16.04.20160222-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Sun Aug 20 00:39:04 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-07-17 (33 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: libaccounts-glib
Title: package gir1.2-accounts-1.0:amd64 1.21+16.04.20160222-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libaccounts-glib (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package gir1.2-accounts-1.0:amd64 1.21+16.04.20160222-0ubuntu1 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in libaccounts-glib package in Ubuntu:
  New

Bug description:
  Error occurred while installing Unity on Ubuntu Mate 16.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gir1.2-accounts-1.0:amd64 1.21+16.04.20160222-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Aug 20 00:39:04 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-07-17 (33 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libaccounts-glib
  Title: package gir1.2-accounts-1.0:amd64 1.21+16.04.20160222-0ubuntu1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

[Justin Erenkrantz]

We have tested these packages in zesty-proposed (openssl-1.0.2g-
1ubuntu11.1) and can confirm that the SHA extension codepath is executed
correctly and we see the accompanying expected performance improvements.

Thanks!

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Committed
Status in openssl source package in Yakkety:
  Fix Committed
Status in openssl source package in Zesty:
  Fix Committed
Status in openssl source package in Artful:
  Fix Released

Bug description:
  [Impact]

  * Context:

  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
  64bit only (Confirmed with AMD representative). Current OpenSSL
  version in Ryzens still calls SHA for SSSE3 routine as result a number
  of extensions were effectively masked on Ryzen and shows no
  improvement.

  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

  [2] - sha_ni: SHA1/SHA256 Instruction Extensions

  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...

  * Program to performs the CPUID check:

  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions

  ... Availability of the Intel® SHA Extensions on a particular
  processor can be determined by checking the SHA CPUID bit in
  CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
  using inline assembly, performs the CPUID check:

  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;

     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;

     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );

     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --

  On CPU with sha_ni the program return "1". Otherwise it return "0".

  [Test Case]

   * Reproducible with Xenial/Zesty/Artful release.

   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8

  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s

  * Openssl speed
  $ openssl speed sha1
  Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
  Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
  Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
  Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
  Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55

  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)

  [Regression Potential]

   * Note : IRC discussion with infinity :
  
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8

   * Note from irc discussion with apw and rbasak :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2

   * It basically allow openssl to take benefit of sha extension
  potential (mostly performance-wise) now that new 

[Touch-packages] [Bug 1687257] Re: AMD Radeon 480RX Proprietary Driver Management Issue

[Justin]

Thank you, that works to install steam, though installing steam via the
deb provided on steams website still doesn't work though and it's well
documented:

https://askubuntu.com/questions/771032/steam-not-opening-in-
ubuntu-16-04-lts

Also, why not include AMD drivers by default in the proprietary driver
manager on systems its supported in (ie 16.04)? I reinstalled 16.04 to
be able to use the drivers and had to manually install them.

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

Title:
  AMD Radeon 480RX Proprietary Driver Management Issue

Status in Ubuntu GNOME:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu Gnome 17.04 and have an AMD Radeon RX 480 graphics
  card, driving a monitor via display port with a little speaker
  connected to it via a standard analog audio cable in the back of the
  monitor (which would normally be driven by audio through display
  port).

  This is caused by a known issue in the open source amd driver that the
  kernels working to resolve, but will apparently take awhile due to
  some sort of technical issues: https://askubuntu.com/questions/792156
  /amdgpu-driver-wont-play-audio-over-displayport .

  Now that's fine, and there's nothing you guys here can do to fix this.
  However, the proprietary Ubuntu driver should be made available in the
  standard proprietary driver section of Ubuntu, since the non-
  proprietary driver has an incredibly difficult confusing installation
  installation method for Linux beginners, and not having audio through
  display port is a critical problem for certain PC configurations (like
  mine), people who are making their own steam machines, etc.

  Related Reddit thread attempting to triage:
  https://www.reddit.com/user/KezzBee .

  Please contact me if you have any questions or want to have me test
  things with my graphics card.

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

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

[Touch-packages] [Bug 1687257] Re: AMD Radeon 480RX Proprietary Driver Management Issue

[Justin]

AMDGPU pro does support 16.04 and it's still not an option for on it in
16.04.2 Gnome.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: software-center (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: software-center (Ubuntu)

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

Title:
  AMD Radeon 480RX Proprietary Driver Management Issue

Status in Ubuntu GNOME:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu Gnome 17.04 and have an AMD Radeon RX 480 graphics
  card, driving a monitor via display port with a little speaker
  connected to it via a standard analog audio cable in the back of the
  monitor (which would normally be driven by audio through display
  port).

  This is caused by a known issue in the open source amd driver that the
  kernels working to resolve, but will apparently take awhile due to
  some sort of technical issues: https://askubuntu.com/questions/792156
  /amdgpu-driver-wont-play-audio-over-displayport .

  Now that's fine, and there's nothing you guys here can do to fix this.
  However, the proprietary Ubuntu driver should be made available in the
  standard proprietary driver section of Ubuntu, since the non-
  proprietary driver has an incredibly difficult confusing installation
  installation method for Linux beginners, and not having audio through
  display port is a critical problem for certain PC configurations (like
  mine), people who are making their own steam machines, etc.

  Related Reddit thread attempting to triage:
  https://www.reddit.com/user/KezzBee .

  Please contact me if you have any questions or want to have me test
  things with my graphics card.

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

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

[Touch-packages] [Bug 1686275] [NEW] System message indicated a bug on reboot. Shows on reboot always.

[Justin Ngan]

Public bug reported:

System message indicated a bug on reboot. Shows on reboot always.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-49-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Apr 25 22:02:42 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GM206 [GeForce GTX 950] [1043:8581]
InstallationDate: Installed on 2017-03-12 (44 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
MachineType: Hewlett-Packard 550-009
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-49-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2015
dmi.bios.vendor: AMI
dmi.bios.version: 80.06
dmi.board.name: 2B2C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 1.01
dmi.chassis.asset.tag: MXX52512YG
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr80.06:bd04/01/2015:svnHewlett-Packard:pn550-009:pvr1.00:rvnHewlett-Packard:rn2B2C:rvr1.01:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 550-009
dmi.product.version: 1.00
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Apr 25 21:58:26 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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


** Tags: amd64 apport-bug ubuntu xenial

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/xorg/+question/628593

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

Title:
  System message indicated a bug on reboot. Shows on reboot always.

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  System message indicated a bug on reboot. Shows on reboot always.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 25 22:02:42 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM206 [GeForce GTX 950] [1043:8581]
  InstallationDate: Installed on 2017-03-12 (44 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Hewlett-Packard 550-009
  ProcEnviron:
   

[Touch-packages] [Bug 1496163] Re: i915 firmware is not copied to initrd

[Justin King-Lacroix]

Yep, that's good. Thanks!

** Tags added: verification-done

** Tags removed: verification-needed

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

Title:
  i915 firmware is not copied to initrd

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Fix Committed
Status in initramfs-tools source package in Vivid:
  Won't Fix
Status in initramfs-tools source package in Wily:
  Fix Released

Bug description:
  [ Impact ]

  On Skylake, skl_dmc firmware is not incorporated into the initramfs.
  This is because it is a symlink to a versioned blob and the initramfs-
  tools hook does not dereference symlinks. As the driver is actually
  loaded from the initramfs, the firmware is missing for the lifetime of
  the boot, which means that the GPU cannot enter its lowest available
  power states plus some hotplugging scenarios are broken. This all
  manifests itself as such in dmesg:

  [0.728803] i915 :00:02.0: Direct firmware load for 
i915/skl_dmc_ver1.bin failed with error -2
  [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to 
load firmware i915/skl_dmc_ver1.bin (0)

  [ Test Case ]

  After the fix has been applied and the initrd regenerates, the
  firmware should load successfully after a reboot.

  [ Regression Potential ]

  Unlikely, as the fix is part of Ubuntu since Wily.

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

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

[Touch-packages] [Bug 1575757] Re: Can't install kernel-nfs-server inside lxc container

[Justin]

My appologies if I'm missing something, but I cannot get the raw.lxc
setting to work for lxc.aa_profile=unconfined. I've tried setting it but
it doesn't seem to take. The .conf file that gets generated in
/var/log/lxd///&:lxd-factual-shrew_:
lxc.aa_profile=unconfined

It appears that the second entry is ignored. Is this expected? Is there
a way to work around the first lxc.aa_profile setting being created?

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

Title:
  Can't install kernel-nfs-server inside lxc container

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to virtualize a package that depends on NFS by installing
  it in an LXC container.

  The commands

  sudo apt-get install nfs-kernel-server
  sudo lxc-create -n nfstest -t download -- -d ubuntu -r xenial -a amd64
  sudo lxc-start -n nfstest
  sudo lxc-attach -n nfstest apt-get update
  sudo lxc-attach -n nfstest apt-get install nfs-kernel-server

  should install NFS server software inside the container, but instead
  fail with

  ...
  Not creating home directory `/var/lib/nfs'.
  nfs-utils.service is a disabled or a static unit, not starting it.
  Setting up nfs-kernel-server (1:1.2.8-9ubuntu12) ...
  A dependency job for nfs-server.service failed. See 'journalctl -xe' for 
details.
  nfs-server.service couldn't start.
  Creating config file /etc/exports with new version
  Creating config file /etc/default/nfs-kernel-server with new version
  A dependency job for nfs-server.service failed. See 'journalctl -xe' for 
details.
  invoke-rc.d: initscript nfs-kernel-server, action "start" failed.
  dpkg: error processing package nfs-kernel-server (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for systemd (229-4ubuntu4) ...
  Errors were encountered while processing:
   nfs-kernel-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  sudo lxc-attach -n nfstest journalctl -xe reports:

  Apr 27 15:42:59 nfstest systemd[1]: Failed to mount NFSD configuration 
filesystem
  -- Subject: Unit proc-fs-nfsd.mount has failed
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- Unit proc-fs-nfsd.mount has failed.
  -- The result is failed.

  Presumably this is intended, and there is a way to configure lxc to allow
  running nfs servers inside it (there are rumors of success on the web), but 
  https://help.ubuntu.com/lts/serverguide/lxc.html  is silent on the issue,
  and doesn't even mention the word nfs.
  Likewise, https://help.ubuntu.com/lts/serverguide/network-file-system.html
  doesn't even mention lxc.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.0-0ubuntu2
  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
  CurrentDesktop: Unity
  Date: Wed Apr 27 08:19:41 2016
  InstallationDate: Installed on 2016-03-26 (32 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

[Justin King-Lacroix]

Any idea when this will be released to Trusty?

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Trusty:
  Invalid
Status in initramfs-tools source package in Trusty:
  Fix Committed
Status in cryptsetup source package in Vivid:
  Invalid
Status in initramfs-tools source package in Vivid:
  Won't Fix

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
severe error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

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

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

[Touch-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

[Justin King-Lacroix]

i915 drivers are now in the initramfs, as required.

** Tags added: verification-done

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Trusty:
  Invalid
Status in initramfs-tools source package in Trusty:
  Fix Committed
Status in cryptsetup source package in Vivid:
  Invalid
Status in initramfs-tools source package in Vivid:
  Won't Fix

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
severe error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

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

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

[Touch-packages] [Bug 1642704] Re: initramfs-tools on Trusty doesn't handle symlinks in newer linux-firmware packages correctly

[Justin King-Lacroix]

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

This duplicate mark is true, but that bug isn't gaining much traction.
We really need this fixed.

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

Title:
  initramfs-tools on Trusty doesn't handle symlinks in newer linux-
  firmware packages correctly

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  $ update-initramfs -k 4.4.0-47-generic -c
  update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic
  $ sudo cat /boot/initrd.img-4.4.0-47-generic |unxz |cpio -i 
--no-absolute-filenames 
  185780 blocks
  $ ls lib/firmware/i915/
  $ ls /lib/firmware/i915/
  bxt_dmc_ver1_04.bin  bxt_dmc_ver1.bin@skl_dmc_ver1.bin@  
skl_guc_ver4_3.bin
  bxt_dmc_ver1_05.bin  skl_dmc_ver1_23.bin  skl_guc_ver1_1059.bin  
skl_guc_ver4.bin@
  bxt_dmc_ver1_06.bin  skl_dmc_ver1_26.bin  skl_guc_ver1.bin@
  $

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

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

[Touch-packages] [Bug 1642707] Re: initramfs-tools on Trusty doesn't include i915_bpo.ko

[Justin King-Lacroix]

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

Checked, and this is fixed in the version in -proposed- from that bug.

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

Title:
  initramfs-tools on Trusty doesn't include i915_bpo.ko

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  New

Bug description:
  initramfs-tools on Trusty doesn't include i915_bpo.ko, causing
  problems on Skylake

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

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

[Touch-packages] [Bug 1642707] Re: initramfs-tools on Trusty doesn't include i915_bpo.ko

[Justin King-Lacroix]

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

Trusty is the one I care about, not Zesty.

What does a "test case" mean in detail? Happy to help, I just want to
know exactly what I need to do.

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

Title:
  initramfs-tools on Trusty doesn't include i915_bpo.ko

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  New

Bug description:
  initramfs-tools on Trusty doesn't include i915_bpo.ko, causing
  problems on Skylake

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

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

[Touch-packages] [Bug 1496163] Re: i915 firmware is not copied to initrd

[Justin King-Lacroix]

Hi guys,

This is still biting us. Can we please have this fixed? See LP #1642704
for details. The fix is one character.

Justin

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

Title:
  i915 firmware is not copied to initrd

Status in Skylinux:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Vivid:
  In Progress
Status in initramfs-tools source package in Wily:
  Fix Released

Bug description:
  On Skylake, the skl_dmc firmware is failing to load. From dmesg:

  [0.728803] i915 :00:02.0: Direct firmware load for 
i915/skl_dmc_ver1.bin failed with error -2
  [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to 
load firmware i915/skl_dmc_ver1.bin (0)

  This means the GPU can't enter its lowest available power states, plus
  many display hotplugging scenarios (that only the skl_dmc firmware can
  handle) are broken.

  On a whim I tried some other firmware versions:

  1) pointed the skl_dmc_ver1.bin symlink to skl_dmc_ver1_18.bin
  (instead of skl_dmc_ver1_19.bin)

  2) downloaded the latest (skl_dmc_ver1_21.bin) and pointed the
  skl_dmc_ver1.bin symlink to it

  But neither corrected the situation.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-10-generic 4.2.0-10.11
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1251 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 15 16:21:24 2015
  HibernationDevice: RESUME=UUID=637df075-0afa-420f-a3ca-342be8bf297f
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:0833 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 004: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader 
Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic 
root=UUID=f967534a-9cc3-4d1a-a7f3-72d28959e3c6 ro i915.verbose_state_checks=1 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-10-generic N/A
   linux-backports-modules-4.2.0-10-generic  N/A
   linux-firmware1.147
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0403
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0403:bd08/19/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1447756] Re: [SRU] segfault in log.c code causes phone reboot loops

[Justin King-Lacroix]

Not really. The bug is hugely intermittent as it stands.

However, I can confirm we're experiencing this on our fleet.

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

Title:
  [SRU] segfault in log.c code causes phone reboot loops

Status in Canonical System Image:
  Fix Released
Status in upstart :
  Fix Committed
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Utopic:
  Won't Fix
Status in upstart source package in Vivid:
  Won't Fix
Status in upstart source package in Wily:
  Fix Released
Status in upstart package in Ubuntu RTM:
  Fix Released

Bug description:
  = Summary =

  The version of Upstart in vivid is affected by a coule of bugs relating
  to the flushing data from early-boot jobs to disk which can both result
  in a crash:

  == Problem 1 ==

  An internal list is mishandled meaning a crash could occur randomly.

  == Problem 2 ==

  Jobs which spawn processes in the background then themselves exit can
  cause a crash due.

  = Explanation of how Upstart flushes early job output =

  If an Upstart job starts *and ends* early in the boot sequence (before
  the log partition is mounted and writable) and produces output to its
  stdout/stderr, Upstart will cache the output for later flushing by
  adding the 'Log' object associated with the 'Job' to a list.

  When the log partition is mounted writable, the
  /etc/init/flush-early-job-log.conf job is run which calls "initctl
  notify-disk-writeable". This is a signal to Upstart to flush its cache
  of early-boot job output which takes the form of iterating the
  'log_unflushed_files' list and flushing all the 'Log' entries to disk.

  = Code Specifics =

  There are 2 issues (note that the numbers used below match those used in
  the Summary).

  == Problem 1 detail ==

  Due to a bug in the way the 'log_unflushed_files' list is handled (the
  'Log' cannot be added to the list directly, so is added via an
  intermediary ('NihListElem') node), a crash can result when iterating
  the list since the 'Log' is freed, but NOT the intermediary node. The
  implication is that it is possible for the intermediary node to be
  attempt to dereference already-freed data, resulting in a crash.

  == Problem 2 detail ==

  If a job spawns a process in the background, then itself exits, that
  jobs 'Log' entry will be added to the 'log_unflushed_files' list. But,
  if the background process produces output and then exits before Upstart
  attempts to flush the original jobs data to disk, the 'NihIo'
  corresponding to the log will be serviced automatically and the data
  flushed to disk. The problem comes when Upstart receives the
  notification to flush the 'log_unflushed_files' list, since that list
  now contains an entry which has already been freed (since all its data
  has already been flushed). The result is an assertion failure.

  = Fix =

  == Problem 1 fix ==

  Correct the 'log_unflushed_files' list handling by freeing the
  'NihListElem' (which will automatically free the 'Log' object), not by
  simply freeing the 'Log' object itself.

  * Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/
  * New Upstart test added to avoid regression?: Yes.

  == Problem 2 fix ==

  Correct the assumption that the only entries in the
  'log_unflushed_files' list will always have data to flush by checking if
  there is in fact any data to flush; if not, remove the entry from the
  'log_unflushed_files' list since it has already been handled
  automatically by the 'NihIo'.

  * Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix
  * New Upstart test added to avoid regression?: Yes.

  = Workarounds =

  If a system is affected by this bug, it will be manifested by a crash
  early in the boot sequence.

  To overcome the issue, either:

  a) Boot by adding "--no-log" to the kernel command-line.

  b) Disable the flush-early-job-log job (assuming the machine is
  bootable) by running the following:

 $ echo manual | sudo tee -a /etc/init/flush-early-job-log.override

  = Impact =

  The issue has been present in Upstart since logging was introduced but
  no known instances of crashes relating to these problems have been
  reported prior to this bug being reported (which relates the the issue
  being seen on a very small subset of specific Ubuntu Touch phone
  hardware where Upstart is used as the system init daemon).

  Note that vivid still uses Upstart for managing the graphical session,
  but now uses systemd by default for the system init daemon. Since the session 
(Upstart) init does not even require 
  a flush-early-job-log, the exposure to both the bug and the updated fix 
codepath is extremely limited.

  = Test Case =

  This bug is extremely hard to surface so the approach is simply to
  check that the internal list can be iterated correctly by:

  1) Booting the system 

[Touch-packages] [Bug 1642704] [NEW] initramfs-tools on Trusty doesn't handle symlinks in newer linux-firmware packages correctly

[Justin King-Lacroix]

Public bug reported:

$ update-initramfs -k 4.4.0-47-generic -c
update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic
$ sudo cat /boot/initrd.img-4.4.0-47-generic |unxz |cpio -i 
--no-absolute-filenames 
185780 blocks
$ ls lib/firmware/i915/
$ ls /lib/firmware/i915/
bxt_dmc_ver1_04.bin  bxt_dmc_ver1.bin@skl_dmc_ver1.bin@  
skl_guc_ver4_3.bin
bxt_dmc_ver1_05.bin  skl_dmc_ver1_23.bin  skl_guc_ver1_1059.bin  
skl_guc_ver4.bin@
bxt_dmc_ver1_06.bin  skl_dmc_ver1_26.bin  skl_guc_ver1.bin@
$

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


** Tags: trusty

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

Title:
  initramfs-tools on Trusty doesn't handle symlinks in newer linux-
  firmware packages correctly

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  $ update-initramfs -k 4.4.0-47-generic -c
  update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic
  $ sudo cat /boot/initrd.img-4.4.0-47-generic |unxz |cpio -i 
--no-absolute-filenames 
  185780 blocks
  $ ls lib/firmware/i915/
  $ ls /lib/firmware/i915/
  bxt_dmc_ver1_04.bin  bxt_dmc_ver1.bin@skl_dmc_ver1.bin@  
skl_guc_ver4_3.bin
  bxt_dmc_ver1_05.bin  skl_dmc_ver1_23.bin  skl_guc_ver1_1059.bin  
skl_guc_ver4.bin@
  bxt_dmc_ver1_06.bin  skl_dmc_ver1_26.bin  skl_guc_ver1.bin@
  $

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

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

[Touch-packages] [Bug 1642707] Re: initramfs-tools on Trusty doesn't include i915_bpo.ko

[Justin King-Lacroix]

Bug is on hooks/framebuffer: add a line "copy_modules_dir
kernel/ubuntu/i915"

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

Title:
  initramfs-tools on Trusty doesn't include i915_bpo.ko

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  initramfs-tools on Trusty doesn't include i915_bpo.ko, causing
  problems on Skylake

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

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

[Touch-packages] [Bug 1642707] [NEW] initramfs-tools on Trusty doesn't include i915_bpo.ko

[Justin King-Lacroix]

Public bug reported:

initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems
on Skylake

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


** Tags: trusty

** Tags added: trusty

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

Title:
  initramfs-tools on Trusty doesn't include i915_bpo.ko

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  initramfs-tools on Trusty doesn't include i915_bpo.ko, causing
  problems on Skylake

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

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

[Touch-packages] [Bug 1447756] Re: [SRU] segfault in log.c code causes phone reboot loops

[Justin King-Lacroix]

Yep, this is definitely affecting Trusty as well. Is there any chance
the fix will be backported?

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

Title:
  [SRU] segfault in log.c code causes phone reboot loops

Status in Canonical System Image:
  Fix Released
Status in upstart :
  Fix Committed
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Utopic:
  Won't Fix
Status in upstart source package in Vivid:
  Won't Fix
Status in upstart source package in Wily:
  Fix Released
Status in upstart package in Ubuntu RTM:
  Fix Released

Bug description:
  = Summary =

  The version of Upstart in vivid is affected by a coule of bugs relating
  to the flushing data from early-boot jobs to disk which can both result
  in a crash:

  == Problem 1 ==

  An internal list is mishandled meaning a crash could occur randomly.

  == Problem 2 ==

  Jobs which spawn processes in the background then themselves exit can
  cause a crash due.

  = Explanation of how Upstart flushes early job output =

  If an Upstart job starts *and ends* early in the boot sequence (before
  the log partition is mounted and writable) and produces output to its
  stdout/stderr, Upstart will cache the output for later flushing by
  adding the 'Log' object associated with the 'Job' to a list.

  When the log partition is mounted writable, the
  /etc/init/flush-early-job-log.conf job is run which calls "initctl
  notify-disk-writeable". This is a signal to Upstart to flush its cache
  of early-boot job output which takes the form of iterating the
  'log_unflushed_files' list and flushing all the 'Log' entries to disk.

  = Code Specifics =

  There are 2 issues (note that the numbers used below match those used in
  the Summary).

  == Problem 1 detail ==

  Due to a bug in the way the 'log_unflushed_files' list is handled (the
  'Log' cannot be added to the list directly, so is added via an
  intermediary ('NihListElem') node), a crash can result when iterating
  the list since the 'Log' is freed, but NOT the intermediary node. The
  implication is that it is possible for the intermediary node to be
  attempt to dereference already-freed data, resulting in a crash.

  == Problem 2 detail ==

  If a job spawns a process in the background, then itself exits, that
  jobs 'Log' entry will be added to the 'log_unflushed_files' list. But,
  if the background process produces output and then exits before Upstart
  attempts to flush the original jobs data to disk, the 'NihIo'
  corresponding to the log will be serviced automatically and the data
  flushed to disk. The problem comes when Upstart receives the
  notification to flush the 'log_unflushed_files' list, since that list
  now contains an entry which has already been freed (since all its data
  has already been flushed). The result is an assertion failure.

  = Fix =

  == Problem 1 fix ==

  Correct the 'log_unflushed_files' list handling by freeing the
  'NihListElem' (which will automatically free the 'Log' object), not by
  simply freeing the 'Log' object itself.

  * Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/
  * New Upstart test added to avoid regression?: Yes.

  == Problem 2 fix ==

  Correct the assumption that the only entries in the
  'log_unflushed_files' list will always have data to flush by checking if
  there is in fact any data to flush; if not, remove the entry from the
  'log_unflushed_files' list since it has already been handled
  automatically by the 'NihIo'.

  * Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix
  * New Upstart test added to avoid regression?: Yes.

  = Workarounds =

  If a system is affected by this bug, it will be manifested by a crash
  early in the boot sequence.

  To overcome the issue, either:

  a) Boot by adding "--no-log" to the kernel command-line.

  b) Disable the flush-early-job-log job (assuming the machine is
  bootable) by running the following:

 $ echo manual | sudo tee -a /etc/init/flush-early-job-log.override

  = Impact =

  The issue has been present in Upstart since logging was introduced but
  no known instances of crashes relating to these problems have been
  reported prior to this bug being reported (which relates the the issue
  being seen on a very small subset of specific Ubuntu Touch phone
  hardware where Upstart is used as the system init daemon).

  Note that vivid still uses Upstart for managing the graphical session,
  but now uses systemd by default for the system init daemon. Since the session 
(Upstart) init does not even require 
  a flush-early-job-log, the exposure to both the bug and the updated fix 
codepath is extremely limited.

  = Test Case =

  This bug is extremely hard to surface so the approach is simply to
  check that the internal list can be iterated correctly by:

  1) Booting the system with upstart
 

[Touch-packages] [Bug 1603729] Re: webapp option --enable-media-hub-audio breaks audio stream

[Justin McPherson]

** Branch linked: lp:~justinmcp/media-hub/1603729

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

Title:
  webapp option --enable-media-hub-audio breaks audio stream

Status in Canonical System Image:
  Confirmed
Status in webapps-sprint:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  My webapp "KlassikRadio" does not work any more.

  Opening the webapp opens the window as expected. Nevertheless the
  audio keeps dry. The phone remains silent.

  I have played around and found out that the option: --enable-media-
  hub-audio breaks the audio stream. When I take this option off the
  KlassikRadio.desktop file it works.

  I am using:

  current build number: 387
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-07-16 08:46:05
  version version: 387
  version ubuntu: 20160716
  version device: 20160606-ab415b2
  version custom: 20160701-981-38-14

  Nevertheless this issue is around since several weeks. I assume the
  option still works with OTA11 but I can not proof this right now.

  Can someone have a look? Is the option not available any more in the
  latest release or is it just a bug? The option is still mentioned in:

  https://developer.ubuntu.com/en/phone/web/ubuntu-webapps-guide/

  Thanks for your support. If someone wants to test this, the
  KlassikRadio app version 0.30 has this option enabled. I will put
  another version (0.31) in the store in the next days before OTA12
  comes along, where I will take this option out and replace it with
  "keep-display-on" in the apparmor-file.

  The keep-display-on solution is not nice. Are there any other options
  I could use alternatively?

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

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

[Touch-packages] [Bug 1606051] [NEW] dhclient fails to get address after latest patches

[Justin Alcorn]

Public bug reported:

>From ASkUbuntu entry http://askubuntu.com/questions/801136/recent-
patches-broke-dhclient/802390

Running 16.04.01 LTS recently upgraded from 15.10. System is a home firewall 
with enp1s0 as LAN interface statically assigned and enp2s0 is WAN interface 
using DHCP, connected to modem.
Ran apt-get upgrade and on reboot enp2s0 had no address. running ifdown enp2s0 
and then ifup enp2s0 gave me

root@sam:~# ifup enp2s0
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/enp2s0/d0:50:99:21:80:f8
Sending on   LPF/enp2s0/d0:50:99:21:80:f8
Sending on   Socket/fallback
DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 3 (xid=0xd998571a)
send_packet: Network is down
dhclient.c:2098: Failed to send 300 byte long packet over enp2s0 interface.
receive_packet failed on enp2s0: Network is down
DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 5 (xid=0xd998571a)
send_packet: Network is down
Running ifconfig enp2s0 up and dhclient enp2s0 gave similar results, but 
eventually /var/log/syslog showed a dhclient ipv4 lease being obtained - but 
the enp2s0 had only an IPv6 address, which appears to have come from 
avahi-daemon.

I then manually configured the enp2s0 interface with ifconfig enp2s0
xxx.xxx.xxx.xxx netmask 255.255.248.0 and put in a default route based
on the lease info in dhclient.leases and I'm back online. But if I
reboot or try to get dhclient to work, I continue to get the network is
down errors.

apparmor is disabled, so that's not it. iptables is set to allow all
DHCP traffic (67/udp and 68/udp) and all RELATED,ESTABLISHED traffic
from enp2s0.

enp2s0 and enp2s0 are the same hardware.

root@sam:~# lshw -class network
  *-network
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:01:00.0
   logical name: enp1s0
   version: 01
   serial: 04:8d:38:5d:20:17
   size: 100Mbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm vpd msi pciexpress bus_master cap_list rom ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full ip=yyy.yyy.yyy.yyy latency=0 link=yes 
multicast=yes port=MII speed=100Mbit/s
   resources: irq:38 ioport:e000(size=256) memory:ffa0-ffa00fff 
memory:ffa2-ffa3
  *-network
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:02:00.0
   logical name: enp2s0
   version: 11
   serial: d0:50:99:21:80:f8
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 
ip=xxx.xxx.xxx.xxx latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
   resources: irq:40 ioport:d000(size=256) memory:ff90-ff900fff 
memory:d080-d0803fff
Ideas? remember, this happened right after patching.

networking network-manager dhclient

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-client 4.3.3-5ubuntu12.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jul 24 15:33:19 2016
InstallationDate: Installed on 2016-03-01 (145 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: isc-dhcp
UpgradeStatus: Upgraded to xenial on 2016-06-22 (32 days ago)
mtime.conffile..etc.dhcp.debug: 2016-06-28T18:13:33.371977

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  dhclient fails to get address after latest patches

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  From ASkUbuntu entry http://askubuntu.com/questions/801136/recent-
  patches-broke-dhclient/802390

  Running 16.04.01 LTS recently upgraded from 15.10. System is a home firewall 
with enp1s0 as LAN interface statically assigned and enp2s0 is WAN interface 
using DHCP, connected to modem.
  Ran apt-get upgrade and on reboot enp2s0 had no address. running ifdown 
enp2s0 and then ifup enp2s0 gave me

  root@sam:~# ifup enp2s0
  Internet Systems 

[Touch-packages] [Bug 1584072] [NEW] package lib32z1-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386

[Justin Michael Cloutier]

Public bug reported:

Just trying to install the tools to build the Android Open Source
Project. Nothing special to note, I just ran the command that is
recommended on the AOSP website.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lib32z1-dev (not installed)
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Fri May 20 10:05:35 2016
ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which 
is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
InstallationDate: Installed on 2016-05-19 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.10ubuntu1
SourcePackage: zlib
Title: package lib32z1-dev (not installed) failed to install/upgrade: trying to 
overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package 
zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package lib32z1-dev (not installed) failed to install/upgrade: trying
  to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in
  package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4

Status in zlib package in Ubuntu:
  New

Bug description:
  Just trying to install the tools to build the Android Open Source
  Project. Nothing special to note, I just ran the command that is
  recommended on the AOSP website.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lib32z1-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri May 20 10:05:35 2016
  ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', 
which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: zlib
  Title: package lib32z1-dev (not installed) failed to install/upgrade: trying 
to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package 
zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1529395] Re: Cannot receive file from smartphone

[Justin Goetz]

Similar issue as well. Running 15.10 and transferring file from Android
KitKat device. Error Log:

May 16 17:17:23 justin-pc001-i7 obexd[3231]: CONNECT(0x0), (null)(0x)
May 16 17:17:23 justin-pc001-i7 obexd[3231]: CONNECT(0x0), (null)(0x0)
May 16 17:17:24 justin-pc001-i7 obexd[3231]: PUT(0x2), (null)(0x)
May 16 17:17:24 justin-pc001-i7 gnome-session[2874]: ** 
(gnome-user-share:3218): WARNING **: 'Bonded' authorization method not 
implemented
May 16 17:17:24 justin-pc001-i7 obexd[3231]: Agent replied with an error: 
org.bluez.obex.Error.Rejected, Not Authorized
May 16 17:17:24 justin-pc001-i7 obexd[3231]: PUT(0x2), FORBIDDEN(0x43)
May 16 17:17:24 justin-pc001-i7 obexd[3231]: DISCONNECT(0x1), (null)(0x)
May 16 17:17:24 justin-pc001-i7 obexd[3231]: DISCONNECT(0x1), SUCCESS(0x20)
May 16 17:17:24 justin-pc001-i7 obexd[3231]: disconnected: Transport got 
disconnected
May 16 17:17:24 justin-pc001-i7 bluetoothd[20826]: Unable to get io data for 
Object Push: getpeername: Transport endpoint is not connected (107)

I have obexftp installed as well as enabled Personal file sharing options for 
bluetooth. 
Hope this bug can get fixed soon.

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

Title:
  Cannot receive file from smartphone

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-user-share package in Ubuntu:
  Confirmed
Status in obexd package in Ubuntu:
  Confirmed

Bug description:
  Im today send from my telephone to computer music and 
  error's telephone displayed 

  im have activated options with receive files in gnome-user-share but
  this not working

  system log
  Dec 26 20:09:21 MATEUSZ-PIELA obexd[2215]: PUT(0x2), (null)(0x)
  Dec 26 20:09:21 MATEUSZ-PIELA gnome-session[1597]: ** 
(gnome-user-share:2206): WARNING **: 'Bonded' authorization method not 
implemented
  Dec 26 20:09:21 MATEUSZ-PIELA obexd[2215]: Agent replied with an error: 
org.bluez.obex.Error.Rejected, Not Authorized
  Dec 26 20:09:21 MATEUSZ-PIELA obexd[2215]: PUT(0x2), FORBIDDEN(0x43)
  Dec 26 20:09:21 MATEUSZ-PIELA obexd[2215]: DISCONNECT(0x1), (null)(0x)
  Dec 26 20:09:21 MATEUSZ-PIELA obexd[2215]: DISCONNECT(0x1), SUCCESS(0x20)
  Dec 26 20:09:21 MATEUSZ-PIELA obexd[2215]: disconnected: Transport got 
disconnected
  Dec 26 20:09:21 MATEUSZ-PIELA bluetoothd[663]: Unable to get io data for 
Object Push: getpeername: Transport endpoint is not connected (107)

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

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

[Touch-packages] [Bug 1479045] Re: E: Method gave invalid 103 Redirect message

[Justin Kremer]

Unfortunately, I just ran into this, too.  I am running Ubuntu 15.10 with apt 
Version: 1.0.10.2ubuntu1 which is slightly newer than the version  originally 
reported. 
I have no idea about apt 1.1 in 16.04. 
I was able to work around by only removing /var/lib/apt/lists/partial/*
Let me know if any additional information would be helpful. I found this while 
searching for the issue because I couldn't find any errors or logs that gave me 
very useful information. I was originally using 'apt-get update' in a terminal, 
and the Software & Updates preference pane gave the same error and told me to 
check my Internet connection.  (haha)

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

Title:
  E: Method gave invalid 103 Redirect message

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when running `apt update` or equivalent, the progress stops
  with error "E: Method gave invalid 103 Redirect message". This seems
  to happen especially when http:://mirrors.ubuntu.com/mirrors.txt is
  used.

  Current sources.list on this laptop is below. This happens with other
  my devices running Ubuntu too which sources.list is
  https://raw.githubusercontent.com/Mikaela/shell-
  things/a5c9156eb41826e3c2cb05ce09f9981d01ce979d/etc/apt/sources.list/15.04

  ```
  # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
  # newer versions of the distribution.
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid main restricted universe 
multiverse

  ## Major bug fix updates produced after the final vivid of the
  ## distribution.
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-updates main restricted 
universe multiverse

  ## N.B. software from this repository may not have been tested as
  ## extensively as that contained in the main vivid, although it includes
  ## newer versions of some applications which may provide useful features.
  ## Also, please note that software in backports WILL NOT receive any review
  ## or updates from the Ubuntu security team.
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-backports main restricted 
universe multiverse
  deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-security main restricted 
universe multiverse
  deb http://security.ubuntu.com/ubuntu vivid-security main restricted universe 
multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid main restricted 
universe multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-updates main restricted 
universe multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-backports main 
restricted universe multiverse
  deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-security main 
restricted universe multiverse
  deb-src http://security.ubuntu.com/ubuntu vivid-security main restricted 
universe multiverse

  ## Uncomment the following two lines to add software from Canonical's
  ## 'partner' repository.
  ## This software is not part of Ubuntu, but is offered by Canonical and the
  ## respective vendors as a service to Ubuntu users.
  deb http://archive.canonical.com/ubuntu vivid partner
  deb-src http://archive.canonical.com/ubuntu vivid partner

  # https://wiki.ubuntu.com/DebuggingProgramCrash
  # sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  deb http://ddebs.ubuntu.com vivid main restricted universe multiverse
  deb http://ddebs.ubuntu.com vivid-updates main restricted universe multiverse
  # Ignore unless you have enabled proposed below
  #deb http://ddebs.ubuntu.com vivid-proposed main restricted universe 
multiverse

  # https://wiki.ubuntu.com/Testing/EnableProposed
  #deb mirror://mirrors.ubuntu.com/mirrors.txt vivid-proposed main restricted 
universe multiverse
  #deb-src mirror://mirrors.ubuntu.com/mirrors.txt vivid-proposed main 
restricted universe multiverse
  ```

  This has been happening for a long time, possibly years and I was
  surprised that I wasn't able to find bug report by searching bugs for
  package "apt" with search term "103" redirect.

  I have learned that workaround for this issue is `cd
  /var/lib/apt/lists;rm *;cd partial;rm *;cd`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop:
   
  Date: Tue Jul 28 19:25:58 2015
  InstallationDate: Installed on 2015-07-14 (14 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

Re: [Touch-packages] [Bug 1483888] Ringtone cannot be heard when jack/headphones plugged

[Justin]

not just Aquarius E5 is affected by this bug - also affects my Meizu
MX5, and still not working following latest update

On 21 Oct 2015, at 19:20, Pat McGowan wrote:

> Other phones seem to always ring through speakers unless silent mode is
> on
> 
> ** Changed in: canonical-devices-system-image
>   Importance: Undecided => High
> 
> ** Changed in: canonical-devices-system-image
>   Status: New => Confirmed
> 
> ** Changed in: canonical-devices-system-image
>Milestone: None => ww46-2015
> 
> ** Changed in: canonical-devices-system-image
> Assignee: (unassigned) => Bill Filler (bfiller)
> 
> ** Also affects: ubuntu-ux
>   Importance: Undecided
>   Status: New
> 
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1479395).
> https://bugs.launchpad.net/bugs/1483888
> 
> Title:
>  Ringtone cannot be heard when jack/headphones plugged
> 
> Status in Canonical System Image:
>  Confirmed
> Status in Ubuntu UX:
>  New
> Status in telephony-service package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  Aquaris E5: Ringtone cannot be heard when jack/headphones are plugged.
> 
>  This I consider a bug, since user cannot depend on the such a device
>  with hearing calls in the morning.
> 
>  Typical scenario: listening to music/watching movies during the night
>  and falling asleep. It already happened several times to me that I did
>  not get awakened by the phone in the morning, since headphones were
>  plugged into the device and all the sounds could be heard only in
>  headphones.
> 
>  (The equivalent for the alarm clock is bug 1364647.)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1483888/+subscriptions

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

Title:
  Ringtone cannot be heard when jack/headphones plugged

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  Aquaris E5: Ringtone cannot be heard when jack/headphones are plugged.

  This I consider a bug, since user cannot depend on the such a device
  with hearing calls in the morning.

  Typical scenario: listening to music/watching movies during the night
  and falling asleep. It already happened several times to me that I did
  not get awakened by the phone in the morning, since headphones were
  plugged into the device and all the sounds could be heard only in
  headphones.

  (The equivalent for the alarm clock is bug 1364647.)

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

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

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

[Justin]

I had this problem about a month ago and deleted old kernels and it
worked fine at that point. I had tried a few different flavors before I
settled on Lubuntu so I thought that might be why I had the older kernel
versions floating around. Here I am with the same problem again.

Filesystem   Size  Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root  228G   14G  204G   7% /
none 4.0K 0  4.0K   0% /sys/fs/cgroup
udev 479M  8.0K  479M   1% /dev
tmpfs 99M  1.5M   98M   2% /run
none 5.0M 0  5.0M   0% /run/lock
none 493M   76K  493M   1% /run/shm
none 100M   24K  100M   1% /run/user
/dev/sda2237M  232M 0 100% /boot

sda2 is chock full again so I checked my kernels:

i   linux-image-3.16.0-44-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-3.16.0-45-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-3.16.0-46-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-3.16.0-48-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-3.16.0-49-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-3.16.0-50-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-extra-3.16.0-44-gen - Linux kernel extra modules for version 3.1
i   linux-image-extra-3.16.0-45-gen - Linux kernel extra modules for version 3.1
i   linux-image-extra-3.16.0-46-gen - Linux kernel extra modules for version 3.1
i   linux-image-extra-3.16.0-48-gen - Linux kernel extra modules for version 3.1
i   linux-image-extra-3.16.0-49-gen - Linux kernel extra modules for version 3.1

I am confident that I had deleted all but 49 and 50 last time but here
they are again. I'll admit that I am a relative noob on linux so the
problem may be with the user! I am posting this information primarily to
try and help. I'm going to delete the extra kernels again and see how it
goes.

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

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

Status in initramfs-tools:
  Confirmed
Status in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initramfs-tools

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

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

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

  WORKAROUND:

  Remove unused kernels using computer janitor or manually free space on
  your partition containing the /boot file system.

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

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

[Touch-packages] [Bug 1502380] [NEW] package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

[Justin]

Public bug reported:

Ubuntu 14.04.3 LTS
lightdm:
  Installed: 1.10.5-0ubuntu1.1
  Candidate: 1.10.5-0ubuntu1.1
  Version table:
 *** 1.10.5-0ubuntu1.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.10.0-0ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages


Package sends me into log in loop.  Tried to reconfigure, received error

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: lightdm 1.10.5-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
Uname: Linux 3.16.0-50-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.15
AptOrdering: lightdm: Purge
Architecture: amd64
Date: Fri Oct  2 22:19:25 2015
DuplicateSignature: package:lightdm:1.10.5-0ubuntu1.1:subprocess installed 
post-removal script returned error exit status 1
ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
InstallationDate: Installed on 2015-04-29 (156 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: lightdm
Title: package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04.3 LTS
  lightdm:
Installed: 1.10.5-0ubuntu1.1
Candidate: 1.10.5-0ubuntu1.1
Version table:
   *** 1.10.5-0ubuntu1.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.10.0-0ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  
  Package sends me into log in loop.  Tried to reconfigure, received error

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.5-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
  Uname: Linux 3.16.0-50-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  AptOrdering: lightdm: Purge
  Architecture: amd64
  Date: Fri Oct  2 22:19:25 2015
  DuplicateSignature: package:lightdm:1.10.5-0ubuntu1.1:subprocess installed 
post-removal script returned error exit status 1
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2015-04-29 (156 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: lightdm
  Title: package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1481923] [NEW] Crashes in Chrome on Trusty due to a bug in gtk+ 2.24.23

[Justin Hahn]

Public bug reported:

We are seeing incidences of this bug in Chrome: 
https://code.google.com/p/chromium/issues/detail?id=430910#c5

This is fixed upstream in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=nobug=777142

This is also fixed in vivid apparently (e.g.
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1425401)

Can we get this fix backported to Trusty?

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

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

Title:
  Crashes in Chrome on Trusty due to a bug in gtk+ 2.24.23

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  We are seeing incidences of this bug in Chrome: 
  https://code.google.com/p/chromium/issues/detail?id=430910#c5

  This is fixed upstream in Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=nobug=777142

  This is also fixed in vivid apparently (e.g.
  https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1425401)

  Can we get this fix backported to Trusty?

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

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

[Touch-packages] [Bug 1480189] [NEW] unable to insert pause in dial string

[Justin]

Public bug reported:

the dialer does not handle non numeric values - so it is not possible
use a comma or P to insert a pause. Most phones allow one to save a dial
string in contacts, for a conference call number for example, where a
pause followed by the call code allows very long strings to be entered
automatically.

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

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

Title:
  unable to insert pause in dial string

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  the dialer does not handle non numeric values - so it is not possible
  use a comma or P to insert a pause. Most phones allow one to save a
  dial string in contacts, for a conference call number for example,
  where a pause followed by the call code allows very long strings to be
  entered automatically.

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

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

[Touch-packages] [Bug 1479395] [NEW] silent mode engaged when headset plugged in

[Justin]

Public bug reported:

when a headset is plugged in the ringer turns off. Either set it to
prompt the user to choose silent mode or normal, or cancel this feature.

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

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

Title:
  silent mode engaged when headset plugged in

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  when a headset is plugged in the ringer turns off. Either set it to
  prompt the user to choose silent mode or normal, or cancel this
  feature.

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

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

[Touch-packages] [Bug 837557] Re: fraudulent DigiNotar certificate issuance

[Justin Means]

** Changed in: ca-certificates (Ubuntu)
 Assignee: Jamie Strandboge (jdstrand) = (unassigned)

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

Title:
  fraudulent DigiNotar certificate issuance

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in nss package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  Fix Released
Status in seamonkey package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Fix Released
Status in xulrunner-1.9.2 package in Ubuntu:
  Invalid
Status in ca-certificates source package in Lucid:
  Fix Released
Status in chromium-browser source package in Lucid:
  Fix Released
Status in firefox source package in Lucid:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in qt4-x11 source package in Lucid:
  Fix Released
Status in seamonkey source package in Lucid:
  Won't Fix
Status in thunderbird source package in Lucid:
  Fix Released
Status in xulrunner-1.9.2 source package in Lucid:
  Fix Released
Status in ca-certificates source package in Maverick:
  Fix Released
Status in chromium-browser source package in Maverick:
  Fix Released
Status in firefox source package in Maverick:
  Fix Released
Status in nss source package in Maverick:
  Fix Released
Status in qt4-x11 source package in Maverick:
  Fix Released
Status in seamonkey source package in Maverick:
  Won't Fix
Status in thunderbird source package in Maverick:
  Fix Released
Status in xulrunner-1.9.2 source package in Maverick:
  Fix Released
Status in ca-certificates source package in Natty:
  Fix Released
Status in chromium-browser source package in Natty:
  Fix Released
Status in firefox source package in Natty:
  Fix Released
Status in nss source package in Natty:
  Fix Released
Status in qt4-x11 source package in Natty:
  Fix Released
Status in seamonkey source package in Natty:
  Won't Fix
Status in thunderbird source package in Natty:
  Fix Released
Status in xulrunner-1.9.2 source package in Natty:
  Fix Released
Status in ca-certificates source package in Oneiric:
  Fix Released
Status in chromium-browser source package in Oneiric:
  Fix Released
Status in firefox source package in Oneiric:
  Fix Released
Status in nss source package in Oneiric:
  Fix Released
Status in qt4-x11 source package in Oneiric:
  Fix Released
Status in seamonkey source package in Oneiric:
  Won't Fix
Status in thunderbird source package in Oneiric:
  Fix Released
Status in xulrunner-1.9.2 source package in Oneiric:
  Invalid
Status in ca-certificates package in Debian:
  Fix Released

Bug description:
  USN Information: This is being tracked in USN-1197-*

  NOTE: The Firefox update causes a regression for certain Dutch sites which is 
being tracked in Bug #838322.
  NOTE #2: The current update for Thunderbird still shows the DigiNotar Root CA 
as trusted in the certificate manager.  This is due to Thunderbird using the 
system version of NSS. In this initial update, Thunderbird will actively 
distrust any certificate signed by the DigiNotar Root CA.  Future updates will 
properly show the root CA as distrusted in the certificate manager.

  WORKAROUND (from blog post):
  http://support.mozilla.com/en-US/kb/deleting-diginotar-ca-cert

  -

  http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-
  certificate/

  Qt 4.7 blog post: http://labs.qt.nokia.com/2011/09/07/what-the-
  diginotar-security-breach-means-for-qt-users-continued/

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

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

[Touch-packages] [Bug 1446658] Re: lxc-test-apparmor fails on aarch64

[Justin Zhao]

I also find the same issue in another ARM board, I can confirm that it's just 
following sentence to cause the failed result:
run_cmd lxc-create -t download -n c1 -- -d ubuntu -r trusty -a $ARCH

It will try to check the following file and download a image from website 
indexed in this file, if success, then create a container.
 http://images.linuxcontainers.org//meta/1.0/index-user
Because the parameter $ARCH is arm64 definitely, and I can't find any index 
with arm64 in above file and any arm64 directory in following position yet.
 http://images.linuxcontainers.org/images/ubuntu/vivid/

I guess this is just the root case of this issue.

I also find the similar sentence in following file, and all these test 
cases will fail on ARM board too, I think this is their common root cause.
lxc-test-apparmor-mount
lxc-test-usernic
lxc-test-autostart
lxc-test-usernic.in   

Beside this, I also found there are so many hard-code about trusty in 
multi lxc-tests cases listed as follows:
justin@D02-VIVID:~/lxc/lxc-1.1.2/src/tests$ grep -R 'trusty' .
./lxc-test-apparmor-mount:run_cmd lxc-create -t download -n $cname -- 
-d ubuntu -r trusty -a $ARCH
Binary file ./get_item.o matches
./lxc-test-usernic.in:run_cmd lxc-create -t download -n b1 -- -d 
ubuntu -r trusty -a $ARCH
./lxc-test-autostart:lxc-create -t download -n $CONTAINER_NAME -- -d 
ubuntu -r trusty -a $ARCH
./lxc-test-usernic:run_cmd lxc-create -t download -n b1 -- -d ubuntu 
-r trusty -a $ARCH
Binary file ./lxc-test-get_item matches
Binary file ./lxc-test-createtest matches
./lxc-test-unpriv:run_cmd lxc-create -t download -n c1 -- -d ubuntu -r 
trusty -a $ARCH

I'm afraid that if this will cause that these test cases can't be
compatible to different Ubuntu distribution?

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

Title:
  lxc-test-apparmor fails on aarch64

Status in apparmor package in Ubuntu:
  New

Bug description:
  Running lxc-test-apparmor fails on aarch64 (arm64) systems.

  The following files which are listed in files_to_deny[] in
  src/tests/aa.c:

 /sys/kernel/uevent_helper
 /proc/sys/kernel/sysrq

  are not denied, but should be.

  Perhaps I should be changing the apparmor profile for lxc before
  running the tests (but that's just a guess).

  I'm invoking the tests as:

 # for i in /usr/bin/lxc-test-* ; do $i || touch /tmp/$(basename
  $i).failed; done

  which results in the following failures:

lxc-test-apparmor.failed
lxc-test-autostart.failed
lxc-test-containertests.failed
lxc-test-unpriv.failed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.7-0ubuntu0.1
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.19.2 aarch64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: arm64
  Date: Tue Apr 21 13:17:28 2015
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  --- 
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: arm64
  DistroRelease: Ubuntu 14.04
  KernLog:
   
  Package: lxc 1.0.7-0ubuntu0.1
  PackageArchitecture: arm64
  ProcCmdline: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Tags:  trusty uec-images
  Uname: Linux 3.19.2 aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm libvirtd
  _MarkForUpload: True
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxcsyslog:

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

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

[Touch-packages] [Bug 1442977] Re: Font display issue

[Justin Toniazzo]

** Attachment added: An example of the issue in action.
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1442977/+attachment/4372799/+files/font_display_bug.png

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

Title:
  Font display issue

Status in xorg package in Ubuntu:
  New

Bug description:
  Text is occasionally rendered such that random letters throughout all
  applications are missing. This appears to only affect the system
  default font. Changing the text scaling factor via something like
  Ubuntu Tweak resolves the issue, as does changing the system default
  font. The issue reappears, however, upon reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.2
  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: Sat Apr 11 18:37:40 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.16.0-33-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0665]
  InstallationDate: Installed on 2015-04-08 (3 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed 
root=UUID=270c114a-a104-4702-bfb4-4fde27973a66 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0TRW8H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd03/12/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TRW8H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sat Apr 11 17:30:24 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152 
   vendor SHP
  xserver.version: 2:1.16.0-1ubuntu1.3

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

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

[Touch-packages] [Bug 1442977] [NEW] Font display issue

[Justin Toniazzo]

Public bug reported:

Text is occasionally rendered such that random letters throughout all
applications are missing. This appears to only affect the system default
font. Changing the text scaling factor via something like Ubuntu Tweak
resolves the issue, as does changing the system default font. The issue
reappears, however, upon reboot.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
Uname: Linux 3.16.0-34-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8.2
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: Sat Apr 11 18:37:40 2015
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 3.16.0-33-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 3.16.0-34-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0665]
InstallationDate: Installed on 2015-04-08 (3 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
MachineType: Dell Inc. XPS 13 9343
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed 
root=UUID=270c114a-a104-4702-bfb4-4fde27973a66 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/12/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0TRW8H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd03/12/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TRW8H:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Sat Apr 11 17:30:24 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5152 
 vendor SHP
xserver.version: 2:1.16.0-1ubuntu1.3

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


** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu utopic

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

Title:
  Font display issue

Status in xorg package in Ubuntu:
  New

Bug description:
  Text is occasionally rendered such that random letters throughout all
  applications are missing. This appears to only affect the system
  default font. Changing the text scaling factor via something like
  Ubuntu Tweak resolves the issue, as does changing the system default
  font. The issue reappears, however, upon reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.2
  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: Sat Apr 11 18:37:40 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.16.0-33-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0665]
  InstallationDate: Installed on 2015-04-08 (3 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: Dell Inc. XPS 13 9343
  

[Touch-packages] [Bug 1418626] Re: Embedded YouTube videos stuttering and not playing back smoothly

[Justin McPherson]

At this time, and from experimentation - a change of UA has no effect on
the container+codecs chosen by YT in the embedded case.

Changing the UA does affect the the mobile YT page.

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

Title:
  Embedded YouTube videos stuttering and not playing back smoothly

Status in Oxide Webview:
  New
Status in Web Browser App:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  Related to bug https://bugs.launchpad.net/webbrowser-app/+bug/1417258.

  Embedded youtube videos, like this:
  
http://m.bleacherreport.com/articles/2352016-papa-johns-airs-wrong-commercial-congratulates-seahawks-after-super-bowl

  or this:
  http://pages.ebay.com/shoptheworld/

  do not play back correctly. They exhibit stuttering and stopping, with
  oxide-renderer process using over 100% CPU.

  This was worked around on YouTube.com (and webapp) by using overriden
  UA string which makes YouTube send us a stream that we can playback
  smoothly. But this UA string is not presented to embedded videos
  within other sites.

  We should figure out how we can send the UA override to embedded
  videos (if possible), and if not what change could we make to our
  default UA string such that YouTube gives us content that we can
  render more efficiently.

  Other ideas?

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

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

[Touch-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage

[justin]

Experiencing same problem in Precise.  
Temporary fix by:sudo mv /usr/lib/unity/unity-panel-service ~
Then:ps -u | grep unity  to check service is stopped.

My conclusion is:  if there weren't bugs, we wouldn't need exterminators!
Cheers!

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

Title:
  unity-panel-service memory leak and 100% CPU usage

Status in The Application Menu:
  Fix Released
Status in Application Menu Indicator 13.10 series:
  Fix Released
Status in The Ubuntu Power Consumption Project:
  Fix Released
Status in Unity:
  Invalid
Status in Ubuntu:
  Fix Released
Status in indicator-appmenu package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid
Status in The Saucy Salamander:
  Fix Released
Status in indicator-appmenu source package in Saucy:
  Fix Released

Bug description:
  Impact: high CPU/memory usage from unity-panel-service

  Test case:

  Open a large image in the GIMP and activate a lot of items from the
  global menu. Using shortcuts is enough and faster to reproduce this
  bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity-
  panel-service increases steadily and it uses a lot of CPU shortly
  after activating the menu items in a short time.

  Regression potential: check that the menus are stable/working as they
  should

  -
  Just going about my business on Ubuntu Raring amd64 on an x230 and I heard 
the fan kick into action.  top showed me that unity-panel-service was consuming 
all the free cycles on one of my CPUs.  I killed it before my machine 
overheated, so I didn't attach a debugger to see why it was totally pegging out 
a  CPU.

  I'm not sure if this adds any context, but I was using a LibreOffice
  spreadsheet and I could not insert a table because the menu had lost
  it's mind, and then I observed the overly loaded CPU a very short
  while after that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+subscriptions

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

[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

[Justin Ossevoort]

I don't understand why this issue is not being picked up. It should
probably be considered a security bug, because it prevents people from
using the software updates.

I know my way around apt manually, but people that don't will be missing
their much needed security updates. And for every person that bother
reporting this issue here there are probably dozens that don't and are
oblivious of the update problem.

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

Title:
  launcher does not show minimized update manager while clicked

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix

Bug description:
  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

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

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

[Touch-packages] [Bug 789049] Re: gpgkeys doesn't find the key thru http proxy

[Justin Dossey]

This bug is actually with GnuPG; I have reported it here:

https://bugs.g10code.com/gnupg/issue1799

As this affects all current users of Ubuntu who must use a proxy, I
would recommend a Canonical-side workaround: configure the Squid servers
supporting keyserver.ubuntu.com to serve requests when no Host: header
is provided.

Currently, keyserver.ubuntu.com returns a 400 Bad Request when no Host:
header is provided.


** Bug watch added: GnuPG Bugs #1799
   https://bugs.g10code.com/gnupg/issue1799

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

Title:
  gpgkeys doesn't find the key thru http proxy

Status in GNU Privacy Guard:
  New
Status in gnupg package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnupg

  gpgkeys (called from apt-key) doesn't find a key when using a http
  proxy (set from env http_proxy):

  gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring 
/etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring 
/etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver-options 
http-proxy='http://10.51.0.95:3128/' --keyserver keyserver.ubuntu.com 
--recv-keys 10E239FF
  gpg: requesting key 10E239FF from hkp server keyserver.ubuntu.com
  gpgkeys: key 10E239FF not found on keyserver
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0

  on squid access.log:

  1306490082.847119 127.0.0.1 TCP_MISS/503 1478 GET
  http://keyserver.ubuntu.com:11371/pks/lookup? - DIRECT/91.189.89.49
  text/html

  while on a server without proxy works as expected:

  gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring 
/etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring 
/etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver 
keyserver.ubuntu.com --recv-keys 10E239FF
  gpg: requesting key 10E239FF from hkp server keyserver.ubuntu.com
  gpg: key 10E239FF: Launchpad Zentyal 2.0 series not changed
  gpg: Total number processed: 1
  gpg:  unchanged: 1

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

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

[Touch-packages] [Bug 1406177] Re: [20ANCTO1WW, Realtek ALC3232, Speaker, Internal] No sound at all (speakers or headphones)

[Justin]

Feel free to close this bug, I rebooted from the original Windows 8
drive and couldn't get the sounds to work either, even when re-
installing the sound drivers. It's just silent, even though sound output
registers in the volume control. So it would appear that this might be a
hardware issue. I'll have lenovo take a look and if I have further
issues I'll open another one referencing this one.

Fwiw, apparently sounds can be routed through the mini-DP port (via
HDMI), but I do not have an adapter so I did not try.

** Changed in: alsa-driver (Ubuntu)
   Status: New = Invalid

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

Title:
  [20ANCTO1WW, Realtek ALC3232, Speaker, Internal] No sound at all
  (speakers or headphones)

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  justin@j-ll-len:~$ lsb_release -rd
  Description:  Ubuntu 14.10
  Release:  14.10

  Expected:
  Sounds playback works out of the box on 14.10.

  What happens:
  Sound does not work out of the box on 14.10.

  Detailed report:

  After struggling and giving up on 14.04 on a Lenovo T440p (random
  complete lock-ups that wouldn't even respond to magic sysrq keys) I
  attempted 14.10 and it appears to work fine. No crashes, nvidia
  drivers install, all is well with the latest 2.28 BIOS version. This
  machine apparently has some issues with particular BIOS versions 
  1.14 (https://answers.launchpad.net/ubuntu/+question/246834).

  No matter what sounds settings I fiddle (via the GUI sound settings or
  alsamixer from the terminal) I cannot get it to play the test sounds
  or sounds in an application (Chrome, etc). The card is not muted, and
  it is detected in sound settings. The machine came with Windows, but I
  did not test sound before installing Ubuntu. I will test that shortly
  and update the bug with those results (to help determine if it might
  be a hardware failure). Hopefully the bug has attached relevant log
  output from the command I ran ubuntu-bug -s audio. But I'll aso
  attach the output of alsa-info.sh.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  justin 2307 F pulseaudio
   /dev/snd/pcmC1D0c:   justin 2307 F...m pulseaudio
   /dev/snd/controlC1:  justin 2307 F pulseaudio
justin 5731 F alsamixer
  CurrentDesktop: Unity
  Date: Sun Dec 28 19:36:19 2014
  InstallationDate: Installed on 2014-12-29 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  justin 2307 F pulseaudio
   /dev/snd/pcmC1D0c:   justin 2307 F...m pulseaudio
   /dev/snd/controlC1:  justin 2307 F pulseaudio
justin 5731 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [20ANCTO1WW, Realtek ALC3232, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET74WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET74WW(2.28):bd10/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1406177] Re: [20ANCTO1WW, Realtek ALC3232, Speaker, Internal] No sound at all (speakers or headphones)

[Justin]

Feel free to close this bug, I rebooted from the original Windows 8
drive and couldn't get the sounds to work either, even when re-
installing the sound drivers. It's just silent, even though sound output
registers in the volume control. So it would appear that this might be a
hardware issue. I'll have lenovo take a look and if I have further
issues I'll open another one referencing this one.

Fwiw, apparently sounds can be routed through the mini-DP port (via
HDMI), but I do not have an adapter so I did not try.

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

Title:
  [20ANCTO1WW, Realtek ALC3232, Speaker, Internal] No sound at all
  (speakers or headphones)

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  justin@j-ll-len:~$ lsb_release -rd
  Description:  Ubuntu 14.10
  Release:  14.10

  Expected:
  Sounds playback works out of the box on 14.10.

  What happens:
  Sound does not work out of the box on 14.10.

  Detailed report:

  After struggling and giving up on 14.04 on a Lenovo T440p (random
  complete lock-ups that wouldn't even respond to magic sysrq keys) I
  attempted 14.10 and it appears to work fine. No crashes, nvidia
  drivers install, all is well with the latest 2.28 BIOS version. This
  machine apparently has some issues with particular BIOS versions 
  1.14 (https://answers.launchpad.net/ubuntu/+question/246834).

  No matter what sounds settings I fiddle (via the GUI sound settings or
  alsamixer from the terminal) I cannot get it to play the test sounds
  or sounds in an application (Chrome, etc). The card is not muted, and
  it is detected in sound settings. The machine came with Windows, but I
  did not test sound before installing Ubuntu. I will test that shortly
  and update the bug with those results (to help determine if it might
  be a hardware failure). Hopefully the bug has attached relevant log
  output from the command I ran ubuntu-bug -s audio. But I'll aso
  attach the output of alsa-info.sh.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  justin 2307 F pulseaudio
   /dev/snd/pcmC1D0c:   justin 2307 F...m pulseaudio
   /dev/snd/controlC1:  justin 2307 F pulseaudio
justin 5731 F alsamixer
  CurrentDesktop: Unity
  Date: Sun Dec 28 19:36:19 2014
  InstallationDate: Installed on 2014-12-29 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  justin 2307 F pulseaudio
   /dev/snd/pcmC1D0c:   justin 2307 F...m pulseaudio
   /dev/snd/controlC1:  justin 2307 F pulseaudio
justin 5731 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [20ANCTO1WW, Realtek ALC3232, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET74WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET74WW(2.28):bd10/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1406177] [NEW] [20ANCTO1WW, Realtek ALC3232, Speaker, Internal] No sound at all (speakers or headphones)

[Justin]

Public bug reported:

justin@j-ll-len:~$ lsb_release -rd
Description:Ubuntu 14.10
Release:14.10

Expected:
Sounds playback works out of the box on 14.10.

What happens:
Sound does not work out of the box on 14.10.

Detailed report:

After struggling and giving up on 14.04 on a Lenovo T440p (random
complete lock-ups that wouldn't even respond to magic sysrq keys) I
attempted 14.10 and it appears to work fine. No crashes, nvidia drivers
install, all is well with the latest 2.28 BIOS version. This machine
apparently has some issues with particular BIOS versions  1.14
(https://answers.launchpad.net/ubuntu/+question/246834).

No matter what sounds settings I fiddle (via the GUI sound settings or
alsamixer from the terminal) I cannot get it to play the test sounds or
sounds in an application (Chrome, etc). The card is not muted, and it is
detected in sound settings. The machine came with Windows, but I did not
test sound before installing Ubuntu. I will test that shortly and update
the bug with those results (to help determine if it might be a hardware
failure). Hopefully the bug has attached relevant log output from the
command I ran ubuntu-bug -s audio. But I'll aso attach the output of
alsa-info.sh.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  justin 2307 F pulseaudio
 /dev/snd/pcmC1D0c:   justin 2307 F...m pulseaudio
 /dev/snd/controlC1:  justin 2307 F pulseaudio
  justin 5731 F alsamixer
CurrentDesktop: Unity
Date: Sun Dec 28 19:36:19 2014
InstallationDate: Installed on 2014-12-29 (0 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  justin 2307 F pulseaudio
 /dev/snd/pcmC1D0c:   justin 2307 F...m pulseaudio
 /dev/snd/controlC1:  justin 2307 F pulseaudio
  justin 5731 F alsamixer
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [20ANCTO1WW, Realtek ALC3232, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GLET74WW (2.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ANCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGLET74WW(2.28):bd10/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20ANCTO1WW
dmi.product.version: ThinkPad T440p
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug utopic

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

Title:
  [20ANCTO1WW, Realtek ALC3232, Speaker, Internal] No sound at all
  (speakers or headphones)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  justin@j-ll-len:~$ lsb_release -rd
  Description:  Ubuntu 14.10
  Release:  14.10

  Expected:
  Sounds playback works out of the box on 14.10.

  What happens:
  Sound does not work out of the box on 14.10.

  Detailed report:

  After struggling and giving up on 14.04 on a Lenovo T440p (random
  complete lock-ups that wouldn't even respond to magic sysrq keys) I
  attempted 14.10 and it appears to work fine. No crashes, nvidia
  drivers install, all is well with the latest 2.28 BIOS version. This
  machine apparently has some issues with particular BIOS versions 
  1.14 (https://answers.launchpad.net/ubuntu/+question/246834).

  No matter what sounds settings I fiddle (via the GUI sound settings or
  alsamixer from the terminal) I cannot get it to play the test sounds
  or sounds in an application (Chrome, etc). The card is not muted, and
  it is detected in sound settings. The machine came with Windows, but I
  did not test sound before installing Ubuntu. I will test that shortly
  and update the bug with those results (to help determine if it might
  be a hardware failure). Hopefully the bug has attached relevant log
  output from the command I ran ubuntu-bug -s audio. But I'll aso
  attach the output of alsa-info.sh.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature

[Touch-packages] [Bug 1364466] Re: /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-service-2.0': double free or corruption (fasttop): ADDR ***

[Justin McPherson]

Code here; https://github.com/jhodapp/gst-plugins-bad/pull/10

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

Title:
  /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-
  service-2.0': double free or corruption (fasttop): ADDR ***

Status in the base for Ubuntu mobile products:
  In Progress
Status in gstreamer package in Ubuntu:
  In Progress
Status in mediascanner2 package in Ubuntu:
  Invalid
Status in gstreamer package in Ubuntu RTM:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediascanner2.  This problem was most recently seen with
  version 0.104+14.10.20140825-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/354f10fdaba609ee33dd0a2868637ec79c590b56
  and
  https://errors.ubuntu.com/problem/01fcf2789e27c0abf6922c68c02a408b907fab83
  contains more details.

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

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

[Touch-packages] [Bug 1352654] Re: No longer able to install packages with PackageKit

[Justin McPherson]

** Package changed: packagekit (Ubuntu) = aptdaemon (Ubuntu)

** Changed in: aptdaemon (Ubuntu)
 Assignee: (unassigned) = Justin McPherson (justinmcp)

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

Title:
  No longer able to install packages with PackageKit

Status in aptdaemon package in Ubuntu:
  New

Bug description:
  If you try to install with the cmdline tool (apt-get install
  packagekit-tools)

  
  justin@ubuntu:~$ pkcon install unity-webapps-reddit
  Resolving [=] 
  Loading cache [=] 
  Finished  [=] 
  Fatal error: The version 2.4.16+13.10.20130924.2-0ubuntu1/Ubuntu of 
unity-webapps-reddit isn't available.
  

  Use of the PackageKit API has the same results.

  justin@ubuntu:~$ lsb_release -rd 
  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10

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

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

[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

[Justin Ossevoort]

I'm experiencing this exact same problem after upgrading to 14.10 from
14.04. Later I did a clean 14.10 install (on a completely new ssd) and
that too showed exactly the same problem.

The only things special about my setup:
- Full disk encryption
- Btrfs based
- Multiple monitors

I wouldn't expect the first two to have anything to do with this, bu the
last one might.

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

Title:
  launcher does not show minimized update manager while clicked

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “update-manager” package in Ubuntu:
  Confirmed
Status in “unity” source package in Precise:
  Fix Released
Status in “update-manager” source package in Precise:
  Confirmed
Status in “unity” source package in Quantal:
  Fix Released
Status in “update-manager” source package in Quantal:
  Confirmed

Bug description:
  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

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

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

[Touch-packages] [Bug 1364466] Re: /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-service-2.0': double free or corruption (fasttop): ADDR ***

[Justin McPherson]

I have tested with the results of #1386571 , and the problem still
remains.

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

Title:
  /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-
  service-2.0': double free or corruption (fasttop): ADDR ***

Status in “gstreamer” package in Ubuntu:
  Confirmed
Status in “mediascanner2” package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediascanner2.  This problem was most recently seen with
  version 0.104+14.10.20140825-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/354f10fdaba609ee33dd0a2868637ec79c590b56
  and
  https://errors.ubuntu.com/problem/01fcf2789e27c0abf6922c68c02a408b907fab83
  contains more details.

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

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

[Touch-packages] [Bug 1352654] Re: No longer able to install packages with PackageKit

[Justin McPherson]

Just a heads up; this still seems to be a problem.

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

Title:
  No longer able to install packages with PackageKit

Status in “packagekit” package in Ubuntu:
  New

Bug description:
  If you try to install with the cmdline tool (apt-get install
  packagekit-tools)

  
  justin@ubuntu:~$ pkcon install unity-webapps-reddit
  Resolving [=] 
  Loading cache [=] 
  Finished  [=] 
  Fatal error: The version 2.4.16+13.10.20130924.2-0ubuntu1/Ubuntu of 
unity-webapps-reddit isn't available.
  

  Use of the PackageKit API has the same results.

  justin@ubuntu:~$ lsb_release -rd 
  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10

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

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

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

[Justin Fortier]

Yeah having the same issue here, and it was causing issues with my
puppet script to fail because it's not exiting cleanly with a 0/1 exit
status. I fixed the puppet script to accept error code 139 which seems
to be the error code it exits with.

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

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

Status in “apt” package in Ubuntu:
  Fix Released
Status in “apt” source package in Precise:
  Triaged

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

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

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

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

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

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

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

[Touch-packages] [Bug 1353157] Re: PCI/internal sound card not detected

[Justin Brash]

I got my sound card working by compiling kernel 3.16.2 and using that.
How do I find out if / when the ubuntu kernel is updated to support my
card?

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

Title:
  PCI/internal sound card not detected

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Asus Xonar Essesnce STX II sound card not detected by ALSA.  This is a
  fairly new sound card on the market.  I've tested the card I have
  under windows 8.1 with the drivers downloaded from Asus, and all works
  perfectly.  I'm 100% sure I've physically installed and connected the
  card correctly.  Unfortunately I've had no joy getting it detected by
  Ubuntu 14.04.1 64bit.  Please help!  I don't want to send the card
  back and I don't want to have to move to Windows!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  justin 2369 F pulseaudio
   /dev/snd/controlC1:  justin 2369 F pulseaudio
   /dev/snd/controlC0:  justin 2369 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  5 23:28:37 2014
  InstallationDate: Installed on 2014-04-28 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

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

[Justin Brash]

Public bug reported:

Asus Xonar Essesnce STX II sound card not detected by ALSA.  This is a
fairly new sound card on the market.  I've tested the card I have under
windows 8.1 with the drivers downloaded from Asus.  I'm 100% sure I've
physically installed and connected the card correctly.  Unfortunately
I've had no joy getting it detected by Ubuntu 14.04.1 64bit.  Please
help!  I don't want to send the card back and I don't want to have to
move to Windows!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  justin 2369 F pulseaudio
 /dev/snd/controlC1:  justin 2369 F pulseaudio
 /dev/snd/controlC0:  justin 2369 F pulseaudio
CurrentDesktop: Unity
Date: Tue Aug  5 23:28:37 2014
InstallationDate: Installed on 2014-04-28 (99 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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


** Tags: amd64 apport-bug trusty

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

Title:
  PCI/internal sound card not detected

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Asus Xonar Essesnce STX II sound card not detected by ALSA.  This is a
  fairly new sound card on the market.  I've tested the card I have
  under windows 8.1 with the drivers downloaded from Asus.  I'm 100%
  sure I've physically installed and connected the card correctly.
  Unfortunately I've had no joy getting it detected by Ubuntu 14.04.1
  64bit.  Please help!  I don't want to send the card back and I don't
  want to have to move to Windows!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  justin 2369 F pulseaudio
   /dev/snd/controlC1:  justin 2369 F pulseaudio
   /dev/snd/controlC0:  justin 2369 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  5 23:28:37 2014
  InstallationDate: Installed on 2014-04-28 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

-- 
Mailing list: https://launchpad.net

[Touch-packages] [Bug 1353157] Re: PCI/internal sound card not detected

[Justin Brash]

** Description changed:

  Asus Xonar Essesnce STX II sound card not detected by ALSA.  This is a
  fairly new sound card on the market.  I've tested the card I have under
- windows 8.1 with the drivers downloaded from Asus.  I'm 100% sure I've
- physically installed and connected the card correctly.  Unfortunately
- I've had no joy getting it detected by Ubuntu 14.04.1 64bit.  Please
- help!  I don't want to send the card back and I don't want to have to
- move to Windows!
+ windows 8.1 with the drivers downloaded from Asus, and all works
+ perfectly.  I'm 100% sure I've physically installed and connected the
+ card correctly.  Unfortunately I've had no joy getting it detected by
+ Ubuntu 14.04.1 64bit.  Please help!  I don't want to send the card back
+ and I don't want to have to move to Windows!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  justin 2369 F pulseaudio
-  /dev/snd/controlC1:  justin 2369 F pulseaudio
-  /dev/snd/controlC0:  justin 2369 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  justin 2369 F pulseaudio
+  /dev/snd/controlC1:  justin 2369 F pulseaudio
+  /dev/snd/controlC0:  justin 2369 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  5 23:28:37 2014
  InstallationDate: Installed on 2014-04-28 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

Title:
  PCI/internal sound card not detected

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Asus Xonar Essesnce STX II sound card not detected by ALSA.  This is a
  fairly new sound card on the market.  I've tested the card I have
  under windows 8.1 with the drivers downloaded from Asus, and all works
  perfectly.  I'm 100% sure I've physically installed and connected the
  card correctly.  Unfortunately I've had no joy getting it detected by
  Ubuntu 14.04.1 64bit.  Please help!  I don't want to send the card
  back and I don't want to have to move to Windows!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  justin 2369 F pulseaudio
   /dev/snd/controlC1:  justin 2369 F pulseaudio
   /dev/snd/controlC0:  justin 2369 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  5 23:28:37 2014
  InstallationDate: Installed on 2014-04-28 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled

[Touch-packages] [Bug 1352654] [NEW] No longer able to install packages with PackageKit

[Justin McPherson]

Public bug reported:

If you try to install with the cmdline tool (apt-get install packagekit-
tools)


justin@ubuntu:~$ pkcon install unity-webapps-reddit
Resolving [=] 
Loading cache [=] 
Finished  [=] 
Fatal error: The version 2.4.16+13.10.20130924.2-0ubuntu1/Ubuntu of 
unity-webapps-reddit isn't available.


Use of the PackageKit API has the same results.

justin@ubuntu:~$ lsb_release -rd 
Description:Ubuntu Utopic Unicorn (development branch)
Release:14.10

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

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

Title:
  No longer able to install packages with PackageKit

Status in “packagekit” package in Ubuntu:
  New

Bug description:
  If you try to install with the cmdline tool (apt-get install
  packagekit-tools)

  
  justin@ubuntu:~$ pkcon install unity-webapps-reddit
  Resolving [=] 
  Loading cache [=] 
  Finished  [=] 
  Fatal error: The version 2.4.16+13.10.20130924.2-0ubuntu1/Ubuntu of 
unity-webapps-reddit isn't available.
  

  Use of the PackageKit API has the same results.

  justin@ubuntu:~$ lsb_release -rd 
  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10

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

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