date:20180817

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Not working proper

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rohit  1642 F pulseaudio
  Date: Tue Feb 20 15:31:30 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=4d934564-93f4-44fa-a0a2-40391da06695
  InstallationDate: Installed on 2018-01-29 (22 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7d503abe-28c9-44cd-9fb8-b357ae7619cd ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.5, Python 3.5.2, python3-minimal, 3.5.1-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7.1
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to artful on 2018-02-13 (7 days ago)
  dmi.bios.date: 11/11/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WVG4110H.86A.0015.2010..1718
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DG41WV
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE90316-104
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWVG4110H.86A.0015.2010..1718:bd11/11/2010:svn:pn:pvr:rvnIntelCorporation:rnDG41WV:rvrAAE90316-104:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1787480] Re: bugpattern checking not working for a ubiquity bug report

2018-08-17 Thread Francis Ginther

** Tags added: id-5b75e3e0cb90d91c3377324a

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

Title:
  bugpattern checking not working for a ubiquity bug report

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Phillip Susi wrote a bug pattern for ubiquity / grub-installer at
  https://bazaar.launchpad.net/~ubuntu-bugcontrol/apport/ubuntu-
  bugpatterns/revision/584. While the bug pattern works, tested with
  test-local and search-bugs from that branch new bug reports are still
  appearing in Launchpad.

  I confirmed that the pattern exists in https://people.canonical.com
  /~ubuntu-archive/bugpatterns/bugpatterns.xml and that using that url
  instead of a local file in test-local works. So it seems to be
  something with apport's ui.py or report.py when the bug report is
  being filed.

  The best way to test this would be a Live CD where the bug will
  actually occur.

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

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

[Touch-packages] [Bug 160999] Re: Apport doesn't overwrite existing core files

2018-08-17 Thread Vasilis

Same problem here!

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

Title:
  Apport doesn't overwrite existing core files

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  While debugging some code, I noticed that existing core files aren't
  being overwritten when they should be.  According to core(5), the
  following file should be overwritten, but it's not:

  bam:/tmp$ id -un
  gerald
  bam:/tmp$ ls -l core
  -rw--- 1 gerald gerald 3407872 2007-10-30 21:22 core
  bam:/tmp$ date
  Thu Nov  8 09:36:23 PST 2007
  bam:/tmp$ ./coretst 
  Segmentation fault (core dumped)
  bam:/tmp$ ls -l core
  -rw--- 1 gerald gerald 3407872 2007-10-30 21:22 core

  Creating the initial core file works fine:

  bam:/tmp$ rm core
  bam:/tmp$ ./coretst 
  Segmentation fault (core dumped)
  bam:/tmp$ ls -l core
  -rw--- 1 gerald gerald 163840 2007-11-08 09:36 core
  bam:/tmp$ date
  Thu Nov  8 09:36:49 PST 2007

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

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

[Touch-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

2018-08-17 Thread Francis Ginther

** Tags added: id-5b75e82507956e57463be7d9

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

Title:
  Unattended upgrades removed linux-image-generic

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  On a fairly fresh install of 18.04 with no modifications whatsoever to
  the unattended-upgrades configuration, it decided to remove linux-
  image-generic which also removed linux-modules-extra which caused
  sound drivers to disappear, etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 13:17:30 2018
  InstallationDate: Installed on 2018-07-24 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.

2018-08-17 Thread kikito

@Coeur Noir: I know.

I tested this day with a LiveUSB Cosmic Cuttlefish (Gnome-shell): same
bug.

(C'est un bug Gnome et pas un bug Unity :-) )

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

Title:
  Clock : incorrect date format in FR in Unity panel …bionic.

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Hi,

  Here is Ubuntu 18.04 with Unity session ( I know… )

  System language and regional settings are set to French.

  In regional setting the date reads

  day number month year hour minute…

  which is correct for French.

  But the clock in the Unity panel reads

  day month number year hour minute…

  which looks more English than French order.

  Any config file I might edit to make my clock « more French » ?

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

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

[Touch-packages] [Bug 1427807] Re: usermod's man refers to ---sub-uids but accepts only ---subuids

2018-08-17 Thread Simon Déziel

The bug is fixed in Bionic.

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

Title:
  usermod's man refers to --*-sub-uids but accepts only --*-subuids

Status in shadow package in Ubuntu:
  Won't Fix

Bug description:
  The man page refers to sub-uids and sub-gids but those don't take any
  "-" between sub and [ug]ids. The help message conforms to what the
  command accepts though.

  $ man usermod | grep -F -- -sub
 -v, --add-sub-uids FIRST-LAST
 -V, --del-sub-uids FIRST-LAST
 This option may be specified multiple times to remove multiple 
ranges to a users account. When both --del-sub-uids and --add-sub-uids are 
specified remove of all subordinate uid ranges happens before any
 -w, --add-sub-gids FIRST-LAST
 -W, --del-sub-gids FIRST-LAST
 This option may be specified multiple times to remove multiple 
ranges to a users account. When both --del-sub-gids and --add-sub-gids are 
specified remove of all subordinate gid ranges happens before any

  $ usermod --help | grep -F -- -sub
-v, --add-subuids FIRST-LAST  add range of subordinate uids
-V, --del-subuids FIRST-LAST  remvoe range of subordinate uids
-w, --add-subgids FIRST-LAST  add range of subordinate gids
-W, --del-subgids FIRST-LAST  remvoe range of subordinate gids

  
  More info on the environment:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  $ apt-cache policy passwd
  passwd:
Installed: 1:4.1.5.1-1ubuntu9
Candidate: 1:4.1.5.1-1ubuntu9
Version table:
   *** 1:4.1.5.1-1ubuntu9 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: passwd 1:4.1.5.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 13:37:50 2015
  InstallationDate: Installed on 2014-01-26 (400 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1786809] Re: Update to 2.57.90

2018-08-17 Thread Jeremy Bicha

This bug was fixed in the package glib-networking - 2.57.90-1
Sponsored for Iain Lane (laney)

---
glib-networking (2.57.90-1) experimental; urgency=medium

  * debian/*: Update for experimental / 2.57
  * New upstream release 2.57.90 (LP: #1786809)
- Properly check for server errors in connection tests
- Perform certificate verification during, not after, TLS handshake
- Avoid trailing dots in SNI hostnames
- Send fallback SCSV with fallback connection attempts
- Fail unsafe rehandshake attempts initiated by API request
- Fix memory leaks when calling g_tls_connection_gnutls_get_certificate()
- Use GnuTLS system trust and remove build option to specify cert bundle
- Fix criticals when child streams outlast the parent GTlsConnection
- Fix crash when setting client cert without private key
- Never install GIO modules outside build prefix
- Don't install test files if installed tests are disabled
- Fix build with -Dpkcs11=false
- g_tls_certificate_verify() no longer manually verifies certificate
  activation/expiration time, matching the current behavior of
  g_tls_database_verify_chain().
  * debian/control*:
- Remove libp11-kit BD - upstream has disabled this by default now.
- Standards-Version → 4.2.0, no changes required.

 -- Iain Lane   Thu, 16 Aug 2018 10:40:20 +0200

** Changed in: glib-networking (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 glib-networking in Ubuntu.
https://bugs.launchpad.net/bugs/1786809

Title:
  Update to 2.57.90

Status in glib-networking package in Ubuntu:
  Fix Released

Bug description:
  Do it

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

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

[Touch-packages] [Bug 1785764] Re: Ubuntu default colour profile distorts colours on some machines (white looks green, too dark, or under-saturated)

2018-08-17 Thread brandon lockley

So a little off topic but as it seems to be related do you have ant
thoughts on why this didn't fix night mode in my case? In case you
missed in in my previous post deleting the colour profiles fixed chrome
and image viewer but did not fix the night mode issue.

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

Title:
  Ubuntu default colour profile distorts colours on some machines (white
  looks green, too dark, or under-saturated)

Status in colord package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 18.04.1 LTS 
  Running on an i7-6700k with a GTX 1080
  Reproducible with nvidia-driver-396 or xserver-xorg-video-nouveau
  and a single 4K screen (TV) connected via HDMI.

  The issue:
  Any dark content displayed by an effected application (e.g. a very dark image 
or dark themed web page) is much darker than intended making it almost 
unusable. 

  This only effects applications that are launched when the 4K screen is
  connected. If i disconnect the 4K screen, launch the app via a
  different 1080p monitor then reconnect the 4K screen the app remains
  unaffected.

  The only apps i have found so far that are effected by this are Google
  Chrome and Image Viewer. That said this is only noticeable when the
  app is displaying dark contend so if other apps are affected it may be
  impossible to tell.

  The attached screenshot uses a black to white gradient image to clearly 
demonstrate the issue. 
  Is seems like it may be an issue with colour depth as bellow a certain 
brightness it just goes strait to black.

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

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

[Touch-packages] [Bug 1787600] [NEW] kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960): apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor.gnome-system-monitor" n

Public bug reported:

This log repeats so many times in file /var/log/syslog and
/var/log/kern.log, causing the size of 2 files exceed 100Mb

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

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

Title:
  kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960):
  apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor
  .gnome-system-monitor" name="/run/mount/utab" pid=2265 comm="gnome-
  system-mo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Status in apparmor package in Ubuntu:
  New

Bug description:
  This log repeats so many times in file /var/log/syslog and
  /var/log/kern.log, causing the size of 2 files exceed 100Mb

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

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

[Touch-packages] [Bug 1787602] [NEW] Ubuntu 18.04 won't boot on full disk

2018-08-17 Thread dronus

Public bug reported:

The basic systemd configuration is not tolerating a full root fs.

Ubuntu 18.04 with a full root fs boots into a state where systemd
messages are visible on screen, no graphical environment, no response to
keyboard, no possibility to switch VTs. It still reacts to ACPI power
switch, shutting down.

The startup process should be configured in a way that would allow back
off from full fs situations.

This is critical as any user is allowed to fill the root fs as long as home is 
inside the root fs.
 
That can easily happen accidentally, eg. by download tools not removing 
interrupted downloads for later resuming them. Those would exit when the disk 
is full but leave the file in place. If shutdown is still working (which it is 
under some circumstances I've tested) this leads to a full disk at boot 
scenario, braking the whole system just by legitimate user operations.

Test procedure:
Open terminal.
Run
cat /dev/zero >zeroes

Wait until disk full.
Reboot by UI buttons.

What should happen:
System boots into a intermediate state where the problem is clearly mentioned 
and there is some back off. Ideally it should run the graphical desktop and 
notify the user to delete some files or present a tool to do so. If not 
possible, it could exit to a emergency root console showing some explanation 
what happened and what can be done about now.
System could also provide a small emergency reservation file, which it can 
automatically remove on boot if running out of disk space and notifiy the user 
about.

What happens:
System boots to an almost completely unresponsive state (keyboard locked).


Also it seems the Guest accounts can be used to fill up the disk either, so 
this could be used for denial of service, breaking a users machine without 
having login access.

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

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

Title:
  Ubuntu 18.04 won't boot on full disk

Status in systemd package in Ubuntu:
  New

Bug description:
  The basic systemd configuration is not tolerating a full root fs.

  Ubuntu 18.04 with a full root fs boots into a state where systemd
  messages are visible on screen, no graphical environment, no response
  to keyboard, no possibility to switch VTs. It still reacts to ACPI
  power switch, shutting down.

  The startup process should be configured in a way that would allow
  back off from full fs situations.

  This is critical as any user is allowed to fill the root fs as long as home 
is inside the root fs.
   
  That can easily happen accidentally, eg. by download tools not removing 
interrupted downloads for later resuming them. Those would exit when the disk 
is full but leave the file in place. If shutdown is still working (which it is 
under some circumstances I've tested) this leads to a full disk at boot 
scenario, braking the whole system just by legitimate user operations.

  Test procedure:
  Open terminal.
  Run
  cat /dev/zero >zeroes

  Wait until disk full.
  Reboot by UI buttons.

  What should happen:
  System boots into a intermediate state where the problem is clearly mentioned 
and there is some back off. Ideally it should run the graphical desktop and 
notify the user to delete some files or present a tool to do so. If not 
possible, it could exit to a emergency root console showing some explanation 
what happened and what can be done about now.
  System could also provide a small emergency reservation file, which it can 
automatically remove on boot if running out of disk space and notifiy the user 
about.

  What happens:
  System boots to an almost completely unresponsive state (keyboard locked).

  
  Also it seems the Guest accounts can be used to fill up the disk either, so 
this could be used for denial of service, breaking a users machine without 
having login access.

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

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

[Touch-packages] [Bug 1752737] Re: [2.3.0-6434] mDNS observer problems

2018-08-17 Thread Andres Rodriguez

** Changed in: maas/2.4
Milestone: 2.4.2 => 2.4.3

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

Title:
  [2.3.0-6434] mDNS observer problems

Status in Avahi:
  Unknown
Status in MAAS:
  Triaged
Status in MAAS 2.4 series:
  Triaged
Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  I see avahi-browser choking on non-utf8 characters in my rackd.log:

  ==> rackd.log <==
  2018-02-28 16:54:33 provisioningserver.utils.services: [info] mDNS 
observation process started.
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
Traceback (most recent call last):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 87, in 
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
main()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 83, in main
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
run()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 52, in run
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
from provisioningserver.__main__ import main
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/__main__.py", line 55, 
in 
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
main()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line 
91, in __call__
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
self.execute(argv)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line 
86, in execute
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
args.handler.run(args)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
221, in run
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
_observe_mdns(reader, output, args.verbose)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
145, in _observe_mdns
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in observer(events):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
161, in _observe_resolver_found
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in filter(_p_resolver_found, events):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
125, in _extract_mdns_events
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in map(parse_avahi_event, lines):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
(result, consumed) = self._buffer_decode(data, self.errors, final)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc8 in position 240: 
invalid continuation byte
  2018-02-28 16:54:36 provisioningserver.utils.services: [critical] mDNS 
observation process failed.

  Traceback (most recent call last):
  Failure: twisted.internet.error.ProcessTerminated: A process has ended with a 
probable error condition: process ended with exit code 1.

  ==> regiond.log <==
  2018-02-28 16:54:50 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK 
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
  2018-02-28 16:55:20 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK 
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)

  ==> maas.log <==
  Feb 28 16:53:52 MAAS-RC01 maas.interface: [info] ens33 (physical) on 
MAAS-RC01: New MAC, IP binding observed: 08:eb:74:ca:d3:6f, 192.168.1.82

  Similar traceback when running from command line:

  maasuser@MAAS-RC01:~$ maas-rack observe-mdns
  {"hostname": "Apple-TV", "interface": "ens33", "address": "192.168.1.81"}
  Got SIGTERM, quitting.
  Traceback (most recent call last):
File "/usr/sbin/maas-rack", line 87, in 
  main()
File "/usr/sbin/maas-rack

[Touch-packages] [Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

2018-08-17 Thread BSA

Not worked for me. System was upgraded from Xenial to Bionic. Previously was 
unity desktop, now is gnome3.
Text editor never clears background.
I try to remove ~/.xinputrc and relogin, but nothing changed.

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

Title:
  gedit edit window  is transparent when using Ambiance and Radiance
  themes

Status in gedit package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Expired

Bug description:
  In a freshly booted and fully updated Ubuntu 16.10 the edit window of
  gedit is transparent using the *Classic* colour scheme. Other colour
  schemes seem to work as intended.

  The text of loaded files shows against the desktop wallpaper but when
  no files are loaded gedit displays its edit window or pane as it
  should do.

  To clarify this bug is only apparent when a file is loaded.

  I don't know when this started as I don't normally used gedit to edit
  files. I haven't found any other application affected by this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gedit 3.20.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  6 21:01:35 2016
  InstallationDate: Installed on 2016-03-11 (179 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1619307] Re: Switching to USB sound device stops USB mouse clicks from registering Edit

2018-08-17 Thread Leônidas

Hello, I noticed that this thread is closed. How to re-enable it?

I'm experiencing the exact same problem using a Jabra Evolve 65. When
using the usb bluetooth dongle every time a sound is reproduced the
mouse stops clicking.

When i'm using the Jabra USB cable instead, it works correclty

Ubuntu 16.04

thank you!

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

Title:
  Switching to USB sound device stops USB mouse clicks from registering
  Edit

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a JABRA Evolve 80 headset with the 3.5mm plugged into the JABRA
  Evolve 80 Link UC. Once I plug the JABRA Evolve Link UC USB into my
  computer, the mouse pointer is somehow "captured" by the last active
  window. I can switch windows via alt-tab but left clicks in the new
  window still won't work, they will only work in the "old" window.

  WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the 
following:
  Section "InputClass"
   Identifier "Jabra"
  MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS"
   Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0"
  EndSection

  and restart xorg-server.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Sep  1 14:47:55 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535]
  MachineType: Dell Inc. Latitude E6530
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0JC5MT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Sep  1 11:27:32 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 812
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1228079] Re: Login issue: Lightdm + LDAP + Kerberos

2018-08-17 Thread jim koehler

** Changed in: lightdm (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Login issue: Lightdm + LDAP + Kerberos

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  lightdm 1.7.15-0ubuntu1, Ubuntu 13.10

  - Local users can login without problems on command line and LightDM
  - Kerberos/LDAP authenticated users can login on command line

  - Kerberos/LDAP authenticated users cannot login with LigthDM. If you
  provide a valid user/password the screen gets blank before you return
  to the login screen. The .xession-errors includes "/usr/sbin/lightdm-
  session: 5: exec: init: not found"

  - If you add init to the users path (e.g., ln -s /sbin/init /bin/init)
  the user does no longer return back to LightDM but gets a blank
  screen. Several errors related to "init" in the .xsession-errors.
  First of them is "init: Failed to spawn upstart-file-bridge main
  process: unable to execute: No such file or directory"

  .xession-errors for both setup attached to this bug report

  No problems with Ubuntu 12.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.15-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  Date: Fri Sep 20 12:21:13 2013
  InstallationDate: Installed on 2013-09-20 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2018-08-17 Thread DaMoisture

Thanks Egor! Connection stayed up all day!!

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1619307] Re: Switching to USB sound device stops USB mouse clicks from registering Edit

2018-08-17 Thread Christopher M. Penalver

Leônidas (leonidasklein), it is most helpful if you use the computer the 
problem is reproducible with and file a new report with Ubuntu, by first 
ensuring the package xdiagnose is installed, and click the Yes button for 
attaching additional debugging information after running the following from a 
terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

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

Title:
  Switching to USB sound device stops USB mouse clicks from registering
  Edit

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a JABRA Evolve 80 headset with the 3.5mm plugged into the JABRA
  Evolve 80 Link UC. Once I plug the JABRA Evolve Link UC USB into my
  computer, the mouse pointer is somehow "captured" by the last active
  window. I can switch windows via alt-tab but left clicks in the new
  window still won't work, they will only work in the "old" window.

  WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the 
following:
  Section "InputClass"
   Identifier "Jabra"
  MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS"
   Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0"
  EndSection

  and restart xorg-server.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Sep  1 14:47:55 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535]
  MachineType: Dell Inc. Latitude E6530
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0JC5MT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Sep  1 11:27:32 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 812
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1787613] [NEW] after fresh install again broken dependencies

2018-08-17 Thread vollmanr

Public bug reported:

the built-in screen does not work properly (since 8 months, after an
update of 16.04LTS). The interesting message is:

The following packages have unmet dependencies:
 xserver-xorg-video-intel : Depends: xorg-video-abi-20
Depends: xserver-xorg-core (>= 2:1.17.99.902)
E: Unable to correct problems, you have held broken packages.


LAPTOP IDEAPAD 15IBD

external monitor works fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Aug 17 17:41:02 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:382a]
InstallationDate: Installed on 2018-08-15 (2 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: LENOVO INVALID
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=4b7dd599-0b13-489a-9717-7b9cf1555ea0 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/30/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN11WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: VIUU4
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: INVALID
dmi.modalias: 
dmi:bvnLENOVO:bvrE0CN11WW:bd06/30/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNODPK:cvnLENOVO:ct10:cvrINVALID:
dmi.product.family: IDEAPAD
dmi.product.name: INVALID
dmi.product.version: INVALID
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: Fri Aug 17 16:08:28 2018
xserver.configfile: default
xserver.errors:
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: modeset

** 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/1787613

Title:
  after fresh install again broken dependencies

Status in xorg package in Ubuntu:
  New

Bug description:
  the built-in screen does not work properly (since 8 months, after an
  update of 16.04LTS). The interesting message is:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-20
  Depends: xserver-xorg-core (>= 2:1.17.99.902)
  E: Unable to correct problems, you have held broken packages.

  
  LAPTOP IDEAPAD 15IBD

  external monitor works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Aug 17 17:41:02 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:382a]
  InstallationDate: Installed on 2018-08-15 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

2018-08-17 Thread Keith

Same issue - only latest Ubunutu updates and OS (GUI based) as of today.
Did following:

> rm /etc/initramfs-tools/conf.d/resume
> sudo update-initramfs -u

Resume file is gone and issue still happens. Please help with any other
solutions to this issue.

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1783571] Re: Set Yaru as default

2018-08-17 Thread Iain Lane

OK, I think I got everything. We talked with Khurshid on IRC and an MP
should be coming - please someone from ~ubuntu-desktop upload that when
it arrives. (Feel free to ping on IRC if necessary.)

** Tags removed: block-proposed

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

Title:
  Set Yaru as default

Status in gnome-session package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-settings package in Ubuntu:
  In Progress
Status in ubuntu-sounds package in Ubuntu:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Won't Fix
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Set Yaru as default ubuntu 18.10 theme.

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

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

[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

2018-08-17 Thread Dylan

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

"After pulling my hair for several days, I found this:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842

/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf has the
following content:

[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:wwan

Removing the file and restarting NetworkManager did the trick."



This worked for me.  Thank you so much.

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Touch-packages] [Bug 1783571] Re: Set Yaru as default

This bug was fixed in the package ubuntu-settings - 18.10.1

---
ubuntu-settings (18.10.1) cosmic; urgency=medium

  [ Iain Lane ]
  * Work around meson bug #3914 by creating the symlink in packaging instead
of using the upstream build system. This change should be reverted once
that bug is fixed.

  [ Didier Roche ]
  * Set Suru theme and settings as default. (LP: #1783571)

 -- Iain Lane   Fri, 17 Aug 2018 12:39:12 +0100

** Changed in: ubuntu-settings (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: gnome-shell (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 ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1783571

Title:
  Set Yaru as default

Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-sounds package in Ubuntu:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Won't Fix
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Set Yaru as default ubuntu 18.10 theme.

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

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

[Touch-packages] [Bug 1783571] Re: Set Yaru as default

This bug was fixed in the package gnome-shell - 3.29.90-2ubuntu1

---
gnome-shell (3.29.90-2ubuntu1) cosmic; urgency=medium

  * Merge with debian, remaining changes
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ 50_add_ubuntu_desktop_detect.patch
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ 71_smarter_alt_tab.patch
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ ubuntu-lightdm-user-switching.patch
  - Allow user switching when using LightDM.
+ ubuntu_lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu_gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu_background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu_gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ ubuntu_block_mode_extension_update.patch
  - Don't allow ubuntu mode extension to update
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch
  - Fix possible crash on cache loading
+ js-ui-Choose-some-actors-to-cache-on-the-GPU.patch
  - Improve rendering of shell elements moving rendering to GPU
+ debian/rules:
  - Run dh_translations and work around an issue with Rosetta and plural
translations
  - Run dh_install with fail-missing
  * d/p/ubuntu_background_login.patch,
d/p/ubuntu_block_mode_extension_update.patch,
d/p/50_add_ubuntu_desktop_detect.patch,
d/p/ubuntu_gdm.patch,
d/p/ubuntu_gdm_alternatives.patch,
d/p/ubuntu-lightdm-user-switching.patch,
d/p/ubuntu_lock_on_suspend.patch,
d/p/71_smarter_alt_tab.patch:
- Using Gbp-Pq Topic to ubuntu (so they get moved to debian/patches/ubuntu)
  * d/p/main-show-a-critical-message-on-gnome-shell-crash.patch,
d/p/global-make-possible-to-set-debug-flags-dynamically.patch,
d/p/main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
d/p/main-add-backtrace-crashes-all-and-backtrace-all.patch,
d/p/sessionMode-add-support-for-debugFlags-parameter.patch:
- Allow to get better debug informations on crashes, and in case interactive
  user informations
  * d/p/st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
d/p/st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
- Handle NULL scroll bars in st-scroll-view (LP: #1725312)
  * d/p/js-main-Throw-error-if-no-valid-default-stylesheet-is-fou.patch:
- Be informative if gnome-shell tries to load an invalid default theme
  * debian/ubuntu-session-mods/ubuntu.json:
- Enable JS stacktrace printing on gnome-shell crashes using debugFlags

  [ Didier Roche ]
  * Remove ubuntu.css and related assets:
- Don't install them anymore, as we rely on Yaru as our default theme.
- Remove older alternative on upgrades to this version and removals.
  * Set Yaru theme as default for the ubuntu mod (LP: #1783571)
  * Set default gdm theme as upstream GDM. Will be overriden in the Yaru
package.

  [ Iain Lane ]
  * debian/control{,.in}: Make gnome-shell-common Recommend
yaru-theme-gnome-shell, since we reference its css file in our
styleSheetName.

gnome-shell (3.29.90-2) experimental; urgency=medium

  * Team upload
  * Build-depend on GLib 2.57.2 for the new approach to overriding
GSettings per desktop
  * d/p/Update-Brazilian-Portuguese-translation.patch,
d/p/showOSD-Fix-handling-of-defined-falsy-parameters.patch,
d/p/data-Fix-comment-in-schema.patch,
d/p/workspace-Fix-infinite-loop-when-finding-parent-window-of.patch,
d/p/workspace-Simplify-detecting-added-dialogs-after-closing-.patch,
d/p/tools-fix-XDG-desktop-syntax-in-gnome-shell-overrides-mig.patch,
d/p/Updated-Slovenian-translation.patch

[Touch-packages] [Bug 1782190] Re: Set default interface font size to 11 for communitheme sessions

This bug was fixed in the package ubuntu-settings - 18.10.1

---
ubuntu-settings (18.10.1) cosmic; urgency=medium

  [ Iain Lane ]
  * Work around meson bug #3914 by creating the symlink in packaging instead
of using the upstream build system. This change should be reverted once
that bug is fixed.

  [ Didier Roche ]
  * Set Suru theme and settings as default. (LP: #1783571)

 -- Iain Lane   Fri, 17 Aug 2018 12:39:12 +0100

** Changed in: ubuntu-settings (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Set default interface font size to 11 for communitheme sessions

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * communitheme snap users see the gnome shell overview window
  thumbnail labels cutted off

   * 18.04 users can install the communitheme snap from within gnome-
  software

   * To fix this the default font size of the interface needs to be
  switched to 11 (again)

  [Test Case]

   * Install ubuntu

   * install the communitheme snap

   * reboot

   * select the communitheme snap session and login

   * Open "activities" by clicking "activities" in the GNOME shell's
  upper left corner or by pressing the super/ubuntu/windows key

   * Each window thumbnail is labeled with a text which is now cut

   * This is caused by a bug in gnome-shell which can't handle any other
  font size than 11 for any other font beside cantarell

  * install the new ubuntu-settings version

  * open again activities

  * check that window thumbnails aren't cut anymore

  [Regression Potential]

   * It's affecting only the communitheme session, not available by
  default and reverting to the same default than ubuntu main session

  [Other Info]

   * Gitlab upstream issue: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/378

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

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

[Touch-packages] [Bug 1783571] Re: Set Yaru as default

This bug was fixed in the package gnome-session - 3.29.90-1ubuntu1

---
gnome-session (3.29.90-1ubuntu1) cosmic; urgency=medium

  * Merge with debian, remaining changes:
- debian/control.in:
  + Recommend session-migration
  + Move xwayland dependency to gnome-session and make gnome-session
Arch: any
  + Split gnome-startup-applications to a separate binary package so
that it can be uninstalled without breaking the system
  + Add unity-session
- Split ubuntu-session out of gnome-session.
- Add upstart user session and systemd user session:
  debian/data, debian/gnome-session-bin.user-session.upstart
- debian/gnome-session-bin.postinst, debian/gnome-session-bin.prerm:
   Moved registering gnome-session binary as a session manager to
   gnome-session-bin package
- Add gnome-session-wayland transitional package
- don't install gnome-mimeapps.list (installed by desktop-file-utils in
  Ubuntu):
  debian/gnome-session-common.dirs, gnome-session-common.install,
  gnome-session-common.maintscript, gnome-session-common.postinst
- debian/patches/103_kill_the_fail_whale.patch:
  + Kill the Fail Whale as it tends to be more annoying than helpful
- debian/patches/22_support_autostart_delay.patch:
  + Bugzilla patch to support adding a delay to autostart apps, using
a "X-GNOME-Autostart-Delay" key in the desktop file
- debian/patches/50_ubuntu_sessions.patch:
  + Add ubuntu session tweaks
- debian/patches/51_remove_session_saving_from_gui.patch:
  + Add GNOME_SESSION_SAVE environment variable for people wanting to
use the save session still, knowing that it can break your system
if used unwisely
- debian/patches/53_add_sessionmigration.patch:
  + launch session-migration if present at the start of the session.
This sync tool runns different session migration scripts that can be
provided in various desktop packages.
- debian/patches/95_dbus_request_shutdown.patch:
  + Add "RequestShutdown" and "RequestReboot" DBus methods to allow
other applications to shutdown or reboot the machine via the session
manager.
- debian/patches/ignore_gsettings_region.patch:
  + Ignore the "region" gsettings value - users' setting of LC_*
variables saved in ~/.pam_environment.
- debian/patches/revert_remove_gnome_session_properties.patch:
  + Don't merge translations into gnome-session-properties.desktop
  * debian/patches/50_ubuntu_sessions.patch:
- moved to debian/patches/ubuntu/ubuntu-sessions.patch (using gbp topic)

  [ Didier Roche ]
  * Remove gnome-themes-extra and gtk2-engines-pixbuf Recommends.
Those are pulled by the themes as needed.
  * ubuntu-session now depends on yaru-theme-gnome-shell, as the mod
refers to it. (LP: #1783571)

gnome-session (3.29.90-1) experimental; urgency=medium

  * New upstream revision
  * debian/*: Update for experimental (3.29/3.30 series)
  * 
debian/patches/debian/Revert-main-Remove-GNOME_DESKTOP_SESSION_ID-envvar.patch:
- revert removal of GNOME_DESKTOP_SESSION_ID not to break apps using it

gnome-session (3.28.1-1) unstable; urgency=medium

  * New upstream release
  * Drop patch included in new release

 -- Marco Trevisan (Treviño)   Fri, 17 Aug 2018
03:12:08 +0200

** Changed in: gnome-session (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 ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1783571

Title:
  Set Yaru as default

Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-sounds package in Ubuntu:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Won't Fix
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Set Yaru as default ubuntu 18.10 theme.

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

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

[Touch-packages] [Bug 269541] Re: gconfd-2 becomes orphane when parent process crashes

** Changed in: gconf
   Status: New => Won't Fix

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

Title:
  gconfd-2 becomes orphane when parent process crashes

Status in gconf:
  Won't Fix
Status in gconf package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gconf2

  When using a thin client kind of way (Nomachine NX or LTSP), it stays
  running when the connection crashes for some reason or when
  terminating the session on the serverside. gnome-session gets killed
  correctly, but gconfd stays running. It won't detect that the gnome-
  session isn't running anymore.

  I expected the process to detect when the parent dies, the process
  itself will close.

  Process: /usr/lib/libgconf2-4/gconfd-2
  Ubuntu release: Description:Ubuntu 8.04.1
  Release:8.04
  Package:
  gconf2:
Installed: 2.22.0-0ubuntu3
Candidate: 2.22.0-0ubuntu3
Version table:
   *** 2.22.0-0ubuntu3 0
  500 http://nl.archive.ubuntu.com hardy/main Packages
  100 /var/lib/dpkg/status

  process list (1000 is here a user id):
  # ps aux | grep 1000
  1000 29763  0.0  0.0  35596  5796 ?S20:00   0:00 
/usr/lib/libgconf2-4/gconfd-2 5
  root 30857  0.0  0.0   5164   848 pts/0S+   20:12   0:00 grep 1000

  strace log:
  restart_syscall(<... resuming interrupted call ...>) = 0
  poll([{fd=7, events=POLLIN}, {fd=9, events=POLLIN|POLLPRI}, {fd=11, 
events=POLLIN|POLLPRI}], 3, 15) = 0
  poll([{fd=7, events=POLLIN}, {fd=9, events=POLLIN|POLLPRI}, {fd=11, 
events=POLLIN|POLLPRI}], 3, 0) = 0
  poll([{fd=7, events=POLLIN}, {fd=9, events=POLLIN|POLLPRI}, {fd=11, 
events=POLLIN|POLLPRI}], 3, 692) = 0
  poll([{fd=7, events=POLLIN}, {fd=9, events=POLLIN|POLLPRI}, {fd=11, 
events=POLLIN|POLLPRI}], 3, 0) = 0
  poll([{fd=7, events=POLLIN}, {fd=9, events=POLLIN|POLLPRI}, {fd=11, 
events=POLLIN|POLLPRI}], 3, 29307) = 0
  poll([{fd=7, events=POLLIN}, {fd=9, events=POLLIN|POLLPRI}, {fd=11, 
events=POLLIN|POLLPRI}], 3, 3) = 0
  poll([{fd=7, events=POLLIN}, {fd=9, events=POLLIN|POLLPRI}, {fd=11, 
events=POLLIN|POLLPRI}], 3, 3) = 0
  poll([{fd=7, events=POLLIN}, {fd=9, events=POLLIN|POLLPRI}, {fd=11, 
events=POLLIN|POLLPRI}], 3, 0) = 0
  

  Workaround: running `gconftool-2 --shutdown` as the owner of the
  gconfd-2 process, will close it though. But the process needs to close
  by itself.

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

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

[Touch-packages] [Bug 1756755] Re: package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-08-17 Thread Steve McConnel

system had been upgraded from trusty to xenial in the past

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

Title:
  package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed
  systemd-shim package post-removal script subprocess returned error
  exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from xenial to bionic failed the removal of systemd-shim.
  I think the messages were the same as the following, that I can reproduce by 
running "apt upgrade" from the upgraded system:

  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Mar 18 22:52:00 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-01-11 (1892 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed 
systemd-shim package post-removal script subprocess returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-03-18 (0 days ago)

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

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

[Touch-packages] [Bug 1268543] Re: CVE-2013-5211 ntp DDos

** Changed in: ntp (Debian)
   Status: New => Fix Released

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

Title:
  CVE-2013-5211 ntp DDos

Status in ntp package in Ubuntu:
  Won't Fix
Status in ntp package in Debian:
  Fix Released

Bug description:
  The monlist feature in ntp_request.c in ntpd in NTP before 4.2.7p26
  allows remote attackers to cause a denial of service (traffic
  amplification) via forged (1) REQ_MON_GETLIST or (2) REQ_MON_GETLIST_1
  requests, as exploited in the wild in December 2013.

  http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-5211

  http://bugs.ntp.org/show_bug.cgi?id=1532

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

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

[Touch-packages] [Bug 1787641] [NEW] package keyboard-configuration 1.108ubuntu15.4 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 10

2018-08-17 Thread Alexandr

Public bug reported:

error when booting the operating system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: keyboard-configuration 1.108ubuntu15.4
ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
Uname: Linux 4.4.0-133-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Aug 17 22:49:58 2018
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 10
InstallationDate: Installed on 2018-08-17 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
SourcePackage: console-setup
Title: package keyboard-configuration 1.108ubuntu15.4 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package keyboard-configuration 1.108ubuntu15.4 failed to
  install/upgrade: подпроцесс установлен сценарий post-installation
  возвратил код ошибки 10

Status in console-setup package in Ubuntu:
  New

Bug description:
  error when booting the operating system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: keyboard-configuration 1.108ubuntu15.4
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  Uname: Linux 4.4.0-133-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Aug 17 22:49:58 2018
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 10
  InstallationDate: Installed on 2018-08-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.108ubuntu15.4 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1761971] Re: ps2 keyboard not working after upgrade 16.04 -> 18.04

2018-08-17 Thread Philippe Coval

Any clues since 1st report ? I am also affected and will investigate as
I am able to reproduce using xinit.


** Bug watch added: freedesktop.org Bugzilla #103561
   https://bugs.freedesktop.org/show_bug.cgi?id=103561

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

Title:
  ps2 keyboard not working after upgrade 16.04 -> 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  the problem seems to be related to xorg

  Symptomes: no key works in xorg but the device 
  /dev/input/event2 is there and works according to evtest

  The keyboard works during startup and in the text consoles.

  "solution": I am now using a second usb keyboard 
  (/dev/input/event4 on my machine)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Apr  7 12:48:36 2018
  DistUpgraded: 2018-04-07 09:51:42,601 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.8, 4.10.0-42-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1494]
  InstallationDate: Installed on 2017-12-27 (100 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite CMT PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=aabc1b46-62b2-4910-870e-ff827d8783dd ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-04-07 (0 days ago)
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.15
  dmi.board.asset.tag: CZC2250RZC
  dmi.board.name: 1494
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC2250RZC
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:svnHewlett-Packard:pnHPCompaq8200EliteCMTPC:pvr:rvnHewlett-Packard:rn1494:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq 8200 Elite CMT PC
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Apr  7 12:35:27 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu3
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1761971] Re: ps2 keyboard not working after upgrade 16.04 -> 18.04

2018-08-17 Thread Philippe Coval

Workaound :

rmmod hp_wmi


https://bugs.freedesktop.org/show_bug.cgi?id=103561

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

Title:
  ps2 keyboard not working after upgrade 16.04 -> 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  the problem seems to be related to xorg

  Symptomes: no key works in xorg but the device 
  /dev/input/event2 is there and works according to evtest

  The keyboard works during startup and in the text consoles.

  "solution": I am now using a second usb keyboard 
  (/dev/input/event4 on my machine)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Apr  7 12:48:36 2018
  DistUpgraded: 2018-04-07 09:51:42,601 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.8, 4.10.0-42-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1494]
  InstallationDate: Installed on 2017-12-27 (100 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite CMT PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=aabc1b46-62b2-4910-870e-ff827d8783dd ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-04-07 (0 days ago)
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.15
  dmi.board.asset.tag: CZC2250RZC
  dmi.board.name: 1494
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC2250RZC
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:svnHewlett-Packard:pnHPCompaq8200EliteCMTPC:pvr:rvnHewlett-Packard:rn1494:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq 8200 Elite CMT PC
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Apr  7 12:35:27 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu3
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1385903] Re: imagemagick crashes with "stack smashing detected"

2018-08-17 Thread Steve Beattie

Hi,

Thanks for preparing the debiff. However, this issue was addressed in
the interim in USN 3706-1 http://www.ubuntu.com/usn/usn-3706-1 (libjpeg-
turbo 1.3.0-0ubuntu2.1) for trusty.

Thanks again.

** Changed in: libjpeg-turbo (Ubuntu Trusty)
   Status: Confirmed => Fix Released

** Changed in: libjpeg-turbo (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  imagemagick crashes with "stack smashing detected"

Status in libjpeg-turbo package in Ubuntu:
  Fix Released
Status in libjpeg-turbo source package in Precise:
  Won't Fix
Status in libjpeg-turbo source package in Trusty:
  Fix Released
Status in libjpeg-turbo source package in Utopic:
  Won't Fix
Status in libjpeg-turbo source package in Vivid:
  Won't Fix

Bug description:
  Every now and then imagemagick convert crashes like this:

  $ convert -rotate 270 003632r270.jpg koe.jpg
  *** stack smashing detected ***: convert terminated
  Aborted (core dumped)

  This is perfectly reproducible and happens in every Ubuntu 14.04 box
  I have at hand that has ImageMagick in it, but not in 12.04.
  I'll attach the file used in above example (I have several more
  in case someone wants them).
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tt 2149 F pulseaudio
  CurrentDesktop: LXDE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  IwConfig:
   br0   no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/09/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GM
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1787474] Re: pygobject fails to build in Ubuntu 18.10

2018-08-17 Thread Christoph Reiter

I think this is https://gitlab.gnome.org/GNOME/gobject-
introspection/commit/1f5c81048d762f4866137e1e3221d85b9b611d8b which
isn't in a release yet. I'll ask for a release.

I also noticed that the pygobject test suite fails due to sys.excepthook
== apport_excepthook, I'll look into that.

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

Title:
  pygobject fails to build in Ubuntu 18.10

Status in pygobject package in Ubuntu:
  New

Bug description:
  pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.

  pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS.
  3.29.2-1 does build successfully in Debian unstable.

  I confirmed that the problem is reproducible in a local sbuild. I
  confirm that the test hang also happens with python 3.7.

  By the way, I had to manually cancel the builds since they were still
  hanging after 20 hours.

  Build log
  -
  https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898

  Build log excerpt
  -

  I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build; 
python2.7 -m pytest tests
  = test session starts 
==
  platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
  rootdir: /<>, inifile:
  collected 1374 items

  tests/test_atoms.py ...  [  
0%]
  tests/test_cairo.py .[  
2%]
  tests/test_docstring.py ...x.[  
3%]
  tests/test_error.py ...  [  
4%]
  tests/test_everything.py Trace/breakpoint trap (core dumped)
  E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd 
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
  make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:22: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes 
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
  Scanning for processes to kill in build PACKAGEBUILD-15263898
  Build killed with signal TERM after 150 minutes of inactivity

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

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

[Touch-packages] [Bug 1787474] Re: pygobject fails to build in Ubuntu 18.10

2018-08-17 Thread Christoph Reiter

We do test against gnome master now with gitlab-CI, so hopefully this
will be noticed earlier in future releases.

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

Title:
  pygobject fails to build in Ubuntu 18.10

Status in pygobject package in Ubuntu:
  New

Bug description:
  pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.

  pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS.
  3.29.2-1 does build successfully in Debian unstable.

  I confirmed that the problem is reproducible in a local sbuild. I
  confirm that the test hang also happens with python 3.7.

  By the way, I had to manually cancel the builds since they were still
  hanging after 20 hours.

  Build log
  -
  https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898

  Build log excerpt
  -

  I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build; 
python2.7 -m pytest tests
  = test session starts 
==
  platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
  rootdir: /<>, inifile:
  collected 1374 items

  tests/test_atoms.py ...  [  
0%]
  tests/test_cairo.py .[  
2%]
  tests/test_docstring.py ...x.[  
3%]
  tests/test_error.py ...  [  
4%]
  tests/test_everything.py Trace/breakpoint trap (core dumped)
  E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd 
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
  make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:22: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes 
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
  Scanning for processes to kill in build PACKAGEBUILD-15263898
  Build killed with signal TERM after 150 minutes of inactivity

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

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

[Touch-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled

2018-08-17 Thread Brian Murray

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

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

Title:
  LibreOffice crashed but apport didn't log a crash file in /var/crash
  despite being enabled

Status in apport package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  What is expected to happen is when LibreOffice crashes, a crash report
  is created in the /var/crash folder.

  What happened instead is LibreOffice crashed but apport didn't create
  a crash file in the /var/crash folder, despite running and being
  enabled. Apport creating crash files in /var/crash used to happen in
  Xenial, and in prior releases. Other programs that crash are picked up
  by apport so appears LO+apport issue.

  LibreOffice has reference to placing crash files as per:
  cat /etc/libreoffice/sofficerc | grep crash
  CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash

  I don't have any 3rd party LO plugins installed.

  apt-show-versions -r libreoffice*
  libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-avmedia-backend-gstreamer:i386 not installed
  libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-base-core:i386 not installed
  libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-calc:i386 not installed
  libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-core:i386 not installed
  libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-dev:i386 not installed
  libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-draw:i386 not installed
  libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gnome:i386 not installed
  libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-gtk:i386 not installed
  libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
  libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-impress:i386 not installed
  libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-math:i386 not installed
  libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-ogltrans:i386 not installed
  libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-pdfimport:i386 not installed
  libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
  libreoffice-writer:i386 not installed

  cat /etc/default/apport
  # set this to 0 to disable apport, or to 1 to enable it
  # you can temporarily override this with
  # sudo service apport start force_start=1
  enabled=1

  cat /etc/apport/crashdb.conf
  # map crash database names to CrashDatabase implementations and URLs

  default = 'ubuntu'

  def get_oem_project():
  '''Determine OEM project name from Distribution Channel Descriptor

  Return None if it cannot be determined or does not exist.
  '''
  try:
  dcd = open('/var/lib/ubuntu_dist_channel').read()
  if dcd.startswith('canonical-oem-'):
  return dcd.split('-')[2]
  except IOError:
  return None

  databases = {
  'ubuntu': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'dupdb_url': 
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
  'distro': 'ubuntu',
  'problem_types': ['Bug', 'Package'],
  'escalation_tag': 'bugpattern-needed',
  'escalated_tag': 'bugpattern-written',
  },
  'canonical-oem': {
  'impl': 'launchpad',
  'bug_pattern_url': 
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
  'project': get_oem_project(),
  },
  'debug': {
  # for debugging
  'impl': 'memory',
  'bug_pattern_url': '/tmp/bugpatterns.xml',
  'distro': 'debug'
  },
  }
  mo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.0.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 24 17:03:37 2016
  InstallationDate: Installed on 2015-12-18 (37 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-01-20 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun

[Touch-packages] [Bug 1787645] [NEW] Most, but not all, boots from cold, I get a Low Graphics Mode error

2018-08-17 Thread Roger Davis

Public bug reported:

After an update (kernel?), I have begun to receive the message "Running
in Low Graphics Mode" at boot. I can tell it to use Default setting from
the options it offers, and get by it, after which things look and work
normally until a reboot, which may or may not occur correctly.

If I select extra graphics debug messages and display boot messages in
Xdiagnose, this problem DOES NOT occur.  If I deselect those, the
problem begins again.

I don't know which update caused it, but it was somewhere around mid or
early May.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Aug 17 12:02:03 2018
DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.38, 4.15.0-30-generic, x86_64: installed
 virtualbox, 5.1.38, 4.15.0-32-generic, x86_64: installed
 virtualbox, 5.1.38, 4.4.0-133-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
InstallationDate: Installed on 2014-07-07 (1502 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro quiet plymouth:debug=1 
plymouth:debug=1=1=1=1=1 splash plymouth:debug=1=1=1=1=1=1=1=1=1 
plymouth:debug=1=1=1=1=1=1=1=1=1=1=1=1=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-12-18 (607 days ago)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
dmi.board.name: DZ77BH-55K
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39008-400
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
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: Fri Aug 17 12:00:19 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4~16.04.1

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


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

Title:
  Most, but not all, boots from cold, I get a Low Graphics Mode error

Status in xorg package in Ubuntu:
  New

Bug description:
  After an update (kernel?), I have begun to receive the message
  "Running in Low Graphics Mode" at boot. I can tell it to use Default
  setting from the options it offers, and get by it, after which things
  look and work normally until a reboot, which may or may not occur
  correctly.

  If I select extra graphics debug messages and display boot messages in
  Xdiagnose, this problem DOES NOT occur.  If I deselect those, the
  problem begins again.

  I don't know which update caused it, but it was somewhere around mid
  or early May.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Aug 17 12:02:03 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.38, 4.15.0-30-generic, x86_64: installed
   virtualbox, 5.1.38, 4.15.0-32-generi

[Touch-packages] [Bug 1787533] Re: package libcurl4-openssl-dev:amd64 7.58.0-2ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti

2018-08-17 Thread Seth Arnold

** Information type changed from Private Security to Public

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

Title:
  package libcurl4-openssl-dev:amd64 7.58.0-2ubuntu3.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in curl package in Ubuntu:
  New

Bug description:
  fdgfdgfdg

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libcurl4-openssl-dev:amd64 7.58.0-2ubuntu3.2
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   apt-transport-https:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Aug 13 18:21:57 2018
  DuplicateSignature:
   package:libcurl4-openssl-dev:amd64:7.58.0-2ubuntu3.2
   Setting up libharfbuzz-gobject0:amd64 (1.7.2-1ubuntu1) ...
   dpkg: error processing package libcurl4-openssl-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-08-13 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: curl
  Title: package libcurl4-openssl-dev:amd64 7.58.0-2ubuntu3.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1787533] Re: package libcurl4-openssl-dev:amd64 7.58.0-2ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti

2018-08-17 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 curl in Ubuntu.
https://bugs.launchpad.net/bugs/1787533

Title:
  package libcurl4-openssl-dev:amd64 7.58.0-2ubuntu3.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in curl package in Ubuntu:
  New

Bug description:
  fdgfdgfdg

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libcurl4-openssl-dev:amd64 7.58.0-2ubuntu3.2
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   apt-transport-https:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Aug 13 18:21:57 2018
  DuplicateSignature:
   package:libcurl4-openssl-dev:amd64:7.58.0-2ubuntu3.2
   Setting up libharfbuzz-gobject0:amd64 (1.7.2-1ubuntu1) ...
   dpkg: error processing package libcurl4-openssl-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-08-13 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: curl
  Title: package libcurl4-openssl-dev:amd64 7.58.0-2ubuntu3.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1787650] [NEW] package grilo-plugins-0.3-base 0.3.5-1ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-08-17 Thread John

Public bug reported:

I don't know what happened.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grilo-plugins-0.3-base 0.3.5-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Fri Aug 17 15:43:45 2018
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
InstallationDate: Installed on 2017-04-05 (499 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: grilo-plugins
Title: package grilo-plugins-0.3-base 0.3.5-1ubuntu1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: Upgraded to bionic on 2018-08-17 (0 days ago)

** Affects: grilo-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package grilo-plugins-0.3-base 0.3.5-1ubuntu1 failed to
  install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error
  exit status 2

Status in grilo-plugins package in Ubuntu:
  New

Bug description:
  I don't know what happened.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: grilo-plugins-0.3-base 0.3.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Aug 17 15:43:45 2018
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2017-04-05 (499 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: grilo-plugins
  Title: package grilo-plugins-0.3-base 0.3.5-1ubuntu1 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (0 days ago)

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

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

[Touch-packages] [Bug 1787651] [NEW] Mouse stop clicking Jabra

2018-08-17 Thread Leônidas

Public bug reported:

I'm experiencing a problem using a Jabra Evolve 65. When using the usb
bluetooth dongle every time a sound is reproduced the mouse stops
clicking.

When i'm using the Jabra USB cable instead, it works correclty

Ubuntu 16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-lowlatency 4.10.3
Uname: Linux 4.10.0-14-lowlatency x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Aug 17 17:32:38 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2245]
InstallationDate: Installed on 2016-04-24 (845 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20HES4KF02
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-lowlatency 
root=/dev/mapper/vg_ldt-lv_root ro resume=/dev/mapper/vg_ldt-lv_swap
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/10/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1QET68W (1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HES4KF02
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: 
dmi:bvnLENOVO:bvrN1QET68W(1.43):bd11/10/2017:svnLENOVO:pn20HES4KF02:pvrThinkPadT470:rvnLENOVO:rn20HES4KF02:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20HES4KF02
dmi.product.version: ThinkPad T470
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 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Aug 17 15:57:50 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4157 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

Title:
  Mouse stop clicking Jabra

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm experiencing a problem using a Jabra Evolve 65. When using the usb
  bluetooth dongle every time a sound is reproduced the mouse stops
  clicking.

  When i'm using the Jabra USB cable instead, it works correclty

  Ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-lowlatency 4.10.3
  Uname: Linux 4.10.0-14-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Aug 17 17:32:38 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2245]
  InstallationDate: Installed on 2016-04-24 (845 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20HES4KF02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-lowlatency 
root=/dev/mapper/vg_ldt-lv_root ro resume=/dev/mapper/vg_ldt-lv_swap
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HES4KF02
  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: 
dmi:

[Touch-packages] [Bug 1619307] Re: Switching to USB sound device stops USB mouse clicks from registering Edit

2018-08-17 Thread Leônidas

@penalvch I've reported the bug. please see it at
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1787651

Thank you!

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

Title:
  Switching to USB sound device stops USB mouse clicks from registering
  Edit

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a JABRA Evolve 80 headset with the 3.5mm plugged into the JABRA
  Evolve 80 Link UC. Once I plug the JABRA Evolve Link UC USB into my
  computer, the mouse pointer is somehow "captured" by the last active
  window. I can switch windows via alt-tab but left clicks in the new
  window still won't work, they will only work in the "old" window.

  WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the 
following:
  Section "InputClass"
   Identifier "Jabra"
  MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS"
   Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0"
  EndSection

  and restart xorg-server.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Sep  1 14:47:55 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535]
  MachineType: Dell Inc. Latitude E6530
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0JC5MT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Sep  1 11:27:32 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 812
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1048956] Re: Support converting from 's' to 'as' on the fly in migrations with gsettings-data-convert

** Changed in: gconf
   Status: New => Won't Fix

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

Title:
  Support converting from 's' to 'as' on the fly in migrations with
  gsettings-data-convert

Status in gconf:
  Won't Fix
Status in gconf package in Ubuntu:
  Fix Released

Bug description:
  Sometimes a simple gconf -> gsettings conversion is not enough. An
  example would be trying to convert
  /apps/metacity/window_keybindings/move_to_workspace_left to
  org.gnome.desktop.wm.keybindings's move-to-workspace-left.

  It'd be useful to try migrating as a string array instead in these
  cases.

  This affects getting bug #1046190 completely fixed.

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

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

[Touch-packages] [Bug 1761971] Re: ps2 keyboard not working after upgrade 16.04 -> 18.04

2018-08-17 Thread Philippe Coval

It was observed on:

Product: "HP Compaq 8200 Elite CMT PC"

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

Title:
  ps2 keyboard not working after upgrade 16.04 -> 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  the problem seems to be related to xorg

  Symptomes: no key works in xorg but the device 
  /dev/input/event2 is there and works according to evtest

  The keyboard works during startup and in the text consoles.

  "solution": I am now using a second usb keyboard 
  (/dev/input/event4 on my machine)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Apr  7 12:48:36 2018
  DistUpgraded: 2018-04-07 09:51:42,601 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.8, 4.10.0-42-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1494]
  InstallationDate: Installed on 2017-12-27 (100 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite CMT PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=aabc1b46-62b2-4910-870e-ff827d8783dd ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-04-07 (0 days ago)
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.15
  dmi.board.asset.tag: CZC2250RZC
  dmi.board.name: 1494
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC2250RZC
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:svnHewlett-Packard:pnHPCompaq8200EliteCMTPC:pvr:rvnHewlett-Packard:rn1494:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq 8200 Elite CMT PC
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Apr  7 12:35:27 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu3
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1787651] Re: Mouse stop clicking Jabra

2018-08-17 Thread Christopher M. Penalver

Leônidas, thank you for reporting this and helping make Ubuntu better.

1) To see if this is already resolved in Ubuntu, could you please test
this via http://cdimage.ubuntu.com/daily-live/current/ and advise to the
results?

2) To clarify, does the following provide a WORKAROUND:
 Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the following and 
restart xorg-server:
Section "InputClass"
 Identifier "Jabra"
MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS"
 Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0"
EndSection

** Tags added: bios-outdated-1.52

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

** Summary changed:

- Mouse stop clicking Jabra 
+ Mouse stops clicking using Jabra Evolve 65 via bluetooth

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

Title:
  Mouse stops clicking using Jabra Evolve 65 via bluetooth

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm experiencing a problem using a Jabra Evolve 65. When using the usb
  bluetooth dongle every time a sound is reproduced the mouse stops
  clicking.

  When i'm using the Jabra USB cable instead, it works correclty

  Ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-lowlatency 4.10.3
  Uname: Linux 4.10.0-14-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Aug 17 17:32:38 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2245]
  InstallationDate: Installed on 2016-04-24 (845 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20HES4KF02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-lowlatency 
root=/dev/mapper/vg_ldt-lv_root ro resume=/dev/mapper/vg_ldt-lv_swap
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HES4KF02
  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: 
dmi:bvnLENOVO:bvrN1QET68W(1.43):bd11/10/2017:svnLENOVO:pn20HES4KF02:pvrThinkPadT470:rvnLENOVO:rn20HES4KF02:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HES4KF02
  dmi.product.version: ThinkPad T470
  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 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Aug 17 15:57:50 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4157 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1787663] [NEW] package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess was killed by

2018-08-17 Thread Michael Dooley

Public bug reported:

After updating and upgrading system remotely earlier this morning, I
restarted ubuntu-mate bionic and apport wanted to report this. No idea
what is going on.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: keyboard-configuration 1.178ubuntu2.6
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 console-setup-linux:amd64: Install
 console-setup:amd64: Install
 keyboard-configuration:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Aug 17 11:55:36 2018
ErrorMessage: installed keyboard-configuration package post-installation script 
subprocess was killed by signal (Trace/breakpoint trap), core dumped
InstallationDate: Installed on 2018-05-03 (105 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: console-setup
Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: 
installed keyboard-configuration package post-installation script subprocess 
was killed by signal (Trace/breakpoint trap), core dumped
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package keyboard-configuration 1.178ubuntu2.6 failed to
  install/upgrade: installed keyboard-configuration package post-
  installation script subprocess was killed by signal (Trace/breakpoint
  trap), core dumped

Status in console-setup package in Ubuntu:
  New

Bug description:
  After updating and upgrading system remotely earlier this morning, I
  restarted ubuntu-mate bionic and apport wanted to report this. No idea
  what is going on.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu2.6
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   console-setup-linux:amd64: Install
   console-setup:amd64: Install
   keyboard-configuration:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Aug 17 11:55:36 2018
  ErrorMessage: installed keyboard-configuration package post-installation 
script subprocess was killed by signal (Trace/breakpoint trap), core dumped
  InstallationDate: Installed on 2018-05-03 (105 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.178ubuntu2.6 failed to 
install/upgrade: installed keyboard-configuration package post-installation 
script subprocess was killed by signal (Trace/breakpoint trap), core dumped
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1787663] Re: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess was killed by s

2018-08-17 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 console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1787663

Title:
  package keyboard-configuration 1.178ubuntu2.6 failed to
  install/upgrade: installed keyboard-configuration package post-
  installation script subprocess was killed by signal (Trace/breakpoint
  trap), core dumped

Status in console-setup package in Ubuntu:
  New

Bug description:
  After updating and upgrading system remotely earlier this morning, I
  restarted ubuntu-mate bionic and apport wanted to report this. No idea
  what is going on.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu2.6
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   console-setup-linux:amd64: Install
   console-setup:amd64: Install
   keyboard-configuration:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Aug 17 11:55:36 2018
  ErrorMessage: installed keyboard-configuration package post-installation 
script subprocess was killed by signal (Trace/breakpoint trap), core dumped
  InstallationDate: Installed on 2018-05-03 (105 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.178ubuntu2.6 failed to 
install/upgrade: installed keyboard-configuration package post-installation 
script subprocess was killed by signal (Trace/breakpoint trap), core dumped
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1787294] Re: ".ico" icon files are shown as random noise

2018-08-17 Thread Damiön la Bagh

Here is the Upstream Bug report

https://gitlab.gnome.org/GNOME/gtk/issues/1279

side note: When will Launchpad be updated with rich images and header
templates like the gitlab bug tracker?

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

Title:
  ".ico" icon files are shown as random noise

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Steps to reproduce
  Create an .ico file (for using the same icon between multiple platforms)
  create a desktop file linking to the ico file.

  here is an example of the one that doesn't work

  [Desktop Entry]
  Type=Application
  Version=0.9.4
  Name=ChromisPos
  Comment=Chromis Point of Sale
  Icon=/opt/chromispos/pos.ico
  Exec=/opt/chromispos/start.sh
  Terminal=false
  Path=/opt/chromispos

  gnome-shell (possibly dashtodock) displays this icon as a wash of
  noise. (see screenshot)

  In 16.04 the .ico works fine, and switching to Unity desktop also
  shows the .ico just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 00:29:47 2018
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2015-11-15 (1004 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago)

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

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

[Touch-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

2018-08-17 Thread xjbhenry

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

I encountered same problem, and I found the work around.

I believe this was because libglx from xorg over-written the one from
amd/nvidia.

For people using nvidia graphic cards, you can do:

sudo mv /usr/lib/xorg/modules/extensions/libglx.so 
/usr/lib/xorg/modules/extensions/libglx.so.bac
sudo ln -s /usr/lib/nvidia-396/xorg/libglx.so 
/usr/lib/xorg/modules/extensions/libglx.so
Then restart. 

I belive amd users can do the similar thing.

reference: https://devtalk.nvidia.com/default/topic/830711/linux/failed-
to-initialize-the-glx-module-please-check-in-your-x-log-file-that-the-
glx-module-has-been-lo/

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3V-A
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1787474] Re: pygobject fails to build in Ubuntu 18.10

2018-08-17 Thread Christoph Reiter

New 1.57.3 g-i tarball is out.

For the apport thing (I'm not sure if this is relevant in your build
environment):
https://gitlab.gnome.org/GNOME/pygobject/commit/d9ddad7bcac86d37a9010c8cd529a0e6ca1a9f48

PyGObject tests might still fail because of
https://gitlab.gnome.org/GNOME/glib/commit/0319dac01d64f9f95cf84c511a1679ba469e6cbb
-> needs a new glib release.

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

Title:
  pygobject fails to build in Ubuntu 18.10

Status in pygobject package in Ubuntu:
  New

Bug description:
  pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.

  pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS.
  3.29.2-1 does build successfully in Debian unstable.

  I confirmed that the problem is reproducible in a local sbuild. I
  confirm that the test hang also happens with python 3.7.

  By the way, I had to manually cancel the builds since they were still
  hanging after 20 hours.

  Build log
  -
  https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898

  Build log excerpt
  -

  I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build; 
python2.7 -m pytest tests
  = test session starts 
==
  platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
  rootdir: /<>, inifile:
  collected 1374 items

  tests/test_atoms.py ...  [  
0%]
  tests/test_cairo.py .[  
2%]
  tests/test_docstring.py ...x.[  
3%]
  tests/test_error.py ...  [  
4%]
  tests/test_everything.py Trace/breakpoint trap (core dumped)
  E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd 
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
  make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:22: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes 
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
  Scanning for processes to kill in build PACKAGEBUILD-15263898
  Build killed with signal TERM after 150 minutes of inactivity

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

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

[Touch-packages] [Bug 1787294] Re: ".ico" icon files are shown as random noise

2018-08-17 Thread Damiön la Bagh

Upstream moved the bug to gtk-pixbuf as they knew of some problems with
ico's in gdk-pixbuf

https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/86

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

Title:
  ".ico" icon files are shown as random noise

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Steps to reproduce
  Create an .ico file (for using the same icon between multiple platforms)
  create a desktop file linking to the ico file.

  here is an example of the one that doesn't work

  [Desktop Entry]
  Type=Application
  Version=0.9.4
  Name=ChromisPos
  Comment=Chromis Point of Sale
  Icon=/opt/chromispos/pos.ico
  Exec=/opt/chromispos/start.sh
  Terminal=false
  Path=/opt/chromispos

  gnome-shell (possibly dashtodock) displays this icon as a wash of
  noise. (see screenshot)

  In 16.04 the .ico works fine, and switching to Unity desktop also
  shows the .ico just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 00:29:47 2018
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2015-11-15 (1004 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago)

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

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

[Touch-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settin

2018-08-17 Thread Theo Linkspfeifer

xubuntu-desktop depends on lightdm-gtk-greeter, and yet while performing
the test case apt wants to pull in unity-greeter instead (see `apt
depends lightdm`). This will install various indicator- packages plus
gnome-control-center.

Explicitly installing the needed package gives the expected result:

sudo apt install xubuntu-desktop lightdm-gtk-greeter

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1787675] [NEW] package systemd-shim failed to install/during upgrade:to 18.04

2018-08-17 Thread Robert Parsons

Public bug reported:

I was running the software updater to install ubuntu 18.04, when I got the 
error message,
"Could not install systemd-shim."

I continued on with the install and got the message, "Could not install
"/var/cache/apt/...deb" package."

I continued on with the install and got the message "Could not install
upgrade."

I rebooted and it looks like it did upgrade most of the applications.

I ran the software updater and it tells me "Not all updates can be
installed" and that I have to run a partial install.  I do this and get
the message "Could not install 'systemd-shim'.  The upgrade has aborted.
Your system could be in an unusable state. A recovery will run now (dpkg
--configure -a)."

I tryed Synaptic and it tells me that systemd-shim is "Marked for
removal".  I try and Apply the change and get the error  message "E:
systemd-shim: installed systemd-shim package post-removal script
subprocess returned error exit status 2".

So how do I fix this so that I can finish the install?

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
Date: Fri Aug 17 12:16:55 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2010-05-12 (3018 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
UpgradeStatus: Upgraded to bionic on 2018-08-17 (0 days ago)

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


** Tags: apport-package bionic i386 third-party-packages

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

Title:
  package systemd-shim failed to install/during upgrade:to 18.04

Status in systemd package in Ubuntu:
  New

Bug description:
  I was running the software updater to install ubuntu 18.04, when I got the 
error message,
  "Could not install systemd-shim."

  I continued on with the install and got the message, "Could not
  install "/var/cache/apt/...deb" package."

  I continued on with the install and got the message "Could not install
  upgrade."

  I rebooted and it looks like it did upgrade most of the applications.

  I ran the software updater and it tells me "Not all updates can be
  installed" and that I have to run a partial install.  I do this and
  get the message "Could not install 'systemd-shim'.  The upgrade has
  aborted. Your system could be in an unusable state. A recovery will
  run now (dpkg --configure -a)."

  I tryed Synaptic and it tells me that systemd-shim is "Marked for
  removal".  I try and Apply the change and get the error  message "E:
  systemd-shim: installed systemd-shim package post-removal script
  subprocess returned error exit status 2".

  So how do I fix this so that I can finish the install?

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Fri Aug 17 12:16:55 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2010-05-12 (3018 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (0 days ago)

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

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

[Touch-packages] [Bug 1696418] Re: gnome-help/shell-introduction.page link to removed files

2018-08-17 Thread Brian Murray

Hello Narcis, or anyone else affected,

Accepted gnome-user-docs into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gnome-user-
docs/3.8.2-1ubuntu0.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: gnome-user-docs (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-trusty

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

Title:
  gnome-help/shell-introduction.page link to removed files

Status in gnome-user-docs package in Ubuntu:
  Invalid
Status in language-pack-gnome-es-base package in Ubuntu:
  Invalid
Status in gnome-user-docs source package in Trusty:
  Fix Committed
Status in language-pack-gnome-es-base source package in Trusty:
  Won't Fix

Bug description:
  [Impact]

  The latest language pack update for trusty at 2016-07-20 did (for
  unknown reason) not include the localized gnome-help pages, so gnome-
  help is displayed in English whatever the session language is.

  The proposed upload sets the NO_PKG_MANGLE variable, so the package is
  built without language stripping. This works around the failure with
  the language packs.

  [Test Case]

  Open gnome-help with a non-English language (using Spanish as
  example):

  LANGUAGE=es yelp help:gnome-help

  Current package: Showed in English

  Proposed package: Showed in Spanish

  [Regression Potential]

  Negligible. This is in practice a no-change rebuild.

  [Original description]

  p.e.:
  /usr/share/help/es/gnome-help/shell-introduction.page
  is a link to /usr/share/help-langpack/es/gnome-help/shell-introduction.page

  A lot of pages became broken links since some update of language-pack-
  gnome-*-base lost target files.

  Most of missing files are listed at:
  https://packages.ubuntu.com/trusty/all/language-pack-gnome-*-base/filelist

  (Replace "*" by any packaged language, such as "es")

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-user-guide 3.8.2-1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CasperVersion: 1.340
  CurrentDesktop: GNOME
  Date: Wed Jun  7 13:15:08 2017
  LiveMediaBuild: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-user-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

Launchpad has imported 16 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=103078.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2017-10-03T16:44:06+00:00 Sergio Callegari wrote:

Software rendering with recent mesa (either LLVMPipe, softpipe or swr)
breaks matlab.

Seen with MATLAB 2016a on Kubuntu 17.04 with the latest (git) mesa as of
today.

Graphic commands (e.g. plot) hang and make it impossible to close Matlab
cleanly.

On llvmpipe the 'opengl info' matlab command crashes with

Error using hgopengl
Java exception occurred:
java.lang.RuntimeException: Waited 5000ms for: <38d5ebf2, 64757a04>[count 2 [
add. 0, orig 2], qsz 0, owner
, add.owner Startup Class Loader-SharedResourceRunner] -

at
jogamp.common.util.locks.RecursiveLockImpl01Unfairish.lock(RecursiveLockImpl01Unfairish.java:198)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:199)
at com.jogamp.opengl.GLProfile.getDefaultDevice(GLProfile.java:2003)
at com.jogamp.opengl.GLCapabilities.(GLCapabilities.java:84)
at
com.mathworks.hg.uij.OpenGLUtils$MyGLListener.getGLInformation(OpenGLUtils.java:320)
at
com.mathworks.hg.uij.OpenGLUtils$MyGLListener.getGLData(OpenGLUtils.java:498)
at com.mathworks.hg.uij.OpenGLUtils.getGLData(OpenGLUtils.java:78)

Error in hgopengl

On softpipe, the same command hangs.

This is curious because matlab has itself a software rendering mode,
that seems to rely on mesa X11. The opengl info for it returns

Version: '2.1 Mesa 10.5.2'
Vendor: 'Brian Paul'
Renderer: 'Mesa X11'
MaxTextureSize: 16384
Visual: 'Visual 0x72, (RGBA 32 bits (8 8 8 8), Z
depth 16 bits, Hardware acceleratio…'
Software: 'true'
HardwareSupportLevel: 'none (known graphics driver issues)'
SupportsGraphicsSmoothing: 0
SupportsDepthPeelTransparency: 1
SupportsAlignVertexCenters: 0
Extensions: {151x1 cell}
MaxFrameBufferSize: 16384

So, it looks like mesa was supporting matlab 2016a just fine at the time
of 10.5.2 and that we are now facing a regression.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1742894/comments/0

On 2017-10-03T17:09:01+00:00 Emil-l-velikov wrote:

Hi Sergio,

I won't be looking at the issue, I'm afraid yet here's a couple of
ideas/suggestions that should help:

- try to track down the first Mesa version (ideally a commit) that breaks things
- isolate that the issue is not LLVM related by rebuilding mesa without it
- check that the correct libraries are picked (using strace or LD_DEBUG=libs)
Matlab might be shipping libraries (say libc/libstdc++) that are older than the
ones Mesa is build against.
- try to get more verbose information of the issue - not sure if the dev. will
have a matlab license to debug themselves

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1742894/comments/1

On 2017-10-04T06:48:26+00:00 Sergio Callegari wrote:

Hi,

I totally understand the difficulty in looking into an issue related to
(expensive) commercial, that - as such - is hard to reproduce.

Thanks for the suggestion, even if - on a machine that is in use - I
will not be able to do any bisection.

I'll try to work on the last point aka get more verbose information.

In any case, my intent was mostly to assure that a trace of the problem
is present on the bug tracker, in case other users run into the issue
and possibly to guide them if they need to get new hardware with the
need to run Matlab on it.

Unfortunately the Matlab experience on Linux is sad. Not working with
nouveau. Not working with soft rendering, either. Working with its own
soft rendering, but with many limitations. Fortunately, it seems OK on
intel graphics.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1742894/comments/2

On 2017-10-04T17:52:10+00:00 Brianp-h wrote:

Sergio, I installed the 30-day trial of Matlab r2017b and typed 'opengl
info' in the command window. I did not get a java exception. I got an
error message that reads:

"""
MATLAB has experienced a low-level graphics error, and may not have drawn
correctly.
Read about what you can do to prevent this issue at Resolving Low-Level
Graphics Issues then restart MATLAB.
To share details of this issue with MathWorks technical support,
please include this file with your service request.
"""

[Touch-packages] [Bug 1787650] Re: package grilo-plugins-0.3-base 0.3.5-1ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-08-17 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: fsys-tarfile-error

** Changed in: grilo-plugins (Ubuntu)
   Status: New => Invalid

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

Title:
  package grilo-plugins-0.3-base 0.3.5-1ubuntu1 failed to
  install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error
  exit status 2

Status in grilo-plugins package in Ubuntu:
  Invalid

Bug description:
  I don't know what happened.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: grilo-plugins-0.3-base 0.3.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Aug 17 15:43:45 2018
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2017-04-05 (499 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: grilo-plugins
  Title: package grilo-plugins-0.3-base 0.3.5-1ubuntu1 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (0 days ago)

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

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

[Touch-packages] [Bug 1787600] Re: kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960): apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor.gnome-system-monitor" nam

2018-08-17 Thread John Johansen

Sadly yes. AppArmor currently doesn't do audit message deduping, leaving
it entirely to the audit infrastructure. Which means denial messages can
fill the logs.

There is current work to fix this by providing a dedup cache that will
hopefully land in 4.20


** Changed in: apparmor (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960):
  apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor
  .gnome-system-monitor" name="/run/mount/utab" pid=2265 comm="gnome-
  system-mo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Status in apparmor package in Ubuntu:
  New

Bug description:
  This log repeats so many times in file /var/log/syslog and
  /var/log/kern.log, causing the size of 2 files exceed 100Mb

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

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

[Touch-packages] [Bug 1772338] Re: Deprecation warning compiling against unity.vapi

2018-08-17 Thread Robert Ancell

** Changed in: libunity (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: libunity (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Deprecation warning compiling against unity.vapi

Status in libunity package in Ubuntu:
  Triaged

Bug description:
  Vala 0.31.1 deprecated the "Deprecated" code attribute, replacing it
  with "Version". The copy of unity.vapi shipped by libunity-dev in
  bionic still uses the Deprecated attribute, however.

  I.e. in unity.vapi:

  [Deprecated (replacement = "AppInfoManager.get_default")]
  public static Unity.AppInfoManager get_instance ();

  Should instead be:

  [Version (deprecated = true, replacement = "AppInfoManager.get_default")]
  public static Unity.AppInfoManager get_instance ();

  This causes a deprecation warning when compiling against it,
  regardless of whether any deprecated calls are actually being made by
  the code being compiled. While a minor issue, it would be good to have
  fixed since it makes it impossible to develop against it with fatal
  warnings enabled, which is bad for QA.

  The Unity build seems to generate that file as per usual (as a valac
  build artefact) so I would assume this should be fixed by a simple
  rebuild using vala >= 0.31.1, but surely the version of libunity-dev
  that shipped with bionic would have been rebuild against valac that
  ships with bionic (0.40)? So I'm not sure why Deprecated is still
  present in the vapi.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libunity-dev 7.1.4+18.04.20180209.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 21 10:45:08 2018
  InstallationDate: Installed on 2015-07-22 (1033 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: libunity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1772338] Re: Deprecation warning compiling against unity.vapi

2018-08-17 Thread Robert Ancell

That tag comes from src/unity-appinfo-manager.vala so a code change is required:
https://code.launchpad.net/~robert-ancell/libunity/update-deprecation-tags/+merge/353363

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

Title:
  Deprecation warning compiling against unity.vapi

Status in libunity package in Ubuntu:
  Triaged

Bug description:
  Vala 0.31.1 deprecated the "Deprecated" code attribute, replacing it
  with "Version". The copy of unity.vapi shipped by libunity-dev in
  bionic still uses the Deprecated attribute, however.

  I.e. in unity.vapi:

  [Deprecated (replacement = "AppInfoManager.get_default")]
  public static Unity.AppInfoManager get_instance ();

  Should instead be:

  [Version (deprecated = true, replacement = "AppInfoManager.get_default")]
  public static Unity.AppInfoManager get_instance ();

  This causes a deprecation warning when compiling against it,
  regardless of whether any deprecated calls are actually being made by
  the code being compiled. While a minor issue, it would be good to have
  fixed since it makes it impossible to develop against it with fatal
  warnings enabled, which is bad for QA.

  The Unity build seems to generate that file as per usual (as a valac
  build artefact) so I would assume this should be fixed by a simple
  rebuild using vala >= 0.31.1, but surely the version of libunity-dev
  that shipped with bionic would have been rebuild against valac that
  ships with bionic (0.40)? So I'm not sure why Deprecated is still
  present in the vapi.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libunity-dev 7.1.4+18.04.20180209.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 21 10:45:08 2018
  InstallationDate: Installed on 2015-07-22 (1033 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: libunity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

2018-08-17 Thread guillermo

Used Ubuntu 18.04 in my 8 year old Toshiba Satellite L675 laptop for
months without issues, progressed to 18.04.1, no problems, until
upgraded to kernel 4.15.0-32-generic 2 days ago, then, same bug as
described. only in my case the waiting didn't finished automatically so
I had to manually hit the keyboard to obtain a message for press the
Enter key to boot. I fixed it editing /etc/initramfs-tools/conf.d/resume
to RESUME=none and then regenerating initramfs with sudo update-
initramfs -u. Now I boot again without delays.

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1696418] Re: gnome-help/shell-introduction.page link to removed files

2018-08-17 Thread Gunnar Hjalmarsson

Verified the test case using gnome-user-guide 3.8.2-1ubuntu0.1 from
trusty-proposed.

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

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

Title:
  gnome-help/shell-introduction.page link to removed files

Status in gnome-user-docs package in Ubuntu:
  Invalid
Status in language-pack-gnome-es-base package in Ubuntu:
  Invalid
Status in gnome-user-docs source package in Trusty:
  Fix Committed
Status in language-pack-gnome-es-base source package in Trusty:
  Won't Fix

Bug description:
  [Impact]

  The latest language pack update for trusty at 2016-07-20 did (for
  unknown reason) not include the localized gnome-help pages, so gnome-
  help is displayed in English whatever the session language is.

  The proposed upload sets the NO_PKG_MANGLE variable, so the package is
  built without language stripping. This works around the failure with
  the language packs.

  [Test Case]

  Open gnome-help with a non-English language (using Spanish as
  example):

  LANGUAGE=es yelp help:gnome-help

  Current package: Showed in English

  Proposed package: Showed in Spanish

  [Regression Potential]

  Negligible. This is in practice a no-change rebuild.

  [Original description]

  p.e.:
  /usr/share/help/es/gnome-help/shell-introduction.page
  is a link to /usr/share/help-langpack/es/gnome-help/shell-introduction.page

  A lot of pages became broken links since some update of language-pack-
  gnome-*-base lost target files.

  Most of missing files are listed at:
  https://packages.ubuntu.com/trusty/all/language-pack-gnome-*-base/filelist

  (Replace "*" by any packaged language, such as "es")

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-user-guide 3.8.2-1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CasperVersion: 1.340
  CurrentDesktop: GNOME
  Date: Wed Jun  7 13:15:08 2017
  LiveMediaBuild: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-user-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1695998] Re: geisview crash on Segmentation fault (17.04)

2018-08-17 Thread Jeremy Bicha

** Also affects: geis (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  geisview crash on Segmentation fault (17.04)

Status in Geis:
  New
Status in geis package in Ubuntu:
  New
Status in Debian:
  New

Bug description:
  geisview from geis-tools_2.2.17+16.04.20160126-0ubuntu1_amd64 crash on 
segmentation fault on Ubuntu 17.04 with 4.10.0-21 kernel.
  Here the output:

  >> geisview
  /usr/lib/python3/dist-packages/geisview/classview.py:22: PyGIWarning: Gtk was 
imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
  Segmentation fault (core dumped)

  
  I'm new on this so please help me and tell me if I need to provide more 
information and how.

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

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

[Touch-packages] [Bug 334763] Re: pam-auth-update should ignore backup files in /usr/share/pam-configs/krb5

** Changed in: pam (Debian)
   Status: New => Fix Released

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

Title:
  pam-auth-update should ignore backup files in /usr/share/pam-
  configs/krb5

Status in pam package in Ubuntu:
  Confirmed
Status in pam package in Debian:
  Fix Released

Bug description:
  pam-auth-updates uses ALL files in /usr/share/pam-configs, even
  obvious backup files (name~)

  this causes confusion, as the profile shows up twice in the pam-auth-
  update dialog

  PS: I stumbled over this bug/mis-feature when I edited /usr/share/pam-
  configs/krb5 to set minimum_uid from 1000 to 2000

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

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

[Touch-packages] [Bug 1787600] Re: kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960): apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor.gnome-system-monitor" nam

Thanks John for your answer.
So do you know what cause this bunch of audit messages, and how could I fix 
that?

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

Title:
  kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960):
  apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor
  .gnome-system-monitor" name="/run/mount/utab" pid=2265 comm="gnome-
  system-mo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Status in apparmor package in Ubuntu:
  New

Bug description:
  This log repeats so many times in file /var/log/syslog and
  /var/log/kern.log, causing the size of 2 files exceed 100Mb, and the
  journal folder increase to several Gbs, causing no space left in
  "Filesystem root".

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

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

[Touch-packages] [Bug 1787600] Re: kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960): apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor.gnome-system-monitor" nam

** Description changed:

  This log repeats so many times in file /var/log/syslog and
- /var/log/kern.log, causing the size of 2 files exceed 100Mb
+ /var/log/kern.log, causing the size of 2 files exceed 100Mb, and the
+ journal folder increase to several Gbs, causing no space left in
+ "Filesystem root".

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

Title:
  kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960):
  apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor
  .gnome-system-monitor" name="/run/mount/utab" pid=2265 comm="gnome-
  system-mo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Status in apparmor package in Ubuntu:
  New

Bug description:
  This log repeats so many times in file /var/log/syslog and
  /var/log/kern.log, causing the size of 2 files exceed 100Mb, and the
  journal folder increase to several Gbs, causing no space left in
  "Filesystem root".

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

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

[Touch-packages] [Bug 886075] Re: gsettings-data-convert crashed with SIGSEGV in g_settings_delay()

** Changed in: gconf
   Status: New => Won't Fix

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

Title:
  gsettings-data-convert crashed with SIGSEGV in g_settings_delay()

Status in gconf:
  Won't Fix
Status in gconf package in Ubuntu:
  Triaged

Bug description:
  This was upon logging in, just after rebooting because Unity/Compiz
  crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gconf2 3.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CheckboxSubmission: dd3689fa6394f60ec14dbe98d0bab891
  CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
  Date: Fri Nov  4 12:09:33 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gsettings-data-convert
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  ProcCmdline: gsettings-data-convert
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9ce86c0462:mov0x18(%rbx),%rdi
   PC (0x7f9ce86c0462) ok
   source "0x18(%rbx)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gconf
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_delay () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? ()
   ?? ()
  Title: gsettings-data-convert crashed with SIGSEGV in g_settings_delay()
  UpgradeStatus: Upgraded to oneiric on 2011-10-11 (23 days ago)
  UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vde2-net

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

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

[Touch-packages] [Bug 1787600] Re: kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960): apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor.gnome-system-monitor" nam

2018-08-17 Thread John Johansen

Its being caused by the gnome system-monitor snap. Its author is missing
some permissions required to use it properly on your system. It looks
like the system monitor is running and it keeps polling the file causing
this denial.

The apparmor rule to fix this is
  
/run/mount/utab r,


You could add it to the file in 
  /var/lib/snapd/apparmor/profiles/snap.gnome-system-monitor  (it actually 
might be under a slightly different variant of - and .)

and manually replace using the apparmor parser

  sudo apparmor_parser -r /var/lib/snapd/apparmor/profiles/snap.gnome-
system-monitor

Unfortunately snappy may update this file on you and you will loose the
rule you have added.

The best solution is to contact the snap author so he can update the
snap to include the new permission in the snaps security manifest.

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

Title:
  kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960):
  apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor
  .gnome-system-monitor" name="/run/mount/utab" pid=2265 comm="gnome-
  system-mo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Status in apparmor package in Ubuntu:
  New

Bug description:
  This log repeats so many times in file /var/log/syslog and
  /var/log/kern.log, causing the size of 2 files exceed 100Mb, and the
  journal folder increase to several Gbs, causing no space left in
  "Filesystem root".

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

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

[Touch-packages] [Bug 1787600] Re: kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960): apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor.gnome-system-monitor" nam

Thank you so much John, I'm trying your solution.
Based on your answer, it seems like this problem is not because of something 
special in my computer. Does that mean this problem occurs on every other 
computers running Ubuntu with gnome (Ubuntu 18.01) ?
(I'm new to Ubuntu, so may have some silly questions :-)

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

Title:
  kernel: [ 6230.503218] audit: type=1400 audit(1534512537.321:398960):
  apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor
  .gnome-system-monitor" name="/run/mount/utab" pid=2265 comm="gnome-
  system-mo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Status in apparmor package in Ubuntu:
  New

Bug description:
  This log repeats so many times in file /var/log/syslog and
  /var/log/kern.log, causing the size of 2 files exceed 100Mb, and the
  journal folder increase to several Gbs, causing no space left in
  "Filesystem root".

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

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

[Touch-packages] [Bug 601936] Re: gconfd-2 crashed with SIGSEGV in ORBit_get_union_tag()

** Changed in: gconf
   Status: New => Won't Fix

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

Title:
  gconfd-2 crashed with SIGSEGV in ORBit_get_union_tag()

Status in gconf:
  Won't Fix
Status in gconf package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gconf

  dont know whats this programm.. so it crashed dont know how and why.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: libgconf2-4 2.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  Architecture: i386
  Date: Mon Jul  5 18:06:30 2010
  ExecutablePath: /usr/lib/libgconf2-4/gconfd-2
  InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
  ProcCmdline: /usr/lib/libgconf2-4/gconfd-2
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.utf8
  Signal: 11
  SourcePackage: gconf
  StacktraceTop:
   ORBit_get_union_tag () from /usr/lib/libORBit-2.so.0
   ORBit_marshal_value () from /usr/lib/libORBit-2.so.0
   ORBit_marshal_arg () from /usr/lib/libORBit-2.so.0
   ORBit_small_invoke_adaptor () from /usr/lib/libORBit-2.so.0
   ?? () from /usr/lib/libORBit-2.so.0
  Title: gconfd-2 crashed with SIGSEGV in ORBit_get_union_tag()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Touch-packages] [Bug 355240] Re: gconftool-2 crashed with SIGSEGV in markup_dir_lookup_subdir()

** Changed in: gconf
   Status: New => Won't Fix

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

Title:
  gconftool-2 crashed with SIGSEGV in markup_dir_lookup_subdir()

Status in gconf:
  Won't Fix
Status in gconf package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gconf

  hi 
  im running under 9.04 beta, 
  asus a7n8x-e deluxe
  barton xp 3200

  i have even no idea what gconf is :)
  best rgrds :)
  Ł

  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/gconftool-2
  NonfreeKernelModules: nvidia
  Package: gconf2 2.26.0-0ubuntu1
  ProcCmdline: gconftool --get /desktop/gnome/url-handlers/http/command
  ProcEnviron:
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: gconf
  StacktraceTop:
   ?? () from /usr/lib/libgconf2-4/2/libgconfbackend-xml.so
   ?? () from /usr/lib/libgconf2-4/2/libgconfbackend-xml.so
   ?? () from /usr/lib/libgconf2-4/2/libgconfbackend-xml.so
   ?? () from /usr/lib/libgconf2-4/2/libgconfbackend-xml.so
   markup_dir_lookup_subdir ()
  Title: gconftool-2 crashed with SIGSEGV in markup_dir_lookup_subdir()
  Uname: Linux 2.6.28-11-generic i686
  UserGroups: adm admin cdrom lpadmin plugdev sambashare

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

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

[Touch-packages] [Bug 473880] Re: gconfd-2 assert failure: GConf:ERROR:gconf-sources.c:872:prepend_unset_notify: assertion failed: (modified_sources != NULL)

** Changed in: gconf
   Status: New => Won't Fix

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

Title:
  gconfd-2 assert failure: GConf:ERROR:gconf-
  sources.c:872:prepend_unset_notify: assertion failed:
  (modified_sources != NULL)

Status in gconf:
  Won't Fix
Status in gconf package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gconf

  i can;t change my desktop background

  ProblemType: Crash
  Architecture: i386
  AssertionMessage: GConf:ERROR:gconf-sources.c:872:prepend_unset_notify: 
assertion failed: (modified_sources != NULL)
  CrashCounter: 1
  Date: Wed Nov  4 08:47:08 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/lib/libgconf2-4/gconfd-2
  NonfreeKernelModules: nvidia
  Package: libgconf2-4 2.28.0-0ubuntu2
  ProcCmdline: /usr/lib/libgconf2-4/gconfd-2
  ProcCwd: /
  ProcEnviron:
   SHELL=/bin/bash
   LANG=pl_PL.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  Signal: 6
  SourcePackage: gconf
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/tls/i686/cmov/libc.so.6
   abort () from /lib/tls/i686/cmov/libc.so.6
   g_assertion_message () from /lib/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/libglib-2.0.so.0
  Title: gconfd-2 assert failure: 
GConf:ERROR:gconf-sources.c:872:prepend_unset_notify: assertion failed: 
(modified_sources != NULL)
  Uname: Linux 2.6.31-14-generic i686
  UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare
  XsessionErrors:
   (gnome-settings-daemon:2101): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:2234): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:2218): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (gnome-panel:2214): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to 
allocate widget with width -5 and height 24

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

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

[Touch-packages] [Bug 1777438] Re: Empty Packages file breaks apt updating

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

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

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

Title:
  Empty Packages file breaks apt updating

Status in apt package in Ubuntu:
  Expired

Bug description:
  I maintain an internal repository for wheezy, jessie, trusty, xenial
  an bionic. With bionic started to see an issue that apt-get update
  waits for a long time and eventually fails with:

  Reading package lists... Done
  W: Failed to fetch 
https://my_repo_url/dists/bionic/myrepo/binary-i386/Packages  Undetermined 
Error [IP: 1.2.3.4 443]
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  I don't have packages in binary-i386 but I do in binary-amd64. The
  reason seems to be that Packages file is empty (as created by dpkg-
  scanpackages), since if I manually add just "#" to the file, updating
  works again.

  Empty Packages -file works in previous versions, so this seems to be a
  regression.

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

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

[Touch-packages] [Bug 1775676] Re: file is not showing in a good format

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

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

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

Title:
  file is not showing in a good format

Status in xorg package in Ubuntu:
  Expired

Bug description:
  all my files are not shpoing well

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Jun  7 18:55:36 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:172a]
  InstallationDate: Installed on 2018-05-26 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP EliteBook 8440p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=ff2e3855-9d5d-4ca8-abf2-661b693284ca ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.20
  dmi.board.name: 172A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.20:bd09/05/2011:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8440p
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.1-0~b~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.1-0~b~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1615144] Re: BUG: unable to handle kernel NULL pointer dereference

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

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

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

Title:
  BUG: unable to handle kernel NULL pointer dereference

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  The latest update from the Xenial InRelease repository makes the
  following processes consume 100% CPU:

  thermald(1.5-2ubuntu2)
  imap(Dovecot 1:2.2.22-1ubuntu2)
  imap-login  (Dovecot 1:2.2.22-1ubuntu2)

  and eventualy (after 1-2 minutes) render the system completely unresponsive.
  "NMI watchdog: Watchdog detected hard LOCKUP on cpu 0".

  I was able to recreate the problem on my test system, so whatever is
  missing in this report should be easy to simulate on another system.
  All apparmor profiles are standard.

  # aa-status
  apparmor module is loaded.
  49 profiles are loaded.
  13 profiles are in enforce mode.
 /sbin/dhclient
 /usr/bin/freshclam
 /usr/lib/NetworkManager/nm-dhcp-client.action
 /usr/lib/NetworkManager/nm-dhcp-helper
 /usr/lib/chromium-browser/chromium-browser//browser_java
 /usr/lib/chromium-browser/chromium-browser//browser_openjdk
 /usr/lib/chromium-browser/chromium-browser//sanitized_helper
 /usr/lib/connman/scripts/dhclient-script
 /usr/sbin/clamd
 /usr/sbin/mysqld
 /usr/sbin/named
 /usr/sbin/ntpd
 /usr/sbin/tcpdump
  36 profiles are in complain mode.
 /usr/lib/chromium-browser/chromium-browser
 /usr/lib/chromium-browser/chromium-browser//chromium_browser_sandbox
 /usr/lib/chromium-browser/chromium-browser//lsb_release
 /usr/lib/chromium-browser/chromium-browser//xdgsettings
 /usr/lib/dovecot/anvil
 /usr/lib/dovecot/auth
 /usr/lib/dovecot/config
 /usr/lib/dovecot/deliver
 /usr/lib/dovecot/dict
 /usr/lib/dovecot/dovecot-lda
 /usr/lib/dovecot/dovecot-lda///usr/sbin/sendmail
 /usr/lib/dovecot/imap
 /usr/lib/dovecot/imap-login
 /usr/lib/dovecot/lmtp
 /usr/lib/dovecot/log
 /usr/lib/dovecot/managesieve
 /usr/lib/dovecot/managesieve-login
 /usr/lib/dovecot/pop3
 /usr/lib/dovecot/pop3-login
 /usr/lib/dovecot/ssl-params
 /usr/sbin/avahi-daemon
 /usr/sbin/dnsmasq
 /usr/sbin/dnsmasq//libvirt_leaseshelper
 /usr/sbin/dovecot
 /usr/sbin/identd
 /usr/sbin/mdnsd
 /usr/sbin/nmbd
 /usr/sbin/nscd
 /usr/sbin/smbd
 /usr/sbin/smbldap-useradd
 /usr/sbin/smbldap-useradd///etc/init.d/nscd
 /usr/{sbin/traceroute,bin/traceroute.db}
 /{usr/,}bin/ping
 klogd
 syslog-ng
 syslogd
  25 processes have profiles defined.
  5 processes are in enforce mode.
 /usr/bin/freshclam (2942)
 /usr/sbin/clamd (3080)
 /usr/sbin/mysqld (3767)
 /usr/sbin/named (3634)
 /usr/sbin/ntpd (3468)
  20 processes are in complain mode.
 /usr/lib/dovecot/anvil (3827)
 /usr/lib/dovecot/auth (3845)
 /usr/lib/dovecot/auth (4503)
 /usr/lib/dovecot/config (3830)
 /usr/lib/dovecot/imap (6139)
 /usr/lib/dovecot/imap (6952)
 /usr/lib/dovecot/imap-login (3826)
 /usr/lib/dovecot/imap-login (3832)
 /usr/lib/dovecot/imap-login (6048)
 /usr/lib/dovecot/imap-login (7924)
 /usr/lib/dovecot/imap-login (12248)
 /usr/lib/dovecot/imap-login (12740)
 /usr/lib/dovecot/imap-login (12816)
 /usr/lib/dovecot/imap-login (14112)
 /usr/lib/dovecot/imap-login (14508)
 /usr/lib/dovecot/imap-login (14533)
 /usr/lib/dovecot/log (3828)
 /usr/lib/dovecot/managesieve-login (12794)
 /usr/lib/dovecot/ssl-params (4498)
 /usr/sbin/dovecot (3816)
  0 processes are unconfined but have a profile defined.

  
  # uname -r
  4.4.0-34-generic

  
  # apt-get install apparmor
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Suggested packages:
apparmor-profiles-extra apparmor-docs apparmor-utils
  The following packages will be upgraded:
apparmor
  1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
  Need to get 446 kB of archives.
  After this operation, 4,096 B of additional disk space will be used.
  Get:1 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 apparmor 
amd64 2.10.95-0ubuntu2.2 [446 kB]
  Fetched 446 kB in 0s (4,172 kB/s)
  Preconfiguring packages ...
  (Reading database ... 115108 files and directories currently installed.)
  Preparing to unpack .../apparmor_2.10.95-0ubuntu2.2_amd64.deb ...
  Unpacking apparmor (2.10.95-0ubuntu2.2) over (2.10.95-0ubuntu2) ...
  Processing triggers for systemd (229-4ubuntu7) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up apparmor (2.10.95-0ubuntu2.2) ...
  Installing new version of config file 
/etc/apparmor.d/ab

[Touch-packages] [Bug 1786990] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

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

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

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

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  nouvelle mise à jour d'Ubuntu échouée

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Aug 14 15:20:07 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-04-09 (1953 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago)

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

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

[Touch-packages] [Bug 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster

2018-08-17 Thread Andrii

@Jacopo Yes, sometimes. Even restarting audacity or arecord does the trick. 
What really annoying is the noise level. And, yes I've tried everything under 
Windows 10 and sound records perfectly. The problem is that I hate too use 
Windows :)
Oh, I've updated linux kernel to 4.18 and the problem is still there.

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

Title:
  [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x
  faster

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recording applications (audacity, arecord, gnome-sound-recorder)
  record extremely slowly (at what seems to be 0,1x speed), which means
  that at playback the sound is played at a very high pitch and much
  faster than the original.

  To help you understand the issue, I've attached an archive containing two 
files recorded at the same time, one with arecord -f cd and the other with a 
stand-alone Olympus recorder.
  A video of Audacity's behavior when trying to record is also available: 
https://youtu.be/Fe20eQNvZVA
  Look at the seconds hand of the xclock and how much it is moving before 
Audacity is done recording one second of audio.

  Things I've already tried:
  *  Purging and reinstalling Audacity
  *  Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki
  *  Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 
audacity as suggested on AskUbuntu
  *  Reinstalling Ubuntu on a new hard disk
  *  Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 
daily and Xubuntu 17.10.1, 18.04)

  The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard.

  The problem can be reproduced as follows:

  * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've 
tested with)
  * Install audacity via the terminal
  * Start recording, microphone is connected to the rear microphone jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacopo 2417 F pulseaudio
   /dev/snd/controlC0:  jacopo 2417 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 18 09:35:50 2018
  InstallationDate: Installed on 2018-03-03 (45 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: None of the above
  Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 777565] Re: gconfd saved_state file has executable tag set