[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

[Shih-Yuan Lee]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Tags added: oem-bug-1769562

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

Title:
  dell_wmi: Unknown key codes

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions

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

[Touch-packages] [Bug 1771264] [NEW] [Dell Latitude Black Headphone Out] Audio from both headphone and speaker

[waqar baig]

Public bug reported:

My headphones are detected when plugged in.
But when I choose headphones from sound setting, the audio still comes from 
speaker and headphones.
This happens only when its a 3.5mm headphone jack.
Works fine with a usb one.
Please help.

Thanks,
Waqar Baig

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   webwerks   5005 F...m pulseaudio
 /dev/snd/controlC0:  webwerks   5005 F pulseaudio
 /dev/snd/pcmC1D0c:   webwerks   5005 F...m pulseaudio
 /dev/snd/controlC1:  webwerks   5005 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 15 10:35:43 2018
InstallationDate: Installed on 2016-08-24 (628 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: No auto-mute between outputs
Title: [Latitude E6230, IDT 92HD93BXX, Black Headphone Out, Left] No automute
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 08FR4N
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd12/10/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn08FR4N:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6230
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  [Dell Latitude Black Headphone Out] Audio from both headphone and
  speaker

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My headphones are detected when plugged in.
  But when I choose headphones from sound setting, the audio still comes from 
speaker and headphones.
  This happens only when its a 3.5mm headphone jack.
  Works fine with a usb one.
  Please help.

  Thanks,
  Waqar Baig

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   webwerks   5005 F...m pulseaudio
   /dev/snd/controlC0:  webwerks   5005 F pulseaudio
   /dev/snd/pcmC1D0c:   webwerks   5005 F...m pulseaudio
   /dev/snd/controlC1:  webwerks   5005 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 15 10:35:43 2018
  InstallationDate: Installed on 2016-08-24 (628 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No auto-mute between outputs
  Title: [Latitude E6230, IDT 92HD93BXX, Black Headphone Out, Left] No automute
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 08FR4N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd12/10/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn08FR4N:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6230
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04

[Wes]

Well I think it pertains to ubuntu's architecture in general not just
systemd but whatever.

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

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

Title:
  forced use of systemd-networkd interferes with ifupdown in 18.04

Status in systemd package in Ubuntu:
  New

Bug description:
  For several reasons, we are not able to use netplan nor systemd-
  networkd due to legacy applications that expect ifupdown's pre-up and
  post-up script mechanism.  The documentation around 18.04's
  (premature, I feel) wholesale adoption of netplan claims that one can
  revert to old behaviour by merely installing ifupdown (amongst
  assertions that netplan will never offer a mechanism for configuring
  pre-up and post-up actions even for network managers that support
  them).

  However when ifupdown is installed, systemd-networkd still tries to
  manage interfaces.  If you 'systemctl disable systemd-networkd', upon
  next reboot it is automatically re-enabled.  We tried disabling any
  systemd units even remotely related to networking and yet systemd-
  networkd still runs.  If it hasn't been configured, it tries to DHCP.
  On networks that don't provide DHCP this results in a stupendously
  long stall during boot.  Currently it appears to be impossible to tell
  systemd-networkd not to run in a clean manner that won't get reverted
  on package upgrades.

  I sincerely hope this is is a bug/oversight and not intentional.  We
  need to be able to disable systemd-networkd properly.

  Thanks

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

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

[Touch-packages] [Bug 1771236] [NEW] forced use of systemd-networkd interferes with ifupdown in 18.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

For several reasons, we are not able to use netplan nor systemd-networkd
due to legacy applications that expect ifupdown's pre-up and post-up
script mechanism.  The documentation around 18.04's (premature, I feel)
wholesale adoption of netplan claims that one can revert to old
behaviour by merely installing ifupdown (amongst assertions that netplan
will never offer a mechanism for configuring pre-up and post-up actions
even for network managers that support them).

However when ifupdown is installed, systemd-networkd still tries to
manage interfaces.  If you 'systemctl disable systemd-networkd', upon
next reboot it is automatically re-enabled.  We tried disabling any
systemd units even remotely related to networking and yet systemd-
networkd still runs.  If it hasn't been configured, it tries to DHCP.
On networks that don't provide DHCP this results in a stupendously long
stall during boot.  Currently it appears to be impossible to tell
systemd-networkd not to run in a clean manner that won't get reverted on
package upgrades.

I sincerely hope this is is a bug/oversight and not intentional.  We
need to be able to disable systemd-networkd properly.

Thanks

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


** Tags: bot-comment
-- 
forced use of systemd-networkd interferes with ifupdown in 18.04
https://bugs.launchpad.net/bugs/1771236
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1722185] Re: gnome-software (11) g_io_channel_shutdown → pk_client_helper_copy_stdout_cb → g_main_dispatch → g_main_context_dispatch → g_main_context_iterate

[Robert Ancell]

I can still reproduce after the above change, but that does fix some
possibly related errors.

I can reproduce reliably, as it seems to be due to the debconf-
communicate window not closing for some reason. The shell prompts you to
force quit, and clicking that is causing packagekit-glib (and thus
gnome-software) to crash.

** Changed in: packagekit (Ubuntu)
   Importance: Undecided => High

** Changed in: packagekit (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: packagekit (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Changed in: packagekit (Ubuntu)
   Status: Confirmed => In Progress

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

** Changed in: packagekit (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  gnome-software (11) g_io_channel_shutdown →
  pk_client_helper_copy_stdout_cb → g_main_dispatch →
  g_main_context_dispatch → g_main_context_iterate

Status in packagekit package in Ubuntu:
  In Progress
Status in packagekit source package in Bionic:
  Triaged

Bug description:
  Test Case:
  1. Download opera deb file from opera.com
  2. Run the file to launch gnome-software
  3. Install it
  4. Proceed with the debconf prompt

  Actual result
  It hangs and generate this crashes when the user closes the debconf window.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1286840] Re: pulseaudio crashed with signal 7 in elf_machine_rel()

[Launchpad Bug Tracker]

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

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

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

Title:
  pulseaudio crashed with signal 7 in elf_machine_rel()

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  me pone error al iniciar y tarda mucho en arrancar

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Sun Mar  2 17:09:29 2014
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-02-20 (9 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140220.1)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Signal: 7
  SourcePackage: pulseaudio
  StacktraceTop:
   elf_machine_rel (reloc=0xb765fbd0, skip_ifunc=, 
reloc_addr_arg=, version=0xb6d1dba8, sym=0xb7658d14, 
map=0xb770d930) at ../sysdeps/i386/dl-machine.h:337
   elf_dynamic_do_Rel (skip_ifunc=, lazy=0, nrelative=, relsize=, reladdr=, map=) at 
do-rel.h:137
   _dl_relocate_object (scope=0xb770dae8, reloc_mode=1, consider_profiling=0) 
at dl-reloc.c:264
   dl_main (phdr=, phnum=, user_entry=0xbf80a95c, 
auxv=0xbf80aa40) at rtld.c:2204
   _dl_sysdep_start (start_argptr=start_argptr@entry=0xbf80a9f0, 
dl_main=dl_main@entry=0xb7710650 ) at ../elf/dl-sysdep.c:249
  Title: pulseaudio crashed with signal 7 in elf_machine_rel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/20/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1120Y4
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1120Y4:bd08/20/2009:svnSonyCorporation:pnVGN-NW21EF_S:pvrC602NXNT:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-NW21EF_S
  dmi.product.version: C602NXNT
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1273805] Re: pulseaudio crashed with SIGABRT in pa_rtsp_setparameter()

[Launchpad Bug Tracker]

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

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_rtsp_setparameter()

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Happened in background while trying to play YouTube video

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erik  15615 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 28 19:46:56 2014
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2011-09-14 (867 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_rtsp_setparameter () from /usr/lib/pulse-4.0/modules/librtp.so
   pa_raop_client_set_volume () from /usr/lib/pulse-4.0/modules/libraop.so
   pa_sink_set_mute () from /usr/lib/libpulsecore-4.0.so
   ?? () from /usr/lib/pulse-4.0/modules/libprotocol-native.so
   pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
  Title: pulseaudio crashed with SIGABRT in pa_rtsp_setparameter()
  UpgradeStatus: Upgraded to trusty on 2013-12-09 (50 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 06/19/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0HN341
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/19/2013:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D830
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1290542] Re: pulseaudio crashed with SIGSEGV in prepare_next_write_item()

[Launchpad Bug Tracker]

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

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

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

Title:
  pulseaudio crashed with SIGSEGV in prepare_next_write_item()

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  crashed while watching video via hdmi display port and hdmi
  displayport audio

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   2416 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 10 21:27:32 2014
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-03-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   main ()
  Title: pulseaudio crashed with SIGSEGV in pa_mainloop_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1299219] Re: pulseaudio crashed with SIGILL in pa_alsa_ucm_mapping_context_free()

[Launchpad Bug Tracker]

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

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

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

Title:
  pulseaudio crashed with SIGILL in pa_alsa_ucm_mapping_context_free()

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  seen when just logging in for the first time after a reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Mar 28 21:02:15 2014
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-02-22 (34 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140220.1)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  Signal: 4
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_ucm_mapping_context_free () from 
/usr/lib/pulse-4.0/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-4.0/modules/libalsa-util.so
   pa_alsa_profile_set_drop_unsupported () from 
/usr/lib/pulse-4.0/modules/libalsa-util.so
   pa_alsa_profile_set_probe () from /usr/lib/pulse-4.0/modules/libalsa-util.so
   module_alsa_card_LTX_pa__init () from 
/usr/lib/pulse-4.0/modules/module-alsa-card.so
  Title: pulseaudio crashed with SIGILL in pa_alsa_ucm_mapping_context_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1642078] Re: [HP Pavilion 14-av005la (ENERGY STAR)] Black screen at startup

[Launchpad Bug Tracker]

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

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

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

Title:
  [HP Pavilion 14-av005la (ENERGY STAR)] Black screen at startup

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The laptop starts up fine but the screen is black; even though the
  screen is black I can hear the drum sound prompting me to log in.

  WORKAROUND: Reboot once, sometimes twice.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov 15 17:56:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:8246]
  InstallationDate: Installed on 2016-11-10 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.03
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8246
  dmi.board.vendor: HP
  dmi.board.version: 98.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.03:bd05/03/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn8246:rvr98.11:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Nov 15 17:21:18 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2
  xserver.video_driver: amdgpu

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

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

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

[Bug Watch Updater]

** Changed in: pulseaudio
   Status: Confirmed => Fix Released

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

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

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Triaged

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

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

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

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

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

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Daniel Axtens]

This is not a full solution. In Xenial this renaming works even if
initramfs has *not* been updated and there is no 70-persistent-net.rules
file in the initial ramdisk. I'm still figuring out why this is, but it
means that even if my patch were applied, there would be a regression in
bionic vs xenial.

Here's a snippet from dmesg showing the same device being renamed twice,
this is a xenial guest. It shows the device going from the kernel name
(eth0) to the udev slot based name (ens16), to the name specified in the
udev rules file that is *not* present in initrd.

ubuntu@xt2:~$ dmesg|grep renamed
[2.428015] virtio_net virtio3 ens16: renamed from eth0
[5.317990] virtio_net virtio3 ens3: renamed from ens16

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[Kunwardeep Singh]

I am using Dell Inspiron 15R (N5010) and this bug affects my system as
described above. Waiting for the fix.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in bluez package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1722185] Re: gnome-software (11) g_io_channel_shutdown → pk_client_helper_copy_stdout_cb → g_main_dispatch → g_main_context_dispatch → g_main_context_iterate

[Robert Ancell]

https://github.com/hughsie/PackageKit/pull/250

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

Title:
  gnome-software (11) g_io_channel_shutdown →
  pk_client_helper_copy_stdout_cb → g_main_dispatch →
  g_main_context_dispatch → g_main_context_iterate

Status in packagekit package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Confirmed

Bug description:
  Test Case:
  1. Download opera deb file from opera.com
  2. Run the file to launch gnome-software
  3. Install it
  4. Proceed with the debconf prompt

  Actual result
  It hangs and generate this crashes when the user closes the debconf window.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1722185] Re: gnome-software (11) g_io_channel_shutdown → pk_client_helper_copy_stdout_cb → g_main_dispatch → g_main_context_dispatch → g_main_context_iterate

[Robert Ancell]

Seems to be an issue in PackageKit - it doesn't unregister callbacks
when the PkClientHelper object is finalized.

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

** No longer affects: gnome-software (Ubuntu Bionic)

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

Title:
  gnome-software (11) g_io_channel_shutdown →
  pk_client_helper_copy_stdout_cb → g_main_dispatch →
  g_main_context_dispatch → g_main_context_iterate

Status in packagekit package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Confirmed

Bug description:
  Test Case:
  1. Download opera deb file from opera.com
  2. Run the file to launch gnome-software
  3. Install it
  4. Proceed with the debconf prompt

  Actual result
  It hangs and generate this crashes when the user closes the debconf window.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1722185] Re: gnome-software (11) g_io_channel_shutdown → pk_client_helper_copy_stdout_cb → g_main_dispatch → g_main_context_dispatch → g_main_context_iterate

[Robert Ancell]

** Description changed:

+ Test Case:
+ 1. Download opera deb file from opera.com
+ 2. Run the file to launch gnome-software
+ 3. Install it
+ 4. Proceed with the debconf prompt
+ 
+ Actual result
+ It hangs and generate this crashes when the user closes the debconf window.
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

Title:
  gnome-software (11) g_io_channel_shutdown →
  pk_client_helper_copy_stdout_cb → g_main_dispatch →
  g_main_context_dispatch → g_main_context_iterate

Status in packagekit package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Confirmed

Bug description:
  Test Case:
  1. Download opera deb file from opera.com
  2. Run the file to launch gnome-software
  3. Install it
  4. Proceed with the debconf prompt

  Actual result
  It hangs and generate this crashes when the user closes the debconf window.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1722185] Re: gnome-software (11) g_io_channel_shutdown → pk_client_helper_copy_stdout_cb → g_main_dispatch → g_main_context_dispatch → g_main_context_iterate

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-software (11) g_io_channel_shutdown →
  pk_client_helper_copy_stdout_cb → g_main_dispatch →
  g_main_context_dispatch → g_main_context_iterate

Status in packagekit package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Confirmed

Bug description:
  Test Case:
  1. Download opera deb file from opera.com
  2. Run the file to launch gnome-software
  3. Install it
  4. Proceed with the debconf prompt

  Actual result
  It hangs and generate this crashes when the user closes the debconf window.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1722185] Re: gnome-software (11) g_io_channel_shutdown → pk_client_helper_copy_stdout_cb → g_main_dispatch → g_main_context_dispatch → g_main_context_iterate

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-software (11) g_io_channel_shutdown →
  pk_client_helper_copy_stdout_cb → g_main_dispatch →
  g_main_context_dispatch → g_main_context_iterate

Status in packagekit package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Confirmed

Bug description:
  Test Case:
  1. Download opera deb file from opera.com
  2. Run the file to launch gnome-software
  3. Install it
  4. Proceed with the debconf prompt

  Actual result
  It hangs and generate this crashes when the user closes the debconf window.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1771239] [NEW] [Inspiron 5537, Realtek ALC3223, Speaker, Internal] No sound at all

[Elias Soares]

Public bug reported:

My sound was working just fine, then tonight I came to use my notebook,
and noticed that there was no sound from any applications.

Using the ubuntu settings sound test, I was getting audio from both
speaker and headphones, but moving the volume bar doesn't do any
feedback, chrome and spotivyhave no audio.

Reinstalled the pulseaudio, now moving the volume bar plays the feedback
"beep", but still no audio from applications, and no more audio on
speaker test!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  esoares6391 F pulseaudio
 /dev/snd/controlC0:  esoares6391 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon May 14 22:11:08 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-09-18 (603 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Áudio interno - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm2642 F pulseaudio
  esoares6391 F pulseaudio
 /dev/snd/controlC0:  gdm2642 F pulseaudio
  esoares6391 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Inspiron 5537, Realtek ALC3223, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to bionic on 2017-10-24 (202 days ago)
dmi.bios.date: 08/25/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0YK7DY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A09
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5537:pvrA09:rvnDellInc.:rn0YK7DY:rvrA00:cvnDellInc.:ct8:cvrA09:
dmi.product.family: 00
dmi.product.name: Inspiron 5537
dmi.product.version: A09
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [Inspiron 5537, Realtek ALC3223, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My sound was working just fine, then tonight I came to use my
  notebook, and noticed that there was no sound from any applications.

  Using the ubuntu settings sound test, I was getting audio from both
  speaker and headphones, but moving the volume bar doesn't do any
  feedback, chrome and spotivyhave no audio.

  Reinstalled the pulseaudio, now moving the volume bar plays the
  feedback "beep", but still no audio from applications, and no more
  audio on speaker test!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  esoares6391 F pulseaudio
   /dev/snd/controlC0:  esoares6391 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 14 22:11:08 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-09-18 (603 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2642 F pulseaudio
esoares6391 F pulseaudio
   /dev/snd/controlC0:  gdm2642 F pulseaudio
esoares6391 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Inspiron 5537, Realtek ALC3223, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to bionic on 2017-10-24 (202 days ago)
  dmi.bios.date: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0YK7DY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 

[Touch-packages] [Bug 1722185] Re: gnome-software (11) g_io_channel_shutdown → pk_client_helper_copy_stdout_cb → g_main_dispatch → g_main_context_dispatch → g_main_context_iterate

[Robert Ancell]

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

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

Title:
  gnome-software (11) g_io_channel_shutdown →
  pk_client_helper_copy_stdout_cb → g_main_dispatch →
  g_main_context_dispatch → g_main_context_iterate

Status in packagekit package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Confirmed

Bug description:
  Test Case:
  1. Download opera deb file from opera.com
  2. Run the file to launch gnome-software
  3. Install it
  4. Proceed with the debconf prompt

  Actual result
  It hangs and generate this crashes when the user closes the debconf window.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1771232] Re: Lightdm no longer works after 18.04 upgrade

[Kevin Dalley]

** Attachment added: "Results of systemctl status lightdm"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1771232/+attachment/5139562/+files/lightdm-status

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

Title:
  Lightdm no longer works after 18.04 upgrade

Status in lightdm package in Ubuntu:
  New

Bug description:
  Both lightdm and gdm3 no longer work after the 18.04 upgrade, though I
  have been able to use lxdm, somewhat, if I use LXDE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon May 14 17:06:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (1092 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2018-05-10T11:40:28.736754
  mtime.conffile..etc.pam.d.lightdm-greeter: 2018-05-10T11:40:45.424698

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

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

[Touch-packages] [Bug 1771232] Re: Lightdm no longer works after 18.04 upgrade

[Kevin Dalley]

I commented out pam_kwallet.so in /etc/pam.d/
lightdm and lightdm-greeter

since this shared library does not exist, and I received warning
messages about it.

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

Title:
  Lightdm no longer works after 18.04 upgrade

Status in lightdm package in Ubuntu:
  New

Bug description:
  Both lightdm and gdm3 no longer work after the 18.04 upgrade, though I
  have been able to use lxdm, somewhat, if I use LXDE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon May 14 17:06:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (1092 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2018-05-10T11:40:28.736754
  mtime.conffile..etc.pam.d.lightdm-greeter: 2018-05-10T11:40:45.424698

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

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

[Touch-packages] [Bug 1771235] [NEW] ext4 failed

[Romero Rolim de Santana]

Public bug reported:

Instable system with frozen and necessary reboot

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon May 14 21:25:26 2018
DistUpgraded: 2018-05-12 04:48:36,552 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Samsung Electronics Co Ltd Skylake GT2 [HD Graphics 520] 
[144d:c136]
InstallationDate: Installed on 2018-05-12 (2 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3L
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-12 (2 days ago)
dmi.bios.date: 06/01/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P09AFN.043.170601.KS
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP900X3L-KW1BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL8830A0A-C01-G001-S0001+10.0.14393
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09AFN.043.170601.KS:bd06/01/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3L:pvrP09AFN:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3L-KW1BR:rvrSGL8830A0A-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.family: SAMSUNG ATIV
dmi.product.name: 900X3L
dmi.product.version: P09AFN
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
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 May 12 04:17:44 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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

Title:
  ext4 failed

Status in xorg package in Ubuntu:
  New

Bug description:
  Instable system with frozen and necessary reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon May 14 21:25:26 2018
  DistUpgraded: 2018-05-12 04:48:36,552 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Samsung Electronics Co Ltd Skylake GT2 [HD Graphics 520] 
[144d:c136]
  InstallationDate: Installed on 2018-05-12 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3L
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (2 days ago)
  dmi.bios.date: 06/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09AFN.043.170601.KS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP900X3L-KW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8830A0A-C01-G001-S0001+10.0.14393
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 

[Touch-packages] [Bug 1771232] [NEW] Lightdm no longer works after 18.04 upgrade

[Kevin Dalley]

Public bug reported:

Both lightdm and gdm3 no longer work after the 18.04 upgrade, though I
have been able to use lxdm, somewhat, if I use LXDE.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: LXDE
Date: Mon May 14 17:06:53 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (1092 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.pam.d.lightdm: 2018-05-10T11:40:28.736754
mtime.conffile..etc.pam.d.lightdm-greeter: 2018-05-10T11:40:45.424698

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


** Tags: amd64 apport-bug bionic

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

Title:
  Lightdm no longer works after 18.04 upgrade

Status in lightdm package in Ubuntu:
  New

Bug description:
  Both lightdm and gdm3 no longer work after the 18.04 upgrade, though I
  have been able to use lxdm, somewhat, if I use LXDE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon May 14 17:06:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-18 (1092 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2018-05-10T11:40:28.736754
  mtime.conffile..etc.pam.d.lightdm-greeter: 2018-05-10T11:40:45.424698

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

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

[Touch-packages] [Bug 1771033] Re: [needs-packaging] python3-avahi is missing in Ubuntu/debian

[Brian Murray]

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

** Summary changed:

- python3-avahi is missing in Ubuntu/debian
+ [needs-packaging] python3-avahi is missing in Ubuntu/debian

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

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

Title:
  [needs-packaging] python3-avahi is missing in Ubuntu/debian

Status in avahi package in Ubuntu:
  New
Status in avahi package in Debian:
  New

Bug description:
  Under Ubuntu 18.04 if you install the package Gajim the local account
  is permanently disabled because of missing dependencies.

  https://dev.gajim.org/gajim/gajim/issues/9125

  The required package is python3-avahi

  The python3-avahi package is missing, apt-get is unable to find it.

  This is a vital feature for us, we use Gajim internally without
  internet, and this simply works, no adding accounts, no information or
  messages sent over the internet, it all works locally.

  I hope this package can be added, if this is the wrong place to file
  this bug I applologize. I don't have a lot of experience reporting
  bugs.

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

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

[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.14.1-0ubuntu3.28

---
apport (2.14.1-0ubuntu3.28) trusty-security; urgency=medium

  * REGRESSION UPDATE: Fix regression that caused a Traceback in the
container support (LP: #1733366)
- data/apport: add a second os.path.exists check to ensure we do not
  receive a Traceback in is_container_id() and add an exception handler in
  case either name space can not be found.

 -- Brian Murray   Fri, 20 Apr 2018 14:11:44 -0700

** Changed in: apport (Ubuntu Trusty)
   Status: In Progress => Fix Released

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

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/b6b178fe6ed572189dbfe2627876ed9e9d59ace2

  ---

  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:

  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

[Mathieu Trudel-Lapierre]

Verification-done on artful: nplan 0.32~17.10.4

As above for the xenial tests: I get an IPv6 address when I should, and
no IPv6 address when I shouldn't, based on the setup of the LXD bridge.
Behavior is as expected.

** Tags removed: verification-needed verification-needed-artful 
verification-needed-xenial
** Tags added: verification-done-artful verification-done-xenial

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in nplan source package in Xenial:
  Fix Committed
Status in nplan source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  All users of netplan.

  [Test case]

  == LXD containers ==
  1) Start an LXD container (artful or bionic)
  2) Verify that an IPv6 address is present
  3) Verify that the system is brought up in a reasonable time (does not wait 2 
minutes to be reachable).

  == servers / cloud instances ==
  1) Start a bionic system, with no IPv6 connectivity (no router to advertise a 
prefix)
  2) Verify that the system boots quickly (does not wait 2 minutes to be 
reachable).

  [Regression potential]
  Since this changes default IPv6 behavior, care should be taken to validate 
that systems are maintaining IPv6 connectivity when it is available, and 
similarly that systems where no IPv6 connectivity is available on the network 
are behaving correctly: there should not be long boot delays, and no extra IPv6 
addresses aside from link-local addresses generated by the kernel.

  --

  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
     lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
    name: eth0
    subnets:
    - type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
     Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
     Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
     Memory: 2.0M
    CPU: 19ms
     CGroup: /system.slice/systemd-networkd.service
     └─118 /lib/systemd/systemd-networkd

  Nov 13 18:37:34 bionic-demo systemd[1]: Starting 

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

[Mathieu Trudel-Lapierre]

Verification-done on xenial: nplan 0.32~16.04.5

nplan-configured LXD container appears to behave as expected: on a setup
with IPv6 enabled, I get an IPv6 address on the container without a
startup delay. In a host with IPv6 disabled on the lxd bridge, the
container also starts up appropriately, with no IPv6 address, as
expected.

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in nplan source package in Xenial:
  Fix Committed
Status in nplan source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  All users of netplan.

  [Test case]

  == LXD containers ==
  1) Start an LXD container (artful or bionic)
  2) Verify that an IPv6 address is present
  3) Verify that the system is brought up in a reasonable time (does not wait 2 
minutes to be reachable).

  == servers / cloud instances ==
  1) Start a bionic system, with no IPv6 connectivity (no router to advertise a 
prefix)
  2) Verify that the system boots quickly (does not wait 2 minutes to be 
reachable).

  [Regression potential]
  Since this changes default IPv6 behavior, care should be taken to validate 
that systems are maintaining IPv6 connectivity when it is available, and 
similarly that systems where no IPv6 connectivity is available on the network 
are behaving correctly: there should not be long boot delays, and no extra IPv6 
addresses aside from link-local addresses generated by the kernel.

  --

  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
     lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
    name: eth0
    subnets:
    - type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
     Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
     Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
     Memory: 2.0M
    CPU: 19ms
     CGroup: /system.slice/systemd-networkd.service
     └─118 /lib/systemd/systemd-networkd

  Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
  Nov 13 18:37:34 bionic-demo 

[Touch-packages] [Bug 1739005] Re: (QT5 bug?) In Kubuntu 17.10 the printing options (size, quality...) don't show in printer properties dialog

[Launchpad Bug Tracker]

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

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

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

Title:
  (QT5 bug?) In Kubuntu 17.10 the printing options (size, quality...)
  don't show in printer properties dialog

Status in cups package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I just moved to Kubuntu 17.10.

  When I want to print a pdf doc (okular), a picture (gwenview), a mail
  etc. the tab specifying the printer options, as duplex printing,
  printing quality, paper size etc. doesn't appear anymore.

  My printer is an Epson WF-7620 and the drivers are up to date. I can
  still modify the printing options via cups (localhost:631) or the kde
  settings panel.

  It seems to be a Qt bug as I found this report : 
https://bugreports.qt.io/browse/QTBUG-54464
  This reports seems to mention that the problem has found a solution and that 
this solution will be included in next spring qt version. I'm not able to work 
this out by myself but this is a really annoying issue and I don't like much 
the idea of waiting 6 more months with it.

  Any chance someone could build an official update with a patch?

  Thanks in advance for your work an any answer...

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

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

[Touch-packages] [Bug 1769346] Re: Unable to install 18.04 server AMD64 with targeted kernel: initramfs-tools

[Manny Flores]

Confirming that I get this same error on a fresh new install of 18.04
server. Not sure why there's a reference to i386 since this is a 64-bit
server installation.

error: file '/boot/grub/i386-pc/normal.mod' not found.
Entering rescue mode...
grub rescue>

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

Title:
  Unable to install 18.04 server AMD64 with targeted kernel: initramfs-
  tools

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Trying to install from: ubuntu-18.04-server-amd64.iso

  at boot: F6->expert mode and F4->minimal VM

  I go through the usual steps but when it comes to the "install the
  system" phase, if I select normal (not live) and then "targeted", the
  installation stops with an error on initramfs.

  The error doesn't occur if I use a generic kernel instead of the
  targeted one.

  at that phase I'm not yet able to install reportbug so below you'll
  find what I found in syslog. VM running under ESXi 6.7.

  Thanks!

  May  5 12:52:58 in-target: (Reading database ... 100%^M(Reading database ... 
11077 files and directories currently installed.)^M
  May  5 12:52:58 in-target: Preparing to unpack 
.../0-linux-headers-4.15.0-20_4.15.0-20.21_all.deb ...^M
  May  5 12:52:58 in-target: Unpacking linux-headers-4.15.0-20 (4.15.0-20.21) 
...^M
  May  5 12:53:03 in-target: Selecting previously unselected package 
linux-headers-4.15.0-20-generic.^M
  May  5 12:53:03 in-target: Preparing to unpack 
.../1-linux-headers-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
  May  5 12:53:03 in-target: Unpacking linux-headers-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:05 in-target: Selecting previously unselected package 
linux-headers-generic.^M
  May  5 12:53:05 in-target: Preparing to unpack 
.../2-linux-headers-generic_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:05 in-target: Unpacking linux-headers-generic (4.15.0.20.23) 
...^M
  May  5 12:53:05 in-target: Selecting previously unselected package 
linux-headers-virtual.^M
  May  5 12:53:05 in-target: Preparing to unpack 
.../3-linux-headers-virtual_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:05 in-target: Unpacking linux-headers-virtual (4.15.0.20.23) 
...^M
  May  5 12:53:05 in-target: Selecting previously unselected package 
linux-modules-4.15.0-20-generic.^M
  May  5 12:53:05 in-target: Preparing to unpack 
.../4-linux-modules-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
  May  5 12:53:05 in-target: Unpacking linux-modules-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:08 in-target: Selecting previously unselected package 
linux-image-4.15.0-20-generic.^M
  May  5 12:53:08 in-target: Preparing to unpack 
.../5-linux-image-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
  May  5 12:53:08 in-target: Unpacking linux-image-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:08 in-target: Selecting previously unselected package 
linux-image-virtual.^M
  May  5 12:53:08 in-target: Preparing to unpack 
.../6-linux-image-virtual_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:08 in-target: Unpacking linux-image-virtual (4.15.0.20.23) ...^M
  May  5 12:53:08 in-target: Selecting previously unselected package 
linux-virtual.^M
  May  5 12:53:08 in-target: Preparing to unpack 
.../7-linux-virtual_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:08 in-target: Unpacking linux-virtual (4.15.0.20.23) ...^M
  May  5 12:53:09 in-target: Setting up linux-modules-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:09 in-target: Setting up linux-image-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:09 in-target: I: /vmlinuz.old is now a symlink to 
boot/vmlinuz-4.15.0-20-generic^M
  May  5 12:53:09 in-target: I: /initrd.img.old is now a symlink to 
boot/initrd.img-4.15.0-20-generic^M
  May  5 12:53:09 in-target: I: /vmlinuz is now a symlink to 
boot/vmlinuz-4.15.0-20-generic^M
  May  5 12:53:09 in-target: I: /initrd.img is now a symlink to 
boot/initrd.img-4.15.0-20-generic^M
  May  5 12:53:09 in-target: Setting up linux-image-virtual (4.15.0.20.23) ...^M
  May  5 12:53:10 in-target: Setting up linux-headers-4.15.0-20 (4.15.0-20.21) 
...^M
  May  5 12:53:10 in-target: Setting up linux-headers-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:10 in-target: Setting up linux-headers-generic (4.15.0.20.23) 
...^M
  May  5 12:53:10 in-target: Setting up linux-headers-virtual (4.15.0.20.23) 
...^M
  May  5 12:53:10 in-target: Setting up linux-virtual (4.15.0.20.23) ...^M
  May  5 12:53:10 in-target: Processing triggers for 
linux-image-4.15.0-20-generic (4.15.0-20.21) ...^M
  May  5 12:53:10 in-target: /etc/kernel/postinst.d/initramfs-tools:^M
  May  5 12:53:10 in-target: update-initramfs: Generating 
/boot/initrd.img-4.15.0-20-generic^M
  May  5 12:53:10 in-target: mkinitramfs: failed to determine device for /^M
  May  5 12:53:10 in-target: mkinitramfs: workaround is 

[Touch-packages] [Bug 1771216] [NEW] Disabling one of multiple wlan chipsets

[Josy]

Public bug reported:

I have attached multiple WLANs to my computer. One is build-in (pci) and one is 
connected via usb.
The Ubuntu Gnome GUI shows 2 WLANs and for both a different signal strength. 
When however I disable one of the WLANs via the "Turn Off" option, it is 
expected that only this WLAN is deactivated, however both WLANs get disabled at 
the same time. When enabling one of them afterwards, both get enabled again. 
There does not seem to be a way to disable one of them alone. 

lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge
00:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI 
bridge (int gfx)
00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI 
bridge (PCIE port 0)
00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI 
bridge (PCIE port 3)
00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI 
bridge (PCIE port 4)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 
Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 
Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 3a)
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 11h Processor 
HyperTransport Configuration (rev 40)
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 11h Processor 
Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 11h Processor 
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 11h Processor 
Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 11h Processor 
Link Control
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RS780M [Mobility Radeon HD 3200]
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8042 PCI-E Fast 
Ethernet Controller (rev 10)
06:00.0 Network controller: Broadcom Limited BCM4322 802.11a/b/g/n Wireless LAN 
Controller (rev 01)

lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 04f2:b083 Chicony Electronics Co., Ltd CKF7063 Webcam 
(HP)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 03f0:171d Hewlett-Packard Bluetooth 2.0 Interface 
[Broadcom BCM2045]
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n 
Wireless Network Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: rfkill 2.31.1-0.4ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon May 14 23:15:51 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
 libsmartcols1 2.31.1-0.4ubuntu3
InstallationDate: Installed on 2016-12-24 (506 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: util-linux
UpgradeStatus: Upgraded to bionic on 2018-05-11 (2 days ago)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot when turning of via gui"
   
https://bugs.launchpad.net/bugs/1771216/+attachment/5139491/+files/Screenshot%20from%202018-05-14%2023-31-41.png

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

Title:
  Disabling one of multiple wlan 

[Touch-packages] [Bug 1771212] Re: Ubuntu 18.04 doesn't detect stylus

[Mad Baron]

** Package changed: unity-control-center (Ubuntu) => gnome-control-
center-signon (Ubuntu)

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

Title:
  Ubuntu 18.04 doesn't detect stylus

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Even though Ubuntu detects the Wacom Bamboo Pad CTH-300 model tablet
  itself I can't draw with the stylus.  For some reason Ubuntu can
  identify the tablet but not the stylus; I can move the cursor with the
  stylus I can only draw faint straight lines on my drawing apps (I
  can't even drag and select with it).  I'm using the gnome Xorg build
  instead of Wayland, which many users suggested but I still encounter
  the same problem.  I would use the Unity build but it keeps freezing 5
  or 10 minutes after logging in.

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

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

[Touch-packages] [Bug 1771212] [NEW] Ubuntu 18.04 doesn't detect stylus

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Even though Ubuntu detects the Wacom Bamboo Pad CTH-300 model tablet
itself I can't draw with the stylus.  For some reason Ubuntu can
identify the tablet but not the stylus; I can move the cursor with the
stylus I can only draw faint straight lines on my drawing apps (I can't
even drag and select with it).  I'm using the gnome Xorg build instead
of Wayland, which many users suggested but I still encounter the same
problem.  I would use the Unity build but it keeps freezing 5 or 10
minutes after logging in.

** Affects: gnome-control-center-signon (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Ubuntu 18.04 doesn't detect stylus
https://bugs.launchpad.net/bugs/1771212
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gnome-control-center-signon in Ubuntu.

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[ilia fata]

I have a Dell Inspiron N5010 laptop and this bug affected my system.
hope to fix the bug soon.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in bluez package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1761867] Re: Can not remove nvidia-390.x drivers

[Doug McMahon]

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

** This bug is no longer a duplicate of bug 1761593
   Uninstall left nouveau blacklisted

** This bug has been marked a duplicate of bug 175
   Using "Software and Updates -> Additional Drivers" to Switch Fails

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

Title:
  Can not remove nvidia-390.x drivers

Status in software-properties package in Ubuntu:
  New

Bug description:
  What additional drivers does do is to remove the nvidia-driver-390
  metapackage. This has no practical effect in removing the driver & lib
  packages other than having them marked for autoremove

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.25
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr  6 16:42:17 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Thomas Diesenreiter]

See photo of the screen attached.

** Attachment added: "IMG_20180514_224101.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204/+attachment/5139476/+files/IMG_20180514_224101.jpg

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
  InstallationDate: Installed on 2013-11-21 (1635 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P00ACX
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3F-K01DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3F
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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: Fri Apr 22 16:22:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Touch-packages] [Bug 1771204] [NEW] Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

[Thomas Diesenreiter]

Public bug reported:

My laptop was running fine for years, but after the latest update to 18.04 and 
the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
https://bugs.freedesktop.org/show_bug.cgi?id=64332

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon May 14 22:31:29 2018
DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0f9]
InstallationDate: Installed on 2013-11-21 (1635 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe 
plymouth:debug
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago)
dmi.bios.date: 04/26/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P00ACX
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP900X3F-K01DE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 900X3F
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
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: Fri Apr 22 16:22:53 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1495 
 vendor BOE
xserver.version: 2:1.17.2-1ubuntu9.1

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


** Tags: amd64 apport-bug bionic corruption third-party-packages ubuntu

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

Title:
  Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  My laptop was running fine for years, but after the latest update to 18.04 
and the reboot there were horizontal lines everywhere. It seems like its a 
regression of an older bug, because its the same bug with the same strange 
behaviour as listed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=64332

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 14 22:31:29 2018
  DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd 

[Touch-packages] [Bug 1771205] [NEW] This error cause fail of system

[Norbert Banas]

Public bug reported:

Sorry, I cannot write about it right now.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon May 14 21:51:11 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0725]
InstallationDate: Installed on 2018-04-19 (24 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1bcf:2c00 Sunplus Innovation Technology Inc. 
 Bus 001 Device 002: ID 8087:07dc Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 11-3162
ProcEnviron:
 LANGUAGE=pl
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=4d2bbd82-2c08-4d05-b7b1-f90a3e290e20 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/19/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.8
dmi.board.name: 0FCNP5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.8:bd04/19/2016:svnDellInc.:pnInspiron11-3162:pvr1.0.8:rvnDellInc.:rn0FCNP5:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 11-3162
dmi.product.version: 1.0.8
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

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

Title:
  This error cause fail of system

Status in xorg package in Ubuntu:
  New

Bug description:
  Sorry, I cannot write about it right now.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon May 14 21:51:11 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0725]
  InstallationDate: Installed on 2018-04-19 (24 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2c00 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 8087:07dc Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 11-3162
  ProcEnviron:
   LANGUAGE=pl
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=4d2bbd82-2c08-4d05-b7b1-f90a3e290e20 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.8
  dmi.board.name: 0FCNP5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 

[Touch-packages] [Bug 1766542] Re: Installation blocks when the machine is behind a proxy server

[Steve Langasek]

Robert, can you please provide complete steps to reproduce this bug?  My
understanding from discussion elsewhere that this is specific to oem-
config mode; is that correct?

If your network is incorrectly configured and you have a route to the
Internet but traffic is dropped, it is expected that an initial
connection to the apt mirror will have to hit a tcp connection timeout
(by default, ~128 seconds); so that might qualify as "several minutes".
What behavior are you seeing that is "too long", and how long do you
expect this to take?

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

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

Title:
  Installation blocks when the machine is behind a proxy server

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Incomplete
Status in apt source package in Bionic:
  New
Status in ubiquity source package in Bionic:
  New

Bug description:
  When the machine is behind a proxy server, the installation will block
  for a while (several minutes) to retrieve the package lists. The
  timeouts are too long and makes user feels the machine may have some
  problems.

  The symptom is similar with bug #14599, but it seems the apt-setup
  module was rewritten.

  Another method to trigger this issue is to make the machine cannot
  access to the Internet, for instance: a wrong gateway.

  Image: 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766542/+subscriptions

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

[Touch-packages] [Bug 1749361] Re: package linux-image-extra-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code

[Launchpad Bug Tracker]

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

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

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

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

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Can't tell more

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Feb 14 10:59:34 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2017-04-11 (308 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.13.0-32-generic 4.13.0-32.35~16.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

[Tiago]

Ubuntu 18 is still with the same bug

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771185] [NEW] Secondary monitor not connecting in 18.04 LTS

[Mihai Rusoaie]

Public bug reported:

I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M
(nvidia driver v390) and a Benq W1070 projector.

I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for
a split second and then gets disconnected. In Ubuntu 16.04 projector was
working fine as a mirror display and extended desktop. Here's what I
already tried:

- enable the nouveau driver instead of the nvidia driver -> no result
- enable the on-board intel board with sudo prime-select intel -> no result
- apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no 
result
- disable nouveau driver, disable nvidia driver from the repository and install 
nvidia driver from nvidia website (both 390 and 396) -> no result
- installed CCSM (CompizConfig Settings Manager) and disabled display 
auto-detection -> no result
- played around with the refresh rate (some forums say that the two outputs 
have to be in sync -> no result
- deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still 
the same issue
- tried to manually enable the output with xrandr --output HDMI-1-2 --mode 
1920x1920 -> nothing
- under settings -> devices -> displays I don't see a secondary display (just 
the main one)

I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to
day)

Here is the output of xrandr the very second when I connect the
projector (then HDMI-1-2 goes disconnected and no modes are displayed):

~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis 
y axis) 345mm x 194mm
   1920x1080 60.02*+  60.0159.9759.9659.93
   1680x1050 59.9559.88
   1600x1024 60.17
   1400x1050 59.98
   1600x900  59.9959.9459.9559.82
   1280x1024 60.02
   1440x900  59.89
   1400x900  59.9659.88
   1280x960  60.00
   1440x810  60.0059.97
   1368x768  59.8859.85
   1360x768  59.8059.96
   1280x800  59.9959.9759.8159.91
   1152x864  60.00
   1280x720  60.0059.9959.8659.74
   1024x768  60.0460.00
   960x720   60.00
   928x696   60.05
   896x672   60.01
   1024x576  59.9559.9659.9059.82
   960x600   59.9360.00
   960x540   59.9659.9959.6359.82
   800x600   60.0060.3256.25
   840x525   60.0159.88
   864x486   59.9259.57
   800x512   60.17
   700x525   59.98
   800x450   59.9559.82
   640x512   60.02
   720x450   59.89
   700x450   59.9659.88
   640x480   60.0059.94
   720x405   59.5158.99
   684x384   59.8859.85
   680x384   59.8059.96
   640x400   59.8859.98
   576x432   60.06
   640x360   59.8659.8359.8459.32
   512x384   60.00
   512x288   60.0059.92
   480x270   59.6359.82
   400x300   60.3256.34
   432x243   59.9259.57
   320x240   60.05
   360x202   59.5159.13
   320x180   59.8459.32
DP-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
DP-1-2 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)
  1920x1080 (0x258) 148.500MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.50KHz
v: height 1080 start 1084 end 1089 total 1125   clock  
60.00Hz
  1920x1080 (0x259) 148.500MHz +HSync +VSync
h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
56.25KHz
v: height 1080 start 1084 end 1089 total 1125   clock  
50.00Hz
  1920x1080 (0x25a) 148.352MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.43KHz
v: height 1080 start 1084 end 1089 total 1125   clock  
59.94Hz
  1920x1080i (0x25b) 74.250MHz +HSync +VSync Interlace
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
33.75KHz
v: height 1080 start 1084 end 1094 total 1125   clock  
60.00Hz
  1920x1080i (0x25c) 74.250MHz +HSync +VSync Interlace
h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
28.12KHz
v: height 1080 start 1084 end 1094 total 1125   clock  
50.00Hz
  1920x1080 (0x25d) 74.250MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
33.75KHz
v: height 1080 start 1084 end 1089 total 1125   clock  
30.00Hz
  1920x1080 (0x25e) 74.250MHz +HSync +VSync
h: width  1920 start 2448 end 2492 

[Touch-packages] [Bug 1771188] [NEW] Ubuntu 18.04 System hangs when logging in or rebooting. Shutdown reboots instead. Suspend wakes after suspending.

[George Crum]

Public bug reported:

Originally I thought the system had crashed when logging in or shutdown.
But it turns out it's hanging for about 60-90 seconds.  When shutting
down system will reboot instead.

lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

uname -a
Linux bridge 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

Clean install.
Shutting down system reboots instead.
Suspends does not stay suspended.
Login and shutdown hangs for a long time (60-90 seconds)


Seeing these in logs.

[  197.300273] [ cut here ]
[  197.300274] nouveau :01:00.0: timeout
[  197.300336] WARNING: CPU: 5 PID: 1938 at 
/build/linux-5s7Xkn/linux-4.15.0/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207
 gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
[  197.300336] Modules linked in: msr thunderbolt cmac bnep nouveau ttm arc4 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
videodev btusb btrtl media btbcm btintel bluetooth ecdh_generic nls_iso8859_1 
ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 
nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG 
xt_limit xt_tcpudp xt_addrtype snd_hda_codec_hdmi hid_multitouch 
snd_hda_codec_realtek dell_smbios_wmi snd_hda_codec_generic dell_wmi 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof mxm_wmi dell_laptop 
dell_smbios_smm dell_smbios dcdbas nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_intel xt_conntrack dell_smm_hwmon snd_hda_codec snd_hda_core intel_rapl 
snd_hwdep x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm kvm_intel kvm 
snd_seq_midi
[  197.300373]  snd_seq_midi_event irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc snd_rawmidi ath10k_pci snd_seq ath10k_core aesni_intel 
snd_seq_device ath aes_x86_64 snd_timer crypto_simd glue_helper cryptd 
intel_cstate intel_rapl_perf ip6table_filter mac80211 ip6_tables snd 
nf_conntrack_netbios_ns nf_conntrack_broadcast input_leds joydev nf_nat_ftp 
nf_nat serio_raw cfg80211 idma64 rtsx_pci_ms virt_dma nf_conntrack_ftp memstick 
soundcore nf_conntrack mei_me intel_lpss_pci processor_thermal_device 
intel_pch_thermal shpchp mei intel_lpss intel_soc_dts_iosf libcrc32c wmi 
mac_hid int3403_thermal int340x_thermal_zone int3400_thermal intel_hid 
acpi_thermal_rel acpi_pad tpm_crb sparse_keymap sch_fq_codel parport_pc ppdev 
lp parport iptable_filter ip_tables x_tables autofs4 i915 rtsx_pci_sdmmc
[  197.300397]  i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt 
nvme fb_sys_fops psmouse drm nvme_core rtsx_pci ahci libahci i2c_hid hid video
[  197.300403] CPU: 5 PID: 1938 Comm: Xorg Tainted: GW
4.15.0-20-generic #21-Ubuntu
[  197.300404] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.9.4 
04/23/2018
[  197.300420] RIP: 0010:gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
[  197.300420] RSP: :b8c0847e7750 EFLAGS: 00010286
[  197.300421] RAX:  RBX: 980259b63e20 RCX: 0006
[  197.300422] RDX: 0007 RSI: 0086 RDI: 98027e556490
[  197.300422] RBP: b8c0847e7788 R08: 0001 R09: 0b9f
[  197.300423] R10: c0c6c6d0 R11:  R12: 980258b66c00
[  197.300423] R13: 98024e9b8d80 R14: 002d78c6d8c0 R15: 980257106600
[  197.300424] FS:  7fcbd5229600() GS:98027e54() 
knlGS:
[  197.300425] CS:  0010 DS:  ES:  CR0: 80050033
[  197.300426] CR2: 7fcbcb1ed000 CR3: 00085a34c004 CR4: 003606e0
[  197.300426] Call Trace:
[  197.300442]  gp100_vmm_flush+0x17/0x20 [nouveau]
[  197.300456]  nvkm_vmm_iter.constprop.13+0x2e5/0x880 [nouveau]
[  197.300470]  ? gp100_vmm_pgt_dma+0x220/0x220 [nouveau]
[  197.300483]  ? nvkm_vmm_map_choose+0xb0/0xb0 [nouveau]
[  197.300496]  nvkm_vmm_map+0x21e/0x400 [nouveau]
[  197.300508]  ? gp100_vmm_pgt_dma+0x220/0x220 [nouveau]
[  197.300521]  nvkm_vram_map+0x57/0x80 [nouveau]
[  197.300533]  gf100_mem_map+0xf8/0x180 [nouveau]
[  197.300546]  nvkm_umem_map+0x6b/0x100 [nouveau]
[  197.300556]  nvkm_object_map+0x1a/0x30 [nouveau]
[  197.300565]  nvkm_ioctl_map+0x78/0xe0 [nouveau]
[  197.300573]  nvkm_ioctl+0x11d/0x280 [nouveau]
[  197.300590]  nvkm_client_ioctl+0x12/0x20 [nouveau]
[  197.300597]  nvif_object_ioctl+0x47/0x50 [nouveau]
[  197.300605]  nvif_object_map_handle+0x61/0xb0 [nouveau]
[  197.300621]  nouveau_ttm_io_mem_reserve+0x15c/0x1b0 [nouveau]
[  197.300624]  ttm_mem_io_reserve+0xb8/0xd0 [ttm]
[  197.300626]  ttm_mem_io_reserve_vm+0x31/0x90 [ttm]
[  197.300628]  ttm_bo_vm_fault+0x1b1/0x620 [ttm]
[  197.300631]  ? current_time+0x32/0x70
[  197.300632]  ? radix_tree_lookup+0xd/0x10
[  197.300648]  ? nouveau_gem_ioctl_cpu_prep+0x77/0xa0 [nouveau]
[  197.300663]  ? nouveau_gem_ioctl_pushbuf+0x1660/0x1660 [nouveau]
[  197.300670]  ? drm_ioctl_kernel+0x5f/0xb0 [drm]
[  197.300671]  __do_fault+0x24/0xf0
[  197.300673]  

[Touch-packages] [Bug 1771185] [NEW] Secondary monitor not connecting in 18.04 LTS

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M
(nvidia driver v390) and a Benq W1070 projector.

I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for
a split second and then gets disconnected. In Ubuntu 16.04 projector was
working fine as a mirror display and extended desktop. Here's what I
already tried:

- enable the nouveau driver instead of the nvidia driver -> no result
- enable the on-board intel board with sudo prime-select intel -> no result
- apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no 
result
- disable nouveau driver, disable nvidia driver from the repository and install 
nvidia driver from nvidia website (both 390 and 396) -> no result
- installed CCSM (CompizConfig Settings Manager) and disabled display 
auto-detection -> no result
- played around with the refresh rate (some forums say that the two outputs 
have to be in sync -> no result
- deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still 
the same issue
- tried to manually enable the output with xrandr --output HDMI-1-2 --mode 
1920x1920 -> nothing
- under settings -> devices -> displays I don't see a secondary display (just 
the main one)

I have the latest lxrandr, 0.3.1-1 under Ubuntu 18.04 (updated to day)

Here is the output of xrandr the very second when I connect the
projector (then HDMI-1-2 goes disconnected and no modes are displayed):

~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis 
y axis) 345mm x 194mm
   1920x1080 60.02*+  60.0159.9759.9659.93
   1680x1050 59.9559.88
   1600x1024 60.17
   1400x1050 59.98
   1600x900  59.9959.9459.9559.82
   1280x1024 60.02
   1440x900  59.89
   1400x900  59.9659.88
   1280x960  60.00
   1440x810  60.0059.97
   1368x768  59.8859.85
   1360x768  59.8059.96
   1280x800  59.9959.9759.8159.91
   1152x864  60.00
   1280x720  60.0059.9959.8659.74
   1024x768  60.0460.00
   960x720   60.00
   928x696   60.05
   896x672   60.01
   1024x576  59.9559.9659.9059.82
   960x600   59.9360.00
   960x540   59.9659.9959.6359.82
   800x600   60.0060.3256.25
   840x525   60.0159.88
   864x486   59.9259.57
   800x512   60.17
   700x525   59.98
   800x450   59.9559.82
   640x512   60.02
   720x450   59.89
   700x450   59.9659.88
   640x480   60.0059.94
   720x405   59.5158.99
   684x384   59.8859.85
   680x384   59.8059.96
   640x400   59.8859.98
   576x432   60.06
   640x360   59.8659.8359.8459.32
   512x384   60.00
   512x288   60.0059.92
   480x270   59.6359.82
   400x300   60.3256.34
   432x243   59.9259.57
   320x240   60.05  
   360x202   59.5159.13
   320x180   59.8459.32
DP-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
DP-1-2 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)
  1920x1080 (0x258) 148.500MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.50KHz
v: height 1080 start 1084 end 1089 total 1125   clock  
60.00Hz
  1920x1080 (0x259) 148.500MHz +HSync +VSync
h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
56.25KHz
v: height 1080 start 1084 end 1089 total 1125   clock  
50.00Hz
  1920x1080 (0x25a) 148.352MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.43KHz
v: height 1080 start 1084 end 1089 total 1125   clock  
59.94Hz
  1920x1080i (0x25b) 74.250MHz +HSync +VSync Interlace
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
33.75KHz
v: height 1080 start 1084 end 1094 total 1125   clock  
60.00Hz
  1920x1080i (0x25c) 74.250MHz +HSync +VSync Interlace
h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
28.12KHz
v: height 1080 start 1084 end 1094 total 1125   clock  
50.00Hz
  1920x1080 (0x25d) 74.250MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
33.75KHz
v: height 1080 start 1084 end 1089 total 1125   clock  
30.00Hz
  1920x1080 (0x25e) 74.250MHz +HSync +VSync
h: width  1920 

[Touch-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

[Łukasz Zemczak]

(please ignore the rejection comment above - someone put the wrong bug
number in an SRU so the rejection comment got included here instead)

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Committed

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  SRU Document:

  [Impact]

  We have several Lenovo machines like Lenovo P520 which have 2 analogue
  audio codecs on them, the internal speaker and front headset are
  connected to the 1st codec, the Rear mic, Line in and Line out are
  connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
  lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
  front headset) on the 1st codec can work. To make all audio devices
  work on this machine, upstream provided 3 patches for kernel audio
  driver and 5 patches for alsa-lib. The kernel patches are already in
  the linux-4.12, so this is not a problem anymore under 18.04 since we
  use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to
  backport them to v1.1.3-5, the 5 patches are list as below:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
  4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
  181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
  81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)

  Some explanation for these 5 patches, to make the audio work, the
  alsa-lib needs to add an audio configuration file and verb conf file
  for lenovo machines with dual codecs, these two files are put in a
  folder named by card_long_name, and the name of configuration file
  itself is also named by card_long_name, this is implemented by the
  patches of NO. 3rd and 5th.

  But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
   
  [Test Case]

  On the Lenovo machines with dual codecs (p520), I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can find the conf file and can parse the conf file
  successfully, and I tested the internal speaker, front headset, rear
  mic, line out and line in, all audio devices work well.

  On a HP and Dell machines without dual codecs, I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can't find conf file by card_long_name and card_name, the
  pulseaudio will drive the sound card as before, so all audio functions
  worked well as before.

  [Regression Potential]

  After adding these 5 patches, there 2 two changes introduced into the
  alsa-lib v1.1.3-5ubuntu1:

  1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
  2) before: the ucm parser will search the conf file/folder by card_name only; 
 after: the ucm parser will search the conf file/foler by card_long_name first, 
if it fails, it will fallback to use card_name to search again. So this change 
is compatible with old version.

  There is no regression since there is only one folder named by
  card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with
  dual codecs, it will find the conf file by card_long_name, if it runs
  on other machines, the search by card_long_name will definitely fail
  and fall back to search by card_name, then it will be same as before.
  So the objective of these 5 patches is to let lenovo machines with
  dual codecs find the conf file by card_long_name, let other machines
  fail to search by card_long_name, then fallback to original searching
  method - search by card_name.

  [Other Info]

  Since I could not find the alsa-lib repository in canonical, I just
  generated the debdiff with "apt-get source ...".

To manage notifications about this bug go to:

[Touch-packages] [Bug 1768830] Proposed package upload rejected

[Łukasz Zemczak]

An upload of tomcat8 to bionic-proposed has been rejected from the
upload queue for the following reason: "Invalid bug in the .changes file
- changelog mentions #1765616 but Launchpad-Bugs-Fixed: 1768830
(different).".

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Committed

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  SRU Document:

  [Impact]

  We have several Lenovo machines like Lenovo P520 which have 2 analogue
  audio codecs on them, the internal speaker and front headset are
  connected to the 1st codec, the Rear mic, Line in and Line out are
  connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
  lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
  front headset) on the 1st codec can work. To make all audio devices
  work on this machine, upstream provided 3 patches for kernel audio
  driver and 5 patches for alsa-lib. The kernel patches are already in
  the linux-4.12, so this is not a problem anymore under 18.04 since we
  use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to
  backport them to v1.1.3-5, the 5 patches are list as below:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
  4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
  181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
  81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)

  Some explanation for these 5 patches, to make the audio work, the
  alsa-lib needs to add an audio configuration file and verb conf file
  for lenovo machines with dual codecs, these two files are put in a
  folder named by card_long_name, and the name of configuration file
  itself is also named by card_long_name, this is implemented by the
  patches of NO. 3rd and 5th.

  But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
   
  [Test Case]

  On the Lenovo machines with dual codecs (p520), I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can find the conf file and can parse the conf file
  successfully, and I tested the internal speaker, front headset, rear
  mic, line out and line in, all audio devices work well.

  On a HP and Dell machines without dual codecs, I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can't find conf file by card_long_name and card_name, the
  pulseaudio will drive the sound card as before, so all audio functions
  worked well as before.

  [Regression Potential]

  After adding these 5 patches, there 2 two changes introduced into the
  alsa-lib v1.1.3-5ubuntu1:

  1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
  2) before: the ucm parser will search the conf file/folder by card_name only; 
 after: the ucm parser will search the conf file/foler by card_long_name first, 
if it fails, it will fallback to use card_name to search again. So this change 
is compatible with old version.

  There is no regression since there is only one folder named by
  card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with
  dual codecs, it will find the conf file by card_long_name, if it runs
  on other machines, the search by card_long_name will definitely fail
  and fall back to search by card_name, then it will be same as before.
  So the objective of these 5 patches is to let lenovo machines with
  dual codecs find the conf file by card_long_name, let other machines
  fail to search by card_long_name, then fallback to original searching
  method - search by card_name.

  [Other Info]

  Since I could not find the alsa-lib repository in canonical, I just
  generated the debdiff with "apt-get source ...".

To manage 

[Touch-packages] [Bug 1771173] [NEW] HUD not working for Firefox, LibreOffice & others in 18.04

[TenLeftFingers]

Public bug reported:

In 16.04, invoking the HUD allowed commands to be typed which would
produce a list to choose from. In 18.04, pressing ALT does show the
empty HUD - but typing commands doesn't populate a list for some
applications. I upgraded from 16.04 to 18.04.

Not working:
Firefox, LibreOffice, Audacity (even with pasuspender)

Working:
Gedit

Other apps work, but don't display comprehensive menus like in 16.04.
Eg, gnome-terminal only shows a Terminal menu in the menu bar rather
than File, Edit, View etc that was present on 16.04. Other examples of
these are Baobab, Nautilus.

It didn't affect upgraders until recently according to two commenters
here: https://askubuntu.com/questions/1035794/hud-doesnt-show-menu-
entries-on-18-04-unity

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: hud 14.10+17.10.20170619-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Mon May 14 18:47:52 2018
InstallationDate: Installed on 2016-02-11 (823 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 LANGUAGE=en_IE:en
 TERM=screen-256color
 PATH=(custom, no user)
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
SourcePackage: hud
UpgradeStatus: Upgraded to artful on 2018-05-13 (1 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  HUD not working for Firefox, LibreOffice & others in 18.04

Status in hud package in Ubuntu:
  New

Bug description:
  In 16.04, invoking the HUD allowed commands to be typed which would
  produce a list to choose from. In 18.04, pressing ALT does show the
  empty HUD - but typing commands doesn't populate a list for some
  applications. I upgraded from 16.04 to 18.04.

  Not working:
  Firefox, LibreOffice, Audacity (even with pasuspender)

  Working:
  Gedit

  Other apps work, but don't display comprehensive menus like in 16.04.
  Eg, gnome-terminal only shows a Terminal menu in the menu bar rather
  than File, Edit, View etc that was present on 16.04. Other examples of
  these are Baobab, Nautilus.

  It didn't affect upgraders until recently according to two commenters
  here: https://askubuntu.com/questions/1035794/hud-doesnt-show-menu-
  entries-on-18-04-unity

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hud 14.10+17.10.20170619-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon May 14 18:47:52 2018
  InstallationDate: Installed on 2016-02-11 (823 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_IE:en
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  SourcePackage: hud
  UpgradeStatus: Upgraded to artful on 2018-05-13 (1 days ago)

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

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

[Touch-packages] [Bug 1771062] Re: LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

[Lonnie Lee Best]

** Description changed:

- After Ubuntu 16.04.4 turns off my monitor (due to inactivity time out),
- I cannot get it to come back on without rebooting.
+ After Ubuntu 16.04.4 turns off my monitor (due to inactivity timeout), I
+ cannot get it to come back on without rebooting.
  
  Monitor: LG 27UK650
  Specs:   
http://www.lg.com/us/support/products/documents/27UK650-W%20Spec%20Sheet.pdf
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
-  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
+  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog:
-  
+ 
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May 14 01:15:22 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.8, 4.13.0-41-generic, x86_64: installed
-  nvidia-384, 384.111, 4.13.0-41-generic, x86_64: installed
-  virtualbox, 5.1.34, 4.13.0-41-generic, x86_64: installed
-  virtualbox, 5.1.34, 4.4.0-124-generic, x86_64: installed
+  bbswitch, 0.8, 4.13.0-41-generic, x86_64: installed
+  nvidia-384, 384.111, 4.13.0-41-generic, x86_64: installed
+  virtualbox, 5.1.34, 4.13.0-41-generic, x86_64: installed
+  virtualbox, 5.1.34, 4.4.0-124-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller])
-Subsystem: CLEVO/KAPOK Computer Device [1558:087a]
+  NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller])
+    Subsystem: CLEVO/KAPOK Computer Device [1558:087a]
  InstallationDate: Installed on 2018-05-12 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: System76 Bonobo WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=905343e7-683c-43f3-9ee8-b5e8909f865b ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.version: bonw13
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon May 14 01:02:31 2018
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  
+ 
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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

Title:
  LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

Status in xorg package in Ubuntu:
  New

Bug description:
  After Ubuntu 16.04.4 turns off my monitor (due to inactivity timeout),
  I cannot get it to come back on without rebooting.

  Monitor: LG 27UK650
  Specs:   
http://www.lg.com/us/support/products/documents/27UK650-W%20Spec%20Sheet.pdf

  

[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Olivier Tilloy]

A fix was merged to the upstream master branch:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=d9782589248e61c0cb5aec90e3eb62612891116b

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: Triaged => Incomplete

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

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

Status in The Ubuntu-power-systems project:
  Incomplete
Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

  root@guest:/tmp# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.2 (pvr 004e 1202)
  Model name:POWER8 (architected), altivec supported
  >> Hypervisor vendor: horizontal
  >> Virtualization type:   full
  L1d cache: 32K
  L1i cache: 32K
  NUMA node0 CPU(s): 0,1


   
  Stack trace output:
   no
   
  Oops output:
   no
   

  
  We test what is coming along with distro. If you are not able to see issue 
with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can 
we get this included in 16.04.x train ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions

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

[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Andreas Hasenack]

I believe so, thanks

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap:
  Fix Released
Status in openldap package in Ubuntu:
  Fix Released

Bug description:
  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not 
occuring. 

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $

buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2

  
  (gdb) thr apply all bt

  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 5 (Thread 0x7f2e95378700 (LWP 42142)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)):
  #0  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #1  0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #2  0x7f2ea5303d69 in sasl_client_init () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #3  0x7f2ea594da6c in ldap_int_sasl_init () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #4  0x7f2ea594db2c in ldap_int_sasl_open () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #5  0x7f2ea594e2d4 in ldap_int_sasl_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #6  0x7f2ea5951828 in ldap_sasl_interactive_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #7  0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #8  0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, 
sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063
  #9  0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) 
at ../../../../servers/slapd/syncrepl.c:618
  #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at 
../../../../servers/slapd/syncrepl.c:1548
  #11 0x7f2ea59463a2 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at 
pthread_create.c:333
  #13 0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)):
  ---Type  to continue, or q  to quit---
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e9637a700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 

[Touch-packages] [Bug 1771157] [NEW] /lib/systemd/systemd-journald:6:__read_nocancel:read:server_read_dev_kmsg:source_dispatch:sd_event_dispatch

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
233-6ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f2bd479932870e9b343375a20bc831a89fa43bdd 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful wily xenial yakkety zesty

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

Title:
  /lib/systemd/systemd-
  
journald:6:__read_nocancel:read:server_read_dev_kmsg:source_dispatch:sd_event_dispatch

Status in systemd package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
233-6ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f2bd479932870e9b343375a20bc831a89fa43bdd 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest

[Steve Langasek]

it is not at all clear, based on the source changes included, why
https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 would
fix this issue.

2.27.1-6ubuntu3.5 is also currently blocked from being released to
xenial-updates because the update failed verification.
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1732865

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

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

  root@guest:/tmp# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.2 (pvr 004e 1202)
  Model name:POWER8 (architected), altivec supported
  >> Hypervisor vendor: horizontal
  >> Virtualization type:   full
  L1d cache: 32K
  L1i cache: 32K
  NUMA node0 CPU(s): 0,1


   
  Stack trace output:
   no
   
  Oops output:
   no
   

  
  We test what is coming along with distro. If you are not able to see issue 
with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can 
we get this included in 16.04.x train ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions

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

[Touch-packages] [Bug 1771149] [NEW] Mouse cursor size changes based on what's under it

[cdawg]

Public bug reported:

I have a Lenovo P51 with Nvidia card. 4k display in the laptop and 2
2560x1440 external monitors. The mouse cursor changes between a normal
size and a much much larger size when it is over the background and over
some application's title bars. Other times it is normal size.

I have wiped my gnome 3 settings and re-set all the cursor size settings
to default but nothing helps. I assume it's HiDPI related.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-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  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon May 14 09:08:47 2018
DistUpgraded: 2018-05-13 09:36:57,549 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 18.03.00, 4.13.0-41-generic, x86_64: installed
 fwts-efi-runtime-dkms, 18.03.00, 4.15.0-20-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:224d]
   Subsystem: Lenovo GM107GLM [Quadro M1200 Mobile] [17aa:224d]
InstallationDate: Installed on 2017-12-29 (135 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 20HHCTO1WW
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro acpi_osi=
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-05-13 (0 days ago)
dmi.bios.date: 02/26/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1UET46W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P51
dmi.product.name: 20HHCTO1WW
dmi.product.version: ThinkPad P51
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon May 14 08:17:52 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nouveau" (module does not exist, 0)
 Failed to load module "nouveau" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic ubuntu

** Attachment added: "cursor"
   https://bugs.launchpad.net/bugs/1771149/+attachment/5139301/+files/cursor.png

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

Title:
   Mouse cursor size changes based on what's under it

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Lenovo P51 with Nvidia card. 4k display in the laptop and 2
  2560x1440 external monitors. The mouse cursor changes between a normal
  size and a much much larger size when it is over the background and
  over some application's title bars. Other times it is normal size.

  I have wiped my gnome 3 settings and re-set all the cursor size
  settings to default but nothing helps. I assume it's HiDPI related.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset 

[Touch-packages] [Bug 1771135] Re: unattended upgrades always fail b/c dpkg status database is always locked

[Felix C. Stegerman]

Thanks for the info.  I seem to have missed that.

Any idea what else might be running?  Or a workaround/fix?

These are pretty standard Ubuntu Desktop machines.  And everything
worked fine when I installed them last year.  I doubt it's a strange
configuration on my part.

- Felix

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

Title:
  unattended upgrades always fail b/c dpkg status database is always
  locked

Status in apt package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Hi,

  (Filing this bug against apt since that contains the systemd timers
  and cron job to start unattended-upgrades).

  I'm using unattended-upgrades on several computers.  On the one that
  is on most of the time, updates work as expected.  On the ones that
  are off most of the time, updates are never installed because there is
  always a "dpkg: error: dpkg status database is locked by another
  process".  Running `unattended-upgrade -d` by hand or using aptitude
  works fine.

  I suspect that because these computers are off most of the time, the
  systemd timers for both apt-daily and apt-daily-upgrade are always run
  at the same time during boot and resulting in the dpkg database being
  locked for apt-daily-upgrade.

  I will try disabling the systemd timers and using the cron job instead
  to see if that fixes the problem.

  FYI I also noticed that the cron job will only run when the system is
  on A/C power, whereas the systemd timers do not seem to have any such
  check.

  Thanks.

  - Felix

  ubuntu version: 16.04.4 LTS
  apt version: 1.2.26
  unattended-upgrades version: 0.90ubuntu0.9

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

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

[Touch-packages] [Bug 1771141] Re: package apport 2.20.1-0ubuntu2.16 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

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

** Tags added: hardware-error

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

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

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

Title:
  package apport 2.20.1-0ubuntu2.16 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  Invalid

Bug description:
  apport

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.16
  ProcVersionSignature: hostname 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CrashReports:
   640:1000:116:80200:2018-05-14 20:58:20.141736781 +0530:2018-05-14 
20:58:20.569741249 +0530:/var/crash/_usr_bin_update-manager.1000.crash
   600:0:116:85860:2018-05-14 20:56:07.323184728 +0530:2018-05-14 
20:56:08.323184728 +0530:/var/crash/apport.0.crash
   640:1000:116:55465:2018-05-14 20:58:18.657721137 +0530:2018-05-14 
21:02:14.798003000 +0530:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:0:116:450219:2018-05-14 20:35:03.479148150 +0530:2018-05-14 
20:35:03.555148146 +0530:/var/crash/_lib_systemd_systemd.0.crash
  Date: Mon May 14 20:56:08 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-03-30 (409 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.16 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1726068] Re: debconf socket closes if aptdaemon/PK client exists

[Julian Andres Klode]

** Summary changed:

- software-properties closed, closing debconf socket, while aptdaemon is 
running (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1)
+ debconf socket closes if aptdaemon/PK client exists

** Summary changed:

- debconf socket closes if aptdaemon/PK client exists
+ debconf socket closes if aptdaemon/PK client exits

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

** No longer affects: plasma-discover (Ubuntu)

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

Title:
  debconf socket closes if aptdaemon/PK client exits

Status in apper package in Ubuntu:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in packagekit package in Ubuntu:
  Triaged
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  error message on start up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: 0
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Oct 22 12:33:48 2017
  DpkgHistoryLog:
   Start-Date: 2017-10-22  12:31:01
   Commandline: aptdaemon role='role-commit-packages' sender=':1.94'
   Install: linux-image-generic:amd64 (4.4.0.97.102, automatic), 
libcuda1-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), 
linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
linux-image-extra-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
nvidia-prime:amd64 (0.8.2, automatic), libxnvctrl0:amd64 
(384.90-0ubuntu0~gpu16.04.1, automatic), lib32gcc1:amd64 (1:6.0.1-0ubuntu1, 
automatic), libc6-i386:amd64 (2.23-0ubuntu9, automatic), 
screen-resolution-extra:amd64 (0.17.1, automatic), ocl-icd-libopencl1:amd64 
(2.2.8-1, automatic), libjansson4:amd64 (2.7-3, automatic), bbswitch-dkms:amd64 
(0.8-3ubuntu1, automatic), linux-generic:amd64 (4.4.0.97.102), 
nvidia-opencl-icd-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), 
nvidia-387:amd64 (387.12-0ubuntu0~gpu16.04.1), nvidia-settings:amd64 
(384.90-0ubuntu0~gpu16.04.1, automatic)
  EFITables:
   Oct 22 12:34:32 crs-Ubuntu kernel: efi: EFI v2.40 by American Megatrends
   Oct 22 12:34:32 crs-Ubuntu kernel: efi:  ESRT=0x77e72f98  ACPI=0x77591000  
ACPI 2.0=0x77591000  SMBIOS=0x77e71000  SMBIOS 3.0=0x77e7 
   Oct 22 12:34:32 crs-Ubuntu kernel: esrt: Reserving ESRT space from 
0x77e72f98 to 0x77e72fd0.
   Oct 22 12:34:32 crs-Ubuntu kernel: Secure boot enabled
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-16 (159 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SecureBoot: 6   0   0   0   1
  SourcePackage: shim-signed
  Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted

[Alberto Milone]

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

** Also affects: nvidia-graphics-drivers-340 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** No longer affects: software-properties (Ubuntu Bionic)

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  Uninstall left nouveau blacklisted

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Bionic:
  New
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Triaged

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+subscriptions

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

[Touch-packages] [Bug 1726068] Re: software-properties closed, closing debconf socket, while aptdaemon is running (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/up

[Julian Andres Klode]

** Also affects: plasma-discover (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  software-properties closed, closing debconf socket, while aptdaemon is
  running (package shim-signed
  1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1)

Status in aptdaemon package in Ubuntu:
  Triaged
Status in packagekit package in Ubuntu:
  Triaged
Status in plasma-discover package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  error message on start up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: 0
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Oct 22 12:33:48 2017
  DpkgHistoryLog:
   Start-Date: 2017-10-22  12:31:01
   Commandline: aptdaemon role='role-commit-packages' sender=':1.94'
   Install: linux-image-generic:amd64 (4.4.0.97.102, automatic), 
libcuda1-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), 
linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
linux-image-extra-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
nvidia-prime:amd64 (0.8.2, automatic), libxnvctrl0:amd64 
(384.90-0ubuntu0~gpu16.04.1, automatic), lib32gcc1:amd64 (1:6.0.1-0ubuntu1, 
automatic), libc6-i386:amd64 (2.23-0ubuntu9, automatic), 
screen-resolution-extra:amd64 (0.17.1, automatic), ocl-icd-libopencl1:amd64 
(2.2.8-1, automatic), libjansson4:amd64 (2.7-3, automatic), bbswitch-dkms:amd64 
(0.8-3ubuntu1, automatic), linux-generic:amd64 (4.4.0.97.102), 
nvidia-opencl-icd-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), 
nvidia-387:amd64 (387.12-0ubuntu0~gpu16.04.1), nvidia-settings:amd64 
(384.90-0ubuntu0~gpu16.04.1, automatic)
  EFITables:
   Oct 22 12:34:32 crs-Ubuntu kernel: efi: EFI v2.40 by American Megatrends
   Oct 22 12:34:32 crs-Ubuntu kernel: efi:  ESRT=0x77e72f98  ACPI=0x77591000  
ACPI 2.0=0x77591000  SMBIOS=0x77e71000  SMBIOS 3.0=0x77e7 
   Oct 22 12:34:32 crs-Ubuntu kernel: esrt: Reserving ESRT space from 
0x77e72f98 to 0x77e72fd0.
   Oct 22 12:34:32 crs-Ubuntu kernel: Secure boot enabled
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-16 (159 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SecureBoot: 6   0   0   0   1
  SourcePackage: shim-signed
  Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1757138] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken third party init script installed named "notes-enable-
ptrace" that you will need to remove.


** Changed in: util-linux (Ubuntu)
   Status: New => Invalid

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  got it from automatic failure report

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb 22 14:47:35 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-19 (670 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[QuentinHartman]

I noticed this problem because my wireles KB/Mouse combo became nearly
unusable after upgrading from 17.10 to 18.04. I'm seeing the high CPU
consumption as reported above and the dell HID messages as reported
above. Also, if I unplug the transceiver for my KB/Mouse it stops
working until I reboot.

My machine is a Dell XPS 15 9560. So, also a Dell, but a very new one.

Downgrading to kernel 4.13 has alleviated the symptoms.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in bluez package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1771141] Re: package apport 2.20.1-0ubuntu2.16 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package apport 2.20.1-0ubuntu2.16 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  apport

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.16
  ProcVersionSignature: hostname 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CrashReports:
   640:1000:116:80200:2018-05-14 20:58:20.141736781 +0530:2018-05-14 
20:58:20.569741249 +0530:/var/crash/_usr_bin_update-manager.1000.crash
   600:0:116:85860:2018-05-14 20:56:07.323184728 +0530:2018-05-14 
20:56:08.323184728 +0530:/var/crash/apport.0.crash
   640:1000:116:55465:2018-05-14 20:58:18.657721137 +0530:2018-05-14 
21:02:14.798003000 +0530:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:0:116:450219:2018-05-14 20:35:03.479148150 +0530:2018-05-14 
20:35:03.555148146 +0530:/var/crash/_lib_systemd_systemd.0.crash
  Date: Mon May 14 20:56:08 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-03-30 (409 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.16 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771135] Re: unattended upgrades always fail b/c dpkg status database is always locked

[Julian Andres Klode]

apt-daily and apt-daily-upgrade cannot run at the same time, there's a
lock file in place to prevent that. maybe something else is running.

the timers only run on battery:

$ grep ACPower /lib/systemd/system/apt-daily*
/lib/systemd/system/apt-daily.service:ConditionACPower=true
/lib/systemd/system/apt-daily-upgrade.service:ConditionACPower=true

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

Title:
  unattended upgrades always fail b/c dpkg status database is always
  locked

Status in apt package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Hi,

  (Filing this bug against apt since that contains the systemd timers
  and cron job to start unattended-upgrades).

  I'm using unattended-upgrades on several computers.  On the one that
  is on most of the time, updates work as expected.  On the ones that
  are off most of the time, updates are never installed because there is
  always a "dpkg: error: dpkg status database is locked by another
  process".  Running `unattended-upgrade -d` by hand or using aptitude
  works fine.

  I suspect that because these computers are off most of the time, the
  systemd timers for both apt-daily and apt-daily-upgrade are always run
  at the same time during boot and resulting in the dpkg database being
  locked for apt-daily-upgrade.

  I will try disabling the systemd timers and using the cron job instead
  to see if that fixes the problem.

  FYI I also noticed that the cron job will only run when the system is
  on A/C power, whereas the systemd timers do not seem to have any such
  check.

  Thanks.

  - Felix

  ubuntu version: 16.04.4 LTS
  apt version: 1.2.26
  unattended-upgrades version: 0.90ubuntu0.9

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

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

[Touch-packages] [Bug 1771141] [NEW] package apport 2.20.1-0ubuntu2.16 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Naveen]

Public bug reported:

apport

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.16
ProcVersionSignature: hostname 4.4.0-122.146-generic 4.4.117
Uname: Linux 4.4.0-122-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CrashReports:
 640:1000:116:80200:2018-05-14 20:58:20.141736781 +0530:2018-05-14 
20:58:20.569741249 +0530:/var/crash/_usr_bin_update-manager.1000.crash
 600:0:116:85860:2018-05-14 20:56:07.323184728 +0530:2018-05-14 
20:56:08.323184728 +0530:/var/crash/apport.0.crash
 640:1000:116:55465:2018-05-14 20:58:18.657721137 +0530:2018-05-14 
21:02:14.798003000 +0530:/var/crash/_usr_share_apport_apport-gtk.1000.crash
 640:0:116:450219:2018-05-14 20:35:03.479148150 +0530:2018-05-14 
20:35:03.555148146 +0530:/var/crash/_lib_systemd_systemd.0.crash
Date: Mon May 14 20:56:08 2018
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2017-03-30 (409 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.16 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package apport 2.20.1-0ubuntu2.16 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  apport

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.16
  ProcVersionSignature: hostname 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CrashReports:
   640:1000:116:80200:2018-05-14 20:58:20.141736781 +0530:2018-05-14 
20:58:20.569741249 +0530:/var/crash/_usr_bin_update-manager.1000.crash
   600:0:116:85860:2018-05-14 20:56:07.323184728 +0530:2018-05-14 
20:56:08.323184728 +0530:/var/crash/apport.0.crash
   640:1000:116:55465:2018-05-14 20:58:18.657721137 +0530:2018-05-14 
21:02:14.798003000 +0530:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:0:116:450219:2018-05-14 20:35:03.479148150 +0530:2018-05-14 
20:35:03.555148146 +0530:/var/crash/_lib_systemd_systemd.0.crash
  Date: Mon May 14 20:56:08 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-03-30 (409 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.16 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Ryan Tandy]

On Mon, May 14, 2018 at 02:34:13PM -, Andreas Hasenack wrote:
>Last I tried, I couldn't reproduce it. Can we make the case for an SRU
>without a clear test case?

I'll try and find time this week to work up instructions.

Would a program that demonstrates the issue (test instructions: compile 
and run) be satisfactory for SRU purposes?

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap:
  Fix Released
Status in openldap package in Ubuntu:
  Fix Released

Bug description:
  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not 
occuring. 

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $

buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2

  
  (gdb) thr apply all bt

  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 5 (Thread 0x7f2e95378700 (LWP 42142)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)):
  #0  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #1  0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #2  0x7f2ea5303d69 in sasl_client_init () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #3  0x7f2ea594da6c in ldap_int_sasl_init () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #4  0x7f2ea594db2c in ldap_int_sasl_open () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #5  0x7f2ea594e2d4 in ldap_int_sasl_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #6  0x7f2ea5951828 in ldap_sasl_interactive_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #7  0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #8  0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, 
sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063
  #9  0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) 
at ../../../../servers/slapd/syncrepl.c:618
  #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at 
../../../../servers/slapd/syncrepl.c:1548
  #11 0x7f2ea59463a2 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at 
pthread_create.c:333
  #13 0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)):
  ---Type  to continue, or q  to quit---
  #0  

[Touch-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted

[Alberto Milone]

@Doug: I'm working on the meta-package part for LP: #175 , this is a
separate bug report, only about the blacklist file.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Uninstall left nouveau blacklisted

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+subscriptions

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

[Touch-packages] [Bug 1771135] [NEW] unattended upgrades always fail b/c dpkg status database is always locked

[Felix C. Stegerman]

Public bug reported:

Hi,

(Filing this bug against apt since that contains the systemd timers and
cron job to start unattended-upgrades).

I'm using unattended-upgrades on several computers.  On the one that is
on most of the time, updates work as expected.  On the ones that are off
most of the time, updates are never installed because there is always a
"dpkg: error: dpkg status database is locked by another process".
Running `unattended-upgrade -d` by hand or using aptitude works fine.

I suspect that because these computers are off most of the time, the
systemd timers for both apt-daily and apt-daily-upgrade are always run
at the same time during boot and resulting in the dpkg database being
locked for apt-daily-upgrade.

I will try disabling the systemd timers and using the cron job instead
to see if that fixes the problem.

FYI I also noticed that the cron job will only run when the system is on
A/C power, whereas the systemd timers do not seem to have any such
check.

Thanks.

- Felix

ubuntu version: 16.04.4 LTS
apt version: 1.2.26
unattended-upgrades version: 0.90ubuntu0.9

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

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

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

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

Title:
  unattended upgrades always fail b/c dpkg status database is always
  locked

Status in apt package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Hi,

  (Filing this bug against apt since that contains the systemd timers
  and cron job to start unattended-upgrades).

  I'm using unattended-upgrades on several computers.  On the one that
  is on most of the time, updates work as expected.  On the ones that
  are off most of the time, updates are never installed because there is
  always a "dpkg: error: dpkg status database is locked by another
  process".  Running `unattended-upgrade -d` by hand or using aptitude
  works fine.

  I suspect that because these computers are off most of the time, the
  systemd timers for both apt-daily and apt-daily-upgrade are always run
  at the same time during boot and resulting in the dpkg database being
  locked for apt-daily-upgrade.

  I will try disabling the systemd timers and using the cron job instead
  to see if that fixes the problem.

  FYI I also noticed that the cron job will only run when the system is
  on A/C power, whereas the systemd timers do not seem to have any such
  check.

  Thanks.

  - Felix

  ubuntu version: 16.04.4 LTS
  apt version: 1.2.26
  unattended-upgrades version: 0.90ubuntu0.9

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

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

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

[Joshua Powers]

Hi, thanks for taking the time to file a bug. Based on that last message
from SSH it makes me wonder if the syntax you have is correct.

1) Can you confirm PermitUserEnvironment is set to yes in your
sshd_config?

2) Can you provide more details of the line in question in your
authorized keys file? For example, if I add:

environment="FOO_BAR=1" ssh-rsa B

then connect:

root@x:~# env | grep -i foo
FOO_BAR=1

This question may also be better suited for the community forums as it
is more of a support issue.

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

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

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

Title:
  Doesn't accept environment variable with underscore in its name in
  AuthorizedKeysFile

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  If environment variable name defined in AuthorizedKeysFile contains 
underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and 
throws following error:
  authorized_keys:1: bad key options: invalid environment string

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

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

[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Andreas Hasenack]

Last I tried, I couldn't reproduce it. Can we make the case for an SRU
without a clear test case?

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap:
  Fix Released
Status in openldap package in Ubuntu:
  Fix Released

Bug description:
  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not 
occuring. 

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $

buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2

  
  (gdb) thr apply all bt

  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 5 (Thread 0x7f2e95378700 (LWP 42142)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)):
  #0  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #1  0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #2  0x7f2ea5303d69 in sasl_client_init () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #3  0x7f2ea594da6c in ldap_int_sasl_init () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #4  0x7f2ea594db2c in ldap_int_sasl_open () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #5  0x7f2ea594e2d4 in ldap_int_sasl_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #6  0x7f2ea5951828 in ldap_sasl_interactive_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #7  0x7f2ea5951a4e in ldap_sasl_interactive_bind_s () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #8  0x561fbc556db4 in slap_client_connect (ldp=0x561fbe1e9f68, 
sb=0x561fbe1e9d40) at ../../../../servers/slapd/config.c:2063
  #9  0x561fbc5c699d in do_syncrep1 (si=0x561fbe1e9d10, op=0x7f2e95b787b0) 
at ../../../../servers/slapd/syncrepl.c:618
  #10 do_syncrepl (ctx=, arg=0x561fbe1e5620) at 
../../../../servers/slapd/syncrepl.c:1548
  #11 0x7f2ea59463a2 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #12 0x7f2ea487c6ba in start_thread (arg=0x7f2e95b79700) at 
pthread_create.c:333
  #13 0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 3 (Thread 0x7f2e9637a700 (LWP 42140)):
  ---Type  to continue, or q  to quit---
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e9637a700) at 

[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest

[Frank Heimes]

** Tags added: triage-a

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

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

  root@guest:/tmp# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.2 (pvr 004e 1202)
  Model name:POWER8 (architected), altivec supported
  >> Hypervisor vendor: horizontal
  >> Virtualization type:   full
  L1d cache: 32K
  L1i cache: 32K
  NUMA node0 CPU(s): 0,1


   
  Stack trace output:
   no
   
  Oops output:
   no
   

  
  We test what is coming along with distro. If you are not able to see issue 
with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can 
we get this included in 16.04.x train ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions

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

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

[Stian Soiland-Reyes]

Ronald's solution in #5 fixed it for me - now BTN_7 is no longer
propagated to X as a mouse click. Volume buttons keeps working. The Call
button (previously BTN_1) stops registering according to xev, but that
didn't do anything for me before anyway. (Interested readers may tweak
the button ignores to re-enable)

Would #5 be backported to 16.04.4 TLS given End-of-life is 2021?

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

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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I switch the primary sound device to a USB headset connected to
  my laptop, mouse click events no longer work except in the Sound
  Settings window.  This does not seem to occur when the device is
  connected, only when it is made the default audio device.

  Once this occurs, the mouse events do not work until the device is
  disconnected.  Clicks inside the Sound Settings window are registered
  (including buttons and other tabs inside the System Settings window,
  but not the titlebar or close/minimize/maximize buttons.)  Focus can
  be given to other windows via alt-tab and keyboard input continues to
  function, but mouse events do not register on windows focused in this
  way.

  This is *deeply* weird, BTW.

  Hardware:
  Jabra EVOLVE 80 headset
  lsusb reports: Bus 002 Device 022: ID 0b0e:0305 GN Netcom 

  Steps to reproduce:
  1. Connect the device to a USB port.
  2. Open Sound Settings window.
  3. Select the Jabra USB device as the primary sound device.
  4. Observe that mouse clicks no longer register outside of the System 
Settings window.

  dmesg shows the following during this process:

  [130169.130542] usb 2-2.1.1: new full-speed USB device number 22 using 
xhci_hcd
  [130169.223026] usb 2-2.1.1: New USB device found, idVendor=0b0e, 
idProduct=0305
  [130169.223031] usb 2-2.1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [130169.223034] usb 2-2.1.1: Product: Jabra EVOLVE LINK MS
  [130169.223036] usb 2-2.1.1: Manufacturer: GN Netcom A/S
  [130169.223038] usb 2-2.1.1: SerialNumber: 51E7669007
  [130169.225586] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.227472] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.248162] input: GN Netcom A/S Jabra EVOLVE LINK MS as 
/devices/pci:00/:00:14.0/usb2/2-2/2-2.1/2-2.1.1/2-2.1.1:1.3/0003:0B0E:0305.0013/input/input34
  [130169.302858] hid-generic 0003:0B0E:0305.0013: input,hiddev0,hidraw5: USB 
HID v1.00 Device [GN Netcom A/S Jabra EVOLVE LINK MS] on 
usb-:00:14.0-2.1.1/input3
  [130169.351940] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.352187] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.358162] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.358439] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.361073] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.361323] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.373535] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.373904] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.380322] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.380645] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130177.637403] usb 2-2.1.1: USB disconnect, device number 22

  
  This appears to possibly be related to bug #1371853.

  I'm happy to provide more information, try custom kernels, etc. as
  needed.  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 13 13:00:25 2016
  DistUpgraded: 2016-04-25 16:22:59,827 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-35-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   i915-4.3.3-4.2.0, 2, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-10-03 (222 days 

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

[Stian Soiland-Reyes]

I have the same device (Jabra Evolve 40) and can reproduce in Ubuntu
Gnome 16.04.

The bug seems to be that the mouse button 12 (aka BTN_7) remains pressed
whenever the headset jack is connected to the hub with the volume
buttons. If you disconnect the headset then a ButtonRelease appears and
regular mouse click behaviour is restored.


xev, connecting jack:

ButtonPress event, serial 36, synthetic NO, window 0x41,
root 0x2e4, subw 0x0, time 186231, (162,86), root:(3309,349),
state 0x0, button 12, same_screen YES

Disconnecting jack from hub:

ButtonRelease event, serial 36, synthetic NO, window 0x41,
root 0x2e4, subw 0x0, time 190327, (162,86), root:(3309,349),
state 0x0, button 12, same_screen YES

evtest reports plugging in event as:

Event: time 1526305450.981481, type 4 (EV_MSC), code 4 (MSC_SCAN), value 
ff62
Event: time 1526305450.981481, type 1 (EV_KEY), code 263 (BTN_7), value 1
Event: time 1526305450.981481, -- SYN_REPORT 

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

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

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I switch the primary sound device to a USB headset connected to
  my laptop, mouse click events no longer work except in the Sound
  Settings window.  This does not seem to occur when the device is
  connected, only when it is made the default audio device.

  Once this occurs, the mouse events do not work until the device is
  disconnected.  Clicks inside the Sound Settings window are registered
  (including buttons and other tabs inside the System Settings window,
  but not the titlebar or close/minimize/maximize buttons.)  Focus can
  be given to other windows via alt-tab and keyboard input continues to
  function, but mouse events do not register on windows focused in this
  way.

  This is *deeply* weird, BTW.

  Hardware:
  Jabra EVOLVE 80 headset
  lsusb reports: Bus 002 Device 022: ID 0b0e:0305 GN Netcom 

  Steps to reproduce:
  1. Connect the device to a USB port.
  2. Open Sound Settings window.
  3. Select the Jabra USB device as the primary sound device.
  4. Observe that mouse clicks no longer register outside of the System 
Settings window.

  dmesg shows the following during this process:

  [130169.130542] usb 2-2.1.1: new full-speed USB device number 22 using 
xhci_hcd
  [130169.223026] usb 2-2.1.1: New USB device found, idVendor=0b0e, 
idProduct=0305
  [130169.223031] usb 2-2.1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [130169.223034] usb 2-2.1.1: Product: Jabra EVOLVE LINK MS
  [130169.223036] usb 2-2.1.1: Manufacturer: GN Netcom A/S
  [130169.223038] usb 2-2.1.1: SerialNumber: 51E7669007
  [130169.225586] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.227472] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.248162] input: GN Netcom A/S Jabra EVOLVE LINK MS as 
/devices/pci:00/:00:14.0/usb2/2-2/2-2.1/2-2.1.1/2-2.1.1:1.3/0003:0B0E:0305.0013/input/input34
  [130169.302858] hid-generic 0003:0B0E:0305.0013: input,hiddev0,hidraw5: USB 
HID v1.00 Device [GN Netcom A/S Jabra EVOLVE LINK MS] on 
usb-:00:14.0-2.1.1/input3
  [130169.351940] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.352187] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.358162] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.358439] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.361073] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.361323] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.373535] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.373904] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.380322] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.380645] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130177.637403] usb 2-2.1.1: USB disconnect, device number 22

  
  This appears to possibly be related to bug #1371853.

  I'm happy to provide more information, try custom kernels, etc. as
  needed.  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 13 13:00:25 2016
  DistUpgraded: 2016-04-25 16:22:59,827 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
 

[Touch-packages] [Bug 1767096] Re: Random Xorg crashes

[spodin]

Additionally, from "gdb `cat ExecutablePath` CoreDump" execution:

Reading symbols from /usr/lib/xorg/Xorg...(no debugging symbols found)...done.
[New LWP 1087]
[New LWP 1128]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f98e38e363b in __GI__IO_default_xsputn (f=0x7ffdec2bc5d0, 
data=0x7f98e39fc410 , n=3) at genops.c:422
422 genops.c: No such file or directory.
[Current thread is 1 (Thread 0x7f98e5f3ca00 (LWP 1087))]

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

Title:
  Random Xorg crashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg crashes randomly: environment just freezes for a second and I'm
  getting login screen.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Thu Apr 26 12:57:22 2018
  InstallationDate: Installed on 2018-03-01 (55 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771123] Re: NetworkManager doesn't accept 802.1x password

[Launchpad Bug Tracker]

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

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

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

Title:
  NetworkManager doesn't accept 802.1x password

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Our wired connection needs to be authenticated with a certificate.
  Therefor we need to provide a CRT & KEY to authenticate.

  With 16.04 this worked flawlessly.

  With 18.04, when we setup a connection via the gui and enter the key it says 
the key is not passphrase protected, although it is.
  We cannot add the connection because of this.

  I can add the connection with a very long nmcli command, but this is
  not easy for the endusers.

  Is this a bug?

  Version of network-manager in 18.04 is "1.10.6-2ubuntu1", in 16.04
  this is "1.2.6-0ubuntu0.16.04.2"

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

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

[Touch-packages] [Bug 1771123] [NEW] NetworkManager doesn't accept 802.1x password

[OliWare]

Public bug reported:

Our wired connection needs to be authenticated with a certificate.
Therefor we need to provide a CRT & KEY to authenticate.

With 16.04 this worked flawlessly.

With 18.04, when we setup a connection via the gui and enter the key it says 
the key is not passphrase protected, although it is.
We cannot add the connection because of this.

I can add the connection with a very long nmcli command, but this is not
easy for the endusers.

Is this a bug?

Version of network-manager in 18.04 is "1.10.6-2ubuntu1", in 16.04 this
is "1.2.6-0ubuntu0.16.04.2"

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

** Package changed: software-center (Ubuntu) => network-manager (Ubuntu)

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

Title:
  NetworkManager doesn't accept 802.1x password

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Our wired connection needs to be authenticated with a certificate.
  Therefor we need to provide a CRT & KEY to authenticate.

  With 16.04 this worked flawlessly.

  With 18.04, when we setup a connection via the gui and enter the key it says 
the key is not passphrase protected, although it is.
  We cannot add the connection because of this.

  I can add the connection with a very long nmcli command, but this is
  not easy for the endusers.

  Is this a bug?

  Version of network-manager in 18.04 is "1.10.6-2ubuntu1", in 16.04
  this is "1.2.6-0ubuntu0.16.04.2"

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

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

[Touch-packages] [Bug 1771033] Re: python3-avahi is missing in Ubuntu/debian

[Bug Watch Updater]

** Changed in: avahi (Debian)
   Status: Unknown => New

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

Title:
  python3-avahi is missing in Ubuntu/debian

Status in avahi package in Ubuntu:
  New
Status in avahi package in Debian:
  New

Bug description:
  Under Ubuntu 18.04 if you install the package Gajim the local account
  is permanently disabled because of missing dependencies.

  https://dev.gajim.org/gajim/gajim/issues/9125

  The required package is python3-avahi

  The python3-avahi package is missing, apt-get is unable to find it.

  This is a vital feature for us, we use Gajim internally without
  internet, and this simply works, no adding accounts, no information or
  messages sent over the internet, it all works locally.

  I hope this package can be added, if this is the wrong place to file
  this bug I applologize. I don't have a lot of experience reporting
  bugs.

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

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

[Touch-packages] [Bug 1771123] [NEW] NetworkManager doesn't accept 802.1x password

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Our wired connection needs to be authenticated with a certificate.
Therefor we need to provide a CRT & KEY to authenticate.

With 16.04 this worked flawlessly.

With 18.04, when we setup a connection via the gui and enter the key it says 
the key is not passphrase protected, although it is.
We cannot add the connection because of this.

I can add the connection with a very long nmcli command, but this is not
easy for the endusers.

Is this a bug?

Version of network-manager in 18.04 is "1.10.6-2ubuntu1", in 16.04 this
is "1.2.6-0ubuntu0.16.04.2"

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

-- 
NetworkManager doesn't accept 802.1x password
https://bugs.launchpad.net/bugs/1771123
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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

[Touch-packages] [Bug 1766337] Re: uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't decode byte; invalid continuation byte

[Laurent Bonnaud]

Thank you for the fix!

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

Title:
  uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't
  decode byte; invalid continuation byte

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  New

Bug description:
  Hi,

  here is a python exception I got while reporting a bug:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
  check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in 
check_attachment_for_errors
  trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in 
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070: 
invalid continuation byte

  It can also be seen here:

https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu6
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Apr 23 20:13:24 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771033] Re: python3-avahi is missing in Ubuntu/debian

[Jeremy Bicha]

** Bug watch added: Debian Bug tracker #853239
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853239

** Also affects: avahi (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853239
   Importance: Unknown
   Status: Unknown

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

Title:
  python3-avahi is missing in Ubuntu/debian

Status in avahi package in Ubuntu:
  New
Status in avahi package in Debian:
  Unknown

Bug description:
  Under Ubuntu 18.04 if you install the package Gajim the local account
  is permanently disabled because of missing dependencies.

  https://dev.gajim.org/gajim/gajim/issues/9125

  The required package is python3-avahi

  The python3-avahi package is missing, apt-get is unable to find it.

  This is a vital feature for us, we use Gajim internally without
  internet, and this simply works, no adding accounts, no information or
  messages sent over the internet, it all works locally.

  I hope this package can be added, if this is the wrong place to file
  this bug I applologize. I don't have a lot of experience reporting
  bugs.

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

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

[Touch-packages] [Bug 1747411] Re: Change of default database file format to SQL

[ Christian Ehrhardt ]

nss and corosync being the last on this are in Cosmic now.

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

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

Title:
  Change of default database file format to SQL

Status in certmonger package in Ubuntu:
  Fix Released
Status in corosync package in Ubuntu:
  Fix Released
Status in dogtag-pki package in Ubuntu:
  Fix Released
Status in freeipa package in Ubuntu:
  Fix Released
Status in libapache2-mod-nss package in Ubuntu:
  Won't Fix
Status in nss package in Ubuntu:
  Fix Released

Bug description:
  nss in version 3.35 in upstream changed [2] the default file format [1] (if 
no explicit one is specified).
  For now we reverted that change in bug 1746947 until all packages depending 
on it are ready to work with that correctly.

  This bug here is about to track when the revert can be dropped.
  Therefore we list all known-to-be-affected packages and once all are resolved 
this can be dropped.

  [1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql
  [2]: 
https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3

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

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

[Touch-packages] [Bug 1771111] [NEW] Freezes on Thinkpad R500

[Michal]

Public bug reported:

Problem with black boxes on screen, freezing mouse, random freezes
(1-2s).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
BootLog: /dev/sda1: clean, 586416/5447680 files, 15738435/21777920 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May 14 14:36:13 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e5]
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e5]
InstallationDate: Installed on 2017-11-12 (182 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 271434G
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=0b74ca14-9767-4eca-95ac-fcbedc338d77 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7YET50WW (1.20 )
dmi.board.name: 271434G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7YET50WW(1.20):bd10/30/2008:svnLENOVO:pn271434G:pvrThinkPadR500:rvnLENOVO:rn271434G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad R500
dmi.product.name: 271434G
dmi.product.version: ThinkPad R500
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
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 artful third-party-packages ubuntu wayland-session

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

Title:
  Freezes on Thinkpad R500

Status in xorg package in Ubuntu:
  New

Bug description:
  Problem with black boxes on screen, freezing mouse, random freezes
  (1-2s).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  BootLog: /dev/sda1: clean, 586416/5447680 files, 15738435/21777920 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 14 14:36:13 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e5]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e5]
  InstallationDate: Installed on 2017-11-12 (182 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 271434G
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=0b74ca14-9767-4eca-95ac-fcbedc338d77 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7YET50WW (1.20 )
  dmi.board.name: 271434G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
 

[Touch-packages] [Bug 1770482] Re: package keyboard-configuration 1.178ubuntu2 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error ex

[Launchpad Bug Tracker]

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

** Changed in: console-setup (Ubuntu)
   Status: New => Confirmed

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

Title:
  package keyboard-configuration 1.178ubuntu2 failed to install/upgrade:
  installed keyboard-configuration package post-installation script
  subprocess returned error exit status 1

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  This was caused during an upgrade to ubuntu 18.04 from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 10 21:00:12 2018
  ErrorMessage: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2016-12-13 (513 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  Keyboard:
   XKBLAYOUT="querty"
   BACKSPACE="guess"
   XKBMODEL="pc105"
   XKBVARIANT=""
   XKBOPTIONS=""
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.178ubuntu2 failed to install/upgrade: 
installed keyboard-configuration package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (0 days ago)

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

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

[Touch-packages] [Bug 1767283] Re: nc doesn't support "-s IP" option

[ Christian Ehrhardt ]

Found a much better backport much more suited for the SRU process.
New build in ppa, if it tests fine I'll propose that instead.

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Fix Released
Status in netcat-openbsd source package in Bionic:
  Triaged
Status in netcat-openbsd package in Debian:
  Fix Released

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 388553] Re: Wi-Fi Protected Setup (WPS) not supported

[kbunty]

PS, I know that Ubuntu allows users to do sudo su , I will lets not
divert into how silly that is.

NM is commonly used on most Linux distros and needs a pushbutton
solution , not command line hacking. Let's not deviate from that basic
issue.

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

Title:
  Wi-Fi Protected Setup (WPS) not supported

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

Bug description:
  As the title the Wi-Fi Protected Setup (WPS) is not supported by
  NetworkManager (but is supported by wpa_supplicant).

  The WPS WI-Fi standard is implementated in various newer access points
  and allow user to configure the access point in just a few of steps
  and do all configuring process very simple.

  Specifications: http://www.wi-fi.org/wifi-protected-setup/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/388553/+subscriptions

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

[Touch-packages] [Bug 388553] Re: Wi-Fi Protected Setup (WPS) not supported

[kbunty]

So what is needed here?

This is a major deficiency in Linux as a viable , everyday desktop
solution. Wifi is now an essential part of any OS/software installation.
The abitility to connect to various wifi routers at other people's
houses, cafes etc, where a WPA password is required MUST be available to
the basic lambda user without the need to enter or even know the root pw
or start screwing around with obscure command line editing of config
files.  Jeez this is 2018 , not 1990.

The above link says NM 1.10.x can handle WPS but says not more. AFAICT
it is implemented in low level but there is nothing in the NM GUI
widgets to actually use it.

What is needed here, and is there anything actively in the pipeline?

thx

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

Title:
  Wi-Fi Protected Setup (WPS) not supported

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

Bug description:
  As the title the Wi-Fi Protected Setup (WPS) is not supported by
  NetworkManager (but is supported by wpa_supplicant).

  The WPS WI-Fi standard is implementated in various newer access points
  and allow user to configure the access point in just a few of steps
  and do all configuring process very simple.

  Specifications: http://www.wi-fi.org/wifi-protected-setup/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/388553/+subscriptions

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

[Touch-packages] [Bug 388553] Re: Wi-Fi Protected Setup (WPS) not supported

[kbunty]

PS, I know that Ubuntu allows users to do sudo su , I will lets not
divert into how silly that is.

NM is commonly used on most Linux distros and needs a pushbutton
solution , not command line hacking. Let's not deviate from that basic
issue.

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

Title:
  Wi-Fi Protected Setup (WPS) not supported

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

Bug description:
  As the title the Wi-Fi Protected Setup (WPS) is not supported by
  NetworkManager (but is supported by wpa_supplicant).

  The WPS WI-Fi standard is implementated in various newer access points
  and allow user to configure the access point in just a few of steps
  and do all configuring process very simple.

  Specifications: http://www.wi-fi.org/wifi-protected-setup/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/388553/+subscriptions

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

[Touch-packages] [Bug 1767283] Re: nc doesn't support "-s IP" option

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/netcat-openbsd/+git/netcat-openbsd/+merge/345518

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Fix Released
Status in netcat-openbsd source package in Bionic:
  Triaged
Status in netcat-openbsd package in Debian:
  Fix Released

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1767283] Re: nc doesn't support "-s IP" option

[ Christian Ehrhardt ]

I backported the changes which had a lot of extra noise that had to be dropped.
Now a build is ready in ppa [1]

I haven't actually read the patch too much yet but found the build to not solve 
the issues for me on the example from the man page - so I started taking a 
deeper look.
It really works with the newer upstream version, so the patch needs a backport 
plus soem adaption to work in Bionic.

I found a snippet that I missed on the backport (ugly :-/) a better
version built now and works for me. Due to the complexity thou and my
unfamiliarity with the code I'd ask for some extra testing thou.

I'm proposing an SRU-MP but really any extra check is welcome.

[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3260

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Fix Released
Status in netcat-openbsd source package in Bionic:
  Triaged
Status in netcat-openbsd package in Debian:
  Fix Released

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771102] [NEW] 17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache

[Alexander Sack]

Public bug reported:

When I do as root:

do-release-upgrade

The bionic tarball is downloaded and the python based "bionic" process
is forked. On the screen I see the first "Reading cache..." message and
then the process spikes the CPU to 100% where it stays there forever (I
waited 15-20 minutes and there was no change in CPU state).

Here is the dist-upgrade log file:
2018-05-14 07:17:19,308 INFO uname information: 'Linux kitt 4.13.0-41-generic 
#46-Ubuntu SMP Wed May 2 13:38:30 UTC 2018 x86_64'
2018-05-14 07:17:19,594 INFO apt version: '1.5.1'
2018-05-14 07:17:19,594 INFO python version: '3.6.3 (default, Oct  3 2017, 
21:45:48)
[GCC 7.2.0]'
2018-05-14 07:17:19,596 INFO release-upgrader version '18.04.17' started
2018-05-14 07:17:19,600 INFO locale: 'en_US' 'UTF-8'
2018-05-14 07:17:19,605 INFO screen could not be run
2018-05-14 07:17:19,744 DEBUG Using 'DistUpgradeViewText' view
2018-05-14 07:17:19,788 DEBUG enable dpkg --force-overwrite
2018-05-14 07:17:19,817 DEBUG creating statefile: 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'

strace output of the "bionic" process:

$ sudo strace -f -p 6469
strace: Process 6469 attached with 3 threads
[pid  6546] restart_syscall(<... resuming interrupted poll ...> 
[pid  6547] restart_syscall(<... resuming interrupted poll ...>strace: [ 
Process PID=6469 runs in x32 mode. ]

top output:
   PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  6469 root  20   0  270048  33108  15728 R  99.7  0.1   0:38.85 bionic
  6555 pisymbol  20   0   46736   4376   3344 R   0.7  0.0   0:00.04 top

Looking at this further, it seems that the installer sets the the
"rootdir=/" when it initiates the python-apt's Cache class. This hangs.
I can reproduce this by simply changing it's test code to pass
rootdir="/" and it hangs. It sorta smells like a deadlock issue though
deep in the C++ module (apt_pkg) that backs the python one (GetLock?).
But I'm not 100% sure.

This behavior is seen on my 32-core Threadripper machine (AMD64).

This is 17.10 latest with:

$ dpkg -l python-apt libapt-pkg5.0
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  
Architecture Description
+++-==---=
ii  libapt-pkg5.0:amd641.5.1
amd64package management runtime library
ii  python-apt 1.4.0~beta3build2
amd64Python interface to libapt-pkg

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

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

Title:
  17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache

Status in python-apt package in Ubuntu:
  New

Bug description:
  When I do as root:

  do-release-upgrade

  The bionic tarball is downloaded and the python based "bionic" process
  is forked. On the screen I see the first "Reading cache..." message
  and then the process spikes the CPU to 100% where it stays there
  forever (I waited 15-20 minutes and there was no change in CPU state).

  Here is the dist-upgrade log file:
  2018-05-14 07:17:19,308 INFO uname information: 'Linux kitt 4.13.0-41-generic 
#46-Ubuntu SMP Wed May 2 13:38:30 UTC 2018 x86_64'
  2018-05-14 07:17:19,594 INFO apt version: '1.5.1'
  2018-05-14 07:17:19,594 INFO python version: '3.6.3 (default, Oct  3 2017, 
21:45:48)
  [GCC 7.2.0]'
  2018-05-14 07:17:19,596 INFO release-upgrader version '18.04.17' started
  2018-05-14 07:17:19,600 INFO locale: 'en_US' 'UTF-8'
  2018-05-14 07:17:19,605 INFO screen could not be run
  2018-05-14 07:17:19,744 DEBUG Using 'DistUpgradeViewText' view
  2018-05-14 07:17:19,788 DEBUG enable dpkg --force-overwrite
  2018-05-14 07:17:19,817 DEBUG creating statefile: 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'

  strace output of the "bionic" process:

  $ sudo strace -f -p 6469
  strace: Process 6469 attached with 3 threads
  [pid  6546] restart_syscall(<... resuming interrupted poll ...> 
  [pid  6547] restart_syscall(<... resuming interrupted poll ...>strace: [ 
Process PID=6469 runs in x32 mode. ]

  top output:
 PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
6469 root  20   0  270048  33108  15728 R  99.7  0.1   0:38.85 bionic
6555 pisymbol  20   0   46736   4376   3344 R   0.7  0.0   0:00.04 top

  Looking at this further, it seems that the installer sets the the
  "rootdir=/" when it initiates the 

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

[Diep Pham]

Hello guys, is there any news on this problem? If no one has the time to

> It looks like an upstream issue that needs proper debugging/resolving

Should we just reapply the patch to make Firefox usable for now?

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

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

Status in ibus package in Ubuntu:
  Confirmed

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

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

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

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

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

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


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

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

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

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

[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

[Dimitri John Ledkov]

** Description changed:

  [Impact]
  
-  * Bogus keycode messages produced by the kernel / user annoyance
-  * rfkill keyboard shortcuts not working as intended on some Dell machines
+  * Bogus keycode messages produced by the kernel / user annoyance
+  * rfkill keyboard shortcuts not working as intended on some Dell machines
  
  [Test Case]
  
-  * check that there are no spurious kernel messages about unknown keys
+  * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses
  
-  * check that RFKill key presses work correctly and kill/restore RF
+  * check that RFKill key presses work correctly and kill/restore RF
  capabilities
  
  [Regression Potential]
  
-  * The change is scoped to particular SKUs and thus should only affect them
-  * It is related to matching gsd support, which is in-place on xenial and up
- 
+  * The change is scoped to particular SKUs and thus should only affect them
+  * It is related to matching gsd support, which is in-place on xenial and up
  
  [Solution]
- Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/fa5721cb38c77648e871646fbf38bc799ab42a52
+ Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f
  
  [Original Bug report]
  
  RFKill key produces these messages in kernel log:
  
  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed
  
  This key code is a notification and should be added as KEY_IGNORE here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-
  wmi.c#L263
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

Title:
  dell_wmi: Unknown key codes

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  

[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

[Dimitri John Ledkov]

** Description changed:

+ [Impact]
+ 
+  * Bogus keycode messages produced by the kernel / user annoyance
+  * rfkill keyboard shortcuts not working as intended on some Dell machines
+ 
+ [Test Case]
+ 
+  * check that there are no spurious kernel messages about unknown keys
+ in journalctl upon RFKill key presses
+ 
+  * check that RFKill key presses work correctly and kill/restore RF
+ capabilities
+ 
+ [Regression Potential]
+ 
+  * The change is scoped to particular SKUs and thus should only affect them
+  * It is related to matching gsd support, which is in-place on xenial and up
+ 
+ 
+ [Solution]
+ Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/fa5721cb38c77648e871646fbf38bc799ab42a52
+ 
+ [Original Bug report]
+ 
  RFKill key produces these messages in kernel log:
  
  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed
  
  This key code is a notification and should be added as KEY_IGNORE here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-
  wmi.c#L263
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  dmig   2737 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-15-generic N/A
-  linux-backports-modules-4.15.0-15-generic  N/A
-  linux-firmware 1.173
+  linux-restricted-modules-4.15.0-15-generic N/A
+  linux-backports-modules-4.15.0-15-generic  N/A
+  linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

Title:
  dell_wmi: Unknown key codes

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  
  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/fa5721cb38c77648e871646fbf38bc799ab42a52

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 

[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

[Dimitri John Ledkov]

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

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

** Also affects: linux (Ubuntu Cosmic)
   Importance: Medium
 Assignee: Kai-Heng Feng (kaihengfeng)
   Status: Confirmed

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

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

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

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: linux (Ubuntu Cosmic)

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

Title:
  dell_wmi: Unknown key codes

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  
  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/fa5721cb38c77648e871646fbf38bc799ab42a52

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1771096] [NEW] Missing error message for mount failure and suggestion for action

[Arto Jääskeläinen]

Public bug reported:

Ubuntu 16.04 (Linux Mint 18.3)
Related package: Not sure (system-d?)
Happens: During boot up

Regression:
You'll be greeted with "Welcome to emergency mode!" if something is wrong with 
an additional device connected at /etc/fstab, for example a disk for backups. 

1) That message doesn't give any idea whats's actually going wrong.  
2) There is no option to skip the error.

Earlier there was an error message about failed mount and option "S" to
skip mounting.

Suggested test case:
Insert some non existing UUID for disk into /etc/fstab and you'll see it, just 
an example:
UUID=369dd78c-afcf-4967-81c9-ae672588f158 /mnt/backup ext4 errors=remount-ro 0 
1 
In my case it was an external USB disk for backups. Leaving the cable 
disconnected was a good simple way to test missing device.

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

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

Title:
  Missing error message for mount failure and suggestion for action

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 (Linux Mint 18.3)
  Related package: Not sure (system-d?)
  Happens: During boot up

  Regression:
  You'll be greeted with "Welcome to emergency mode!" if something is wrong 
with an additional device connected at /etc/fstab, for example a disk for 
backups. 

  1) That message doesn't give any idea whats's actually going wrong.  
  2) There is no option to skip the error.

  Earlier there was an error message about failed mount and option "S"
  to skip mounting.

  Suggested test case:
  Insert some non existing UUID for disk into /etc/fstab and you'll see it, 
just an example:
  UUID=369dd78c-afcf-4967-81c9-ae672588f158 /mnt/backup ext4 errors=remount-ro 
0 1 
  In my case it was an external USB disk for backups. Leaving the cable 
disconnected was a good simple way to test missing device.

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Łukasz Zemczak]

Can anyone potentially perform verification of the artful packages? We
usually prefer releasing packages for newer series first, although it's
not really a big deal right now because xenial -> artful is not an
official upgrade path anymore.

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Hadmut Danisch]

Ooops, no, sorry, it works (/tmp/a was missing).

So the kernel is definitely able to mount the file systems, it's just
that ecryptfs-utils and their key management do not work.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

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

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

[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

[Woodrow Shen]

Attached deb patch for bionic

** Patch added: "systemd_237-3ubuntu10_237-3ubuntu11.diff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/+attachment/5139157/+files/systemd_237-3ubuntu10_237-3ubuntu11.diff

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

Title:
  dell_wmi: Unknown key codes

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Hadmut Danisch]

Even a direct


mount -t ecryptfs -o 
ecryptfs_check_dev_ruid,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs
 /tmp/work /tmp/a   

fails with 
[-2] No such file or directory

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

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

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

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/345498

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771081] [NEW] [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Pulseaudio fails to detect card

[Vincenzo]

Public bug reported:

I now have a different problem. I had sound working when i tricked the software 
by having my phone play music. now it has booted up and the sound is lost and 
there is a dummy card in the sound profile. if i add a bluetooth speaker it 
will play to it but with lots of cutting out. i know the quality is good as it 
has played on my machine and i have used the bluetooth speaker from another 
source. it seems to be this software?
regards Vinnychoff

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Mon May 14 09:26:54 2018
InstallationDate: Installed on 2018-05-02 (11 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel
Symptom_Jack: Black Line Out, Rear
Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Pulseaudio fails to 
detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/20/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.15
dmi.board.name: 0K216C
dmi.board.vendor: Dell Inc.
dmi.board.version: ���
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: OEM
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM:
dmi.product.name: Inspiron 530
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Pulseaudio fails
  to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I now have a different problem. I had sound working when i tricked the 
software by having my phone play music. now it has booted up and the sound is 
lost and there is a dummy card in the sound profile. if i add a bluetooth 
speaker it will play to it but with lots of cutting out. i know the quality is 
good as it has played on my machine and i have used the bluetooth speaker from 
another source. it seems to be this software?
  regards Vinnychoff

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 14 09:26:54 2018
  InstallationDate: Installed on 2018-05-02 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel
  Symptom_Jack: Black Line Out, Rear
  Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Pulseaudio fails 
to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.15
  dmi.board.name: 0K216C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 530
  dmi.sys.vendor: Dell Inc.

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

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