[Touch-packages] [Bug 1841290] Re: I am logged in as "live session user", and running the Ubuntu option "try without installing. I am able to create a new user with admin rights, however, I did not lo

2019-10-23 Thread Launchpad Bug Tracker
[Expired for adduser (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  I am logged in as "live session user", and running the Ubuntu option
  "try without installing. I am able to create a new user with admin
  rights, however, I did not log out and back in as the newly created
  user before the system went into sleep mode. When the machine woke
  from sleep and landed on the greeter, or login screen, it got stuck
  there with no login box. I am assuming this is because Ubuntu in live
  session mode is configured to auto login to the Live Session User
  account?

Status in adduser package in Ubuntu:
  Expired

Bug description:
  I am logged in as "live session user", and running the Ubuntu option
  "try without installing. I am able to create a new user with admin
  rights, however, I did not log out and back in as the newly created
  user before the system went into sleep mode. When the machine woke
  from sleep and landed on the greeter, or login screen, it got stuck
  there with no login box. I am assuming this is because Ubuntu in live
  session mode is configured to auto login to the Live Session User
  account?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: adduser 3.118ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CasperVersion: 1.405
  Date: Fri Aug 23 22:55:01 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: adduser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1849540] Re: booting issue

2019-10-23 Thread Daniel van Vugt
Yes I can see those kernel errors causing delays in your logs. They seem
to be referring to the motherboard:

00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI
Express Root Port #6 [8086:9d15] (rev f1) (prog-if 00 [Normal decode])

That's probably either a hardware fault or a kernel bug. If it is a
hardware fault then it might be limited to just your wifi card or
something removable like that...


** Summary changed:

- booting issue
+ "PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)" 
causing boot delays

** Package changed: xorg (Ubuntu) => linux (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/1849540

Title:
  "PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver
  ID)" causing boot delays

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu shows pci bus error severity=corrected when shutting down
  takes time for login page to pop up

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 13:32:16 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5921] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13d1]
  InstallationDate: Installed on 2019-10-09 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b721 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 13d3:5a11 IMC Networks 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook 14_ASUS Laptop X441UAR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=18fd12ef-f3d1-4d80-b60a-a8111a2dd43d ro quiet splash 
i915.alpha_support=1 vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X441UAR.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X441UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX441UAR.308:bd06/11/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook14_ASUSLaptopX441UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook 14_ASUS Laptop X441UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100+git1910190630.fc9336~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1910200730.7ceafa~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1910200730.7ceafa~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1849545] Re: Graphics warning on restart

2019-10-23 Thread Daniel van Vugt
This seems to be a recurring error in your logs:

[26.747] (EE) 
Fatal server error:
[26.747] (EE) Cannot run in framebuffer mode. Please specify busIDs
for all framebuffer devices

That's probably the issue.

** Package changed: xorg (Ubuntu) => xorg-server (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/1849545

Title:
  Xorg repeatedly fails to start [Cannot run in framebuffer mode. Please
  specify busIDs for all framebuffer devices]

Status in xorg-server package in Ubuntu:
  New

Bug description:
  On restart it sometimes happens that I get a message to the effect that my 
graphics are operating in some kind of limited mode. An Xorg error is 
mentioned. On OK I get a few options such as 'try starting in default mode' and 
other options involving various possible tests, none of which seem to do much 
or have much effect.
  Clicking on 'start in default mode' always (so far) allows me to continue 
normally however there follows a message 'ubuntu has experienced an error'
  Wondering what's going on and whether I should be doing something different.
  Somewhat ashamed of my ignorance. Been using Ubuntu for years but haven't 
bothered to delve into the OS :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 19:22:45 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-04-20 (186 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: LENOVO 2241WJE
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=aade17ba-9d15-4eac-86b2-2a2a6c6230bf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 2241WJE
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn2241WJE:pvrThinkPadT500:rvnLENOVO:rn2241WJE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T500
  dmi.product.name: 2241WJE
  dmi.product.version: ThinkPad T500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Oct 23 19:13:21 2019
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

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

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


[Touch-packages] [Bug 1848784] Re: Crash in Qt 5.12.2

2019-10-23 Thread Alex Murray
MITRE has assigned CVE-2019-18281 for this issue.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-18281

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

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

Title:
  Crash in Qt 5.12.2

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+subscriptions

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


[Touch-packages] [Bug 1849399] Re: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key

2019-10-23 Thread Gunnar Hjalmarsson
On 2019-10-24 00:56, Steve Langasek wrote:
> Contents of the file are:
> 
> include "/usr/share/X11/locale/en_US.UTF-8/Compose"
> <\> <)> : "☭"   # HAMMER AND SICKLE

Hmm.. Looking at  and
wondering if that line shouldn't rather read something like this:

: "☭"   # HAMMER AND SICKLE

(which works with IBus provided that there is a defined compose key)

Even if there was a regression due to the 1.5.19 -> 1.5.21 upgrade of
ibus

* the changed behavior is upstream in nature

* a possible upstream issue would basically say: "Why does IBus no
  longer interpret my syntactically incorrect ~/.XCompose file in
  accordance with my intention?"

So I tend to think that this bug should be closed as invalid, unless you
have some convincing arguments for keeping it open. Your call. :)

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

Title:
  ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete
  key

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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


[Touch-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

2019-10-23 Thread Steve Langasek
On Wed, Oct 23, 2019 at 07:24:03PM -, Gunnar Hjalmarsson wrote:
> Also, do you possibly have an ~/.XCompose file which you have played
> with previously?

Why yes, yes I do.

$ ls -l ~/.XCompose 
-rw-r--r-- 1 vorlon vorlon 93 Mar 27  2009 /home/vorlon/.XCompose
$

Moving this file aside and restarting ibus-daemon, the Delete key works as
expected.

Contents of the file are:

include "/usr/share/X11/locale/en_US.UTF-8/Compose"
<\> <)> : "☭"   # HAMMER AND SICKLE

So why is ibus interpreting this file differently in 19.10 than in
previous releases?

** Summary changed:

- ibus in 19.10 breaks the delete key, maps  to ☭
+ ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key

** Changed in: ibus (Ubuntu)
   Importance: High => Medium

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

Title:
  ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete
  key

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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


[Touch-packages] [Bug 1849399] Re: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key

2019-10-23 Thread Steve Langasek
downgrading the bug to 'medium' since most people don't have ~/.XCompose
;)

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

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

Title:
  ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete
  key

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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


[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal

2019-10-23 Thread Brian Murray
I'm setting this to Fix Released as python-apt should migrate with no
issues. If it doesn't feel free to reopen this bug report.

** Changed in: python-apt (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  could not find a distribution template for Ubuntu/focal

Status in python-apt package in Ubuntu:
  Fix Released

Bug description:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources():

  Click on software-properties-gtk icon: I have a message about crash,
  click on 'send' nothing happen.

  I attached crash file

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

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


[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal

2019-10-23 Thread Brian Murray
This'll fix it.

python-apt (1.9.0ubuntu3) focal; urgency=medium

  * data/templates/Ubuntu.info.in: Add focal.

 -- Matthias Klose   Wed, 23 Oct 2019 23:21:34 +0200

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

Title:
  could not find a distribution template for Ubuntu/focal

Status in python-apt package in Ubuntu:
  Fix Released

Bug description:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources():

  Click on software-properties-gtk icon: I have a message about crash,
  click on 'send' nothing happen.

  I attached crash file

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

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


[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal

2019-10-23 Thread Dave Jones
Please note for testing:

add-apt-repository does not operate without the updated package either,
so just download the relevant .debs and install manually with "sudo dpkg
-i" for testing. The package that's really needed is python-apt-common
(which contains the updated template output), but you may as well update
python3-apt as well for the sake of testing.

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

Title:
  could not find a distribution template for Ubuntu/focal

Status in python-apt package in Ubuntu:
  In Progress

Bug description:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources():

  Click on software-properties-gtk icon: I have a message about crash,
  click on 'send' nothing happen.

  I attached crash file

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

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


[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal

2019-10-23 Thread Dave Jones
Updated python-apt package available in the following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/pkg

Branch from which the package was built:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
/python-apt/+ref/focal-entry

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

Title:
  could not find a distribution template for Ubuntu/focal

Status in python-apt package in Ubuntu:
  In Progress

Bug description:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources():

  Click on software-properties-gtk icon: I have a message about crash,
  click on 'send' nothing happen.

  I attached crash file

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

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


[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

2019-10-23 Thread Ryan Harper
The original netplan yaml I was testing was simpler, but also failed so
I tried to see if additional settings would make a difference, but it
did not.

network:
version: 2
ethernets:
interface0:
dhcp4: true
match:
macaddress: '52:54:00:12:34:00'
set-name: interface0
interface1:
addresses:
- 192.168.1.2/24
- 2001:4800:78ff:1b:be76:4eff:fe06:1000/64
match:
macaddress: '52:54:00:12:34:02'
mtu: 
ipv6-mtu: 5634
set-name: interface1

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  New

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

2019-10-23 Thread Ryan Harper
I cannot verify this is working on bionic with ipv6 static addresses.

root@ubuntu:~# lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
root@ubuntu:~# cat /etc/cloud/build.info 
build_name: server
serial: 20191021
root@ubuntu:~# uname -a
Linux ubuntu 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu:~# apt-cache policy netplan.io
netplan.io:
  Installed: 0.98-0ubuntu1~18.04.1
  Candidate: 0.98-0ubuntu1~18.04.1
  Version table:
 *** 0.98-0ubuntu1~18.04.1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 0.40.1~18.04.4 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 0.36.1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
root@ubuntu:~# apt-cache policy systemd
systemd:
  Installed: 237-3ubuntu10.31
  Candidate: 237-3ubuntu10.31
  Version table:
 *** 237-3ubuntu10.31 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 237-3ubuntu10.29 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 237-3ubuntu10 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages


root@ubuntu:~# cat /etc/netplan/50-cloud-init.yaml 
# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
interface0:
dhcp4: true
match:
macaddress: '52:54:00:12:34:00'
set-name: interface0
interface1:
dhcp4: false
dhcp6: false
addresses:
- 192.168.1.2/24
- 2001:4800:78ff:1b:be76:4eff:fe06:1000/64
match:
macaddress: '52:54:00:12:34:02'
mtu: 
ipv6-mtu: 5634
set-name: interface1
accept-ra: false
dhcp6-overrides:
   use-mtu: false
link-local: [ ]

root@ubuntu:~# ip link show interface1
3: interface1:  mtu  qdisc fq_codel state 
UP mode DEFAULT group default qlen 1000
link/ether 52:54:00:12:34:02 brd ff:ff:ff:ff:ff:ff
# sysctl net.ipv6.conf.interface1.mtu 
net.ipv6.conf.interface1.mtu = 

root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link 
[Match]
MACAddress=52:54:00:12:34:02

[Link]
Name=interface1
WakeOnLan=off
MTUBytes=
root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.network 
[Match]
MACAddress=52:54:00:12:34:02
Name=interface1

[Network]
LinkLocalAddressing=no
Address=192.168.1.2/24
Address=2001:4800:78ff:1b:be76:4eff:fe06:1000/64
IPv6AcceptRA=no
IPv6MTUBytes=5634

# journalctl -o short-precise -b 0 | egrep -i "(MTU|interface1)"
Oct 23 21:28:47.968910 ubuntu kernel: virtio_net virtio3 interface1: renamed 
from ens6
Oct 23 21:28:50.636014 ubuntu systemd-networkd[670]: Ignoring 
/run/systemd/network/10-netplan-interface1.network, because it's not a regular 
file with suffix .netdev.
Oct 23 21:28:50.636090 ubuntu systemd-networkd[670]: Ignoring 
/run/systemd/network/10-netplan-interface1.link, because it's not a regular 
file with suffix .netdev.
Oct 23 21:28:50.636706 ubuntu systemd-networkd[670]: Ignoring 
/run/systemd/network/10-netplan-interface1.link, because it's not a regular 
file with suffix .network.
Oct 23 21:28:50.640507 ubuntu systemd-networkd[670]: interface7: Saved original 
MTU: 1500
Oct 23 21:28:50.642454 ubuntu systemd-networkd[670]: interface6: Saved original 
MTU: 1500
Oct 23 21:28:50.643050 ubuntu systemd-networkd[670]: interface5: Saved original 
MTU: 1500
Oct 23 21:28:50.643629 ubuntu systemd-networkd[670]: interface4: Saved original 
MTU: 1500
Oct 23 21:28:50.644214 ubuntu systemd-networkd[670]: interface3: Saved original 
MTU: 1500
Oct 23 21:28:50.644939 ubuntu systemd-networkd[670]: interface2: Saved original 
MTU: 1500
Oct 23 21:28:50.645025 ubuntu systemd-networkd[670]: interface1: New device has 
no master, continuing without
Oct 23 21:28:50.645107 ubuntu systemd-networkd[670]: interface1: Flags change: 
+MULTICAST +BROADCAST
Oct 23 21:28:50.645175 ubuntu systemd-networkd[670]: interface1: Link 3 added
Oct 23 21:28:50.645456 ubuntu systemd-networkd[670]: interface1: udev 
initialized link
Oct 23 21:28:50.647448 ubuntu systemd-networkd[670]: interface1: Saved original 
MTU: 
Oct 23 21:28:50.648100 ubuntu systemd-networkd[670]: interface0: Saved original 
MTU: 1500
Oct 23 21:28:50.648670 ubuntu systemd-networkd[670]: lo: Saved original MTU: 0
Oct 23 21:28:50.655303 ubuntu systemd-networkd[670]: interface1: Interface name 
change detected, interface1 has been renamed to ens6.
Oct 23 21:28:50.655431 ubuntu 

[Touch-packages] [Bug 1845793] Re: Since upgrade to ubuntu 19.10, dhclient doesn't respect the "supersede domain-name-servers" in dhclient.conf

2019-10-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  Since upgrade to ubuntu 19.10, dhclient doesn't respect the "supersede
  domain-name-servers" in dhclient.conf

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  dnsleaktest.com shows my ISP servers instead of the configured ones in
  dnscrypt-proxy. When i checked in network settings it was written the
  DNS for my router, but there is still this line below inside
  /etc/dhcp/dhclient.conf. Also, ifconfig shows that the interface name
  is still the same as below.

  interface "wlp3s0" {
  supersede domain-name-servers 127.0.0.1;
  }

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: isc-dhcp-client 4.4.1-2ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:40:14 2019
  DhclientLeases:
   
  InstallationDate: Installed on 2019-07-23 (66 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago)
  mtime.conffile..etc.dhcp.dhclient.conf: 2019-08-31T22:54:40.376662

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

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


[Touch-packages] [Bug 1847201] Re: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to restart

2019-10-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed
  bluez package post-installation script subprocess returned error exit
  status 1 [Failed to restart bluetooth.service: Unit -.mount is
  masked.]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  made upgrade using update-manager

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: bluez 5.50-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Tue Oct  8 09:52:47 2019
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2019-05-18 (142 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 
rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" 
acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.6ubuntu1.1
   apt  1.8.3
  SourcePackage: bluez
  Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed 
bluez package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E14A1IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-14A1
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: GS40 6QE Phantom
  dmi.product.sku: Default string
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 9C:B6:D0:0A:FA:40  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN 
RX bytes:775 acl:0 sco:0 events:59 errors:0
TX bytes:3668 acl:0 sco:0 commands:59 errors:0

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

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


[Touch-packages] [Bug 1846499] Re: e2scrub_all.service is a disabled or a static unit not running, not starting it.

2019-10-23 Thread Paul White
** Package changed: gnome-software (Ubuntu) => e2fsprogs (Ubuntu)

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

Title:
  e2scrub_all.service is a disabled or a static unit not running, not
  starting it.

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Upon attempting to upgrade form Ubuntu 19.04 to Ubuntu 19.10. The
  installation got stuck with this being the last command line output:

  "e2scrub_all.service is a disabled or a static unit not running, not
  starting it."

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

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


[Touch-packages] [Bug 1846499] [NEW] e2scrub_all.service is a disabled or a static unit not running, not starting it.

2019-10-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Upon attempting to upgrade form Ubuntu 19.04 to Ubuntu 19.10. The
installation got stuck with this being the last command line output:

"e2scrub_all.service is a disabled or a static unit not running, not
starting it."

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


** Tags: 19.10 eoan
-- 
e2scrub_all.service is a disabled or a static unit not running, not starting it.
https://bugs.launchpad.net/bugs/1846499
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to e2fsprogs in Ubuntu.

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


[Touch-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

2019-10-23 Thread Benjamin Drung
Here is the backtrace:

Thread 1 "indicator-datet" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht 
gefunden.
(gdb) bt
#0  0x76eaa3eb in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
#1  0x76e89899 in __GI_abort () at abort.c:79
#2  0x77283b23 in g_assertion_message
(domain=, file=, line=, 
func=0x556310c8 "GDateTime* unity::indicator::datetime::DateTime::get() 
const", message=)
at ../../../glib/gtestutils.c:2912
#3  0x772e032f in g_assertion_message_expr
(domain=domain@entry=0x5562d017 "Indicator-Datetime", 
file=file@entry=0x55631108 
"/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp",
 line=line@entry=171, func=func@entry=0x556310c8 "GDateTime* 
unity::indicator::datetime::DateTime::get() const", 
expr=expr@entry=0x556310a0 "m_dt") at ../../../glib/gtestutils.c:2938
#4  0x555cda9c in unity::indicator::datetime::DateTime::get() const 
(this=0x7fffd878) at ./src/date-time.cpp:171
#5  0x555cdd15 in unity::indicator::datetime::DateTime::get() const 
(this=0x7fffd878) at ./src/date-time.cpp:171
#6  0x555cdd15 in 
unity::indicator::datetime::DateTime::format(std::__cxx11::basic_string, std::allocator > const&) const
(this=this@entry=0x7fffd878, fmt="%F %T %z") at ./src/date-time.cpp:179
#7  0x555d2d83 in 
unity::indicator::datetime::EdsEngine::Impl::get_appointment(_ECalClient*, 
std::shared_ptr<_GCancellable>&, _ECalComponent*, _GTimeZone*) 
(client=, cancellable=Warnung: RTTI symbol not found for class 
'std::_Sp_counted_deleter<_GCancellable*, 
unity::indicator::datetime::EdsEngine::Impl::Impl(std::shared_ptr
 const&)::{lambda(_GCancellable*)#1}, std::allocator, 
(__gnu_cxx::_Lock_policy)2>'
Warnung: RTTI symbol not found for class 
'std::_Sp_counted_deleter<_GCancellable*, 
unity::indicator::datetime::EdsEngine::Impl::Impl(std::shared_ptr
 const&)::{lambda(_GCancellable*)#1}, std::allocator, 
(__gnu_cxx::_Lock_policy)2>'

std::shared_ptr (use count 23, weak count 0) = {...}, 
component=component@entry=0x7fffe405c560 [ECalComponent], 
gtz=gtz@entry=0x556f1960)
at /usr/include/c++/9/bits/char_traits.h:300
#8  0x555dfe7e in 
unity::indicator::datetime::EdsEngine::Impl::add_event_to_subtask(_ECalComponent*,
 unity::indicator::datetime::EdsEngine::Impl::ClientSubtask*, _GTimeZone*)
(gtz=0x556f1960, subtask=0x55774a50, component=0x7fffe405c560 
[ECalComponent]) at ./src/engine-eds.cpp:1166
#9  0x555dfe7e in 
unity::indicator::datetime::EdsEngine::Impl::on_event_fetch_list_done(void*) 
(gsubtask=0x55774a50) at ./src/engine-eds.cpp:866
#10 0x555dfe7e in 
unity::indicator::datetime::EdsEngine::Impl::fetch_detached_instances(_GObject*,
 _GAsyncResult*, void*) (res=, gsubtask=0x55774a50)
at ./src/engine-eds.cpp:744
#11 0x77d2fcc5 in free_get_objects_async_data (goad=0x55788b90) at 
./src/calendar/libecal/e-cal-client.c:2587
#12 0x77d371e4 in got_object_list_as_comps_cb (source_object=, result=0x557a1320, user_data=user_data@entry=0x55788b90) at 
./src/calendar/libecal/e-cal-client.c:2664
#13 0x7748acf6 in g_simple_async_result_complete (simple=0x557a1320 
[GSimpleAsyncResult]) at ../../../gio/gsimpleasyncresult.c:802
#14 0x7748adbf in complete_in_idle_cb_for_thread (_data=0x557a1a40) 
at ../../../gio/gsimpleasyncresult.c:873
#15 0x772b771e in g_main_dispatch (context=0x556a4b80) at 
../../../glib/gmain.c:3179
#16 0x772b771e in g_main_context_dispatch 
(context=context@entry=0x556a4b80) at ../../../glib/gmain.c:3844
#17 0x772b7ad0 in g_main_context_iterate (context=0x556a4b80, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../glib/gmain.c:3917
#18 0x772b7dc3 in g_main_loop_run (loop=0x556e1fe0) at 
../../../glib/gmain.c:4111
#19 0x555b2d55 in main(int, char**) () at ./src/main.cpp:183

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

Title:
  src/date-time.cpp:171:GDateTime*
  unity::indicator::datetime::DateTime::get() const: assertion failed:
  (m_dt)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.10, indicator-datetime
  15.10+19.10.20190819.1-0ubuntu1 crashes right from the start:

  $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service 
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized 
TZID: 

[Touch-packages] [Bug 1849560] Re: Please revise the files installed in /etc/

2019-10-23 Thread Mathieu Trudel-Lapierre
** Tags added: writable-etc

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

Title:
  Please revise the files installed in /etc/

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh-server and openssh-client install various files under /etc:

  /etc/ssh/*
  /etc/systemd/system/sshd.service

  Please see if these files can be moved elsewhere, in accordance with
  FHS: /etc should only contain files writable by the system
  administrator, and in Ubuntu Core 20 we should aim to have no writable
  files in /etc (as it will be included in images, avoid conflict
  resolution on upgrades).

  At a glance, it looks like /etc/systemd/system/sshd.service could be
  moved to /lib/systemd/system, and many of the files in /etc/ssh do
  have suitable locations elsewhere on the system, such as /var/lib/ for
  generated keys, /usr/share/ for default SSH configurations, etc.)

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

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


[Touch-packages] [Bug 1849560] [NEW] Please revise the files installed in /etc/

2019-10-23 Thread Mathieu Trudel-Lapierre
Public bug reported:

openssh-server and openssh-client install various files under /etc:

/etc/ssh/*
/etc/systemd/system/sshd.service

Please see if these files can be moved elsewhere, in accordance with
FHS: /etc should only contain files writable by the system
administrator, and in Ubuntu Core 20 we should aim to have no writable
files in /etc (as it will be included in images, avoid conflict
resolution on upgrades).

At a glance, it looks like /etc/systemd/system/sshd.service could be
moved to /lib/systemd/system, and many of the files in /etc/ssh do have
suitable locations elsewhere on the system, such as /var/lib/ for
generated keys, /usr/share/ for default SSH configurations, etc.)

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

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

Title:
  Please revise the files installed in /etc/

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh-server and openssh-client install various files under /etc:

  /etc/ssh/*
  /etc/systemd/system/sshd.service

  Please see if these files can be moved elsewhere, in accordance with
  FHS: /etc should only contain files writable by the system
  administrator, and in Ubuntu Core 20 we should aim to have no writable
  files in /etc (as it will be included in images, avoid conflict
  resolution on upgrades).

  At a glance, it looks like /etc/systemd/system/sshd.service could be
  moved to /lib/systemd/system, and many of the files in /etc/ssh do
  have suitable locations elsewhere on the system, such as /var/lib/ for
  generated keys, /usr/share/ for default SSH configurations, etc.)

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

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


[Touch-packages] [Bug 1849554] Re: Please move cache files to a different location

2019-10-23 Thread Mathieu Trudel-Lapierre
** Tags added: writable-etc

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

Title:
  Please move cache files to a different location

Status in apparmor package in Ubuntu:
  New

Bug description:
  /etc/apparmor.d/cache is currently used to keep cache files for
  apparmor. Unfortunately, these files are in a location that is
  inconsistent with FHS guidelines for cache.

  Moreover, /etc is not a core path for Ubuntu Core 20, which means it
  is planned to not be writable; and to come directly from images.

  According to the FHS, the best location for apparmor cache files
  should be in a hierarchy under /var/cache.

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

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


[Touch-packages] [Bug 1849559] [NEW] /etc/dbus-1/system.d/wpa_supplicant.conf is in wrong location

2019-10-23 Thread Mathieu Trudel-Lapierre
Public bug reported:

The /etc/dbus-1/system.d/wpa_supplicant.conf is installed in the wrong
location. It is a system-wide default config for dbus, and as such
probably should be in /usr/share/dbus-1/system.d instead; like most
other DBus definitions installed on a typical system.

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


** Tags: writable-etc

** Tags added: writable-etc

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

Title:
  /etc/dbus-1/system.d/wpa_supplicant.conf is in wrong location

Status in wpa package in Ubuntu:
  New

Bug description:
  The /etc/dbus-1/system.d/wpa_supplicant.conf is installed in the wrong
  location. It is a system-wide default config for dbus, and as such
  probably should be in /usr/share/dbus-1/system.d instead; like most
  other DBus definitions installed on a typical system.

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

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


[Touch-packages] [Bug 1849554] [NEW] Please move cache files to a different location

2019-10-23 Thread Mathieu Trudel-Lapierre
Public bug reported:

/etc/apparmor.d/cache is currently used to keep cache files for
apparmor. Unfortunately, these files are in a location that is
inconsistent with FHS guidelines for cache.

Moreover, /etc is not a core path for Ubuntu Core 20, which means it is
planned to not be writable; and to come directly from images.

According to the FHS, the best location for apparmor cache files should
be in a hierarchy under /var/cache.

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


** Tags: writable-etc

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

Title:
  Please move cache files to a different location

Status in apparmor package in Ubuntu:
  New

Bug description:
  /etc/apparmor.d/cache is currently used to keep cache files for
  apparmor. Unfortunately, these files are in a location that is
  inconsistent with FHS guidelines for cache.

  Moreover, /etc is not a core path for Ubuntu Core 20, which means it
  is planned to not be writable; and to come directly from images.

  According to the FHS, the best location for apparmor cache files
  should be in a hierarchy under /var/cache.

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

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


[Touch-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

2019-10-23 Thread Gunnar Hjalmarsson
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-control-center/issues #82
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/82

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  New

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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


[Touch-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

2019-10-23 Thread Gunnar Hjalmarsson
Starting with the side topic (the easy part).

On 2019-10-23 18:50, Steve Langasek wrote:
> Settings -> Region & Language -> Input Sources presents Chinese as
> an option.  It can be reordered in the list, but it is not clickable.
> It has 'view' (eyeball) and 'delete' (trashcan) icons.  The 'view'
> icon pulls up a useless (for Chinese) keymap.

Ok, so you have previously added the Chinese keyboard layout. It's
actually just an alias to the basic English (US) layout.

Please note that the list you see first only shows the options you have
previously made available by adding them. To look for further sources to
add you need to click the + button.

I installed ibus-sunpinyin, relogged in, and found the Chinese
(SunPinyin) option in Settings among the "Other" input sources. Then I
generated the zh_CN.UTF-8 locale, and found that the Chinese item had
been converted to a sub menu, which includes Chinese (SunPinyin)
together with the Chinese XKB layout.

That's how the GNOME design currently works. Not saying I'm too fond of
it. In Unity (with code from GNOME 3.4 or something) the input sources
were simply presented in one long list, and when you started to type the
source you were looking for, it safely showed up.

I have filed an upstream issue about the most apparent shortcoming with
the current design:

https://gitlab.gnome.org/GNOME/gnome-control-center/issues/82

It doesn't directly address the issue you stumbled upon, but it's
closely related.

> What is suspicious about the file?
> 
> I moved the directory aside, started ibus-daemon up again, and the
> problem persists.  The ~/.cache/ibus/compose/e6817ed7.cache file has
> been recreated with identical contents as previously.

It was merely the name of the directory, and the string
"IBusComposeTable" in the contents of the cache file which made me say
that. After all your Delete key seems to do some kind of composing
instead of what it's expected to do.

> The problem persists with these settings, as long as ibus-daemon is
> running.

It's ugly behavior, and all we know so far is that it seems to be caused
by something in $HOME. But it may be due to some other cache file, some
dconf setting, or whatever. I'm out of ideas for now as regards how to
nail it.

Well, one thing you may want to try is to move away the
~/.config/dconf/user file and relogin so it gets recreated with only
default values.

Also, do you possibly have an ~/.XCompose file which you have played
with previously?

*Now* I'm out of ideas.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #82
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/82

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  New

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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


[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal

2019-10-23 Thread Dave Jones
** Changed in: python-apt (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: python-apt (Ubuntu)
   Status: New => In Progress

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

Title:
  could not find a distribution template for Ubuntu/focal

Status in python-apt package in Ubuntu:
  In Progress

Bug description:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources():

  Click on software-properties-gtk icon: I have a message about crash,
  click on 'send' nothing happen.

  I attached crash file

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

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


[Touch-packages] [Bug 1849545] [NEW] Graphics warning on restart

2019-10-23 Thread Jonathan
Public bug reported:

On restart it sometimes happens that I get a message to the effect that my 
graphics are operating in some kind of limited mode. An Xorg error is 
mentioned. On OK I get a few options such as 'try starting in default mode' and 
other options involving various possible tests, none of which seem to do much 
or have much effect.
Clicking on 'start in default mode' always (so far) allows me to continue 
normally however there follows a message 'ubuntu has experienced an error'
Wondering what's going on and whether I should be doing something different.
Somewhat ashamed of my ignorance. Been using Ubuntu for years but haven't 
bothered to delve into the OS :-)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-66-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Oct 23 19:22:45 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
InstallationDate: Installed on 2019-04-20 (186 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
MachineType: LENOVO 2241WJE
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=aade17ba-9d15-4eac-86b2-2a2a6c6230bf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET92WW (3.22 )
dmi.board.name: 2241WJE
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn2241WJE:pvrThinkPadT500:rvnLENOVO:rn2241WJE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T500
dmi.product.name: 2241WJE
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Oct 23 19:13:21 2019
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

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


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

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

Title:
  Graphics warning on restart

Status in xorg package in Ubuntu:
  New

Bug description:
  On restart it sometimes happens that I get a message to the effect that my 
graphics are operating in some kind of limited mode. An Xorg error is 
mentioned. On OK I get a few options such as 'try starting in default mode' and 
other options involving various possible tests, none of which seem to do much 
or have much effect.
  Clicking on 'start in default mode' always (so far) allows me to continue 
normally however there follows a message 'ubuntu has experienced an error'
  Wondering what's going on and whether I should be doing something different.
  Somewhat ashamed of my ignorance. Been using Ubuntu for years but haven't 
bothered to delve into the OS :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  

[Touch-packages] [Bug 1849544] [NEW] package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2019-10-23 Thread Rachel Greenham
Public bug reported:

problem occurred becauuse symlink /initrd.imgpointed to old disco
initrd, resolved by forcibly recreating it, for now...?

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: initramfs-tools 0.133ubuntu10
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Mon Oct 21 17:24:50 2019
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-02-20 (610 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
PackageArchitecture: all
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to eoan on 2019-10-21 (2 days ago)

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


** Tags: amd64 apport-package eoan

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

Title:
  package initramfs-tools 0.133ubuntu10 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  problem occurred becauuse symlink /initrd.imgpointed to old disco
  initrd, resolved by forcibly recreating it, for now...?

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: initramfs-tools 0.133ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 21 17:24:50 2019
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-02-20 (610 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (2 days ago)

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

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


[Touch-packages] [Bug 1849544] Re: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2019-10-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.133ubuntu10 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  problem occurred becauuse symlink /initrd.imgpointed to old disco
  initrd, resolved by forcibly recreating it, for now...?

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: initramfs-tools 0.133ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 21 17:24:50 2019
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-02-20 (610 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (2 days ago)

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

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


[Touch-packages] [Bug 1849543] [NEW] crontab truncates passed in filename to 100 characters

2019-10-23 Thread Henry Paradiz
Public bug reported:

If you want to install cron from a file you run crontab [filename].
Unfortunately the filename is truncated to 100 characters in the source
code set from #define MAX_FNAME 100

The MAX_FNAME should actually be set to PATH_MAX which is 4096

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cron 3.0pl1-128.1ubuntu1
ProcVersionSignature: User Name 4.15.0-1048.50-aws 4.15.18
Uname: Linux 4.15.0-1048-aws x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Wed Oct 23 13:06:13 2019
Ec2AMI: ami-0977c44707608ee22
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t2.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
 TERM=xterm-color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: cron
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ec2-images third-party-packages

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

Title:
  crontab truncates passed in filename to 100 characters

Status in cron package in Ubuntu:
  New

Bug description:
  If you want to install cron from a file you run crontab [filename].
  Unfortunately the filename is truncated to 100 characters in the
  source code set from #define MAX_FNAME 100

  The MAX_FNAME should actually be set to PATH_MAX which is 4096

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cron 3.0pl1-128.1ubuntu1
  ProcVersionSignature: User Name 4.15.0-1048.50-aws 4.15.18
  Uname: Linux 4.15.0-1048-aws x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Wed Oct 23 13:06:13 2019
  Ec2AMI: ami-0977c44707608ee22
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1849540] [NEW] booting issue

2019-10-23 Thread Anand
Public bug reported:

ubuntu shows pci bus error severity=corrected when shutting down
takes time for login page to pop up

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 23 13:32:16 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:5921] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:13d1]
InstallationDate: Installed on 2019-10-09 (14 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:b721 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 13d3:5a11 IMC Networks 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. VivoBook 14_ASUS Laptop X441UAR
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=18fd12ef-f3d1-4d80-b60a-a8111a2dd43d ro quiet splash 
i915.alpha_support=1 vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X441UAR.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X441UAR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX441UAR.308:bd06/11/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook14_ASUSLaptopX441UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook 14_ASUS Laptop X441UAR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100+git1910190630.fc9336~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1910200730.7ceafa~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1910200730.7ceafa~oibaf~b
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

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1849540

Title:
  booting issue

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu shows pci bus error severity=corrected when shutting down
  takes time for login page to pop up

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 13:32:16 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5921] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13d1]
  InstallationDate: Installed on 2019-10-09 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b721 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 13d3:5a11 IMC Networks 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook 14_ASUS Laptop X441UAR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=18fd12ef-f3d1-4d80-b60a-a8111a2dd43d ro quiet splash 
i915.alpha_support=1 vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2019
  dmi.bios.vendor: American 

[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal

2019-10-23 Thread Julian Andres Klode
This is a known issue that always happens when the archive opens for a
new development series. It will be addressed shortly.

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

Title:
  could not find a distribution template for Ubuntu/focal

Status in python-apt package in Ubuntu:
  New

Bug description:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources():

  Click on software-properties-gtk icon: I have a message about crash,
  click on 'send' nothing happen.

  I attached crash file

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

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


[Touch-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

2019-10-23 Thread Steve Langasek
> There is a ~/.cache/ibus/compose folder with a suspicious cache file.
> Can you please rename that folder, relogin, and check if the issue is
> still present.

What is suspicious about the file?

I moved the directory aside, started ibus-daemon up again, and the
problem persists.  The ~/.cache/ibus/compose/e6817ed7.cache file has
been recreated with identical contents as previously.

Here are my gsettings values currently:

$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'us+dvorak-alt-intl'), ('xkb', 'gr+polytonic'), ('xkb', 'cn'), ('xkb', 
'ru')]
$ gsettings get org.freedesktop.ibus.general preload-engines
['xkb:us::eng']
$

The problem persists with these settings, as long as ibus-daemon is
running.

> For an IBus IM to be presented in Settings or ibus-setup, the package -
> in your case ibus-sunpinyin - needs to be installed. But when you say
> that only Chinese is listed in Settings, and assuming that ibus-
> sunpinyin is still installed on your machine, can it possibly be that if
> you click the "Chinese" option in Settings, you end up in a sub menu
> which includes Chinese SunPinyin?

Settings -> Region & Language -> Input Sources presents Chinese as an
option.  It can be reordered in the list, but it is not clickable.  It
has 'view' (eyeball) and 'delete' (trashcan) icons.  The 'view' icon
pulls up a useless (for Chinese) keymap.

The ibus-sunpinyin package is installed.

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  New

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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


[Touch-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

2019-10-23 Thread Steve Langasek
Regardless, it's simply a hypothesis on my part that the fact that I
have configured Chinese input methods in the past may be the cause of
this problem.  The Chinese keyboard setting is not active when this
problem manifests.

** Changed in: ibus (Ubuntu)
   Status: Incomplete => 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/1849399

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  New

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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


[Touch-packages] [Bug 1849534] [NEW] ISO extracted to FAT32 does not support links error

2019-10-23 Thread oldfred
Public bug reported:

Attempting to extract ISO to FAT32 partition for UEFI install which used
to work.

But get error that FAT32 does not support links.

Found these links:
fred@Bionic-Z170N:/media/fred/Ubuntu 20.04 LTS amd64$ find . -type l -ls
 2761  0 lr-xr-xr-x   1 fred fred5 Oct 18 20:36 
./dists/stable -> focal
 2765  0 lr-xr-xr-x   1 fred fred5 Oct 18 20:36 
./dists/unstable -> focal
 1330  0 lr-xr-xr-x   1 fred fred1 Oct 18 20:36 
./ubuntu -> .

** Affects: ubuntu-meta (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-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1849534

Title:
  ISO extracted to FAT32 does not support links error

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Attempting to extract ISO to FAT32 partition for UEFI install which
  used to work.

  But get error that FAT32 does not support links.

  Found these links:
  fred@Bionic-Z170N:/media/fred/Ubuntu 20.04 LTS amd64$ find . -type l -ls
 2761  0 lr-xr-xr-x   1 fred fred5 Oct 18 20:36 
./dists/stable -> focal
 2765  0 lr-xr-xr-x   1 fred fred5 Oct 18 20:36 
./dists/unstable -> focal
 1330  0 lr-xr-xr-x   1 fred fred1 Oct 18 20:36 
./ubuntu -> .

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

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


[Touch-packages] [Bug 1812223] Re: gir test fail on ppc64el

2019-10-23 Thread Evgeny Vereshchagin
Today on GitHub a ppc64el webhook was turned on for the systemd project. The 
fuzzers (built with ASan) crashed there as soon as they started with something 
like
```
757/758 fuzz-varlink:oss-fuzz-14708:address FAIL 0.02 s (exit status 1)

--- command ---
/usr/bin/env 
/tmp/autopkgtest.vdKhS9/build.g6f/systemd/build-deb/fuzz-varlink:address 
/tmp/autopkgtest.vdKhS9/build.g6f/systemd/test/fuzz/fuzz-varlink/oss-fuzz-14708
--- stderr ---
==24171==Shadow memory range interleaves with an existing memory mapping. ASan 
cannot proceed correctly. ABORTING.
==24171==ASan shadow was supposed to be located in the 
[0x01ff-0x11ff] range.
==24171==Process memory map follows:
```
https://github.com/systemd/systemd/pull/13568#issuecomment-545426488

I'm not sure what exactly is going on there but I'm wondering if anyone
runs anything under ASan on ppc64el on a regular basis. Is it even
supported there?

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

Title:
  gir test fail on ppc64el

Status in Meson:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gobject-introspection package in Ubuntu:
  New
Status in meson package in Ubuntu:
  Fix Released

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-disco/disco/ppc64el/m/meson/20190116_031026_4df33@/log.gz

  ninja explain: genmarshal/genmarshalprog is dirty
  [1/75] Generating simple-resources_c with a custom command.
  [2/75] Generating simple-resources_h with a custom command.
  [3/75] Generating res3 with a meson_exe.py custom command.
  [4/75] Compiling C object 
'resources/41d311a@@simple-resources-test@exe/meson-generated_.._simple-resources.c.o'.
  [5/75] Compiling C object 
'resources/41d311a@@simple-resources-test@exe/simple-main.c.o'.
  [6/75] Generating simple-resources_gresource with a custom command.
  [7/75] Generating generated-resources_c with a custom command.
  [8/75] Generating generated-resources_h with a custom command.
  [9/75] Linking target resources/simple-resources-test.
  [10/75] Compiling C object 
'resources/41d311a@@generated-resources-test@exe/meson-generated_.._generated-resources.c.o'.
  [11/75] Generating build-resources_gresource with a custom command.
  [12/75] Compiling C object 
'resources/41d311a@@generated-resources-test@exe/generated-main.c.o'.
  [13/75] Linking target resources/generated-resources-test.
  [14/75] Compiling C object 'gir/dep1/dep2/7cbf35a@@dep2lib@sha/dep2.c.o'.
  [15/75] Linking target gir/dep1/dep2/libdep2lib.so.
  [16/75] Compiling C object 'gir/dep1/07d7481@@dep1lib@sha/dep1.c.o'.
  [17/75] Generating symbol file 
'gir/dep1/dep2/7cbf35a@@dep2lib@sha/libdep2lib.so.symbols'.
  [18/75] Linking target gir/dep1/libdep1lib.so.
  [19/75] Generating symbol file 
'gir/dep1/07d7481@@dep1lib@sha/libdep1lib.so.symbols'.
  [20/75] Compiling C object 'gir/327a146@@gir_lib2@sha/meson-sample2.c.o'.
  [21/75] Linking target gir/libgir_lib2.so.
  [22/75] Generating gsettings-compile-schemas with a custom command.
  [23/75] Compiling C object 'schemas/fd70ea1@@schemaprog@exe/schemaprog.c.o'.
  [24/75] Linking target schemas/schemaprog.
  [25/75] Generating generated-gdbus.c with a custom command.
  [26/75] Generating generated-gdbus.h with a custom command.
  [27/75] Generating generated-gdbus-docbook with a custom command.
  [28/75] Compiling C object 
'gdbus/8d60afc@@gdbus-test@exe/meson-generated_.._generated-gdbus.c.o'.
  [29/75] Compiling C object 'gdbus/8d60afc@@gdbus-test@exe/gdbusprog.c.o'.
  [30/75] Generating MesonDep2-1.0.gir with a custom command.
  g-ir-scanner: link: cc -o 
/tmp/tmpbrjz1hlu/tmp-introspect81qm411v/MesonDep2-1.0 
/tmp/tmpbrjz1hlu/tmp-introspect81qm411v/MesonDep2-1.0.o -L. -Wl,-rpath,. 
-Wl,--no-as-needed -L/tmp/tmpbrjz1hlu/gir/dep1/dep2 
-Wl,-rpath,/tmp/tmpbrjz1hlu/gir/dep1/dep2 -lasan -ldep2lib -lgobject-2.0 
-lglib-2.0 -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread 
-lglib-2.0
  [31/75] Linking target gdbus/gdbus-test.
  [32/75] Generating MesonDep2-1.0.typelib with a custom command.
  [33/75] Generating enums.h with a meson_exe.py custom command.
  [34/75] Generating enums.c with a meson_exe.py custom command.
  [35/75] Compiling C object 
'mkenums/75bf728@@enumprog1@exe/meson-generated_.._enums.c.o'.
  [36/75] Compiling C object 
'mkenums/75bf728@@enumprog1@exe/meson-generated_.._main1.c.o'.
  [37/75] Linking target mkenums/enumprog1.
  [38/75] Generating MesonDep1-1.0.gir with a custom command.
  FAILED: gir/dep1/MesonDep1-1.0.gir 
  /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include 
--no-libtool --namespace=MesonDep1 --nsversion=1.0 --warn-all --output 
gir/dep1/MesonDep1-1.0.gir --c-include=dep1.h 

[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal

2019-10-23 Thread corrado venturini
python3-apt was already installed but I still have the same problem

corrado@corrado-p7-ff-1021:~$ apt policy python3-apt
python3-apt:
  Installed: 1.9.0ubuntu1
  Candidate: 1.9.0ubuntu1
  Version table:
 *** 1.9.0ubuntu1 500
500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-p7-ff-1021:~$

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

Title:
  could not find a distribution template for Ubuntu/focal

Status in python-apt package in Ubuntu:
  New

Bug description:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources():

  Click on software-properties-gtk icon: I have a message about crash,
  click on 'send' nothing happen.

  I attached crash file

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

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


[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal

2019-10-23 Thread Sebastien Bacher
the python3-apt binary should be installed...

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

Title:
  could not find a distribution template for Ubuntu/focal

Status in python-apt package in Ubuntu:
  New

Bug description:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources():

  Click on software-properties-gtk icon: I have a message about crash,
  click on 'send' nothing happen.

  I attached crash file

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

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


[Touch-packages] [Bug 1849517] Re: latest kernel problem 5.3

2019-10-23 Thread Paul White
** Package changed: xorg (Ubuntu) => linux (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/1849517

Title:
  latest kernel problem 5.3

Status in linux package in Ubuntu:
  New

Bug description:
  when i upgraded my system from 19.04 to 19.10 with latest kernel 
5.3.0-19-generic everything works fine except when the system goes to sleep and 
on wakeup the brighness goes to maximum even fresh install of ubuntu 19.10 has 
the same problem .
  i have downgraded the kernel from 
5.3.0-19-generic to 5.0.0-32-generic , now everything works fine . i mean sleep 
mode works and on wakeup returns to normal brightness value . as ubuntu 19.04 
works perfectly on my system with kernel 5.0.0-32-generic now i m using ubuntu 
19.10 with kernel 5.0.0-32-generic thats also working on my laptop.
 i dont know what causing to kernel 5.3.0.19 so remove 
that, my laptop hp g7 245 ryzen 3 2200u
  Thanx

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 20:48:03 2019
  DistUpgraded: 2019-10-23 15:18:23,354 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [103c:8562]
  MachineType: Hewlett-Packard HP 245 G7 Notebook PC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=380079ae-40a6-4aed-8280-2b263a41cf1e ro acpi_osi=Linux quiet splash 
resume=2d8fc2ac-0fa9-4d85-99bc-e3f760724070 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago)
  dmi.bios.date: 07/03/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8562
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 84.24
  dmi.chassis.asset.tag: 5CG9212QLP
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.42:bd07/03/2019:svnHewlett-Packard:pnHP245G7NotebookPC:pvr:rvnHewlett-Packard:rn8562:rvr84.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 245 G7 Notebook PC
  dmi.product.sku: 6JM93PA#ACJ
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1849517] [NEW] latest kernel problem 5.3

2019-10-23 Thread raza
Public bug reported:

when i upgraded my system from 19.04 to 19.10 with latest kernel 
5.3.0-19-generic everything works fine except when the system goes to sleep and 
on wakeup the brighness goes to maximum even fresh install of ubuntu 19.10 has 
the same problem .
i have downgraded the kernel from 
5.3.0-19-generic to 5.0.0-32-generic , now everything works fine . i mean sleep 
mode works and on wakeup returns to normal brightness value . as ubuntu 19.04 
works perfectly on my system with kernel 5.0.0-32-generic now i m using ubuntu 
19.10 with kernel 5.0.0-32-generic thats also working on my laptop.
   i dont know what causing to kernel 5.3.0.19 so remove 
that, my laptop hp g7 245 ryzen 3 2200u
Thanx

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 23 20:48:03 2019
DistUpgraded: 2019-10-23 15:18:23,354 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon 
Vega Mobile Series] [103c:8562]
MachineType: Hewlett-Packard HP 245 G7 Notebook PC
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=380079ae-40a6-4aed-8280-2b263a41cf1e ro acpi_osi=Linux quiet splash 
resume=2d8fc2ac-0fa9-4d85-99bc-e3f760724070 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago)
dmi.bios.date: 07/03/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.42
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8562
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 84.24
dmi.chassis.asset.tag: 5CG9212QLP
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.42:bd07/03/2019:svnHewlett-Packard:pnHP245G7NotebookPC:pvr:rvnHewlett-Packard:rn8562:rvr84.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP 200
dmi.product.name: HP 245 G7 Notebook PC
dmi.product.sku: 6JM93PA#ACJ
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan 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/1849517

Title:
  latest kernel problem 5.3

Status in linux package in Ubuntu:
  New

Bug description:
  when i upgraded my system from 19.04 to 19.10 with latest kernel 
5.3.0-19-generic everything works fine except when the system goes to sleep and 
on wakeup the brighness goes to maximum even fresh install of ubuntu 19.10 has 
the same problem .
  i have downgraded the kernel from 
5.3.0-19-generic to 5.0.0-32-generic , now everything works fine . i mean sleep 
mode works and on wakeup returns to normal brightness value . as ubuntu 19.04 
works perfectly on my system with kernel 5.0.0-32-generic now i m using ubuntu 
19.10 with kernel 5.0.0-32-generic thats also working on my laptop.
 i dont know what causing to kernel 5.3.0.19 so remove 
that, my laptop hp g7 245 ryzen 3 2200u
  Thanx

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 20:48:03 2019
  DistUpgraded: 2019-10-23 15:18:23,354 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py 

[Touch-packages] [Bug 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

2019-10-23 Thread Paride Legovini
Bug status updated accordingly. I set the linux task to Invalid as the
kernel was not involved after all. Thanks again Stéphane and Colin!

** Changed in: lxc (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: lxc (Ubuntu Cosmic)
   Status: Confirmed => Fix Released

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

** Changed in: lxc (Ubuntu Eoan)
   Status: Confirmed => Fix Released

** No longer affects: linux (Ubuntu Eoan)

** No longer affects: linux (Ubuntu Disco)

** No longer affects: linux (Ubuntu Cosmic)

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Cosmic:
  Fix Released
Status in lxc source package in Disco:
  Fix Released
Status in lxc source package in Eoan:
  Fix Released

Bug description:
  I'm not sure exactly what got me into this state, but I have several
  lxc containers that cannot be deleted.

  $ lxc info
  
  api_status: stable
  api_version: "1.0"
  auth: trusted
  public: false
  auth_methods:
  - tls
  environment:
addresses: []
architectures:
- x86_64
- i686
certificate: |
  -BEGIN CERTIFICATE-
  
  -END CERTIFICATE-
certificate_fingerprint: 
3af6f8b8233c5d9e898590a9486ded5c0bec045488384f30ea921afce51f75cb
driver: lxc
driver_version: 3.0.1
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.15.0-23-generic
server: lxd
server_pid: 15123
server_version: "3.2"
storage: zfs
storage_version: 0.7.5-1ubuntu15
server_clustered: false
server_name: milhouse

  $ lxc delete --force b1
  Error: Failed to destroy ZFS filesystem: cannot destroy 
'default/containers/b1': dataset is busy

  Talking in #lxc-dev, stgraber and sforeshee provided diagnosis:

   | short version is that something unshared a mount namespace causing
   | them to get a copy of the mount table at the time that dataset was
   | mounted, which then prevents zfs from being able to destroy it)

  The work around provided was

   | you can unstick this particular issue by doing:
   |  grep default/containers/b1 /proc/*/mountinfo
   | then for any of the hits, do:
   |   nsenter -t PID -m -- umount 
/var/snap/lxd/common/lxd/storage-pools/default/containers/b1
   | then try the delete again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  smoser31412 F pulseaudio
   /dev/snd/controlC2:  smoser31412 F pulseaudio
   /dev/snd/controlC0:  smoser31412 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 28 10:42:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (1071 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  MachineType: 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.174
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0246.2015.0309.1355
  dmi.board.asset.tag: �
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-503
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 3
  dmi.chassis.vendor: �
  dmi.chassis.version: �
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0246.2015.0309.1355:bd03/09/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr:
  dmi.product.family: �
  dmi.product.name: 

[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal

2019-10-23 Thread corrado venturini
package python-apt is not installed. should I install it?
thanks

orrado@corrado-p7-ff-1021:~$ apt policy python-apt
python-apt:
  Installed: (none)
  Candidate: 1.9.0ubuntu1
  Version table:
 1.9.0ubuntu1 500
500 http://it.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
corrado@corrado-p7-ff-1021:~$

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

Title:
  could not find a distribution template for Ubuntu/focal

Status in python-apt package in Ubuntu:
  New

Bug description:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources():

  Click on software-properties-gtk icon: I have a message about crash,
  click on 'send' nothing happen.

  I attached crash file

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

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


[Touch-packages] [Bug 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

2019-10-23 Thread Scott Moser
best. fix. ever.

working after a reboot.

$ snap list lxd
Name  Version  RevTracking  Publisher   Notes
lxd   3.18 12211  stablecanonical✓  -

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

Title:
  lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

Status in linux package in Ubuntu:
  Triaged
Status in lxc package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Triaged
Status in lxc source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  New
Status in lxc source package in Disco:
  New
Status in linux source package in Eoan:
  Triaged
Status in lxc source package in Eoan:
  Confirmed

Bug description:
  I'm not sure exactly what got me into this state, but I have several
  lxc containers that cannot be deleted.

  $ lxc info
  
  api_status: stable
  api_version: "1.0"
  auth: trusted
  public: false
  auth_methods:
  - tls
  environment:
addresses: []
architectures:
- x86_64
- i686
certificate: |
  -BEGIN CERTIFICATE-
  
  -END CERTIFICATE-
certificate_fingerprint: 
3af6f8b8233c5d9e898590a9486ded5c0bec045488384f30ea921afce51f75cb
driver: lxc
driver_version: 3.0.1
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.15.0-23-generic
server: lxd
server_pid: 15123
server_version: "3.2"
storage: zfs
storage_version: 0.7.5-1ubuntu15
server_clustered: false
server_name: milhouse

  $ lxc delete --force b1
  Error: Failed to destroy ZFS filesystem: cannot destroy 
'default/containers/b1': dataset is busy

  Talking in #lxc-dev, stgraber and sforeshee provided diagnosis:

   | short version is that something unshared a mount namespace causing
   | them to get a copy of the mount table at the time that dataset was
   | mounted, which then prevents zfs from being able to destroy it)

  The work around provided was

   | you can unstick this particular issue by doing:
   |  grep default/containers/b1 /proc/*/mountinfo
   | then for any of the hits, do:
   |   nsenter -t PID -m -- umount 
/var/snap/lxd/common/lxd/storage-pools/default/containers/b1
   | then try the delete again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  smoser31412 F pulseaudio
   /dev/snd/controlC2:  smoser31412 F pulseaudio
   /dev/snd/controlC0:  smoser31412 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 28 10:42:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (1071 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  MachineType: 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.174
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0246.2015.0309.1355
  dmi.board.asset.tag: �
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-503
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 3
  dmi.chassis.vendor: �
  dmi.chassis.version: �
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0246.2015.0309.1355:bd03/09/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr:
  dmi.product.family: �
  dmi.product.name: �
  dmi.product.version: �
  dmi.sys.vendor: �

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

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

[Touch-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save

2019-10-23 Thread Olivier Tilloy
As noted in comment #2, I used to be able to observe the problem, but I
cannot any longer. I upgraded my laptop to 19.10 a while ago while it
was still in development, and I couldn't tell for sure when the problem
went away. I didn't do a fresh install, nor did I create a new user or
cleaned up settings in any way.

@Christopher: from your last comment I understand you're still affected.
Have you upgraded to 19.10 ? If not, are you planning to do it in a not-
too-distant future? If so I'd be interested in knowing whether this
resolves the issue for you.

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

Title:
  print page dialog latency when trying to cancel or to save

Status in chromium-browser package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Since less than a month ago, using the print page dialog (which for me
  defaults to saving as PDF) is outlandishly slow. Once opened, if I try
  to close it (click cancel / press Esc) or to use it (click Save or
  press Enter), there is no visible response, and my system hangs for 10
  seconds.  After that though, the operation concludes successfully and
  things return to normal.

  This did not used to happen. Closing or submitting the print-to-PDF
  used to result in the pop-up window closing immediately and the
  browser regaining responsiveness.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-5:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa
   modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-DP-6:
   enabled: disabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM=
   modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 
800x600 640x480 640x480 720x400
  DRM.card0-DP-7:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo=
   modes: 1920x1080
  Date: Mon Jun 17 14:03:12 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2019-01-24 (144 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
   
  Load-Avg-1min: 3.09
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Touch-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

2019-10-23 Thread Gunnar Hjalmarsson
On 2019-10-23 08:09, Steve Langasek wrote:
>> * Which values do the environment variables have?
> 
> $ env | grep -E 'XMOD|_IM'
> GTK_IM_MODULE=ibus
> QT4_IM_MODULE=ibus
> XMODIFIERS=@im=ibus
> CLUTTER_IM_MODULE=ibus
> QT_IM_MODULE=ibus
> $

Looks good.

> I don't know where these are being set, because Xsession is hell.

They are set by im-config on X-sessions on Debian/Ubuntu. (Without im-
config, the most important ones would have been set by GNOME instead.)

>> * Can you reproduce it on a fresh 19.10 (or with a newly created
>> user)?
> 
> No.

Then we know that the issue is caused by something in your $HOME. The
question is what and how it ended up there...

There is a ~/.cache/ibus/compose folder with a suspicious cache file.
Can you please rename that folder, relogin, and check if the issue is
still present.

>> Assuming that you are on standard Ubuntu, using ibus-setup for
>> adding/removing input sources is not the 'right' way
> 
> That's not really a satisfactory position, given that the ibus-setup
> command is shipped in the ibus package, which is seeded as part of
> the Ubuntu Desktop.  If the command should not be used, it should not
> be present.

Fair point. But on non-GNOME desktops ibus-setup is needed, and made
available to the users via an IBus icon. I wouldn't dare to say that you
*never* need to use ibus-setup on a GNOME desktop, but GNOME provides an
integration where XKB layouts and IBus IMs are presented together in
Settings, so normally the users don't need to bother with ibus-setup.

>> it's supposed to be done in Settings -> Region & Language (probably
>> not significant for this issue, but still...).
> 
> I can't find anything under the settings screens that resembles the
> selection of input methods presented by ibus-setup.

The "Input Sources" section in Region & Language is what I'm talking
about. That interface controls the available input sources and saves the
settings as

gsettings get org.gnome.desktop.input-sources sources

The input sources set via ibus-setup are saved as

gsettings get org.freedesktop.ibus.general preload-engines

but on GNOME the latter dconf setting is ignored AFAIK.

> ibus-setup presents 'Chinese SunPinyin', Settings only presents
> 'Chinese'; and removing the Chinese input method from ibus-setup's
> config doesn't change what's displayed in Settings (Chinese is still
> listed here).

For an IBus IM to be presented in Settings or ibus-setup, the package -
in your case ibus-sunpinyin - needs to be installed. But when you say
that only Chinese is listed in Settings, and assuming that ibus-
sunpinyin is still installed on your machine, can it possibly be that if
you click the "Chinese" option in Settings, you end up in a sub menu
which includes Chinese SunPinyin?

** Changed in: ibus (Ubuntu)
   Status: New => Incomplete

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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


[Touch-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

2019-10-23 Thread Adam Niedling
** Tags added: eoan

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

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  Unknown
Status in GTK+:
  Unknown
Status in Mir:
  Fix Released
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

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

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


[Touch-packages] [Bug 1051288] Re: LightDM assumes there's only ONE system default layout

2019-10-23 Thread Adam Niedling
** Tags added: eoan

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

Title:
  LightDM assumes there's only ONE system default layout

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  In Greece, the default system layout is "us,gr":
  $ grep XKBLAYOUT /etc/default/keyboard 
  XKBLAYOUT="us,gr"

  For new users that don't have .dmrc or accountsservice entries and are 
supposed to get the system defaults, LightDM assumes their keyboard layout is 
"us".
  So they can't switch languages in the greeter and they can't input national 
characters until they login, go to gnome settings and manually set the keyboard 
layout.

  A similar bug was
  https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/919200, but
  that was only solved for the single-layout case.

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

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


[Touch-packages] [Bug 1847710] Re: [ThinkPad X1 Yoga 4th Gen][20QGZ4MTUS, Realtek ALC285, Speaker, Internal] The Volume remains the same value.

2019-10-23 Thread Gabriel Zhi Chen
The issue reproduces on Eoan final release version.

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

Title:
  [ThinkPad X1 Yoga 4th Gen][20QGZ4MTUS, Realtek ALC285, Speaker,
  Internal] The Volume remains the same value.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [Steps to reproduce]
  1. Install Ubuntu 19.10 on ThinkPad X1 Yoga 4th Gen
  2. Login system
  3. Navigate to 'System Settings' -> 'Sound'
  4. Adjust the 'System Volume' bar and verify the sound result
  5. Press 'F2 and F3' to adjust system volume

  [Expected result]
  System volume should be heard with several sound level.

  [Actual result]
  No matter what adjusted, the volume remains the same value.

  [Notes]
  Navigate to 'System Settings' -> 'Sound' -> 'Over-Amplification', turn it 'On'
  Then adjust the sound, we could hear the different volume value beyond 100%, 
but it could remains the same value from 0 ~ 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1747 F pulseaudio
   /dev/snd/pcmC0D0p:   u  1747 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 12:01:52 2019
  InstallationDate: Installed on 2019-10-09 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   10月 11 10:57:40 u-ThinkPad-X1-Yoga-4th dbus-daemon[745]: [system] Activating 
via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.36' (uid=124 pid=952 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
   10月 11 10:57:57 u-ThinkPad-X1-Yoga-4th systemd[938]: pulseaudio.service: 
Succeeded.
   10月 11 10:57:59 u-ThinkPad-X1-Yoga-4th dbus-daemon[745]: [system] Rejected 
send message, 2 matched rules; type="method_call", sender=":1.785" (uid=124 
pid=2441 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error 
name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=734 
comm="/usr/lib/bluetooth/bluetoothd " label="unconfined")
   10月 11 10:58:07 u-ThinkPad-X1-Yoga-4th systemd[938]: pulseaudio.service: 
Succeeded.
   10月 11 10:58:07 u-ThinkPad-X1-Yoga-4th systemd[938]: pulseaudio.socket: 
Succeeded.
  Symptom_Type: Volume slider, or mixer problems
  Title: [20QGZ4MTUS, Realtek ALC285, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET39W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QGZ4MTUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET39W(1.22):bd10/04/2019:svnLENOVO:pn20QGZ4MTUS:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QGZ4MTUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QGZ4MTUS
  dmi.product.sku: LENOVO_MT_20QG_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1847709] Re: [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Mic-mute key and its LED can not work on Ubuntu 19.10

2019-10-23 Thread Gabriel Zhi Chen
The issue reproduces on Eoan final release version.

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

Title:
  [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Mic-
  mute key and its LED can not work on Ubuntu 19.10

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [Steps to reproduce]
  1. Install Ubuntu 19.10 on ThinkPad X1 Yoga 4th Gen
  2. Login system
  3. Press mic-mute key several times
  4. Verify the result
  5. Open a terminal and $ record test.wav
  6. Leave the terminal here and make voice, meanwhile, press mic-mute key 
several times

  [Expected result]
  Mic-mute key function and its LED work normally.

  [Actual result]
  Mic-mute key and its LED can not work on Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1747 F pulseaudio
   /dev/snd/pcmC0D0p:   u  1747 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 11:54:01 2019
  InstallationDate: Installed on 2019-10-09 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET39W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QGZ4MTUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET39W(1.22):bd10/04/2019:svnLENOVO:pn20QGZ4MTUS:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QGZ4MTUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QGZ4MTUS
  dmi.product.sku: LENOVO_MT_20QG_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1847708] Re: [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Internal mic is useless in Ubuntu 19.10

2019-10-23 Thread Gabriel Zhi Chen
The issue reproduces on Eeon Final release version.

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

Title:
  [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording]
  Internal mic is useless in Ubuntu 19.10

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [Steps to reproduce]
  1. Install Ubuntu 19.10 on ThinkPad X1 Yoga 4th Gen
  2. Login system
  3. Navigate to 'System Settings' -> 'Sound'
  4. Verify the input and output working or not

  [Expected result]
  Both input and output work normally, user could hear the sound from internal 
speaker, also could record voice from internal mic

  [Actual result]
  Internal speaker works normally, internal mic is useless and got gray always

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1747 F pulseaudio
   /dev/snd/pcmC0D0p:   u  1747 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 11:37:09 2019
  InstallationDate: Installed on 2019-10-09 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET39W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QGZ4MTUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET39W(1.22):bd10/04/2019:svnLENOVO:pn20QGZ4MTUS:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QGZ4MTUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QGZ4MTUS
  dmi.product.sku: LENOVO_MT_20QG_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

2019-10-23 Thread Lilian Tao
okay, thanks a lot for your help. 
I appreciate your time and advises.

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

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

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


[Touch-packages] [Bug 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298

2019-10-23 Thread Sooraj P Suresh
Same issue using Samsung Notebook Model NP930MBE

The sound in headphone is not clear and no sound at all in internal
speaker

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

Title:
  Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel
  - Realtek ALC298

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Unable to get system speakers working running 19.04.  At max volume,
  sound is barely perceptible through headphones.  Pavucontrol shows
  sounds is present, but no amount of adjustments makes a difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 3355 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun 28 00:44:13 2019
  InstallationDate: Installed on 2019-06-05 (22 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AHK.029.190425.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930MBE-K04US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 930MBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
  dmi.product.version: P02AHK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently

2019-10-23 Thread Sebastien Bacher
Ubuntu currently doesn't have a dedicated network-manager maintainer,
you might have more luck reporting issue directly upstream on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager

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

Title:
  network-manager needs to be restarted frequently

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops
  working frequently and the network-manager service needs to be
  restarted. It will die on its own, but can be triggered by switching
  wifi 3 times (sometimes more, sometimes fewer)!

  When it is working, I have:
  ```
  % usr/bin/sudo nmcli device
  DEVICE   TYPE  STATE CONNECTION 
  wlp62s0  wifi  connected ATT964 
  p2p-dev-wlp62s0  wifi-p2p  disconnected  -- 
  enp59s0  ethernet  unavailable   -- 
  lo   loopback  unmanaged --   
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
 description: Wireless interface
 product: Wireless 8260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:3e:00.0
 logical name: wlp62s0
 version: 3a
 serial: e4:b3:18:e3:11:e7
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:133 memory:dc20-dc201fff
  % /usr/bin/sudo lspci -vnnn | grep -A 9 Network
  3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 
[8086:24f3] (rev 3a)
Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010]
Flags: bus master, fast devsel, latency 0, IRQ 133
Memory at dc20 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7
Capabilities: [14c] Latency Tolerance Reporting
  ```
  If I switch between my two wifi routers three times (sometimes more times) 
using the Select Network command on the taskbar, wifi stops working.

  Issuing the commands above yields the following differences:
  ```
  % /usr/bin/sudo nmcli device
  DEVICE   TYPE  STATECONNECTION 
  enp59s0  ethernet  unavailable  -- 
  wlp62s0  wifi  unavailable  -- 
  p2p-dev-wlp62s0  wifi-p2p  unavailable  -- 
  lo   loopback  unmanaged
  
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
   ...snip...
  configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
  ```
  /var/log/syslog reports the following after failing to switch wifi networks:
  ```
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): disconnecting for new activation request.
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): state change: activated -> deactivating (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5485] 
manager: NetworkManager state is now DISCONNECTING
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5548] 
audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" 
name="ATT964" pid=21476 uid=1010 result="success"
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5550] 
device (wlp62s0): state change: deactivating -> disconnected (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): state changed bound -> done
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5572] 
dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5572] 
dhcp6 (wlp62s0): state changed bound -> done
  Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating 
from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING)
  Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: 

[Touch-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

2019-10-23 Thread Will Cooke
** Tags added: desktop-trello-import

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

Title:
  src/date-time.cpp:171:GDateTime*
  unity::indicator::datetime::DateTime::get() const: assertion failed:
  (m_dt)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.10, indicator-datetime
  15.10+19.10.20190819.1-0ubuntu1 crashes right from the start:

  $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service 
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  [...]
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  **
  
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
  Bail out! 
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

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

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


[Touch-packages] [Bug 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

2019-10-23 Thread Paride Legovini
The current stable snap seems to fully address the issue. See:

https://github.com/lxc/lxd/issues/4656#issuecomment-542886330

and following.

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

Title:
  lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

Status in linux package in Ubuntu:
  Triaged
Status in lxc package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Triaged
Status in lxc source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  New
Status in lxc source package in Disco:
  New
Status in linux source package in Eoan:
  Triaged
Status in lxc source package in Eoan:
  Confirmed

Bug description:
  I'm not sure exactly what got me into this state, but I have several
  lxc containers that cannot be deleted.

  $ lxc info
  
  api_status: stable
  api_version: "1.0"
  auth: trusted
  public: false
  auth_methods:
  - tls
  environment:
addresses: []
architectures:
- x86_64
- i686
certificate: |
  -BEGIN CERTIFICATE-
  
  -END CERTIFICATE-
certificate_fingerprint: 
3af6f8b8233c5d9e898590a9486ded5c0bec045488384f30ea921afce51f75cb
driver: lxc
driver_version: 3.0.1
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.15.0-23-generic
server: lxd
server_pid: 15123
server_version: "3.2"
storage: zfs
storage_version: 0.7.5-1ubuntu15
server_clustered: false
server_name: milhouse

  $ lxc delete --force b1
  Error: Failed to destroy ZFS filesystem: cannot destroy 
'default/containers/b1': dataset is busy

  Talking in #lxc-dev, stgraber and sforeshee provided diagnosis:

   | short version is that something unshared a mount namespace causing
   | them to get a copy of the mount table at the time that dataset was
   | mounted, which then prevents zfs from being able to destroy it)

  The work around provided was

   | you can unstick this particular issue by doing:
   |  grep default/containers/b1 /proc/*/mountinfo
   | then for any of the hits, do:
   |   nsenter -t PID -m -- umount 
/var/snap/lxd/common/lxd/storage-pools/default/containers/b1
   | then try the delete again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  smoser31412 F pulseaudio
   /dev/snd/controlC2:  smoser31412 F pulseaudio
   /dev/snd/controlC0:  smoser31412 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 28 10:42:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (1071 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  MachineType: 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.174
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0246.2015.0309.1355
  dmi.board.asset.tag: �
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-503
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 3
  dmi.chassis.vendor: �
  dmi.chassis.version: �
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0246.2015.0309.1355:bd03/09/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr:
  dmi.product.family: �
  dmi.product.name: �
  dmi.product.version: �
  dmi.sys.vendor: �

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

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

[Touch-packages] [Bug 1814072] Re: software-properties-gtk does not recognize https mirrors under Ubuntu Software

2019-10-23 Thread Alex N.
This is partly fixed in Eoan, https sources are now listed under "Other
Software".

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

Title:
  software-properties-gtk does not recognize https mirrors under Ubuntu
  Software

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  1. Change main Ubuntu mirrors to https in /etc/apt/sources.list and do "apt 
update"
  2. Run software-properties-gtk
  3. Go to "Ubuntu Software" tab

  What happens:

  The tab "Ubuntu Software" does not list https mirrors. The
  corresponding boxes are not checked, the correct "Download from" entry
  is not selected and falls back to "Main server". The correct sources
  are just listed under "Other Software".

  What should happen:

  The tab "Ubuntu Software" should recognize the https mirrors from apt
  and tick the corresponding boxes and select the correct server in the
  "Download from" list.

  Ubuntu 18.04
  software-properties-gtk 0.96.24.32.7

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

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


[Touch-packages] [Bug 1849435] [NEW] could not find a distribution template for Ubuntu/focal

2019-10-23 Thread corrado venturini
Public bug reported:

software-properties-gtk crashed with
aptsources.distro.NoDistroTemplateException in get_sources():

Click on software-properties-gtk icon: I have a message about crash,
click on 'send' nothing happen.

I attached crash file

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

** Attachment added: "_usr_bin_software-properties-gtk.1000.crash"
   
https://bugs.launchpad.net/bugs/1849435/+attachment/5299369/+files/_usr_bin_software-properties-gtk.1000.crash

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

Title:
  could not find a distribution template for Ubuntu/focal

Status in software-properties package in Ubuntu:
  New

Bug description:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources():

  Click on software-properties-gtk icon: I have a message about crash,
  click on 'send' nothing happen.

  I attached crash file

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

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


[Touch-packages] [Bug 1847946] Re: initramfs contains modprobe blacklist from all installed kernel versions

2019-10-23 Thread Kai-Heng Feng
** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu)

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  initramfs contains modprobe blacklist from all installed kernel
  versions

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  # lsinitramfs /boot/initrd.img-5.3.0-18-generic | fgrep usr/lib/modprobe.d
  usr/lib/modprobe.d
  usr/lib/modprobe.d/aliases.conf
  usr/lib/modprobe.d/blacklist_linux_5.3.0-13-generic.conf
  usr/lib/modprobe.d/blacklist_linux_5.3.0-17-generic.conf
  usr/lib/modprobe.d/blacklist_linux_5.3.0-18-generic.conf
  usr/lib/modprobe.d/fbdev-blacklist.conf
  usr/lib/modprobe.d/systemd.conf

  I don't think this is the intended behavior.

  The blacklists may have same contents most of the times. But when they
  don't, (user changed kernel package/flavor/etc.) this may cause
  unexpected issues.

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

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


[Touch-packages] [Bug 1847946] [NEW] initramfs contains modprobe blacklist from all installed kernel versions

2019-10-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

# lsinitramfs /boot/initrd.img-5.3.0-18-generic | fgrep usr/lib/modprobe.d
usr/lib/modprobe.d
usr/lib/modprobe.d/aliases.conf
usr/lib/modprobe.d/blacklist_linux_5.3.0-13-generic.conf
usr/lib/modprobe.d/blacklist_linux_5.3.0-17-generic.conf
usr/lib/modprobe.d/blacklist_linux_5.3.0-18-generic.conf
usr/lib/modprobe.d/fbdev-blacklist.conf
usr/lib/modprobe.d/systemd.conf

I don't think this is the intended behavior.

The blacklists may have same contents most of the times. But when they
don't, (user changed kernel package/flavor/etc.) this may cause
unexpected issues.

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


** Tags: eoan
-- 
initramfs contains modprobe blacklist from all installed kernel versions
https://bugs.launchpad.net/bugs/1847946
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools in Ubuntu.

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


[Touch-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

2019-10-23 Thread Steve Langasek
> * Which values do the environment variables have?

$ env | grep -E 'XMOD|_IM'
GTK_IM_MODULE=ibus
QT4_IM_MODULE=ibus
XMODIFIERS=@im=ibus
CLUTTER_IM_MODULE=ibus
QT_IM_MODULE=ibus
$

I don't know where these are being set, because Xsession is hell.

> * Are you possibly on Wayland?

No.

> * Can you reproduce it on a fresh 19.10 (or with a newly created
user)?

No.

> Assuming that you are on standard Ubuntu, using ibus-setup for
> adding/removing input sources is not the 'right' way

That's not really a satisfactory position, given that the ibus-setup
command is shipped in the ibus package, which is seeded as part of the
Ubuntu Desktop.  If the command should not be used, it should not be
present.

> it's supposed to be done in Settings -> Region & Language (probably not
> significant for this issue, but still...).

I can't find anything under the settings screens that resembles the
selection of input methods presented by ibus-setup.  ibus-setup presents
'Chinese SunPinyin', Settings only presents 'Chinese'; and removing the
Chinese input method from ibus-setup's config doesn't change what's
displayed in Settings (Chinese is still listed here).

** Changed in: ibus (Ubuntu)
   Status: Incomplete => 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/1849399

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  New

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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