[Touch-packages] [Bug 453263] Re: evolution-addressbook-export fails with Segmentation fault

2018-11-23 Thread Bug Watch Updater
** 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/453263

Title:
  evolution-addressbook-export fails with Segmentation fault

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

Bug description:
  Binary package hint: evolution

  Hi
  I upgraded to karmic a couple of days ago.

  Description:Ubuntu karmic (development branch)
  Release:9.10

  Since then the evolution-addressbook-export does not work anymore.

  evolution:
Installed: 2.28.0-0ubuntu4
Candidate: 2.28.0-0ubuntu4
Version table:
   *** 2.28.0-0ubuntu4 0
  500 http://gb.archive.ubuntu.com karmic/main Packages
  100 /var/lib/dpkg/status

  Instead of a dump of all my contacts, when I enter

  a ~$ evolution-addressbook-export

  I get

  (evolution-addressbook-export:12812): GLib-GObject-CRITICAL **:
  /build/buildd/glib2.0-2.22.2/gobject/gtype.c:2458: initialization
  assertion failed, use IA__g_type_init() prior to this function

  (evolution-addressbook-export:12812): GLib-GObject-CRITICAL **:
  g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed

  (evolution-addressbook-export:12812): GLib-GObject-CRITICAL **: g_object_ref: 
assertion `G_IS_OBJECT (object)' failed
  Segmentation fault (core dumped)

  I have used the export for about a year and never had any problems. I
  strongly suspect the reason why it does not work anymore is my upgrade
  to karmic beta. The only other reason I could think of is that I
  recently removed most gnome programs from my startup script. They are
  not loaded automatically anymore but they are still installed. Does
  evolution-addressbook-report depend on anything?

  Cheers
  Arian

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

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


[Touch-packages] [Bug 1804910] [NEW] pip3 cannot install gmpy

2018-11-23 Thread Kevin O'Gorman
Public bug reported:

I'm using python3 and want gmpy.  Attempts to install it fail.

I routinely capture the output of maintenance tasks, and am attaching
the results.  This output begins with the text of the shell script I
wrote to do this, which includes calls to the bash functions I wrote to
do this self-referential magic.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python3 3.6.7-1~18.04
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Nov 23 17:44:44 2018
InstallationDate: Installed on 2018-10-18 (36 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "Output of failed run (captured by script(1))"
   
https://bugs.launchpad.net/bugs/1804910/+attachment/5215818/+files/got-gmpy-20181123-1742.script

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

Title:
  pip3 cannot install gmpy

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  I'm using python3 and want gmpy.  Attempts to install it fail.

  I routinely capture the output of maintenance tasks, and am attaching
  the results.  This output begins with the text of the shell script I
  wrote to do this, which includes calls to the bash functions I wrote
  to do this self-referential magic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.7-1~18.04
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 17:44:44 2018
  InstallationDate: Installed on 2018-10-18 (36 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1804908] [NEW] Fails to load 'gmpy'

2018-11-23 Thread Kevin O'Gorman
Public bug reported:

It may be this is a problem in gmpy itself, but since it is not
installed, ubuntu-bug won't let me report a problem with it.

In any event, I routinely capture the output of package maintenance
tasks, and I'm attaching the output of the most recent run of a shell
script I call "do-upgrades".  The errors are near the bottom  It fails
while trying to do something with gmpy, which I would like to have.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6.6
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Nov 23 17:28:25 2018
InstallationDate: Installed on 2018-10-18 (36 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Output of a script (which begins with the text of the 
script)"
   
https://bugs.launchpad.net/bugs/1804908/+attachment/5215814/+files/did-updates-20181123-1722.script

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

Title:
  Fails to load 'gmpy'

Status in apt package in Ubuntu:
  New

Bug description:
  It may be this is a problem in gmpy itself, but since it is not
  installed, ubuntu-bug won't let me report a problem with it.

  In any event, I routinely capture the output of package maintenance
  tasks, and I'm attaching the output of the most recent run of a shell
  script I call "do-upgrades".  The errors are near the bottom  It fails
  while trying to do something with gmpy, which I would like to have.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.6
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 17:28:25 2018
  InstallationDate: Installed on 2018-10-18 (36 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1804908] Re: Fails to load 'gmpy'

2018-11-23 Thread Kevin O'Gorman
I see that this arises when the script calls pip3 to install a python
package.  I'll clean this up to do just that by itself, and re-submit.

Call this one invalid, I guess.

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

Title:
  Fails to load 'gmpy'

Status in apt package in Ubuntu:
  New

Bug description:
  It may be this is a problem in gmpy itself, but since it is not
  installed, ubuntu-bug won't let me report a problem with it.

  In any event, I routinely capture the output of package maintenance
  tasks, and I'm attaching the output of the most recent run of a shell
  script I call "do-upgrades".  The errors are near the bottom  It fails
  while trying to do something with gmpy, which I would like to have.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.6
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 17:28:25 2018
  InstallationDate: Installed on 2018-10-18 (36 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1771041] Re: Remove gconf from Ubuntu

2018-11-23 Thread Jeremy Bicha
** No longer affects: ekiga (Ubuntu)

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

Title:
  Remove gconf from Ubuntu

Status in autopilot-legacy package in Ubuntu:
  New
Status in desktopnova package in Ubuntu:
  New
Status in evolution-indicator package in Ubuntu:
  New
Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in gkdebconf package in Ubuntu:
  New
Status in gnome-mastermind package in Ubuntu:
  New
Status in gnome-phone-manager package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gnomint package in Ubuntu:
  New
Status in gtkwave package in Ubuntu:
  New
Status in guake-indicator package in Ubuntu:
  New
Status in gyrus package in Ubuntu:
  New
Status in jack-mixer package in Ubuntu:
  New
Status in jana package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in ooo-thumbnailer package in Ubuntu:
  New
Status in planner package in Ubuntu:
  New

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  libgnome is sort of a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538

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

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


[Touch-packages] [Bug 1804887] Re: software-properties-qt should not run as root

2018-11-23 Thread Ubuntu Foundations Team Bug Bot
The attachment "partial implementation" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  software-properties-qt should not run as root

Status in software-properties package in Ubuntu:
  New

Bug description:
  s-p-qt should not be run as root (with sudo or pkexec), instead it
  should use the DBus backend like s-p-gtk does. This way the UI runs as
  unprivileged user, and the user is asked for credentials when making
  changes.

  Motivation:
  * Running the UI with sudo is bad.
  * It doesn't work in Wayland. (https://bugs.kde.org/show_bug.cgi?id=391965)
  * The DBus backend already exists and is used by s-p-gtk.

  RFC:
  The attached patch changes s-p-qt to use the DBus service for the settings in 
the first tab (enable/disable components, change server).
  Any comment on how it works or should work?

  Known issues with the patch:
  * When a change fails to be applied the UI doesn't notice and is out of sync 
with system state. That's because the DBus service never returns a value 
(except for DBus error). Solution is to reload the config after every change 
attempt.

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

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


[Touch-packages] [Bug 1804893] [NEW] My ubuntu 18.04.1 freeze random

2018-11-23 Thread kestura
Public bug reported:

I have the problem that the system is freezing and in 10-20 min reboot.
i am looking in internet what can be the problem and i found that can be my 
graphic drive.
Then i am telling the terminal "sudo apt-get install xserver-xorg-video-intel" 
but nothing all was okay.
I tell the terminal than apport-bug xorg. and i found it.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 23 23:20:03 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:161d]
InstallationDate: Installed on 2018-11-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X553MA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi=force
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X553MA.209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X553MA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.209:bd08/08/2014:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X553MA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
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

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  My ubuntu 18.04.1 freeze random

Status in xorg package in Ubuntu:
  New

Bug description:
  I have the problem that the system is freezing and in 10-20 min reboot.
  i am looking in internet what can be the problem and i found that can be my 
graphic drive.
  Then i am telling the terminal "sudo apt-get install 
xserver-xorg-video-intel" but nothing all was okay.
  I tell the terminal than apport-bug xorg. and i found it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 23 23:20:03 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:161d]
  InstallationDate: Installed on 2018-11-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic 
root=/dev/mapper/ub

[Touch-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic

2018-11-23 Thread Christopher Berner
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559

Actually, for the Bose QC35 II, "Headset" is not missing. See below:

Device 2C:41:A1:80:A1:C4 (public)
Name: Christopher's Bose QC35 II
Alias: Christopher's Bose QC35 II
Class: 0x00240418
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific   (-deca-fade-deca-deafdecacaff)
UUID: Serial Port   (1101--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Vendor specific   (81c2e72a-0591-443e-a1ff-05f988593351)
UUID: Vendor specific   (f8d1fbe4-7966-4334-8024-ff96c9330e15)
Modalias: bluetooth:v009Ep4020d0251

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

Title:
  Bluetooth headset HSP/HFP mode not working in Bionic

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

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

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


[Touch-packages] [Bug 1803016] Re: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds

2018-11-23 Thread Natanael
Hello any update ?

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

Title:
  Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Bluetooth and HDMI sound it is ok, but the integrated speakers not
  sounds.

  Distro:
  Description:  Ubuntu 18.10
  Release:  18.10


  Info:
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  hwinfo --sound
  18: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.sos2QFV32t3
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x9dc8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1481 
Revision: 0x30
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable)
Memory Range: 0xb410-0xb41f (rw,non-prefetchable)
IRQ: 140 (1419 events)
Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  natanael   2115 F pulseaudio
   /dev/snd/pcmC0D0p:   natanael   2115 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-11-08 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Q536FD.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Q536FD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrQ536FD.203:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnZenBookQ536FD_Q536FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ536FD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook Q536FD_Q536FD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1804887] [NEW] software-properties-qt should not run as root

2018-11-23 Thread Carlo Vanini
Public bug reported:

s-p-qt should not be run as root (with sudo or pkexec), instead it
should use the DBus backend like s-p-gtk does. This way the UI runs as
unprivileged user, and the user is asked for credentials when making
changes.

Motivation:
* Running the UI with sudo is bad.
* It doesn't work in Wayland. (https://bugs.kde.org/show_bug.cgi?id=391965)
* The DBus backend already exists and is used by s-p-gtk.

RFC:
The attached patch changes s-p-qt to use the DBus service for the settings in 
the first tab (enable/disable components, change server).
Any comment on how it works or should work?

Known issues with the patch:
* When a change fails to be applied the UI doesn't notice and is out of sync 
with system state. That's because the DBus service never returns a value 
(except for DBus error). Solution is to reload the config after every change 
attempt.

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

** Patch added: "partial implementation"
   
https://bugs.launchpad.net/bugs/1804887/+attachment/5215765/+files/0001-Use-DBus-backend-to-make-changes.patch

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

Title:
  software-properties-qt should not run as root

Status in software-properties package in Ubuntu:
  New

Bug description:
  s-p-qt should not be run as root (with sudo or pkexec), instead it
  should use the DBus backend like s-p-gtk does. This way the UI runs as
  unprivileged user, and the user is asked for credentials when making
  changes.

  Motivation:
  * Running the UI with sudo is bad.
  * It doesn't work in Wayland. (https://bugs.kde.org/show_bug.cgi?id=391965)
  * The DBus backend already exists and is used by s-p-gtk.

  RFC:
  The attached patch changes s-p-qt to use the DBus service for the settings in 
the first tab (enable/disable components, change server).
  Any comment on how it works or should work?

  Known issues with the patch:
  * When a change fails to be applied the UI doesn't notice and is out of sync 
with system state. That's because the DBus service never returns a value 
(except for DBus error). Solution is to reload the config after every change 
attempt.

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

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


[Touch-packages] [Bug 1804885] [NEW] Desktop freeze running VirtualBox, Intel graphics

2018-11-23 Thread Michael Thayer
Public bug reported:

When I start a VirtualBox virtual machine (reproducible with the Ubuntu
18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA
emulation and 3D pass-through enabled, my system hangs.  Sometimes I can
recover if I get to a VT fast enough to kill the process.  Also, the OOM
killer sometimes triggers and kills the process or gnome-shell, but the
OOM killer entries in dmesg look like neither of the two are using
excessive memory compared to available system RAM.  When I switch to the
Ubuntu drm-tip kernel packages from the kernel PPA the problem goes
away.  Debugging shows that the hang occurs during the first
glXMakeCurrent call made by the application.  It did not occur using the
standard Ubuntu kernel but running the application under apitrace.  I
can provide the trace if that helps.

Short extract from glxinfo running the 4.20 drm-tip kernel:

Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2)  (0x5916)
Version: 18.2.2
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
Uname: Linux 4.20.0-994-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperVersion: 1.399
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 23 21:13:00 2018
DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:2245]
InstallationDate: Installed on 2018-06-12 (164 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20HES0E73E
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.20.0-994-generic 
root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash 
crashkernel=384M-:128M
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to cosmic on 2018-10-08 (46 days ago)
dmi.bios.date: 09/13/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1QET78W (1.53 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HES0E73E
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470
dmi.product.name: 20HES0E73E
dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470
dmi.product.version: ThinkPad T470
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


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

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

Title:
  Desktop freeze running VirtualBox, Intel graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  When I start a VirtualBox virtual machine (reproducible with the
  Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with
  VMSVGA emulation and 3D pass-through enabled, my system hangs.
  Sometimes I can recover if I get to a VT fast enough to kill the
  process.  Also, the OOM killer sometimes triggers and kills the
  process or gnome-shell, but the OOM killer entries in dmesg look like
  neither of the two are using excessive memory compared to available
  system RAM.  When I switch to the Ubuntu drm-tip kernel packages from
  the kernel PPA the problem goes away.  Debugging shows that the hang

[Touch-packages] [Bug 1799947] Re: [radeon] Application windows in 18.04.01 go black but launcher is still visible

2018-11-23 Thread Paul Chambre
On the flip-side, I still have a corrupted lock screen, and, under
Wayland, two-finger trackpad scrolling doesn't work anymore.

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

Title:
  [radeon] Application windows in 18.04.01 go black but launcher is
  still visible

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Intermittently and randomly, all application windows will go black.
  They are still there, and can be interacted with with keyboard
  shortcuts or if you know where to click with the mouse, but they are
  not drawn.

  The launcher itself is still displayed.

  Clicking Show Applications briefly draws the application window before
  switching to the background and application icons. The application
  icons are shown correctly. Selecting one switches to a black window
  for that application. The application window is again briefly
  displayed when dismissing the application icons by again clicking Show
  Applications.

  TTYs work normally.

  Killing gnome (from another TTY) and allowing it to relaunch results
  in a normal display again.

  This is being seen on an hp 6910p. This system also exhibits a
  corrupted lock screen since upgrade to 18.04.01. Neither of these
  behaviors were seen during two years running 16.04.01.

  Chrome is being used. Current 70.00.3538.77 (64-bit). Chrome is the
  most commonly used application on this machine, so it is possible that
  the behavior is being triggered by Chrome, however, the behavior
  affects all applications, including system applications like software
  update and terminal.

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

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


[Touch-packages] [Bug 1804874] xserver.devices.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "xserver.devices.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215741/+files/xserver.devices.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] make.log.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "make.log.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215739/+files/make.log.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] Xrandr.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1804874/+attachment/5215738/+files/Xrandr.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] XorgLog.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215736/+files/XorgLog.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] XorgLogOld.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215737/+files/XorgLogOld.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] xdpyinfo.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215740/+files/xdpyinfo.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] UnitySupportTest.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215735/+files/UnitySupportTest.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] ProcModules.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215733/+files/ProcModules.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] UdevDb.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1804874/+attachment/5215734/+files/UdevDb.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] ProcEnviron.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215731/+files/ProcEnviron.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] ProcInterrupts.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215732/+files/ProcInterrupts.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] ProcCpuinfoMinimal.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215730/+files/ProcCpuinfoMinimal.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] MonitorsUser.xml.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215728/+files/MonitorsUser.xml.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] ProcCpuinfo.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215729/+files/ProcCpuinfo.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] DistUpgraded.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "DistUpgraded.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215724/+files/DistUpgraded.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] Dependencies.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215723/+files/Dependencies.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] Lspci.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1804874/+attachment/5215726/+files/Lspci.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] DpkgLog.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215725/+files/DpkgLog.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] Lsusb.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1804874/+attachment/5215727/+files/Lsusb.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] Re: can't reconnect mouse/mouse stops working after a while

2018-11-23 Thread Ronalds
apport information

** Tags added: apport-collected bionic third-party-packages ubuntu

** Description changed:

  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used this
  tutorial
  
  "entered following commands :
  
  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "
  
  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
+ --- 
+ ProblemType: Bug
+ .tmp.unity_support_test.0:
+  
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: i386
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CompositorRunning: None
+ CurrentDesktop: GNOME
+ DistroCodename: bionic
+ DistroRelease: Ubuntu 18.04
+ DistroVariant: ubuntu
+ DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
+ GraphicsCard:
+  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
+Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
+ InstallationDate: Installed on 2014-08-26 (1550 days ago)
+ InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
+ MachineType: ASUSTeK Computer Inc. K53E
+ Package: xorg 1:7.7+19ubuntu7.1
+ PackageArchitecture: i386
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
+ Tags: third-party-packages bionic ubuntu
+ Uname: Linux 4.15.0-39-generic i686
+ UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
+ UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
+ _MarkForUpload: True
+ dmi.bios.date: 08/10/2012
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: K53E.221
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: K53E
+ dmi.board.vendor: ASUSTeK Computer Inc.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: ATN12345678901234567
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK Computer Inc.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
+ dmi.product.family: K
+ dmi.product.name: K53E
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK Computer Inc.
+ 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.5-0ubuntu0~18.04.1
+ version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
+ version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
+ 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: Thu Oct 11 13:44:11 2018
+ xserver.configfile: default
+ xserver.errors:
+  
+ xserver.logfile: /var/log/Xorg.0.log
+ xserver.outputs:
+  product id 732 
+  vendor LGD
+ xserver.version: 2:1.18.4-0ubuntu0.7

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215721/+files/BootLog.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  Install

[Touch-packages] [Bug 1804874] CurrentDmesg.txt

2018-11-23 Thread Ronalds
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1804874/+attachment/5215722/+files/CurrentDmesg.txt

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
  InstallationDate: Installed on 2014-08-26 (1550 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: ASUSTeK Computer Inc. K53E
  Package: xorg 1:7.7+19ubuntu7.1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: third-party-packages bionic ubuntu
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53E.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K53E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Thu Oct 11 13:44:11 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1804874] Re: can't reconnect mouse/mouse stops working after a while

2018-11-23 Thread Ronalds
** Description changed:

  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used this
  tutorial
  
  "entered following commands :
  
  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "
  
- 
  Output files are compressed and attached to this bug report.
+ Ubuntu 18.04.1, gnome and kde installed.

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.

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

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


[Touch-packages] [Bug 1804874] Re: can't reconnect mouse/mouse stops working after a while

2018-11-23 Thread C de-Avillez
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  can't reconnect mouse/mouse stops working after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used
  this tutorial

  "entered following commands :

  LANG=C
  dmesg > ~/dmesg
  diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
  cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
  diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "

  Output files are compressed and attached to this bug report.
  Ubuntu 18.04.1, gnome and kde installed.

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

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


[Touch-packages] [Bug 1804874] [NEW] can't reconnect mouse/mouse stops working after a while

2018-11-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used this
tutorial

"entered following commands :

LANG=C
dmesg > ~/dmesg
diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff "


Output files are compressed and attached to this bug report.

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

-- 
can't reconnect mouse/mouse stops working after a while
https://bugs.launchpad.net/bugs/1804874
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1804755] Re: SRU of LXC 3.0.3 (upstream bugfix release)

2018-11-23 Thread Stéphane Graber
And the bionic version too

** Changed in: lxc (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: lxc (Ubuntu Cosmic)
   Status: Triaged => In Progress

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

Title:
  SRU of LXC 3.0.3 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Xenial:
  Triaged
Status in lxc source package in Bionic:
  In Progress
Status in lxc source package in Cosmic:
  In Progress
Status in lxc source package in Disco:
  Fix Released

Bug description:
  LXC upstream released LXC 3.0.3 as a bugfix release with following
  changelog:

   - CONTRIBUTING: Update reference to kernel coding style
   - CONTRIBUTING: Link to latest online kernel docs
   - CONTRIBUTING: Direct readers to CODING_STYLE.md
   - CODING_STYLE: Mention kernel style in introduction
   - CONTRIBUTING: Add 'be' to fix grammar
   - CODING_STLYE: Simplify explanation for use of 'extern'
   - CODING_STLYE: Remove sections implied by 'kernel style'
   - CODING_STYLE: Fix non-uniform heading level
   - CODING_STYLE: Update section header format
   - cmd: Use parenthesis around complex macro
   - cmd: Use 'void' instead of empty parameter list
   - cmd: Do not use braces for single statement block
   - cmd: Fix whitespace issues
   - cmd: Use 'const' for static string constant.
   - cmd: Remove unnecessary whitespace in string
   - cmd: Put trailing */ on a separate line
   - cmd: Remove typo'd semicolon
   - cmd: Do not use comparison to NULL
   - lxc_init: s/SYSDEBUG()/SYSERROR()/g in remove_self
   - tools: lxc-attach: add default log priority & cleanups
   - tools: lxc-cgroup: add default log priority & cleanups
   - tools: lxc-checkpoint: add default log priority & cleanups
   - tools: lxc-console: add default log priority & cleanups
   - tools: lxc-create: add default log priority & cleanups
   - tools: lxc-destroy: add default log priority & cleanups
   - tools: lxc-device: add default log priority & cleanups
   - tools: lxc-execute: add default log priority & cleanups
   - tools: lxc-start: add default log priority & cleanups
   - tools: lxc-stop: add default log priority & cleanups
   - tools: lxc-freeze: add default log priority & cleanups
   - tools: lxc-unfreeze: add default log priority & cleanups
   - storage_utils: move duplicated function from tools
   - tools: fix lxc-execute command parsing
   - lseek - integer overflow
   - cmd: lxc-user-nic: change log macro & cleanups
   - cmd: lxc-usernsexec reorder includes
   - cmd: move declarations to macro.h
   - cmd: use utils.{c,h} helpers in lxc-usernsexec
   - cmd: simplify lxc-usernsexec
   - cmd: use safe number parsers in lxc-usernsexec
   - macro: add missing headers
   - macro: add macvlan properties
   - tools: Indicate container startup failure
   - storage: exit() => _exit(). when exec is failed, child process needs to 
use _exit()
   - tools: lxc-wait: add default log priority & cleanups
   - conf: fix path/lxcpath mixups in tty setup
   - cmd: use goto for cleanup in lxc-usernsexec
   - cmd: Do not reassign variable before it is used
   - cmd: Reduce scope of 'count' variable
   - cmd: Fix format issues found by clang-format
   - list: fix indent
   - utils: split into {file,string}_utils.{c,h}
   - pam_cgfs: build from the same sources as liblxc
   - conf: fix devpts mounting when fully unprivileged
   - macro: s/rexit()/_exit()/g
   - attach: move struct declaration to top
   - macro: move macros from attach.c
   - Makefile: don't allow undefined symbols
   - autotools: check if compiler is new enough
   - log: handle strerror_r() versions
   - autotools: add --{disable,enable}-thread-safety
   - log: fail build on ENFORCE_THREAD_SAFETY error
   - {file,string}_utils: remove NO_LOG
   - initutils: remove useless comment
   - string_utils: remove unnecessary include
   - string_utils: remove unused headers
   - string_utils: add remove_trailing_slashes()
   - Makefile: remove last pam_cgfs special-casing
   - conf: add missing headers
   - Fix typo
   - ifaddrs: add safe implementation of getifaddrs()
   - Makefile: conditionalize ifaddrs.h inclusion
   - execute: skip lxc-init logging when unprivileged
   - execute: pass /proc/self/fd/
   - tests: cleanup get_item.c
   - build: fix musl
   - configure: reorder header checks
   - compiler: add compiler.h header
   - commands: return -1 on lxc_cmd_get_init_pid() err
   - tests: add basic.c
   - tests: cleanup Makefile
   - commands: ensure -1 is sent on EPIPE for init pid
   - macro: add LXC_AUDS_ADDR_LEN
   - macro: move LXC_CMD_DATA_MAX from commands.h
   - macro: add PTR_TO_INT() and INT_TO_PTR()
   - macro: add INTTYPE_TO_STRLEN()
   - caps: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
   - cgfsng: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
   - confile: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
   - log: s/L

[Touch-packages] [Bug 1804755] Re: SRU of LXC 3.0.3 (upstream bugfix release)

2018-11-23 Thread Stéphane Graber
Uploaded to cosmic

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

Title:
  SRU of LXC 3.0.3 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Xenial:
  Triaged
Status in lxc source package in Bionic:
  In Progress
Status in lxc source package in Cosmic:
  In Progress
Status in lxc source package in Disco:
  Fix Released

Bug description:
  LXC upstream released LXC 3.0.3 as a bugfix release with following
  changelog:

   - CONTRIBUTING: Update reference to kernel coding style
   - CONTRIBUTING: Link to latest online kernel docs
   - CONTRIBUTING: Direct readers to CODING_STYLE.md
   - CODING_STYLE: Mention kernel style in introduction
   - CONTRIBUTING: Add 'be' to fix grammar
   - CODING_STLYE: Simplify explanation for use of 'extern'
   - CODING_STLYE: Remove sections implied by 'kernel style'
   - CODING_STYLE: Fix non-uniform heading level
   - CODING_STYLE: Update section header format
   - cmd: Use parenthesis around complex macro
   - cmd: Use 'void' instead of empty parameter list
   - cmd: Do not use braces for single statement block
   - cmd: Fix whitespace issues
   - cmd: Use 'const' for static string constant.
   - cmd: Remove unnecessary whitespace in string
   - cmd: Put trailing */ on a separate line
   - cmd: Remove typo'd semicolon
   - cmd: Do not use comparison to NULL
   - lxc_init: s/SYSDEBUG()/SYSERROR()/g in remove_self
   - tools: lxc-attach: add default log priority & cleanups
   - tools: lxc-cgroup: add default log priority & cleanups
   - tools: lxc-checkpoint: add default log priority & cleanups
   - tools: lxc-console: add default log priority & cleanups
   - tools: lxc-create: add default log priority & cleanups
   - tools: lxc-destroy: add default log priority & cleanups
   - tools: lxc-device: add default log priority & cleanups
   - tools: lxc-execute: add default log priority & cleanups
   - tools: lxc-start: add default log priority & cleanups
   - tools: lxc-stop: add default log priority & cleanups
   - tools: lxc-freeze: add default log priority & cleanups
   - tools: lxc-unfreeze: add default log priority & cleanups
   - storage_utils: move duplicated function from tools
   - tools: fix lxc-execute command parsing
   - lseek - integer overflow
   - cmd: lxc-user-nic: change log macro & cleanups
   - cmd: lxc-usernsexec reorder includes
   - cmd: move declarations to macro.h
   - cmd: use utils.{c,h} helpers in lxc-usernsexec
   - cmd: simplify lxc-usernsexec
   - cmd: use safe number parsers in lxc-usernsexec
   - macro: add missing headers
   - macro: add macvlan properties
   - tools: Indicate container startup failure
   - storage: exit() => _exit(). when exec is failed, child process needs to 
use _exit()
   - tools: lxc-wait: add default log priority & cleanups
   - conf: fix path/lxcpath mixups in tty setup
   - cmd: use goto for cleanup in lxc-usernsexec
   - cmd: Do not reassign variable before it is used
   - cmd: Reduce scope of 'count' variable
   - cmd: Fix format issues found by clang-format
   - list: fix indent
   - utils: split into {file,string}_utils.{c,h}
   - pam_cgfs: build from the same sources as liblxc
   - conf: fix devpts mounting when fully unprivileged
   - macro: s/rexit()/_exit()/g
   - attach: move struct declaration to top
   - macro: move macros from attach.c
   - Makefile: don't allow undefined symbols
   - autotools: check if compiler is new enough
   - log: handle strerror_r() versions
   - autotools: add --{disable,enable}-thread-safety
   - log: fail build on ENFORCE_THREAD_SAFETY error
   - {file,string}_utils: remove NO_LOG
   - initutils: remove useless comment
   - string_utils: remove unnecessary include
   - string_utils: remove unused headers
   - string_utils: add remove_trailing_slashes()
   - Makefile: remove last pam_cgfs special-casing
   - conf: add missing headers
   - Fix typo
   - ifaddrs: add safe implementation of getifaddrs()
   - Makefile: conditionalize ifaddrs.h inclusion
   - execute: skip lxc-init logging when unprivileged
   - execute: pass /proc/self/fd/
   - tests: cleanup get_item.c
   - build: fix musl
   - configure: reorder header checks
   - compiler: add compiler.h header
   - commands: return -1 on lxc_cmd_get_init_pid() err
   - tests: add basic.c
   - tests: cleanup Makefile
   - commands: ensure -1 is sent on EPIPE for init pid
   - macro: add LXC_AUDS_ADDR_LEN
   - macro: move LXC_CMD_DATA_MAX from commands.h
   - macro: add PTR_TO_INT() and INT_TO_PTR()
   - macro: add INTTYPE_TO_STRLEN()
   - caps: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
   - cgfsng: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
   - confile: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
   - log: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
   - lsm: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
   - macro: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
   - lxccontainer: s

[Touch-packages] [Bug 1799947] Re: [radeon] Application windows in 18.04.01 go black but launcher is still visible

2018-11-23 Thread Paul Chambre
Took me a while to figure out how to enable Wayland. Apparently
WaylandEnable needs to be set explicitly to true in custom.conf to
appear in the login choices. Running with it now... One thing I can say
is that it seems to have fixed a problem where my entire Gnome session
would crash when I tried to open a 10MP JPG.

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

Title:
  [radeon] Application windows in 18.04.01 go black but launcher is
  still visible

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Intermittently and randomly, all application windows will go black.
  They are still there, and can be interacted with with keyboard
  shortcuts or if you know where to click with the mouse, but they are
  not drawn.

  The launcher itself is still displayed.

  Clicking Show Applications briefly draws the application window before
  switching to the background and application icons. The application
  icons are shown correctly. Selecting one switches to a black window
  for that application. The application window is again briefly
  displayed when dismissing the application icons by again clicking Show
  Applications.

  TTYs work normally.

  Killing gnome (from another TTY) and allowing it to relaunch results
  in a normal display again.

  This is being seen on an hp 6910p. This system also exhibits a
  corrupted lock screen since upgrade to 18.04.01. Neither of these
  behaviors were seen during two years running 16.04.01.

  Chrome is being used. Current 70.00.3538.77 (64-bit). Chrome is the
  most commonly used application on this machine, so it is possible that
  the behavior is being triggered by Chrome, however, the behavior
  affects all applications, including system applications like software
  update and terminal.

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

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


[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

2018-11-23 Thread Launchpad Bug Tracker
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/1804847

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  
  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
i->uid_set ? i->uid : UID_INVALID,
i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  
  Any help fixing this problem would be highly appreciated. 
  Many thanks,
  Rafael

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

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


[Touch-packages] [Bug 1804864] [NEW] autopkgtest regression TEST-22-TMPFILES are note executable

2018-11-23 Thread Dimitri John Ledkov
Public bug reported:

[Impact]

 * Newly added testcase in a security upload used a traditional GNU
patch format, instead of using extended git patch format, as supported
by GNU patch. Therefore, executable bits on shells scripts were lost,
resulting in autopkgtest failures.

[Test Case]

 * `upstream` test/TEST-22-TMPFILES autopkgtest case should pass.


[Regression Potential] 

 * This is testcode change only.

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

Title:
  autopkgtest regression TEST-22-TMPFILES are note executable

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Newly added testcase in a security upload used a traditional GNU
  patch format, instead of using extended git patch format, as supported
  by GNU patch. Therefore, executable bits on shells scripts were lost,
  resulting in autopkgtest failures.

  [Test Case]

   * `upstream` test/TEST-22-TMPFILES autopkgtest case should pass.

  
  [Regression Potential] 

   * This is testcode change only.

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

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


[Touch-packages] [Bug 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

2018-11-23 Thread Jacques Beckand
Same problem for me with Lubuntu 18.04 System freezes at random times. Screen 
is then completely filled with non-sens signs. Graphic card is NVIDIA GeForce 
6150SE nForce 430. Driver is Nouveau.
Thanks beforehand for your help.

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

Title:
  [GeForce 6150SE nForce 430] PC freezes and crashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  WORKAROUND: Use PPA from https://launchpad.net/~oibaf/+archive/ubuntu
  /graphics-drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  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: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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


[Touch-packages] [Bug 1803743] Re: Sometimes the sound disappears

2018-11-23 Thread Zepem
Thanks.
I am do journalctl -b> justafter.txt when sound disappears. 

** Attachment added: "justafter.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803743/+attachment/5215718/+files/justafter.txt

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

Title:
  Sometimes the sound disappears

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Здравствуйте!
  С переходом на 16.04 lts на моем компьютере иногда стал пропадать звук.  
Определить по какой причине так и не получилось. Если звук пропадает то 
помогает только перезагрузка. Обращался на форум, но безрезультатно 
https://forum.ubuntu.ru/index.php?topic=278602.0   Пару раз переустанавливал 
Убунту 16.04 и один раз Убунту 18.04 - но проблема осталась. Востанавливал по 
инструкции https://help.ubuntu.com/community/SoundTroubleshootingProcedure. 
Первых два шага не помогают. Проблема остается и звук появляется только при 
перезагрузке. Третий шаг это задать вопрос здесь, что я собственно и делаю.  В 
третьем шаге предлагается специальный скрипт, который собирает всю необходимую 
информацию о системе и публикует ее на сайте. вот ссылка на отчет о моей 
системе в момент когда звук отсутствует 
http://www.alsa-project.org/db/?f=e3512ce403985434442eb1d4b4905e5bcab76ac8 
  Помогите, пожалуйста.

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  1288 F pulseaudio
   /dev/snd/controlC0:  a  1288 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: None
  dmi.board.name: H61MLV2
  dmi.board.vendor: BIOSTAR Group
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/02/2012:svnBIOSTARGroup:pnH61MLV2:pvr6.0:rvnBIOSTARGroup:rnH61MLV2:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.family: None
  dmi.product.name: H61MLV2
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group

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

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


[Touch-packages] [Bug 1804856] [NEW] package apport-gtk 2.20.9-0ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2018-11-23 Thread Javier Trenti
Public bug reported:

Hi, this happens after an actualization. Yesterday Ubuntu reported an phyton 
error when uppdating, and today 2 errors from Ubuntu Gnome-shell.
I hope you can fix it.
Regards.

Javier

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: apport-gtk 2.20.9-0ubuntu7.5
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportLog:
 
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
 firefox:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Nov 23 12:22:51 2018
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2018-08-01 (114 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: apport
Title: package apport-gtk 2.20.9-0ubuntu7.5 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package apport-gtk 2.20.9-0ubuntu7.5 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

Status in apport package in Ubuntu:
  New

Bug description:
  Hi, this happens after an actualization. Yesterday Ubuntu reported an phyton 
error when uppdating, and today 2 errors from Ubuntu Gnome-shell.
  I hope you can fix it.
  Regards.

  Javier

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: apport-gtk 2.20.9-0ubuntu7.5
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Nov 23 12:22:51 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2018-08-01 (114 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: apport
  Title: package apport-gtk 2.20.9-0ubuntu7.5 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

2018-11-23 Thread Sebastien Bacher
@SRU team, undo the previous request, we are going to backport the
required systemd changes

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed
Status in xkeyboard-config source package in Disco:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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


[Touch-packages] [Bug 1803059] Re: Nullpointer dereference

2018-11-23 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ Evince segfaults on some pdf documents
+ 
+ * Test case
+ Download and try to open 
https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't 
segfault
+ 
+ * Regression potential
+ Nothing special to test, make sure evince still opens pdfs without issue
+ 
+ -
+ 
  System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10
  10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  
  Evince version: GNOME Document Viewer 3.28.4
  
  While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04
  LTS), a null-pointer dereference was observed, initially this was
  reported to evince but the evince team advised that the issue is in
  poppler, the library used by evince to render PDF, poppler version:
  0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however the
  issue is already fixed in poppler 0.70, but this will still crash your
  evince v3.28.4 in ubuntu if poppler is not updated to v.0.70.
  
  Fuzzing result showing a very important vulnerability in a package
  currently shipped by a major Linux distribution is still of interest,
  even if that Linux distribution does not package the latest released
  upstream version. I think Ubuntu is still using,
  
  Source: poppler
  Version: 0.62.0-2ubuntu2.2
  
  So, most of the systems will be affected to this issue.
  
  Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664

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

Title:
  Nullpointer dereference

Status in poppler package in Ubuntu:
  Fix Committed

Bug description:
  * Impact
  Evince segfaults on some pdf documents

  * Test case
  Download and try to open 
https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't 
segfault

  * Regression potential
  Nothing special to test, make sure evince still opens pdfs without issue

  -

  System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10
  10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Evince version: GNOME Document Viewer 3.28.4

  While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04
  LTS), a null-pointer dereference was observed, initially this was
  reported to evince but the evince team advised that the issue is in
  poppler, the library used by evince to render PDF, poppler version:
  0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however
  the issue is already fixed in poppler 0.70, but this will still crash
  your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70.

  Fuzzing result showing a very important vulnerability in a package
  currently shipped by a major Linux distribution is still of interest,
  even if that Linux distribution does not package the latest released
  upstream version. I think Ubuntu is still using,

  Source: poppler
  Version: 0.62.0-2ubuntu2.2

  So, most of the systems will be affected to this issue.

  Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664

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

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


[Touch-packages] [Bug 1804848] [NEW] Constant subscription requests despite being denied

2018-11-23 Thread Andreas Schildbach
Public bug reported:

I keep getting subscription requests by 2 unknown people, every couple
of hours. I denied and banned these requests numerious times over the
past months, but I keep getting them. Sometimes, there are 20 or more of
these confirmation dialog windows open when I return to my computer.

I'd argue the bad/deny buttons are not working.

Also, the requests should not open on top of each other. If someone
sends multiple requests without me reacting, only the last one is
relevant to me.

I'm using a Google Talk account which is registered to my own domain.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: telepathy-gabble 0.18.4-1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 23 15:40:21 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-21 (945 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: telepathy-gabble
UpgradeStatus: Upgraded to bionic on 2018-04-26 (210 days ago)

** Affects: telepathy-gabble (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Description changed:

  I keep getting subscription requests by 2 unknown people, every couple
  of hours. I denied and banned these requests numerious times over the
  past months, but I keep getting them. Sometimes, there are 20 or more of
  these confirmation dialog windows open when I return to my computer.
  
  I'd argue the bad/deny buttons are not working.
  
  Also, the requests should not open on top of each other. If someone
  sends multiple requests without me reacting, only the last one is
  relevant to me.
+ 
+ I'm using a Google Talk account which is registered to my own domain.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: telepathy-gabble 0.18.4-1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 23 15:40:21 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-21 (945 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: telepathy-gabble
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (210 days ago)

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

Title:
  Constant subscription requests despite being denied

Status in telepathy-gabble package in Ubuntu:
  New

Bug description:
  I keep getting subscription requests by 2 unknown people, every couple
  of hours. I denied and banned these requests numerious times over the
  past months, but I keep getting them. Sometimes, there are 20 or more
  of these confirmation dialog windows open when I return to my
  computer.

  I'd argue the bad/deny buttons are not working.

  Also, the requests should not open on top of each other. If someone
  sends multiple requests without me reacting, only the last one is
  relevant to me.

  I'm using a Google Talk account which is registered to my own domain.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: telepathy-gabble 0.18.4-1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 23 15:40:21 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-21 (945 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: telepathy-gabble
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (210 days ago)

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

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


[Touch-packages] [Bug 1804847] [NEW] systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

2018-11-23 Thread Chris E
Public bug reported:

The following description is taken from:

https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237


Hello everyone,
I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After a 
recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php failed: 
Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp failed: 
Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/log/journal 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

To verify I tried this:

/usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
Reading config file "elasticsearch.conf".
Running create action for entry d /var/run/elasticsearch
Found existing directory "/var/run/elasticsearch".
"/run/elasticsearch" has right mode 40755
chown "/run/elasticsearch" to 120.128
fchownat() of /run/elasticsearch failed: Invalid argument

I can manually chown the directories, e.g. "chown
elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
service successfully.  My suspicion is, this is related to an upgrade of
systemd to 229-4ubuntu21.8.

At this point I don't know what to do.

I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
Tag v237 (and earlier, including 229):
/.../
if (chown(fn,
  i->uid_set ? i->uid : UID_INVALID,
  i->gid_set ? i->gid : GID_INVALID) < 0)
return log_error_errno(errno, "chown(%s) 
failed: %m", path);
}
/.../

Tag v238

/.../
if (fchownat(fd,
 "",
 i->uid_set ? i->uid : UID_INVALID,
 i->gid_set ? i->gid : GID_INVALID,
 AT_EMPTY_PATH) < 0)
return log_error_errno(errno, "fchownat() of %s failed: %m", path);
/.../


Any help fixing this problem would be highly appreciated. 
Many thanks,
Rafael

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  New

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  
  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 

[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

2018-11-23 Thread Dimitri John Ledkov
@SRU team, actually we will cherrypick more things into systemd, to make
systemd & xkeyboard-config play nice with each other, as is destined to
be upstream and in disco.

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

** Also affects: xkeyboard-config (Ubuntu Disco)
   Importance: Low
   Status: Fix Released

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: libxkbcommon (Ubuntu Disco)
   Importance: Undecided
   Status: Fix Released

** Also affects: xorgproto (Ubuntu Disco)
   Importance: Undecided
   Status: Fix Released

** No longer affects: libxkbcommon (Ubuntu Disco)

** No longer affects: xorgproto (Ubuntu Disco)

** No longer affects: systemd (Ubuntu)

** No longer affects: systemd (Ubuntu Disco)

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

** No longer affects: systemd (Ubuntu)

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed
Status in xkeyboard-config source package in Disco:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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


[Touch-packages] [Bug 1804437] Re: Saving new password for VPN (IPSec) fails silently

2018-11-23 Thread Bug Watch Updater
** Changed in: network-manager
   Status: Unknown => Confirmed

** Changed in: network-manager
   Importance: Unknown => Medium

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

Title:
  Saving new password for VPN (IPSec) fails silently

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

Bug description:
  Ubuntu: 18.04
  Involved packages (non-exhaustive list): network-manager, vpnc

  Steps to reproduce:
  1) Open "Network Connections" dialog
  2) Add a non-existing entry for a working IPSec VPN connection, fill all 
required fields but enter a wrong password
  3) Save the entry
  4) Edit entry again, put in the correct password, make sure to fill all 
required fields
  5) Save the entry
  6) Open Edit view of the entry again to verify that the password has not been 
changed with last save action. 

  Expected behavior:
  Either password should be stored when modified and saved -OR- user should be 
notified that password could not be saved for whatever reason. 

  Work-around:
  Delete whole VPN entry and create a new one with the correct password entered 
from the beginning.

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

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


[Touch-packages] [Bug 1784347] Re: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath

2018-11-23 Thread Sebastien Bacher
the previous comment suggests it should be verification-done-bionic
right?

** Tags added: verification-done-bionic

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

Title:
  ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
  partitions name for the mpath

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Bionic:
  Fix Committed

Bug description:
  
  [Impact]
  Any user of Ubuntu on multipath, where the default path separator has been 
changed to something else. This possibly affects other scenarios where the 
partition separator can be changed.

  [Test case]
  1) Install Ubuntu on multipath system
  2) Change /etc/multipath.conf to set "path_separator" to "" or "p".
  3) Reboot
  4) Run 'sudo fdisk -l /dev/mapper/mpathX', to display a device's partitions 
where the path separator would be visible.

  
  [Regression potential]
  Minimal. This only affects display. Default separator on Ubuntu remains 
"-part". If the separator is not one of "", "p", or "-part", then "-part" would 
be used, as is already the case.

  
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-09 11:14:07 
==
  We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the 
Emulex adapter to have the mpath disk.
  Running the fdisk -l and ls -l showing the conflict name for the mpath.

  :~# uname -a
  Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp4:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part1   2048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2  419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3  838862848 1258291199 419428352  200G 83 Linux

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:04 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha3 -> ../dm-3

  == Comment: #2 - Chanh H. Nguyen  - 2018-01-09 11:35:04 
==
  I just modify the partitions and it is still showing the conflicting name on 
partitions.

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha3 -> ../dm-3
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha4 -> ../dm-4
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha5 -> ../dm-5
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha6 -> ../dm-6
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha7 -> ../dm-7
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha8 -> ../dm-8

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot  StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part12048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2   419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3   838862848  964691967 125829120   60G 83 Linux
  /dev/mapper/mpatha-part4   964691968 1258291199 293599232  140G  5 
Extended
  /dev/mapper/mpatha-part5   964694016 1006637055  41943040   20G 83 Linux
  /dev/mapper/mpatha-part6  1006639104 1048582143  41943040   20G 83 Linux
  /dev/mapper/mpatha-part7  1048584192 1090527231  41943040   20G 83 Linux
  /dev/mapper/mpatha-part8  1090529280 1132472319  41943040   20G 83 Linux

  == Comment: #5 - Kyle Mahlkuch  - 2018-06-26 13:50:

[Touch-packages] [Bug 1655033] Re: cannot update system software

2018-11-23 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Unfortunately, we could work on this bug report because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!


** Package changed: xorg (Ubuntu) => ubuntu

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

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

Title:
  cannot update system software

Status in Ubuntu:
  Incomplete

Bug description:
  cannot update or upgrade system software, system slowed up  abit while
  transferring data

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
  Uname: Linux 3.2.0-29-generic-pae i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  Date: Mon Jan  9 19:38:28 2017
  DistUpgraded: 2017-01-09 19:26:42,244 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.1.12, 3.2.0-26-generic-pae, i686: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:5004]
  InstallationMedia: Custom 12.04 - Release i386
  MachineType: LENOVO 3464A69
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic-pae 
root=UUID=9ce4bf3e-0ad1-4283-a652-c7df176ea992 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to precise on 2017-01-09 (0 days ago)
  dmi.bios.date: 05/09/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H2ET31WW(1.09)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3464A69
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH2ET31WW(1.09):bd05/09/2012:svnLENOVO:pn3464A69:pvrLenovoE49:rvnLENOVO:rn3464A69:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3464A69
  dmi.product.version: Lenovo E49
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.7.8-0ubuntu1
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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


[Touch-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

2018-11-23 Thread craig jackson
Re above comment, the UX533 also has the ALC294. I should have made this
clear in that comment.

Thanks,
Craig

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1791484] Re: [FFe] Update tracker and tracker-miners to 2.1.4

2018-11-23 Thread Launchpad Bug Tracker
This bug was fixed in the package tracker-miners - 2.1.5-1build1

---
tracker-miners (2.1.5-1build1) disco; urgency=medium

  * No-change rebuild for icu soname changes.

 -- Matthias Klose   Tue, 13 Nov 2018 09:05:07 +0100

** Changed in: tracker-miners (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  [FFe] Update tracker and tracker-miners to 2.1.4

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker-miners package in Ubuntu:
  Fix Released

Bug description:
  To go along with the rest of GNOME 3.30
  Both tracker and tracker-miners 2.1.4 will be synced from Debian. 

  tracker is not installed by default on any Ubuntu Flavours, but does
  provide an important part of the GNOME-Shell experience.

  These releases bring lots of fixes and a few new features.

  Tracker NEW in 2.1.4 - 2018-09-04
  =

* Fix build with format-security flag

  Translations: da, hr, lv

  NEW in 2.1.3 - 2018-08-30
  =

* Fix resource refcounting issues in database. Reset is advised.
* Drop cardinality from nie:copyright, nie:license, nie:legal and dc:rights
* Fix superfluous ontology checks on second tracker-store run
* Use more SPARQL1.1 correct syntax.
* Allow use of domain rules outside prefix
* Compatibility fixes with C++

  Translations: gl, id, ko

  NEW in 2.1.2 - 2018-08-15
  =

* libtracker-sparql: Delete TrackerResource elements one by one
* libtracker-sparql: Fix compilation with C++
* build: Fixes for FreeBSD
* build: Fixes on meson

  Translations: cs, el, fr, fur, hu, sl, tr, zh_TW

  NEW in 2.1.1 - 2018-08-01
  =

* libtracker-direct: Plug leaks
* libtracker-sparql-backend: Fix fallback from direct to bus
  connection for queries.

  Translations: es, lt, ro

  NEW in 2.1.0 - 2018-07.22
  =

* Brown paper bag release
* All features from unreleased 2.0.5 apply
* One feature was missed: TrackerResource is now able to output
  JSON-LD. This is a new API call, so a minor bump should happen
  as per Semantic Versioning.

From 2.0.5 NEWS:
* build: Make tarballs able to build with meson. Future releases will
  eventually phase out Autotools
* build: Various meson build fixes
* tests: Many fixes to functional tests
* libtracker-miner: Fixed race conditions that may result in spurious
  "parent not indexed yet" warnings.
* libtracker-direct: Majorly rewritten
* tracker-store: Streamlined to use a libtracker-direct connection
  instead of reimplementing most of it.

  Tracker-miners NEW in 2.1.4 - 2018-09-04
  =

  Translations: da, hr, lv

  NEW in 2.1.3 - 2018-08-30
  =

* Unbreak watch on domain ontology owner. Fixes miners spuriously
  exiting.

  NEW in 2.1.2 - 2018-08-30
  =

* Allow use of domain rules outside prefix
* Add core-as-subproject as explicit meson option
* Ensure utf8ness in TrackerResource helpers
* Fix multiple cardinality issues in different extractors/properties
* Other minor SPARQL correctness fixes

  Translations: gl, id, ko

  NEW in 2.1.1 - 2018-08-15
  =

* tracker-miner-fs: Ignore mercurial repositories
* build: Fix build with -Werror=format-security
* tracker-extract: Ensure metadata strings are UTF-8 in JPEG/PNG extractors
* tracker-extract: Do not add named destinations to PDF TOCs
* tracker-extract: Ignore XMP image metadata on PDFs
* tracker-extract: Fix ISO 8601 date string generation on gstreamer 
extractor

  Translations: cs, el, fr, fur, hu, lt, sl, tr, zh_TW

  NEW in 2.1.0 - 2018-07-23
  =

* tests: Many updates and fixes to functional tests
* tracker-extract: Better infrastructure for tests, based on JSON-LD
* tracker-miner-fs: Restart tracker extract from the right domain
* tracker-extract: Persistently avoid files that trigger recoverable
  errors, to avoid log spamming on restarts.

  Translations: de, es, it, pl, pt_BR, ro, sv

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

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


[Touch-packages] [Bug 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

2018-11-23 Thread Launchpad Bug Tracker
This bug was fixed in the package qttools-opensource-src - 5.11.2-5

---
qttools-opensource-src (5.11.2-5) unstable; urgency=medium

  * Build qdoc with QDOC_PASS_ISYSTEM defined. This is needed because qmake
passes Qt include directories as -isystem flags, not as regular -I.
See QTBUG-70896, LP: #1799111.

 -- Dmitry Shachnev   Thu, 15 Nov 2018 11:03:30
+0300

** Changed in: qttools-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in qttools-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Cosmic:
  New
Status in qtdeclarative-opensource-src source package in Cosmic:
  New
Status in qttools-opensource-src source package in Cosmic:
  New
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.

  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine,
  etc.).

  To properly fix this bug, we need changes in qtbase and qttools
  modules. In addition, I will be uploading a no-change rebuild of
  qtdeclarative module to demonstrate that the fixes work.

  If requested, I can also upload no-change rebuilds of some other
  modules to get their -doc packages properly regenerated.

  [Test Case]
  For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.

  For qtdeclarative5-doc-html:
  1. Install qtdeclarative5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.

  [Regression Potential]
  The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.

  The proposed change in qttools can affect more packages. It can result
  in qdoc passing more -isystem flags to clang code analyzer. I am not
  aware of negative consequences of this, but if they happen, these
  consequences will be limited to potential build failures or wrong
  documentation contents.

  [Other Info]
  Description of the fix:

  qdoc is a tool that parses C++ source files and generates
  documentation from them. Recently, qdoc began using clang instead of
  its own C++ parser. Clang needs the C++ standard library to work.
  Starting with llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard
  library is no longer on clang’s default search paths, so we need to
  pass it explicitly as -I flag. The proposed qtbase patch
  (qdoc_default_incdirs.diff) does that.

  That patch fixes documentation build for qtbase, but for other modules
  there is another problem. The Qt headers are installed into
  /usr/include//qt5 directory, but it is also not on Clang
  default search path. qmake passes these directories as -isystem flags,
  but qdoc ignores -isystem by default, unless it is built with
  QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is
  building with this define.

  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

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

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


[Touch-packages] [Bug 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

2018-11-23 Thread Launchpad Bug Tracker
This bug was fixed in the package qtbase-opensource-src - 5.11.2+dfsg-
7ubuntu1

---
qtbase-opensource-src (5.11.2+dfsg-7ubuntu1) disco; urgency=medium

  * Merge from Debian Sid. Remaining changes:
- Add arm64 to the architectures that GLES is enabled on.
- Drop build dependency on libpcre2-dev which is in Universe; configure
  without -system-pcre.

 -- Rik Mills   Mon, 19 Nov 2018 15:49:12 +

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in qttools-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Cosmic:
  New
Status in qtdeclarative-opensource-src source package in Cosmic:
  New
Status in qttools-opensource-src source package in Cosmic:
  New
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.

  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine,
  etc.).

  To properly fix this bug, we need changes in qtbase and qttools
  modules. In addition, I will be uploading a no-change rebuild of
  qtdeclarative module to demonstrate that the fixes work.

  If requested, I can also upload no-change rebuilds of some other
  modules to get their -doc packages properly regenerated.

  [Test Case]
  For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.

  For qtdeclarative5-doc-html:
  1. Install qtdeclarative5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.

  [Regression Potential]
  The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.

  The proposed change in qttools can affect more packages. It can result
  in qdoc passing more -isystem flags to clang code analyzer. I am not
  aware of negative consequences of this, but if they happen, these
  consequences will be limited to potential build failures or wrong
  documentation contents.

  [Other Info]
  Description of the fix:

  qdoc is a tool that parses C++ source files and generates
  documentation from them. Recently, qdoc began using clang instead of
  its own C++ parser. Clang needs the C++ standard library to work.
  Starting with llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard
  library is no longer on clang’s default search paths, so we need to
  pass it explicitly as -I flag. The proposed qtbase patch
  (qdoc_default_incdirs.diff) does that.

  That patch fixes documentation build for qtbase, but for other modules
  there is another problem. The Qt headers are installed into
  /usr/include//qt5 directory, but it is also not on Clang
  default search path. qmake passes these directories as -isystem flags,
  but qdoc ignores -isystem by default, unless it is built with
  QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is
  building with this define.

  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

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

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


[Touch-packages] [Bug 1804417] Re: runuser doesn't authenticate PAM modules

2018-11-23 Thread Tobias Karnat
As a workaround we now use the following configuration as the maintainer
suggested to us:

# cat /etc/pam.d/runuser
#%PAM-1.0
authsufficient  pam_rootok.so
session requiredpam_localuser.so

Which works as well:
# runuser domainuser
runuser: cannot open session: Permission denied

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

Title:
  runuser doesn't authenticate PAM modules

Status in util-linux package in Ubuntu:
  New

Bug description:
  We use the pam_localuser.so PAM module to authenticate only local users for 
root to become.
  Because we don't want that root can become a domain user (as we use sssd with 
ad integration).

  This works well with the su program, but fails with runuser.
  We added the following in front of pam_rootok.so in the files /etc/pam.d/su 
and runuser:
  authrequiredpam_localuser.so

  As I have found out, this behaviour can easily be changed by applying the 
following patch:
  diff -urN util-linux-2.31.1/login-utils/su-common.c 
util-linux-2.31.1/login-utils/su-common.c
  --- util-linux-2.31.1/login-utils/su-common.c   2018-11-21 10:56:05.100179733 
+0100
  +++ util-linux-2.31.1/login-utils/su-common.c   2018-11-21 11:10:40.458312830 
+0100
  @@ -709,7 +709,6 @@
   */
  if (su->restricted)
  errx(EXIT_FAILURE, _("may not be used by non-root 
users"));
  -   return;
  }

  rc = pam_authenticate(su->pamh, 0);

  And it works as expected:
  # runuser domainuser
  runuser: Permission denied

  However, we would always need to recompile util-linux as new security
  updates come out.

  Could this please be applied to the Ubuntu repository and backported for 
bionic?
  I will contact the util-linux maintainer separately in order to get this 
upstream.

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

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


[Touch-packages] [Bug 881137] Re: UFW does not clean iptables setting from /etc/ufw/before.rules

2018-11-23 Thread Maciej Andrzejewski
Is this going to work? 
It was reported on 2011 and last comment on 2015.
It is 2018 and still after restarting ufw rules are added multiple time.
Just add this:
/etc/ufw/after_up
/etc/ufw/after_down
/etc/ufw/before_up
/etc/ufw/before_down

User can manualy add rules to *_up executed when ufw starts and add
rules to be deleted to *_down when ufw is shutting down.

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

Title:
  UFW does not clean iptables setting from /etc/ufw/before.rules

Status in ufw package in Ubuntu:
  Won't Fix

Bug description:
  Adding some additional settings to /etc/ufw/before.rules is not
  deleted when ufw is stopped.

  I added these lines at top of file /etc/ufw/before.rules

  *nat
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE
  COMMIT

  Then I reloaded ufw firewall with command: ufw reload. Output from
  iptables-save

  $ iptables-save -t nat
  *nat
  :PREROUTING ACCEPT [4:478]
  :INPUT ACCEPT [4:478]
  :OUTPUT ACCEPT [0:0]
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE 
  COMMIT

  Then I reloaded ufw firewall again:

  $ iptables-save -t nat
  *nat
  :PREROUTING ACCEPT [4:478]
  :INPUT ACCEPT [4:478]
  :OUTPUT ACCEPT [0:0]
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE 
  -A POSTROUTING -o eth0 -j MASQUERADE 
  COMMIT

  And ufw reload again

  $ iptables-save -t nat
  *nat
  :PREROUTING ACCEPT [4:478]
  :INPUT ACCEPT [4:478]
  :OUTPUT ACCEPT [0:0]
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE 
  -A POSTROUTING -o eth0 -j MASQUERADE 
  -A POSTROUTING -o eth0 -j MASQUERADE
  COMMIT

  And again and postrouting is never deleted when ufw is stopped and
  added again when stared. Same happen if I stop ufw firewall with: $
  stop ufw. nat lines are not cleaned.

  UFW should remove all iptables settings specified in config files
  after ufw is stopped! This can be dangerous if apt-get is updating
  some ufw files and scripts needs to reload ufw (some lines will be
  more times).

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

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


[Touch-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

2018-11-23 Thread AaronMa
** Description changed:

- After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on
- Lenovo 11e 2nd gen machines.
+ SRU:
+ 
+ 
+ [Impact]
+ ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
+ PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
+ runtime suspend mode in old touchpad fw.
+ Then touchpad will not work.
+ LEN2040 on 11e 3rd can reproduce this issue by passing
+ psmouse.synaptics_intertouch=1
+ 
+ These 2 pnp device should be the same one Synaptics s3203_ver5.
+ 
+ [Fix]
+ i2c-i801 should auto suspend when not used, no need runtime pm.
+ 
+ [Test Case]
+ Tested on Thinkpad 11e 3rd.
+ Touchpad works fine.
+ 
+ [Regression Potential]
+ Low, upstream fix cherry-picked.
+ 
+ 4.18 kernel patch, no need for cosmic.
+ 
+ 
+ Original bug report:
+ =
+ After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.
  
  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.
  
  We are currently working around the issue by deploying our own blacklist
  files.
  
  Here is a link to the SRU justification: https://bugs.launchpad.net/hwe-
  next/+bug/1786574

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Incomplete
Status in kmod source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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


[Touch-packages] [Bug 1659534] Re: userdel doesn't supports extrausers

2018-11-23 Thread Stefan Nilsson
** Changed in: snappy
   Status: New => Confirmed

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  Confirmed
Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

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

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