[Touch-packages] [Bug 1829872] Re: No more desktop effects since libdrm upgrade in Bionic

[Thomas Nemeth]

Radeon module blacklisted: nothing changed.

$ lsmod | grep radeon
$

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

Title:
  No more desktop effects since libdrm upgrade in Bionic

Status in libdrm package in Ubuntu:
  Incomplete

Bug description:
  Hello.

  I upgraded my system on 2019-05-09 and since then desktop effects do not work 
anymore. It installed
  a new libdrm stack :

  $ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk 
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
   libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)
  --
   libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)
  --
   libdrm2:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)
  --
   libdrm-intel1:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)
  --
   libdrm-radeon1:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)
  --
   libdrm-common:amd64 (2.4.95-1~18.04.1
   2.4.97-1ubuntu1~18.04.1)

  I have an ATI Radeon that was working fine with KDE until then. I waited to 
see if someone had realized it before creating a bug report... It really is 
annoying : no more transparency, no
  more auto-hide of windows : my workflow is strongly impacted.

  System information :

  $ lsb_release -rd
  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  $ apt-cache policy libdrm2
  libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
   Table de version :
   *** 2.4.97-1ubuntu1~18.04.1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.4.95-1~18.04.1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   2.4.91-2 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:06b2]
  InstallationDate: Installed on 2018-05-05 (397 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Inspiron 5759
  Package: libdrm (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 05NVNV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5759
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1830340] Re: icu 63.2 makes acorn ftbfs (*** stack smashing detected ***: terminated)

[Bug Watch Updater]

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

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

Title:
  icu 63.2 makes acorn ftbfs (*** stack smashing detected ***: 
  terminated)

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

Bug description:
  https://launchpad.net/ubuntu/+source/acorn/5.5.3+ds3-3/+build/16839533

  As you can see, the package is now FTBFS.

  I traced down this to be an icu problem, by starting from a disco
  chroot and then manually upgrading packages until I got the icu
  update.

  I can confirm also icu from debian experimental (and Debian chroot)
  has the same issue.

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

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

[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

[harrytonny]

There are several users are facing these issues related update errors on
their Ubuntu based systems. To resolve these errors can take help from
https://oniton.com/blog/netgear-ex6100-setup/ that will be significant
for them.

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Triaged
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Touch-packages] [Bug 1832141] Re: Panel applets crashing on start

[Daniel van Vugt]

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

Title:
  Panel applets crashing on start

Status in libwnck package in Ubuntu:
  New

Bug description:
   
  SEveral panel applets on both top and right panels. Workspace switcher and 
text output applets raise error dialog on GUI session start. MATE.

  This does not happen to all text output applets and not always the
  same ones. But the workspace switcher (set to 3x3 table) has become
  consistent in the last few days.

  The journal has the following error

  
  The program 'wnck-applet' received an X Window System error.
  This probably reflects a bug in the 
program.
  The error was 'RenderBadPicture 
(invalid Picture parameter)'.
(Details: serial 4910 error_code 
143 request_code 139 (RENDER) minor_code 7)
(Note to programmers: normally, X 
errors are reported asynchronously;
 that is, you will receive the 
error a while after causing it.
 To debug your program, run it with 
the GDK_SYNCHRONIZE environment
 variable to change this behavior. 
You can then get a meaningful
 backtrace from your debugger if 
you break on the gdk_x_error() function.)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Sun Jun  9 12:39:06 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2019-04-25 (45 days ago)
  InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=7a6ead44-b94a-4058-8c40-fda725ccedba ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  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.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N501VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~

[Touch-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

[Daniel van Vugt]

** Summary changed:

- Login freeze during boot after upgrade
+ Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

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

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

** Tags added: vmware

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

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

Status in gdm3 package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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

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

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

[Touch-packages] [Bug 1832133] Re: Mouse unresponsive on Ubuntu 18.04

[Daniel van Vugt]

The only hint of a problem I can see is this from the kernel log:

[ 6402.282272] usb 5-2: USB disconnect, device number 2
[ 6405.688387] usb 5-2: new low-speed USB device number 3 using xhci_hcd
[ 6405.863785] usb 5-2: New USB device found, idVendor=1241, idProduct=
[ 6405.863792] usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 6405.884749] input: HID 1241: as 
/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.0/0003:1241:.0003/input/input19
[ 6405.885322] hid-generic 0003:1241:.0003: input,hidraw1: USB HID v1.00 
Mouse [HID 1241:] on usb-:00:10.0-2/input0

which is concurred by the Xorg log:

[  6402.353] (II) config/udev: removing device HID 1241:
[  6402.353] (**) Option "fd" "29"
[  6402.353] (II) event11 - HID 1241:: device removed
[  6402.361] (II) UnloadModule: "libinput"
[  6402.361] (II) systemd-logind: releasing fd for 13:75
[  6405.965] (II) config/udev: Adding input device HID 1241: 
(/dev/input/mouse2)
[  6405.965] (II) No input driver specified, ignoring this device.
[  6405.965] (II) This device may have been added with another device file.

That suggests the mouse got disconnected and reconnected after 1h46m.

Please reproduce the problem again and as soon as it happens run:

  dmesg > dmesg.txt

and send us the file 'dmesg.txt'.

Please also try a different mouse to see if that avoids the problem.

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

** Changed in: linux (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/1832133

Title:
  Mouse unresponsive on Ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi there,

  I submitted this bug report following advice in
  https://wiki.ubuntu.com/DebuggingMouseDetection

  I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart
  15 Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and
  rarely boot up Windows.

  I use an optical mouse attached to my computer by USB cable. It works
  perfectly on Windows. But on Ubuntu, it will work OK for a couple of
  seconds, but then become less and less responsive, to the point where
  it barely works at all.

  I have a touchpad that works perfectly in both Windows and Ubuntu.

  Result of lsb_release -rd: Description:   Ubuntu 18.04.2 LTS. Release:
18.04
  I am using Xdiagnose version 3.8.8

  Please help!

  Tom.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 17:03:12 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7600G] [103c:216b]
  InstallationDate: Installed on 2018-01-22 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=f7ecd954-9bbe-4c06-9514-a1366c47b763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216B:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion TS 15 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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
  xserver.bootTime: Wed Oct 31 01:15:25 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directo

[Touch-packages] [Bug 1832078] Re: two start need

[Daniel van Vugt]

It sounds like you are saying the first start fails and the second start
succeeds. If that is correct then on the second start please run:

  journalctl -b-1 > prevboot.txt

and send us the file 'prevboot.txt'.

** Tags added: radeon

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

Title:
  two start need

Status in Ubuntu:
  Incomplete

Bug description:
  i don't speak english

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jun  8 05:09:13 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:144b]
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobility Radeon HD 5650 [103c:144b]
  InstallationDate: Installed on 2019-05-11 (28 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=ce1ae318-35fe-47bc-8fb6-7a2662550abd ro quiet splash radeon.audio=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 144B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 65.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.23:bd10/21/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058911242B20010020100:rvnHewlett-Packard:rn144B:rvr65.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 058911242B20010020100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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: Sat Jun  8 04:55:57 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1832106] Re: Some packages could not be installed

[Daniel van Vugt]

Can you please send us a screenshot or photo of the problem you are
experiencing?

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

Title:
  Some packages could not be installed

Status in Ubuntu:
  Incomplete

Bug description:
  sudo apt-get install xserver-xorg-video-intel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  8 12:10:54 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc]
  InstallationDate: Installed on 2019-06-06 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=4c3f6446-77d8-4152-8446-dbda7f591ea6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.21.6
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.6:bd05/20/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.product.sku: 06DC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1832004] Re: [amdgpu] display hanging after laptop opens lid

[Daniel van Vugt]

Please:

1. Reproduce the hang again.

2. Reboot and then immediately run:

   journalctl -b-1 > prevboot.txt

   and send us the file 'prevboot.txt'.


** Summary changed:

- display hanging after laptop opens lid
+ [amdgpu] display hanging after laptop opens lid

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Tags added: amdgpu

** Changed in: xserver-xorg-video-amdgpu (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/1832004

Title:
  [amdgpu] display hanging after laptop opens lid

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  7 14:56:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 5.0.0-15-generic, x86_64: installed
   anbox, 1, 5.0.0-16-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1043:1680]
  InstallationDate: Installed on 2018-08-03 (308 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. E402BA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=c593d94b-7cc0-45ca-a012-f79a49d00093 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E402BA.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E402BA
  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.:bvrE402BA.311:bd09/06/2018:svnASUSTeKCOMPUTERINC.:pnE402BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: E402BA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1832004/+subscriptions

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

[Touch-packages] [Bug 1832060] Re: Backport "add an option that allows rewinds to be disabled"

[Daniel van Vugt]

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

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

Title:
  Backport "add an option that allows rewinds to be disabled"

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio git master added an option that allows rewinds to be
  disabled. I backported it to v12.2, the patch is here:
  https://gitlab.com/nixtux-packaging/pulseaudio-
  ubuntu/blob/master/pulseaudio-12.2/debian/patches/0001-Backport-add-
  an-option-that-allows-rewinds-to-be-dis.patch

  This will help PulseEffects that is being packaged in
  https://bugs.launchpad.net/ubuntu/+bug/1832059 by fixing crackling
  sound when changing the volume level.

  It would be good to have this patches applied in Eoan if PulseAudio
  13.0 does not get to it.

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

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

[Touch-packages] [Bug 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]

[Daniel van Vugt]

You kernel log is showing a problem at the kernel level:

[  349.209981] iwlwifi :05:00.0: Microcode SW error detected.  Restarting 
0x200.
[  349.210223] iwlwifi :05:00.0: Start IWL Error Log Dump:
[  349.210228] iwlwifi :05:00.0: Status: 0x0100, count: 6
[  349.210231] iwlwifi :05:00.0: Loaded firmware version: 29.1044073957.0
...

Please try this:

  sudo apt update
  sudo apt install --reinstall linux-firmware gnome-bluetooth

Then reboot.

If the problem still persists then please:

1. Run:

   dpkg -l > allpackages.txt

   and send us the file 'allpackages.txt'.

2. Reproduce the problem again and then run:
   
   journalctl -b0 > curjournal.txt

   and send us the file 'curjournal.txt'.

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

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

** Also affects: linux-firmware (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-firmware (Ubuntu)
   Status: New => Incomplete

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

Title:
  Bluetooth earphone is connected but disconnected immediately. [Intel
  3165]

Status in bluez package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:

  I have erased and reinstalled Pulseaudio.
  It seems like this can not be done since.

  I tried the following.
  sudo apt-get remove alsa-base pulseaudio
  sudo apt-get install alsa-base pulseaudio

  I did this again.
  sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils
  sudo apt-get install linux-sound-base alsa-base alsa-utils

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluetooth 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Fri Jun  7 20:33:05 2019
  InstallationDate: Installed on 2019-04-04 (64 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7559
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.9
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.sku: 0706
  dmi.product.version: 1.2.9
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 58:FB:84:C1:51:50  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:125274 acl:68 sco:0 events:1720 errors:0
TX bytes:15000 acl:64 sco:0 commands:861 errors:0

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

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

[Touch-packages] [Bug 1831995] Re: Bluetooth earphone is connected but disconnected immediately.

[Daniel van Vugt]

** Tags added: a2dp

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

** Summary changed:

- Bluetooth earphone is connected but disconnected immediately.
+ Bluetooth earphone is connected but disconnected immediately. [Intel 3165]

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

Title:
  Bluetooth earphone is connected but disconnected immediately. [Intel
  3165]

Status in bluez package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:

  I have erased and reinstalled Pulseaudio.
  It seems like this can not be done since.

  I tried the following.
  sudo apt-get remove alsa-base pulseaudio
  sudo apt-get install alsa-base pulseaudio

  I did this again.
  sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils
  sudo apt-get install linux-sound-base alsa-base alsa-utils

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluetooth 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Fri Jun  7 20:33:05 2019
  InstallationDate: Installed on 2019-04-04 (64 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7559
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.9
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.sku: 0706
  dmi.product.version: 1.2.9
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 58:FB:84:C1:51:50  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:125274 acl:68 sco:0 events:1720 errors:0
TX bytes:15000 acl:64 sco:0 commands:861 errors:0

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

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

[Touch-packages] [Bug 1661745] Re: ssh-keyscan does not exit with non-zero return code on error

[Bug Watch Updater]

** Changed in: openssh (Debian)
   Status: Confirmed => Fix Released

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

Title:
  ssh-keyscan does not exit with non-zero return code on error

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  New
Status in openssh package in Debian:
  Fix Released

Bug description:
  On xenial, ssh-keyscan returns zero indicating success, when the
  command fails.

  root@cp1:~# lsb_release -d
  Description:  Ubuntu 16.04.1 LTS

  root@cp1:~# ssh-keyscan -H -t ssh-rsa bad-host
  getaddrinfo bad-host: Name or service not known
  root@cp1:~# echo $?
  0

  On trusty, the exit status is non-zero as expected.

  root@integration-deployer:/home/ubuntu# lsb_release -d
  Description:  Ubuntu 14.04.5 LTS

  root@integration-deployer:/home/ubuntu# ssh-keyscan -H -t ssh-rsa bad-host
  getaddrinfo bad-host: Name or service not known
  root@integration-deployer:/home/ubuntu# echo $?
  255

  This is a incompatibility between Ubuntu 14.04 and 16.04

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

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

[Touch-packages] [Bug 1832138] Re: Login freeze during boot after upgrade

[Launchpad Bug Tracker]

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

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

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

Title:
  Login freeze during boot after upgrade

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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

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

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

[Touch-packages] [Bug 218741] Re: scp cuts UTF8 filenames by bytes instead of characters

[Colin Watson]

I did some experimentation today with different "stty cols" settings,
and I'm pretty sure this is fixed.  I believe that the commit that fixed
it was probably
https://anongit.mindrot.org/openssh.git/commit/?id=0e059cdf5fd86297546c63fa8607c24059118832
(note in particular "take character display widths into account for the
progressmeter", in which case this has been fixed since OpenSSH 7.3p1,
so since Ubuntu 16.10.

** Changed in: openssh (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  scp cuts UTF8 filenames by bytes instead of characters

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: openssh-client

  This is for up-to-date Ubuntu Hardy.

  I left some files for copying today using scp (from the openssh-client 
package). I happened to look at the output and noticed some “bad character” 
symbols on the terminal, as pasted below. (These were copy-pasted from the 
console, in a completely UTF8-based environment. Note that the weird characters 
may confuse your browser, make sure it's detected the correct encoding.)
  
  21 Lied pentru voce și pian „Regen”.flac 100% 9938KB   1.9MB/s   00:05
  03 Lieduri pentru tenor și pian, op. 15 „S 100% 2524KB   2.5MB/s   00:01 
  18 Lied pentru voce și pian „Frauenberuf�� 100%   11MB   1.3MB/s   00:09
  06 Lieduri pentru tenor și pian, op. 15 „S 100% 8961KB   2.2MB/s   00:04
  09 Lieduri pentru bas și pian, op. 4 „Troi 100%   11MB   1.4MB/s   00:08   
  [after resizing the window]
  10 Suita nr. 3 pentru orchestră, op. 27 „Săteasca”_ „Pârâu sub lun� 100%   
13MB   2.6MB/s   00:05

  As it happens, the next character on each filename of the two weird
  lines was, respectively, ” and ă, both of which are of course
  displayed correctly in other places on the same output. Based on this
  and the misalignment of the last columns, I think scp cuts too-long-
  names by counting bytes rather than characters. This is obviously
  wrong in UTF8, since some characters can contain several bytes, in
  which case the lines would be cut too early, and occasionally in the
  “middle” of a character, thus displaying garbage.

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

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

[Touch-packages] [Bug 1832141] [NEW] Panel applets crashing on start

[holiday]

Public bug reported:

 
SEveral panel applets on both top and right panels. Workspace switcher and text 
output applets raise error dialog on GUI session start. MATE.

This does not happen to all text output applets and not always the same
ones. But the workspace switcher (set to 3x3 table) has become
consistent in the last few days.

The journal has the following error


The program 'wnck-applet' received an X Window System error.
This probably reflects a bug in the 
program.
The error was 'RenderBadPicture 
(invalid Picture parameter)'.
  (Details: serial 4910 error_code 143 
request_code 139 (RENDER) minor_code 7)
  (Note to programmers: normally, X 
errors are reported asynchronously;
   that is, you will receive the error 
a while after causing it.
   To debug your program, run it with 
the GDK_SYNCHRONIZE environment
   variable to change this behavior. 
You can then get a meaningful
   backtrace from your debugger if you 
break on the gdk_x_error() function.)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: MATE
Date: Sun Jun  9 12:39:06 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
 virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed
 virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
InstallationDate: Installed on 2019-04-25 (45 days ago)
InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: ASUSTeK COMPUTER INC. N501VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=7a6ead44-b94a-4058-8c40-fda725ccedba ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N501VW.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N501VW
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.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N501VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

Title:
  Panel applets crashing on start

Status in xorg package in Ubuntu:
  New

Bug description:
   
  SEveral panel applets on both top and right panels. Workspace switcher and 
text output applets raise error dialog on GUI session start. MATE.

  This does not happen to all text output applets and not always the
  same ones. But the worksp

[Touch-packages] [Bug 1832138] [NEW] Login freeze during boot after upgrade

[Pat]

Public bug reported:

I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook
Pro.

I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

I can SSH into the system however.

I've found that I can work around the hang/freeze if I uncomment the following 
line in /etc/gdm3/custom.conf;
#WaylandEnable=false

After uncommenting the WaylandEnable=false line and rebooting, then I
see the login prompt as expected and I can then log in and use the
system normally again.

After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as
shown in this 'uname -a' output;

Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a output;

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Sun Jun  9 12:38:37 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2018-05-06 (399 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/13/2018
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
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 freeze 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/1832138

Title:
  Login freeze during boot after upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu

Re: [Touch-packages] [Bug 1768166] Re: Random crashes

[Ping-Wu]

https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/bug/1768166/comments/24


On Sun, Jun 9, 2019 at 12:25 AM Gunnar Hjalmarsson <
1768...@bugs.launchpad.net> wrote:

> Hello,
>
> This is a friendly reminder of my "call for testing" about a week ago.
>
> Before moving the proposed upgrade of ibus-libpinyin and friends to
> bionic-updates, it would be highly desirable to get feedback from a few
> users who speak Simplified Chinese. So if you can help with this, and
> assuming you are on a 18.04 machine, you find the details about how to
> install from -proposed in comment #24 of this bug report.
>
> https://bugs.launchpad.net/ubuntu/+source/ibus-
> libpinyin/+bug/1768166/comments/24
>
> Please submit any feedback you are able to provide as a comment on this
> bug report.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768166
>
> Title:
>   Random crashes
>
> Status in ibus-libpinyin package in Ubuntu:
>   Fix Released
> Status in libpinyin package in Ubuntu:
>   Fix Released
> Status in ibus-libpinyin source package in Bionic:
>   Fix Committed
> Status in libpinyin source package in Bionic:
>   Fix Committed
> Status in ibus-libpinyin source package in Cosmic:
>   Fix Committed
> Status in libpinyin source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   ibus-libpinyin has proved to crash far too often. One or more files in
>   ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
>   directory allows the user to keep using ibus-libpinyin.
>
>   In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
>   present, and the number of crashes has been reduced significantly:
>
>   https://errors.ubuntu.com/?package=ibus-libpinyin&period=month
>
>   Upstream ChangeLog ibus-libpinyin:
>   --
>   version 1.11.0
>   * fixes keypad decimal
>   * fixes emoji candidates
>   * support configurable opencc config
>
>   version 1.10.92
>   * fixes Enter handling
>
>   version 1.10.91
>   * support ime.register_trigger in lua extension
>   * support predicted candidates
>   * support emoji input
>
>   version 1.10.0
>   * bug fixes
>
>   version 1.9.91
>   * migrate to use GSettings
>   * fixes lyx short cut issue
>
>   version 1.9.3
>   * translate input method name in ibus menu
>
>   Upstream ChangeLog libpinyin:
>   -
>   version 2.2.2
>   * minor fixes
>
>   version 2.2.1
>   * fixes predicted candidates
>
>   version 2.2.0
>   * bug fixes
>
>   The proposal is to backport the disco versions of those packages to
>   bionic and cosmic in an attempt to prevent crashes. Proposed uploads
>   are available in this PPA:
>
>   https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
>
>   [Test Case]
>
>   * Install from {bionic,cosmic}-proposed:
> - libpinyin13
> - libpinyin-data
> - ibus-libpinyin
>
>   * Use "Intelligent Pinyin" for typing and confirm that no new issues
> show up when doing so.
>
>   (This is apparently not a confirmation that the upload really fixes
>   the bug. To compensate for that, we will await testing of the
>   -proposed packages by a few Chinese users before considering the
>   uploads verified.)
>
>   Reverse dependencies
>   
>   Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend
> on packages belonging to the libpinyin source package. So additional test
> measures are:
>
>   * Install fcitx-libpinyin and ibus-libzhuyin.
>
>   * Use both those tools for typing Chinese, and confirm that you don't
> observe any adverse effects of the libpinyin upgrade.
>
>   [Regression Potential]
>
>   The changes are mostly bug fixes, so the regression risk should be
>   limited. Also consider that the starting point is a rather unstable
>   functionality.
>
>   NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
>   as much testing as possible. There do not seem to be too many risky
>   changes carried, but such jumps in upstream versions always carry some
>   regression-risk.
>
>   [Original description]
>
>   I have experienced random ibus-libpinyin crashes in bionic.  I cannot
>   reproduce it, but it occurred at least a few times, even after the
>   official bionic release.  Same crashes were also reported in the
>   Ubuntu Chinese forum.
>
>   Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
>   folder.
>
>   I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
>   suggested that we update the version of ibus-libpinyin to 1.10.
>
>   Can we give this update a trial?
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib

Re: [Touch-packages] [Bug 1768166] Re: Random crashes

[Ping-Wu]

The correct link should be:

https://bugs.launchpad.net/ubuntu/+source/ibus-
libpinyin/+bug/1768166/comments/24

On Sun, Jun 9, 2019 at 12:25 AM Gunnar Hjalmarsson <
1768...@bugs.launchpad.net> wrote:

> Hello,
>
> This is a friendly reminder of my "call for testing" about a week ago.
>
> Before moving the proposed upgrade of ibus-libpinyin and friends to
> bionic-updates, it would be highly desirable to get feedback from a few
> users who speak Simplified Chinese. So if you can help with this, and
> assuming you are on a 18.04 machine, you find the details about how to
> install from -proposed in comment #24 of this bug report.
>
> https://bugs.launchpad.net/ubuntu/+source/ibus-
> libpinyin/+bug/1768166/comments/24
>
> Please submit any feedback you are able to provide as a comment on this
> bug report.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768166
>
> Title:
>   Random crashes
>
> Status in ibus-libpinyin package in Ubuntu:
>   Fix Released
> Status in libpinyin package in Ubuntu:
>   Fix Released
> Status in ibus-libpinyin source package in Bionic:
>   Fix Committed
> Status in libpinyin source package in Bionic:
>   Fix Committed
> Status in ibus-libpinyin source package in Cosmic:
>   Fix Committed
> Status in libpinyin source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   ibus-libpinyin has proved to crash far too often. One or more files in
>   ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
>   directory allows the user to keep using ibus-libpinyin.
>
>   In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
>   present, and the number of crashes has been reduced significantly:
>
>   https://errors.ubuntu.com/?package=ibus-libpinyin&period=month
>
>   Upstream ChangeLog ibus-libpinyin:
>   --
>   version 1.11.0
>   * fixes keypad decimal
>   * fixes emoji candidates
>   * support configurable opencc config
>
>   version 1.10.92
>   * fixes Enter handling
>
>   version 1.10.91
>   * support ime.register_trigger in lua extension
>   * support predicted candidates
>   * support emoji input
>
>   version 1.10.0
>   * bug fixes
>
>   version 1.9.91
>   * migrate to use GSettings
>   * fixes lyx short cut issue
>
>   version 1.9.3
>   * translate input method name in ibus menu
>
>   Upstream ChangeLog libpinyin:
>   -
>   version 2.2.2
>   * minor fixes
>
>   version 2.2.1
>   * fixes predicted candidates
>
>   version 2.2.0
>   * bug fixes
>
>   The proposal is to backport the disco versions of those packages to
>   bionic and cosmic in an attempt to prevent crashes. Proposed uploads
>   are available in this PPA:
>
>   https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
>
>   [Test Case]
>
>   * Install from {bionic,cosmic}-proposed:
> - libpinyin13
> - libpinyin-data
> - ibus-libpinyin
>
>   * Use "Intelligent Pinyin" for typing and confirm that no new issues
> show up when doing so.
>
>   (This is apparently not a confirmation that the upload really fixes
>   the bug. To compensate for that, we will await testing of the
>   -proposed packages by a few Chinese users before considering the
>   uploads verified.)
>
>   Reverse dependencies
>   
>   Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend
> on packages belonging to the libpinyin source package. So additional test
> measures are:
>
>   * Install fcitx-libpinyin and ibus-libzhuyin.
>
>   * Use both those tools for typing Chinese, and confirm that you don't
> observe any adverse effects of the libpinyin upgrade.
>
>   [Regression Potential]
>
>   The changes are mostly bug fixes, so the regression risk should be
>   limited. Also consider that the starting point is a rather unstable
>   functionality.
>
>   NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
>   as much testing as possible. There do not seem to be too many risky
>   changes carried, but such jumps in upstream versions always carry some
>   regression-risk.
>
>   [Original description]
>
>   I have experienced random ibus-libpinyin crashes in bionic.  I cannot
>   reproduce it, but it occurred at least a few times, even after the
>   official bionic release.  Same crashes were also reported in the
>   Ubuntu Chinese forum.
>
>   Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
>   folder.
>
>   I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
>   suggested that we update the version of ibus-libpinyin to 1.10.
>
>   Can we give this update a trial?
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions
>

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

[Touch-packages] [Bug 1832133] Re: Mouse unresponsive on Ubuntu 18.04

[Tom Stewart]

The mouse has a left-click button, a right-click button and a
scrollwheel in between that is clickable.

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

Title:
  Mouse unresponsive on Ubuntu 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi there,

  I submitted this bug report following advice in
  https://wiki.ubuntu.com/DebuggingMouseDetection

  I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart
  15 Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and
  rarely boot up Windows.

  I use an optical mouse attached to my computer by USB cable. It works
  perfectly on Windows. But on Ubuntu, it will work OK for a couple of
  seconds, but then become less and less responsive, to the point where
  it barely works at all.

  I have a touchpad that works perfectly in both Windows and Ubuntu.

  Result of lsb_release -rd: Description:   Ubuntu 18.04.2 LTS. Release:
18.04
  I am using Xdiagnose version 3.8.8

  Please help!

  Tom.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 17:03:12 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7600G] [103c:216b]
  InstallationDate: Installed on 2018-01-22 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=f7ecd954-9bbe-4c06-9514-a1366c47b763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216B:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion TS 15 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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
  xserver.bootTime: Wed Oct 31 01:15:25 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

[Touch-packages] [Bug 1832133] Re: Mouse unresponsive on Ubuntu 18.04

[Tom Stewart]

Here are details on my mouse.

Manufacturer: TRUST (www.trust.com)
Model: AMI MOUSE 250S OPTICAL

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

Title:
  Mouse unresponsive on Ubuntu 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi there,

  I submitted this bug report following advice in
  https://wiki.ubuntu.com/DebuggingMouseDetection

  I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart
  15 Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and
  rarely boot up Windows.

  I use an optical mouse attached to my computer by USB cable. It works
  perfectly on Windows. But on Ubuntu, it will work OK for a couple of
  seconds, but then become less and less responsive, to the point where
  it barely works at all.

  I have a touchpad that works perfectly in both Windows and Ubuntu.

  Result of lsb_release -rd: Description:   Ubuntu 18.04.2 LTS. Release:
18.04
  I am using Xdiagnose version 3.8.8

  Please help!

  Tom.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 17:03:12 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7600G] [103c:216b]
  InstallationDate: Installed on 2018-01-22 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=f7ecd954-9bbe-4c06-9514-a1366c47b763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216B:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion TS 15 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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
  xserver.bootTime: Wed Oct 31 01:15:25 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

[Touch-packages] [Bug 1832133] [NEW] Mouse unresponsive on Ubuntu 18.04

[Tom Stewart]

Public bug reported:

Hi there,

I submitted this bug report following advice in
https://wiki.ubuntu.com/DebuggingMouseDetection

I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart 15
Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and
rarely boot up Windows.

I use an optical mouse attached to my computer by USB cable. It works
perfectly on Windows. But on Ubuntu, it will work OK for a couple of
seconds, but then become less and less responsive, to the point where it
barely works at all.

I have a touchpad that works perfectly in both Windows and Ubuntu.

Result of lsb_release -rd: Description: Ubuntu 18.04.2 LTS. Release:18.04
I am using Xdiagnose version 3.8.8

Please help!

Tom.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  9 17:03:12 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7600G] [103c:216b]
InstallationDate: Installed on 2018-01-22 (502 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=f7ecd954-9bbe-4c06-9514-a1366c47b763 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 216B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 30.25
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216B:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion TS 15 Notebook PC
dmi.product.version: 088110305E0620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
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
xserver.bootTime: Wed Oct 31 01:15:25 2018
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.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/1832133

Title:
  Mouse unresponsive on Ubuntu 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi there,

  I submitted this bug report following advice in
  https://wiki.ubuntu.com/DebuggingMouseDetection

  I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart
  15 Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and
  rarely boot up Windows.

  I use an optical mouse attached to my computer by USB cable. It works
  perfectly on Windows. But on Ubuntu, it will work OK for a couple of
  seconds, but then become less and less responsive, to the point where
  it barely works at all.

  I have a touchpad that works perfectly in both Windows and Ubuntu.

  Result of lsb_release -rd: Description:   Ubuntu 18.04.2 LTS. Release:
18.04
  I am using Xdiagnose version 3.8.8

  Please help!

  Tom.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 17:03:12 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tr

[Touch-packages] [Bug 1823382] Re: backport openssl 1.1.1 fixes to bionic and cosmic

[Dimitri John Ledkov]

we really should not have published this SRU, as it has dependencies on
openssl 1.1.1 which is not published, and is thus now uninstallable.

=/

however it has been a while, so might as well wait for openssl 1.1.1 to
be published.

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

Title:
  backport openssl 1.1.1 fixes to bionic and cosmic

Status in neon27 package in Ubuntu:
  Fix Released
Status in neon27 source package in Bionic:
  Fix Released
Status in neon27 source package in Cosmic:
  Fix Released
Status in neon27 source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * neon27 doesn't work with openssl 1.1.1
   * backport fixes from disco to cosmic and bionic to resolve that

  [Test Case]

   * does not FTBFS

  [Regression Potential]

   * currently broken in cosmic, and will break once openssl is upgraded
  in bionic, so for all practical purposes it's completely busted at the
  moment.

  [Other Info]
   
   * Fixes already in disco and unstable.

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

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

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

[Robert G]

I'm having the same problem as @morozov-ml. Starting from recovery mode
seems to work though. This seems to be caused by an update because I've
reverted to an old backup which boots just fine, but after installing
updates it hangs after entering the LUKS password just like before.

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1832128] Re: [To Be Filled By O.E.M., Nvidia GPU 14 HDMI/DP, Digital Out, HDMI] volume slider problem

[Ranjeet Kuruvilla]

** Description changed:

- I upgraded my PC to 19.04. I have headphones using the clinch output and
- USB Audio Speakers. After I added the line "load-module module-udev-
- detect tsched=0" to /etc/pulse/default.pa, the speakers started working,
- but everytime I restart the computer the speakers need to be reselected.
- Also the volume control does not seem to work.
+ I upgraded my PC from 18.04 to 19.04. I have headphones using the clinch
+ output and USB Audio Speakers. After I added the line "load-module
+ module-udev-detect tsched=0" to /etc/pulse/default.pa, the speakers
+ started working, but everytime I restart the computer the speakers need
+ to be reselected. Also the volume slider does not seem to work.
  
  The Audiospeakers had trouble working since 18.04. Please fix that.
+ 
+ Let me suggest a better way to allow controlling of the panel: Make the 
audiopanel a separate control panel.
+ Show a list of devices to be selected. Then show another list of 
audiosources. Allow the control of each device separately with a Volumeslide 
and a Mute button.
+ 
+ If you want to make it very fancy, then allow to each source to be
+ directed to any output, so that I could send the output of one chrome
+ tab to my headphones and the other one to the speakers.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ranju  1744 F pulseaudio
-  /dev/snd/controlC2:  ranju  1744 F pulseaudio
-  /dev/snd/controlC1:  ranju  1744 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ranju  1744 F pulseaudio
+  /dev/snd/controlC2:  ranju  1744 F pulseaudio
+  /dev/snd/controlC1:  ranju  1744 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 13:22:25 2019
  InstallationDate: Installed on 2019-06-08 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: GF108 High Definition Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog:
-  Jun 09 13:17:42 vikrant dbus-daemon[901]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.48' (uid=123 pid=1328 comm="/usr/bin/pulseaudio --daemonize=no 
" label="unconfined")
-  Jun 09 13:17:46 vikrant pulseaudio[1328]: E: [pulseaudio] module.c: Module 
"module-udev-detect" should be loaded once at most. Refusing to load.
-  Jun 09 13:18:51 vikrant systemd[1129]: pulseaudio.service: Succeeded.
-  Jun 09 13:18:51 vikrant systemd[1129]: pulseaudio.socket: Succeeded.
+  Jun 09 13:17:42 vikrant dbus-daemon[901]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.48' (uid=123 pid=1328 comm="/usr/bin/pulseaudio --daemonize=no 
" label="unconfined")
+  Jun 09 13:17:46 vikrant pulseaudio[1328]: E: [pulseaudio] module.c: Module 
"module-udev-detect" should be loaded once at most. Refusing to load.
+  Jun 09 13:18:51 vikrant systemd[1129]: pulseaudio.service: Succeeded.
+  Jun 09 13:18:51 vikrant systemd[1129]: pulseaudio.socket: Succeeded.
  Symptom_Type: Volume slider, or mixer problems
  Title: [To Be Filled By O.E.M., Nvidia GPU 14 HDMI/DP, Digital Out, HDMI] 
volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: N68C-GS FX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd01/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

Title:
  [To Be Filled By O.E.M., Nvidia GPU 14 HDMI/DP, Digital Out, HDMI]
  volume slider problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I upgraded my PC from 18.04 to 19.04. I have headphones using the
  clinch output and USB Audio Speakers. After I added the line "load-
  module module-udev-detect tsched=0" to /etc/pulse/default.pa, the
  speakers started working, but every

[Touch-packages] [Bug 1832120] Re: i386 - Test fails 'test_get_file_package_uninstalled_multiarch'

[Rik Mills]

** Summary changed:

- i386 - Test fails 'get_file_package() on foreign arches and releases'
+ i386 - Test fails 'test_get_file_package_uninstalled_multiarch'

** Description changed:

  Version: 2.20.11-0ubuntu2
  Release: Eoan 19.10
  
  This failure is currently blocking Konsole 19.04.2-0ubuntu1 from
  migrating from proposed.
  
- The test 'get_file_package() on foreign arches and releases' now appears
- to be failing, at least the majority of the time, on i386 with:
+ The test 'test_get_file_package_uninstalled_multiarch' now appears to be
+ failing, at least the majority of the time, on i386 with:
  
  FAIL: test_get_file_package_uninstalled_multiarch (__main__.T)
  get_file_package() on foreign arches and releases
  --
  Traceback (most recent call last):
    File "./test_backend_apt_dpkg.py", line 346, in 
test_get_file_package_uninstalled_multiarch
  True, cache_dir, arch='even')
  AssertionError: OSError not raised by get_file_package
  
  The test history can be seen here:
  
  http://autopkgtest.ubuntu.com/packages/a/apport/eoan/i386
  
  This fails against multiple triggers, including itself in the release
  pocket.
  
  I would also note that the same failure has been seen recently on amd64:
  
  http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64
  
  however that then passed on subsequent retries. Something that does not
  seem to be the case after multiple retries on i386.

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

Title:
  i386 - Test fails 'test_get_file_package_uninstalled_multiarch'

Status in apport package in Ubuntu:
  New

Bug description:
  Version: 2.20.11-0ubuntu2
  Release: Eoan 19.10

  This failure is currently blocking Konsole 19.04.2-0ubuntu1 from
  migrating from proposed.

  The test 'test_get_file_package_uninstalled_multiarch' now appears to
  be failing, at least the majority of the time, on i386 with:

  FAIL: test_get_file_package_uninstalled_multiarch (__main__.T)
  get_file_package() on foreign arches and releases
  --
  Traceback (most recent call last):
    File "./test_backend_apt_dpkg.py", line 346, in 
test_get_file_package_uninstalled_multiarch
  True, cache_dir, arch='even')
  AssertionError: OSError not raised by get_file_package

  The test history can be seen here:

  http://autopkgtest.ubuntu.com/packages/a/apport/eoan/i386

  This fails against multiple triggers, including itself in the release
  pocket.

  I would also note that the same failure has been seen recently on
  amd64:

  http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64

  however that then passed on subsequent retries. Something that does
  not seem to be the case after multiple retries on i386.

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

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

[Touch-packages] [Bug 1832128] [NEW] [To Be Filled By O.E.M., Nvidia GPU 14 HDMI/DP, Digital Out, HDMI] volume slider problem

[Ranjeet Kuruvilla]

Public bug reported:

I upgraded my PC to 19.04. I have headphones using the clinch output and
USB Audio Speakers. After I added the line "load-module module-udev-
detect tsched=0" to /etc/pulse/default.pa, the speakers started working,
but everytime I restart the computer the speakers need to be reselected.
Also the volume control does not seem to work.

The Audiospeakers had trouble working since 18.04. Please fix that.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ranju  1744 F pulseaudio
 /dev/snd/controlC2:  ranju  1744 F pulseaudio
 /dev/snd/controlC1:  ranju  1744 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  9 13:22:25 2019
InstallationDate: Installed on 2019-06-08 (1 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: GF108 High Definition Audio Controller - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_PulseAudioLog:
 Jun 09 13:17:42 vikrant dbus-daemon[901]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.48' (uid=123 pid=1328 comm="/usr/bin/pulseaudio --daemonize=no 
" label="unconfined")
 Jun 09 13:17:46 vikrant pulseaudio[1328]: E: [pulseaudio] module.c: Module 
"module-udev-detect" should be loaded once at most. Refusing to load.
 Jun 09 13:18:51 vikrant systemd[1129]: pulseaudio.service: Succeeded.
 Jun 09 13:18:51 vikrant systemd[1129]: pulseaudio.socket: Succeeded.
Symptom_Type: Volume slider, or mixer problems
Title: [To Be Filled By O.E.M., Nvidia GPU 14 HDMI/DP, Digital Out, HDMI] 
volume slider problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: N68C-GS FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd01/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

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

Title:
  [To Be Filled By O.E.M., Nvidia GPU 14 HDMI/DP, Digital Out, HDMI]
  volume slider problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I upgraded my PC to 19.04. I have headphones using the clinch output
  and USB Audio Speakers. After I added the line "load-module module-
  udev-detect tsched=0" to /etc/pulse/default.pa, the speakers started
  working, but everytime I restart the computer the speakers need to be
  reselected. Also the volume control does not seem to work.

  The Audiospeakers had trouble working since 18.04. Please fix that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ranju  1744 F pulseaudio
   /dev/snd/controlC2:  ranju  1744 F pulseaudio
   /dev/snd/controlC1:  ranju  1744 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 13:22:25 2019
  InstallationDate: Installed on 2019-06-08 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: GF108 High Definition Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog:
   Jun 09 13:17:42 vikrant dbus-daemon[901]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.48' (uid=123 pid=1328 comm="/usr/bin/pulseaudio --daemonize=no 
" label="unconfined")
   Jun 09 13:17:46 vikrant pulseaudio[1328]: E: [pulseaudio] module.c: Module 
"module-udev-detect" should be loaded once at most. Refusing to load.
   Jun 09 13:18:51 vikrant systemd[1129]: pulseaudio.service: Succeeded.
   Jun 09 13:18:51 vikrant systemd[1129]: pulseaudio.socket: Suc

[Touch-packages] [Bug 1768166] Re: Random crashes

[Gunnar Hjalmarsson]

Hello,

This is a friendly reminder of my "call for testing" about a week ago.

Before moving the proposed upgrade of ibus-libpinyin and friends to
bionic-updates, it would be highly desirable to get feedback from a few
users who speak Simplified Chinese. So if you can help with this, and
assuming you are on a 18.04 machine, you find the details about how to
install from -proposed in comment #24 of this bug report.

https://bugs.launchpad.net/ubuntu/+source/ibus-
libpinyin/+bug/1768166/comments/24

Please submit any feedback you are able to provide as a comment on this
bug report.

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

Title:
  Random crashes

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin source package in Bionic:
  Fix Committed
Status in libpinyin source package in Bionic:
  Fix Committed
Status in ibus-libpinyin source package in Cosmic:
  Fix Committed
Status in libpinyin source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  ibus-libpinyin has proved to crash far too often. One or more files in
  ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
  directory allows the user to keep using ibus-libpinyin.

  In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
  present, and the number of crashes has been reduced significantly:

  https://errors.ubuntu.com/?package=ibus-libpinyin&period=month

  Upstream ChangeLog ibus-libpinyin:
  --
  version 1.11.0
  * fixes keypad decimal
  * fixes emoji candidates
  * support configurable opencc config

  version 1.10.92
  * fixes Enter handling

  version 1.10.91
  * support ime.register_trigger in lua extension
  * support predicted candidates
  * support emoji input

  version 1.10.0
  * bug fixes

  version 1.9.91
  * migrate to use GSettings
  * fixes lyx short cut issue

  version 1.9.3
  * translate input method name in ibus menu

  Upstream ChangeLog libpinyin:
  -
  version 2.2.2
  * minor fixes

  version 2.2.1
  * fixes predicted candidates

  version 2.2.0
  * bug fixes

  The proposal is to backport the disco versions of those packages to
  bionic and cosmic in an attempt to prevent crashes. Proposed uploads
  are available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin

  [Test Case]

  * Install from {bionic,cosmic}-proposed:
    - libpinyin13
    - libpinyin-data
    - ibus-libpinyin

  * Use "Intelligent Pinyin" for typing and confirm that no new issues
    show up when doing so.

  (This is apparently not a confirmation that the upload really fixes
  the bug. To compensate for that, we will await testing of the
  -proposed packages by a few Chinese users before considering the
  uploads verified.)

  Reverse dependencies
  
  Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on 
packages belonging to the libpinyin source package. So additional test measures 
are:

  * Install fcitx-libpinyin and ibus-libzhuyin.

  * Use both those tools for typing Chinese, and confirm that you don't
    observe any adverse effects of the libpinyin upgrade.

  [Regression Potential]

  The changes are mostly bug fixes, so the regression risk should be
  limited. Also consider that the starting point is a rather unstable
  functionality.

  NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
  as much testing as possible. There do not seem to be too many risky
  changes carried, but such jumps in upstream versions always carry some
  regression-risk.

  [Original description]

  I have experienced random ibus-libpinyin crashes in bionic.  I cannot
  reproduce it, but it occurred at least a few times, even after the
  official bionic release.  Same crashes were also reported in the
  Ubuntu Chinese forum.

  Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
  folder.

  I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
  suggested that we update the version of ibus-libpinyin to 1.10.

  Can we give this update a trial?

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

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

[Touch-packages] [Bug 1832123] [NEW] [SRU] Bugfix release 1.14.5

[Amr Ibrahim]

Public bug reported:

[ Description ]

We should keep up with GStreamer's bugfix releases in the 1.14 series
that 18.04 shipped with.

[ QA and testing ]

Play a range of videos in Totem. Play a range of audio tracks in
Rhythmbox. Try to stream audio and/or video. Try to install a missing
codec.

In all cases, make sure that everything which worked before still works.

[ Regression potential ]

If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.
---

Highlighted bugfixes in 1.14.5

GStreamer core

-   aggregator: take the pad lock around queue gap event removal
-   aggregator: don’t leak gap buffer when out of segment
-   buffer: fix possible memory corruption in gst_buffer_foreach_meta() when 
removing metas
-   bus: Make removing of signal/bus watches thread-safe
-   bus: Don’t allow removing signal watches with gst_bus_remove_watch()
-   controlbinding: Check if the weak pointer was cleared before explicitly 
removing it
-   ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance 
for late follow-up and delay-resp
-   segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate
-   g-i: annotations fixes

gst-plugins-base

-   audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE)
-   audioringbuffer: Fix wrong memcpy address when reordering channels
-   decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup
-   glviewconvert: fix output when a transformation matrix is used
-   glupload: prevent segfault when updating caps
-   gl/egl: Determine correct format on dmabuf import
-   glupload: dmabuf: be explicit about gl formats used
-   id3tag: validate the year from v1 tags before passing to GstDateTime
-   rtpbasepayload: fix sequence numbers when using buffer lists
-   rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928)
-   rtspconnection: fix GError set over the top of a previous GError
-   rtspconnection: do not duplicate authentication headers
-   subparse: don’t assert when failing to parse subrip timestamp
-   video: various convert sample frame fixes
-   video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, 
A420_10LE/BE to BGRA/RGBA which created corrupted output
-   video-format: Fix GBRA_10/12 alpha channel pixel strides

gst-plugins-good

-   flv: Use 8kHz sample rate for alaw/mulaw audio
-   flvdemux: Do not error out if the first added and chained pad is not linked
-   flvmux: try harder to make sure timestamps are always increasing
-   gdkpixbufdec: output a TIME segment which is what’s expected for raw video
-   matroskademux: fix handling of MS ACM audio
-   matroska: fix handling of FlagInterlaced
-   pulsesink: Deal with not being able to convert a format to caps
-   rtph265depay, rtph264depay; aggregation packet marker handling fixes
-   rtpmp4gdepay: detect broken senders who send AAC with ADTS frames
-   rtprawdepay: keep buffer pool around when flushing/seeking
-   rtpssrcdemux: Forward serialized events to all pads
-   qmlglsink: Handle OPENGL header guard changes
-   qtdemux: fix track language code parsing; ignore corrupted CTTS box
-   qtmux: Correctly set tkhd width/height to the display size
-   splitmuxsink: various timecode meta handling fixes
-   splitmuxsink: make work with audio-only encoders as muxers, e.g. wavenc
-   v4l2sink: fix pool-less allocation query handling
-   v4l2dec/enc: fix use after free when handling events
-   vpx: Fix build against libvpx 1.8
-   webmmux: allow resolutions above 4096

gst-plugins-ugly

-   sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUN
-   x264: Only enable dynamic loading code for x264 before v253

gst-plugins-bad

-   assrender: fix disappearing subtitles when seeking back in time
-   decklinkvideosink: fix segfault when audiosink is closed before videosink
-   decklinkvideosrc: respect pixel format property even if mode is set to auto
-   d3dvideosink: Fix calculating buffer size of packed format; don’t leak 
thread object
-   dtls: Don’t abort on non-fatal issues, make work with newer OpenSSL versions
-   msdk: more robust error handling; fix intel sdk libdir path
-   nvenc: Ensure drain all frames on finish; fix element reuse and clean up 
properly
-   openh264dec: Fix handling of errors when doing EOS
-   shmsrc: fixes a crash when is-live is true due a race condition
-   shmsink: fix possible (racy) deadlock on shutdown
-   siren: Fix invalid floating point operation
-   tsdemux: Skew correction improvements: use upstream DTS if set
-   wasapi: number of segments was always 2 (the absolute minimum) by accident
-   wasapi: Fix infinite loop when the device disappears

gst-libav

-   libav: Update internal snapshot to ffmpeg n3.4.6
-   avdemux: fix negative pts if start_time is bigger than the ts

gst-rtsp-server

-   rtsp-client: Fix crash in close handler and remove timeout GSource

[Touch-packages] [Bug 1832120] [NEW] i386 - Test fails 'get_file_package() on foreign arches and releases'

[Rik Mills]

Public bug reported:

Version: 2.20.11-0ubuntu2
Release: Eoan 19.10

This failure is currently blocking Konsole 19.04.2-0ubuntu1 from
migrating from proposed.

The test 'get_file_package() on foreign arches and releases' now appears
to be failing, at least the majority of the time, on i386 with:

FAIL: test_get_file_package_uninstalled_multiarch (__main__.T)
get_file_package() on foreign arches and releases
--
Traceback (most recent call last):
  File "./test_backend_apt_dpkg.py", line 346, in 
test_get_file_package_uninstalled_multiarch
True, cache_dir, arch='even')
AssertionError: OSError not raised by get_file_package

The test history can be seen here:

http://autopkgtest.ubuntu.com/packages/a/apport/eoan/i386

This fails against multiple triggers, including itself in the release
pocket.

I would also note that the same failure has been seen recently on amd64:

http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64

however that then passed on subsequent retries. Something that does not
seem to be the case after multiple retries on i386.

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

** Description changed:

  Version: 2.20.11-0ubuntu2
  Release: Eoan 19.10
  
  This failure is currently blocking Konsole 19.04.2-0ubuntu1 from
  migrating from proposed.
  
- The test 'get_file_package() on foreign arches and releases' is now
- appears to me failing at least the majority of the time with:
+ The test 'get_file_package() on foreign arches and releases' now appears
+ to be failing, at least the majority of the time, on i386 with:
  
  FAIL: test_get_file_package_uninstalled_multiarch (__main__.T)
  get_file_package() on foreign arches and releases
  --
  Traceback (most recent call last):
-   File "./test_backend_apt_dpkg.py", line 346, in 
test_get_file_package_uninstalled_multiarch
- True, cache_dir, arch='even')
+   File "./test_backend_apt_dpkg.py", line 346, in 
test_get_file_package_uninstalled_multiarch
+ True, cache_dir, arch='even')
  AssertionError: OSError not raised by get_file_package
  
  The test history can be seen here:
  
  http://autopkgtest.ubuntu.com/packages/a/apport/eoan/i386
  
  This fails against multiple triggers, including itself in the release
  pocket.
  
  I would also note that the same failure has been seen recently on amd64:
  
  http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64
  
  however that then passed on subsequent retries. Something that does not
  seem to be the case after multiple retries on i386.

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

Title:
  i386 - Test fails 'get_file_package() on foreign arches and releases'

Status in apport package in Ubuntu:
  New

Bug description:
  Version: 2.20.11-0ubuntu2
  Release: Eoan 19.10

  This failure is currently blocking Konsole 19.04.2-0ubuntu1 from
  migrating from proposed.

  The test 'get_file_package() on foreign arches and releases' now
  appears to be failing, at least the majority of the time, on i386
  with:

  FAIL: test_get_file_package_uninstalled_multiarch (__main__.T)
  get_file_package() on foreign arches and releases
  --
  Traceback (most recent call last):
    File "./test_backend_apt_dpkg.py", line 346, in 
test_get_file_package_uninstalled_multiarch
  True, cache_dir, arch='even')
  AssertionError: OSError not raised by get_file_package

  The test history can be seen here:

  http://autopkgtest.ubuntu.com/packages/a/apport/eoan/i386

  This fails against multiple triggers, including itself in the release
  pocket.

  I would also note that the same failure has been seen recently on
  amd64:

  http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64

  however that then passed on subsequent retries. Something that does
  not seem to be the case after multiple retries on i386.

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

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

[Touch-packages] [Bug 1832077] Re: libneon27-dev builddep can not be installed in recipebuild

[Colin Watson]

This is a problem with libneon27 in Ubuntu bionic itself, not a problem
with Launchpad.  In a clean chroot:

(bionic-amd64)root@niejwein:~# apt install libneon27
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libneon27 : Depends: libssl1.1 (>= 1.1.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

In other words, somebody published the neon27 update for OpenSSL 1.1.1
without the corresponding OpenSSL 1.1.1 update that it depends on.

I guess this will be resolved once
https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~18.04.1 is
published to bionic-updates, but I'm subscribing a couple of people
involved with the update anyway since this seems like a significant
process failure.

** Project changed: launchpad-buildd => neon27 (Ubuntu)

** Also affects: neon27 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** No longer affects: neon27 (Ubuntu)

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

** Changed in: neon27 (Ubuntu Bionic)
   Importance: Undecided => Critical

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

Title:
  libneon27-dev builddep can not be installed in recipebuild

Status in neon27 source package in Bionic:
  Triaged

Bug description:
  It is seems there is an issue with LP buildd in recipebuild. This only 
happens to me in Bionic: 
https://launchpadlibrarian.net/426714753/buildlog.txt.gz
  The other distributions are not affected: 
https://code.launchpad.net/~far2l-team/+recipe/far2l-daily

  Reading package lists...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   builddeps:far2l : Depends: libneon27-dev but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/bionic/+source/neon27/+bug/1832077/+subscriptions

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

[Touch-packages] [Bug 1832077] [NEW] libneon27-dev builddep can not be installed in recipebuild

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

It is seems there is an issue with LP buildd in recipebuild. This only happens 
to me in Bionic: https://launchpadlibrarian.net/426714753/buildlog.txt.gz
The other distributions are not affected: 
https://code.launchpad.net/~far2l-team/+recipe/far2l-daily

Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:far2l : Depends: libneon27-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

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

-- 
libneon27-dev builddep can not be installed in recipebuild
https://bugs.launchpad.net/bugs/1832077
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to neon27 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