[Touch-packages] [Bug 1773157] Re: procps outdated network options, old syncookies, new ecn update please.

[Balint Reczey]

I'm dropping the redundant setting of syncookies from the delta but IMO
ECN should be enabled upstream or in Debian instead of adding a delta
for it in Ubuntu.

Please try to get ECN enabled at upstream or at Debian, we have plenty
of time before the next (LTS) release in case we have to fall back to
adding a delta if upstream and Debian don't want to enable ECN but it
would still be beneficial for Ubuntu to enable it.

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

Title:
  procps outdated network options, old syncookies, new ecn update
  please.

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu version of procps carries it's own  /etc/sysctl.d/10
  -network-security.conf  file explicitly that appears not to be part of
  debian procps version.

  
  Firstly, the section about "# Turn on SYN-flood protections." (came from LP 
#57091 ) is now entirely outdated, upstream kernel has long since turned on 
syncookies by default, so setting this flag explicitly in 
10-network-security.conf is entirely redundant likely since before ubuntu-14.04 
.
  I would like the ubuntu-maintainer to remove that section entirely in cosmic 
onwards.

  [I am going to report debian the similarly outdated syncookies
  comments in sysctl.conf itself].

  
  Secondly, I propose a new 10-network-tuning.conf with:-
  ==
  # Allow ECN for outgoing connections.  Starting with 4.2, there is an adaptive
  # fallback [enabled by default tcp_ecn_fallback option] preventing connection
  # loss even with ecn enabled, also ecn-intolerance is increasingly very rare.
  net.ipv4.tcp_ecn=1
  ==

  I know there is a (small) chance of issues/regressions with ECN
  enabled by default on outgoing but I'm quite sure the issue is very
  rare, like others notice [ref: 1 and 2 below].  Apple's selective
  enablements etc. show this works just as much as my own use for years
  and many similar reports.

  ECN actually being used for outgoing connections really helps with
  latency-reduction with modern routers (both core and edge) using
  queuing disciplines fq_codel or otherwise, able to mark rather than
  drop packets on ECN-enabled flows [helps latency and realtime
  applications].  Now we are just past LTS release is in my view the
  'right time' to finally enable ECN [and obviously easy to revert!].
  If this is disputed, in ANY case I strongly suggest at the very least
  a commented-out ECN section should be included, but 'defaults
  matter'!.

  I was going to suggest a non-default section about
  net.core.default_qdisc [ LP #1436945 ] but this appears to have been
  fixed upstream similarly.

  [1] 
https://www.ietf.org/proceedings/98/slides/slides-98-maprg-tcp-ecn-experience-with-enabling-ecn-on-the-internet-padma-bhooma-00.pdf
  [2] http://seclists.org/nanog/2015/Jun/675

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

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

[Touch-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade

[DSHR]

See https://patchwork.kernel.org/patch/10265345/. Dropping that patch
and recompiling the kernel leads to a situation where alsa and
pulseaudio seem to to be working again.

Adding

default-sample-rate = 48000

to /etc/pulse/daemon.conf leads to working headphones.

Maybe the patch has to be adjusted to newer firmware? A quirk seems to
be really necessary to avoid the specific patch to daemon.conf.

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected

[Leon Liao]

The attached file is the .snoop when I reproduced this bug.

** Attachment added: "hcitrace.snoop"
   
https://bugs.launchpad.net/oem-priority/+bug/1773897/+attachment/5145809/+files/hcitrace.snoop

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337

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

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

[Touch-packages] [Bug 1773897] [NEW] Bluetooth 3.0 mouses are automatically disconnected after connected

[Leon Liao]

Public bug reported:

The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
The fail rate is around 9/10.

1. The bug only occurs on the machine with intel 8265 module.
 I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
 This bug can not be reproduced on the machine with Killer 1435. 

2. This bug can be reproduced since bluez 5.46.
 Using bluez 5.45, this bug can not be reproduced.


Notebook: Dell XPS 13
Wi-Fi/BT module: intel 8265, 8087:0a2b
bluez: 5.48
BT mouse: logitech M337

** Affects: oem-priority
 Importance: Critical
 Status: New

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

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

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

Title:
  Bluetooth 3.0 mouses are automatically disconnected after connected

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337

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

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

[Touch-packages] [Bug 1608054] Re: IPv6 static addresses in multiple interfaces can't be configured thru interfaces file

[Launchpad Bug Tracker]

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

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

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

Title:
  IPv6 static addresses in multiple interfaces can't be configured thru
  interfaces file

Status in ifupdown package in Ubuntu:
  Expired

Bug description:
  Just installed 16.04 over a 14 version. I discovered that the actual
  interfaces file is not working correctly. Tried many choices, even
  using pre-up sleep 10 before configuring the IPv6 manual addresses,
  but didn't worked. This is the example file:

  auto lo
  iface lo inet loopback

  allow-hotplug eth0
  iface eth0 inet static
   mtu 9000
   address 172.16.0.7
   netmask 255.255.255.0
   dns-nameservers 10.10.10.3 80.58.61.250 80.58.61.254 8.8.8.8 8.8.4.4 
2001:470:1f09:495::3 2001:470:20::2

  iface eth0 inet6 auto

  allow-hotplug eth1
  iface eth1 inet static
   mtu 9000
   address 10.10.10.7
   netmask 255.255.255.0

  iface eth1 inet6 static
   autoconf 0
   accept_ra 0
   address 2001:470:1f09:495::7
   netmask 64

  allow-hotplug eth2
  iface eth2 inet static
   mtu 9000
   address 10.10.9.7
   netmask 255.255.255.0
   gateway 10.10.9.1

  iface eth2 inet6 static
   autoconf 0
   accept_ra 0
   address 2001:470:1f1d:275::7
   netmask 64
   gateway fe80::1

  As you can see, both, eth1 and eth2 have manual/static IPv6 addresses.
  Each one is in a different router. Only eth2 is the default gateway
  (eth1 is usen only for internal communication with another LAN).
  However, after reboot, the ifconfig shows:

  eth0  Link encap:Ethernet  direcciónHW 00:0c:29:64:c6:32  
Direc. inet:172.16.0.7  Difus.:172.16.0.255  Másc:255.255.255.0
Dirección inet6: fe80::20c:29ff:fe64:c632/64 Alcance:Enlace
ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST  MTU:9000  Métrica:1
Paquetes RX:17 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:32 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000 
Bytes RX:1500 (1.5 KB)  TX bytes:3805 (3.8 KB)

  eth1  Link encap:Ethernet  direcciónHW 00:0c:29:64:c6:3c  
Direc. inet:10.10.10.7  Difus.:10.10.10.255  Másc:255.255.255.0
Dirección inet6: 2001:470:1f09:495::7/64 Alcance:Global
Dirección inet6: fe80::20c:29ff:fe64:c63c/64 Alcance:Enlace
ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST  MTU:9000  Métrica:1
Paquetes RX:291 errores:0 perdidos:2 overruns:0 frame:0
Paquetes TX:144 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000 
Bytes RX:34692 (34.6 KB)  TX bytes:16360 (16.3 KB)

  eth2  Link encap:Ethernet  direcciónHW 00:0c:29:64:c6:46  
Direc. inet:10.10.9.7  Difus.:10.10.9.255  Másc:255.255.255.0
Dirección inet6: fe80::20c:29ff:fe64:c646/64 Alcance:Enlace
ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST  MTU:9000  Métrica:1
Paquetes RX:1281 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:755 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000 
Bytes RX:105008 (105.0 KB)  TX bytes:1554705 (1.5 MB)

  loLink encap:Bucle local  
Direc. inet:127.0.0.1  Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO  MTU:65536  Métrica:1
Paquetes RX:818 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:818 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1 
Bytes RX:136866 (136.8 KB)  TX bytes:136866 (136.8 KB)

  All what I tried fails. If I issue a manual:
  ip -6 addr add 2001:470:1f1d:275::7/64 dev eth2

  it works.

  I've noticed not sure if this is relevant, that the file
  /etc/network/run/ifstate.eth2 is empty, and /etc/network/run/ifstate
  only contains the other interfaces, but not eth2:

  eth1=eth1
  eth0=eth0
  lo=lo

  Before the upgrade it contained all the interfaces.

  I've used GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0", to keep
  the original interface names, not sure if that's relevant, just in
  case.

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

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

[Touch-packages] [Bug 1759681] Re: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

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

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

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

Title:
  package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in gconf package in Ubuntu:
  Expired

Bug description:
  Error report showed up after doing upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Mar 27 22:17:52 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2011-02-12 (2601 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (0 days ago)

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

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

[Touch-packages] [Bug 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

[Daniel van Vugt]

Reassigning to the modesetting driver. Because it sounds like the
problem is in modesetting, and only fixed by switching to nouveau.

** Also affects: nouveau via
   https://bugs.freedesktop.org/show_bug.cgi?id=106657
   Importance: Unknown
   Status: Unknown

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

** No longer affects: nautilus (Ubuntu)

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

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

** No longer affects: nouveau

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

Title:
  xserver-xorg-video-nouveau is required with nouveau driver to display
  properly gnome apps

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

Bug description:
  When I switch from nvidia to nouveau from software-properties-gtk and
  reboot, with the nouveau driver already running, I experience graphic
  glitches on gnome apps. This is due to "xserver-xorg-video-nouveau"
  missing.

  See bugs here:

  https://bugs.freedesktop.org/show_bug.cgi?id=106657
  https://gitlab.gnome.org/GNOME/nautilus/issues/426

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

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

[Touch-packages] [Bug 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

[Daniel van Vugt]

Please run 'apport-collect 1773651' to automatically send us information
about the hardware and the software that is installed.

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

Title:
  xserver-xorg-video-nouveau is required with nouveau driver to display
  properly gnome apps

Status in Nouveau Xorg driver:
  Unknown
Status in gnome-desktop package in Ubuntu:
  Incomplete
Status in nautilus package in Ubuntu:
  Incomplete
Status in software-properties package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Incomplete

Bug description:
  When I switch from nvidia to nouveau from software-properties-gtk and
  reboot, with the nouveau driver already running, I experience graphic
  glitches on gnome apps. This is due to "xserver-xorg-video-nouveau"
  missing.

  See bugs here:

  https://bugs.freedesktop.org/show_bug.cgi?id=106657
  https://gitlab.gnome.org/GNOME/nautilus/issues/426

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

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

[Touch-packages] [Bug 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.

[Christopher M. Penalver]

Mike L, thank you for reporting this and helping make Ubuntu better.

1) As per the sticker of the mouse itself (not from the Bug Description,
or the result of a terminal command), could you please provide the full
model?

2) As per the title:
"...on dual boot systems..."

is there some dependency on dual booting, where this issue only shows up
when using a dual boot versus not? Are you stating this happens in
Windows also?

3) Regarding your Bug Description:
>"Noticed this bug in 16.04 and earlier for who knows how long."

Did you personally test the mouse on a release earlier than 16.04? If
so, which precisely?

4) As per the sticker of the computer itself (not from the Bug
Description, or the result of a terminal command), could you please
provide the full computer model?

5) Regarding your Bug Description:
>"Installing the workaround package..."

Please state which package precisely (not expect folks to dumpster dive
URLs/guess).

6) Regarding your Bug Description:
>"...or removing the transceiver appears to be a workaround..."

Are you stating that you remove it and then plug it back in? If so, do
you have to keep doing this every so often, or is it good until you
restart?

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

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

** Tags added: 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/1772183

Title:
  Microsoft Mice on dual boot systems can scroll multiple lines at a
  time.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who
  knows how long. See https://askubuntu.com/questions/47100/mouse-wheel-
  scrolling-too-fast. Installing the workaround package or removing the
  transceiver appears to be a workaround for the time being. Xorg should
  automatically scroll normally, not multiple lines at time after
  rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu
  mentions the bug dating back to Natty.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-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..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 13:02:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.49
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DE
  dmi.board.vendor: HP
  dmi.board.version: 64.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  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: 

[Touch-packages] [Bug 1772917] Re: cannot maximize window

[Christopher M. Penalver]

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

Title:
  cannot maximize window

Status in unity package in Ubuntu:
  New

Bug description:
  I set auto hide Launcher,but when I do this,I cannot maximize window:the 
window cannot cover the launcher area
  my english is not very well,if you can understand Chinese ,pls read the 
follow Chinese words:
  我设置了启动器自动隐藏,而且启动器也自动隐藏了,但是最大化窗口的时候发现当前窗口并不能完全最大化:最大化的窗口不会覆盖启动器区域

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-127.153~14.04.1-generic 4.4.128
  Uname: Linux 4.4.0-127-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.28
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 23 21:09:25 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV610/M74 [Mobility Radeon HD 2400 
XT] [1002:94c8] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:012b]
  InstallationDate: Installed on 2018-04-30 (22 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  MachineType: Acer Aspire 4920
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=d3655307-16da-4f7c-8a4a-1037c602bd35 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.20
  dmi.board.name: Tahoe
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.20:bd02/01/2008:svnAcer:pnAspire4920:pvr0100:rvnAcer:rnTahoe:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 4920
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 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: Wed May 23 20:59:07 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1773015] Re: appli Notes

[Christopher M. Penalver]

LLAMAs, thank you for reporting this and helping make Ubuntu better.

1) Regarding your Bug Description:
>"Does not start."

What precisely does not start?

2) Is this something that started to happen after an update? If so,
which and when precisely?

3) If you remove the following non-default kernel parameters you are using, is 
it still reproducible:
plymouth:debug vesafb.invalid=1 drm.debug=0xe nopat

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

** Tags added: latest-bios-1qcn32ww

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

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

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

Title:
  appli Notes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Bug.Does not start.

  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: Wed May 23 22:39:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mullins [Radeon R4/R5 Graphics] [17aa:3808]
  InstallationDate: Installed on 2017-08-11 (285 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 80UM
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=a61d7236-19c8-4add-9fcb-be6756ebdfeb ro plymouth:debug 
vesafb.invalid=1 drm.debug=0xe nopat
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Lenovo
  dmi.bios.version: 1QCN32WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 7E1
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-17ACL
  dmi.modalias: 
dmi:bvnLenovo:bvr1QCN32WW:bd08/18/2016:svnLENOVO:pn80UM:pvrLenovoideapad110-17ACL:rvnLENOVO:rnNano7E1:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad110-17ACL:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UM
  dmi.product.version: Lenovo ideapad 110-17ACL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.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
  xserver.bootTime: Wed May 23 10:29:30 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: radeon

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

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

[Touch-packages] [Bug 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor

[Christopher M. Penalver]

Neal McBurnett, thank you for reporting this and helping make Ubuntu
better.

1) As per the sticker of the monitors (not from the Bug Description, or
the result of a terminal command), could you please provide the full
manufacturer and model?

2) Are you using any dongles/adapters to connect to either monitor?

3) To clarify, if you boot up with nothing attach, then login, then
attach both the VGA and HDMI, are you then able to configure all three
screens to display the desired output while logged in?

4) Was there a release newer than Trusty, but older then Bionic where
this issue wasn't reproducible?

5) Regarding desktop environment, are you presently using GNOME, Unity,
etc.?

6) Could you please post the output of the following terminal command (not 
manually attach files):
ls -la /var/crash

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

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

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

Title:
  No login prompt when booting bionic with both hdmi and vga monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm running bionic on a Lenovo X230 laptop.
  It works fine to boot it with either my hdmi monitor or my VGA monitor.
  It also works to attach the VGA monitor after booting and logging in with the 
HTMI monitor.

  But if both are connected while I boot, the graphical login prompt
  never appears, and just the mouse appears in the laptop window on a
  blue screen, with the HDMI monitor showing a blank blue screen, and
  the VGA monitor getting no signal.

  This monitor configuration worked fine with this computer in Trusty.

  I ran apport-bug to report the problem, and chose the first option:
  "Display (X.org)". I'm not positive what I'm running, but note that
  after booting and getting both monitors plugged in and running after
  login, I see both an Xwayland process and an Xorg process.  I suggest
  also changing apport-bug to appropriately reflect that wayland is
  somehow involved, and I hope that the included debug info will include
  any appropriate wayland info.  I note that it does seem to be possible
  to get some info via `apport-bug xwayland`.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Mon May 28 11:40:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2018-05-01 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 343522U
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=51612d4c-57c8-45d0-b308-86df52604f07 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA1WW (2.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA1WW(2.61):bd02/12/2015:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go 

[Touch-packages] [Bug 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor

[Christopher M. Penalver]

** Tags added: bios-outdated-2.70 regression-release

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

Title:
  No login prompt when booting bionic with both hdmi and vga monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm running bionic on a Lenovo X230 laptop.
  It works fine to boot it with either my hdmi monitor or my VGA monitor.
  It also works to attach the VGA monitor after booting and logging in with the 
HTMI monitor.

  But if both are connected while I boot, the graphical login prompt
  never appears, and just the mouse appears in the laptop window on a
  blue screen, with the HDMI monitor showing a blank blue screen, and
  the VGA monitor getting no signal.

  This monitor configuration worked fine with this computer in Trusty.

  I ran apport-bug to report the problem, and chose the first option:
  "Display (X.org)". I'm not positive what I'm running, but note that
  after booting and getting both monitors plugged in and running after
  login, I see both an Xwayland process and an Xorg process.  I suggest
  also changing apport-bug to appropriately reflect that wayland is
  somehow involved, and I hope that the included debug info will include
  any appropriate wayland info.  I note that it does seem to be possible
  to get some info via `apport-bug xwayland`.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Mon May 28 11:40:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2018-05-01 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 343522U
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=51612d4c-57c8-45d0-b308-86df52604f07 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA1WW (2.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA1WW(2.61):bd02/12/2015:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1772638] Re: Segfault in libmutter-2.so after suspend/resume using wayland. Core files are always truncated and invalid while the default shell is zsh.

[Daniel van Vugt]

... because what we see from your crashes is:

UnreportableReason  
Invalid core dump: BFD: warning: /tmp/apport_core_r0cnuvqg is truncated: 
expected core file size >= 923877376, found: 1114112

UnreportableReason  
Invalid core dump: BFD: warning: /tmp/apport_core_8lexsvus is truncated: 
expected core file size >= 846290944, found: 2162688

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

Title:
  Segfault in libmutter-2.so after suspend/resume using wayland. Core
  files are always truncated and invalid while the default shell is zsh.

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi,

  i have the problem when running the gnome wayland session in ubuntu
  18.04 that in ~1 out of 5 resume/suspend cycles a segfault in
  libmutter-2.so occurs which then kills my current session. Here is my
  journctl from the crash:

  Mai 22 12:39:03 x1 systemd[1]: Reached target Sleep.
  Mai 22 12:39:03 x1 systemd[1]: Starting Suspend...
  Mai 22 12:39:03 x1 systemd-sleep[2349]: Suspending system...
  Mai 22 12:39:03 x1 kernel: PM: suspend entry (s2idle)
  Mai 22 12:39:03 x1 kernel: PM: Syncing filesystems ... done.
  Mai 22 12:39:03 x1 gnome-shell[1483]: Failed to set CRTC mode 2560x1440: 
Permission denied
  Mai 22 12:39:03 x1 wpa_supplicant[976]: nl80211: deinit ifname=wlp2s0 
disabled_11b_rates=0
  Mai 22 12:39:03 x1 kernel: gnome-shell[1483]: segfault at 20 ip 
7ff704b28b17 sp 7ffd6c1cd1b0 error 4 in 
libmutter-2.so.0.0.0[7ff704a3b000+156000]
  Mai 22 12:39:03 x1 kernel: [drm] Reducing the compressed framebuffer size. 
This may lead to less power savings than a non-reduced-size. Try to increase 
stolen memory size if available in BIOS.
  Mai 22 13:11:15 x1 kernel: Freezing user space processes ... (elapsed 0.001 
seconds) done.
  Mai 22 13:11:15 x1 kernel: OOM killer disabled.
  Mai 22 13:11:15 x1 kernel: Freezing remaining freezable tasks ... (elapsed 
0.001 seconds) done.
  Mai 22 13:11:15 x1 kernel: Suspending console(s) (use no_console_suspend to 
debug)
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: unknown possible thermal alarm or 
keyboard event received
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: unhandled HKEY event 0x6032
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: please report the conditions when 
this event happened to ibm-acpi-de...@lists.sourceforge.net
  Mai 22 13:11:15 x1 kernel: [drm] GuC: Loaded firmware 
i915/kbl_guc_ver9_39.bin (version 9.39)
  Mai 22 13:11:15 x1 kernel: i915 :00:02.0: GuC firmware version 9.39
  Mai 22 13:11:15 x1 kernel: i915 :00:02.0: GuC submission enabled
  Mai 22 13:11:15 x1 kernel: i915 :00:02.0: HuC disabled
  Mai 22 13:11:15 x1 kernel: [drm] Reducing the compressed framebuffer size. 
This may lead to less power savings than a non-reduced-size. Try to increase 
stolen memory size if available in BIOS.
  Mai 22 13:11:15 x1 kernel: OOM killer enabled.
  Mai 22 13:11:15 x1 kernel: Restarting tasks ... done.
  Mai 22 13:11:15 x1 systemd-logind[986]: Lid opened.
  Mai 22 13:11:15 x1 kernel: rfkill: input handler enabled
  Mai 22 13:11:15 x1 systemd[1]: Started Run anacron jobs.
  Mai 22 13:11:15 x1 anacron[2420]: Anacron 2.3 started on 2018-05-22
  Mai 22 13:11:15 x1 anacron[2420]: Normal exit (0 jobs run)
  Mai 22 13:11:15 x1 kernel: thermal thermal_zone6: failed to read out thermal 
zone (-61)
  Mai 22 13:11:15 x1 tilix[1980]: Error reading events from display: Broken pipe
  Mai 22 13:11:15 x1 update-notifier[1901]: Error reading events from display: 
Broken pipe
  Mai 22 13:11:15 x1 systemd-sleep[2349]: System resumed.
  Mai 22 13:11:15 x1 kernel: PM: suspend exit
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: (EE)
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: Fatal server error:
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: (EE) failed to read Wayland 
events: Broken pipe
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: (EE)
  Mai 22 13:11:15 x1 systemd[1]: Started Suspend.
  Mai 22 13:11:15 x1 systemd[1]: sleep.target: Unit not needed anymore. 
Stopping.
  Mai 22 13:11:15 x1 systemd[1]: Stopped target Sleep.
  Mai 22 13:11:15 x1 systemd[1]: Reached target Suspend.
  Mai 22 13:11:15 x1 systemd[1]: suspend.target: Unit not needed anymore. 
Stopping.
  Mai 22 13:11:15 x1 systemd[1]: Stopped target Suspend.
  Mai 22 13:11:15 x1 gnome-session[1455]: gnome-session-binary[1455]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 11
  Mai 22 13:11:15 x1 gnome-session-binary[1455]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 11
  Mai 22 13:11:15 x1 gnome-session-binary[1455]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Mai 22 13:11:15 x1 kdeconnectd.desktop[1725]: ICE default IO error handler 
doing an exit(), pid = 1725, errno = 11
  Mai 22 13:11:15 x1 

[Touch-packages] [Bug 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions

[Daniel van Vugt]

OK, thanks. H.264 high profile sounds like something your hardware
supports.

For the moment I suggest using 'mpv', or if you need totem then use this
workaround to play it less efficiently:

  sudo apt remove gstreamer1.0-vaapi


** Attachment removed: "totem"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1770725/+attachment/5145653/+files/Captura%20de%20pantalla%20de%202018-05-28%2013-43-34.png

** Attachment removed: "Description of the movie"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1770725/+attachment/5145633/+files/Captura%20de%20pantalla%20de%202018-05-28%2013-35-01.png

** Summary changed:

- [i915 SNB] You can not see the image of the movie in Wayland sessions
+ [i915 SNB] Totem window is all black in Wayland sessions

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Incomplete => New

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

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

Title:
  [i915 SNB] Totem window is all black in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1772638] Re: Segfault in libmutter-2.so after suspend/resume using wayland. Core files are always truncated and invalid while the default shell is zsh.

[Daniel van Vugt]

I wonder if the truncated core files are a bug in apport? Maybe apport's
not waiting long enough for the core files to be written. They should be
around 1GB each.

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

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

Title:
  Segfault in libmutter-2.so after suspend/resume using wayland. Core
  files are always truncated and invalid while the default shell is zsh.

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi,

  i have the problem when running the gnome wayland session in ubuntu
  18.04 that in ~1 out of 5 resume/suspend cycles a segfault in
  libmutter-2.so occurs which then kills my current session. Here is my
  journctl from the crash:

  Mai 22 12:39:03 x1 systemd[1]: Reached target Sleep.
  Mai 22 12:39:03 x1 systemd[1]: Starting Suspend...
  Mai 22 12:39:03 x1 systemd-sleep[2349]: Suspending system...
  Mai 22 12:39:03 x1 kernel: PM: suspend entry (s2idle)
  Mai 22 12:39:03 x1 kernel: PM: Syncing filesystems ... done.
  Mai 22 12:39:03 x1 gnome-shell[1483]: Failed to set CRTC mode 2560x1440: 
Permission denied
  Mai 22 12:39:03 x1 wpa_supplicant[976]: nl80211: deinit ifname=wlp2s0 
disabled_11b_rates=0
  Mai 22 12:39:03 x1 kernel: gnome-shell[1483]: segfault at 20 ip 
7ff704b28b17 sp 7ffd6c1cd1b0 error 4 in 
libmutter-2.so.0.0.0[7ff704a3b000+156000]
  Mai 22 12:39:03 x1 kernel: [drm] Reducing the compressed framebuffer size. 
This may lead to less power savings than a non-reduced-size. Try to increase 
stolen memory size if available in BIOS.
  Mai 22 13:11:15 x1 kernel: Freezing user space processes ... (elapsed 0.001 
seconds) done.
  Mai 22 13:11:15 x1 kernel: OOM killer disabled.
  Mai 22 13:11:15 x1 kernel: Freezing remaining freezable tasks ... (elapsed 
0.001 seconds) done.
  Mai 22 13:11:15 x1 kernel: Suspending console(s) (use no_console_suspend to 
debug)
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: unknown possible thermal alarm or 
keyboard event received
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: unhandled HKEY event 0x6032
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: please report the conditions when 
this event happened to ibm-acpi-de...@lists.sourceforge.net
  Mai 22 13:11:15 x1 kernel: [drm] GuC: Loaded firmware 
i915/kbl_guc_ver9_39.bin (version 9.39)
  Mai 22 13:11:15 x1 kernel: i915 :00:02.0: GuC firmware version 9.39
  Mai 22 13:11:15 x1 kernel: i915 :00:02.0: GuC submission enabled
  Mai 22 13:11:15 x1 kernel: i915 :00:02.0: HuC disabled
  Mai 22 13:11:15 x1 kernel: [drm] Reducing the compressed framebuffer size. 
This may lead to less power savings than a non-reduced-size. Try to increase 
stolen memory size if available in BIOS.
  Mai 22 13:11:15 x1 kernel: OOM killer enabled.
  Mai 22 13:11:15 x1 kernel: Restarting tasks ... done.
  Mai 22 13:11:15 x1 systemd-logind[986]: Lid opened.
  Mai 22 13:11:15 x1 kernel: rfkill: input handler enabled
  Mai 22 13:11:15 x1 systemd[1]: Started Run anacron jobs.
  Mai 22 13:11:15 x1 anacron[2420]: Anacron 2.3 started on 2018-05-22
  Mai 22 13:11:15 x1 anacron[2420]: Normal exit (0 jobs run)
  Mai 22 13:11:15 x1 kernel: thermal thermal_zone6: failed to read out thermal 
zone (-61)
  Mai 22 13:11:15 x1 tilix[1980]: Error reading events from display: Broken pipe
  Mai 22 13:11:15 x1 update-notifier[1901]: Error reading events from display: 
Broken pipe
  Mai 22 13:11:15 x1 systemd-sleep[2349]: System resumed.
  Mai 22 13:11:15 x1 kernel: PM: suspend exit
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: (EE)
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: Fatal server error:
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: (EE) failed to read Wayland 
events: Broken pipe
  Mai 22 13:11:15 x1 org.gnome.Shell.desktop[1483]: (EE)
  Mai 22 13:11:15 x1 systemd[1]: Started Suspend.
  Mai 22 13:11:15 x1 systemd[1]: sleep.target: Unit not needed anymore. 
Stopping.
  Mai 22 13:11:15 x1 systemd[1]: Stopped target Sleep.
  Mai 22 13:11:15 x1 systemd[1]: Reached target Suspend.
  Mai 22 13:11:15 x1 systemd[1]: suspend.target: Unit not needed anymore. 
Stopping.
  Mai 22 13:11:15 x1 systemd[1]: Stopped target Suspend.
  Mai 22 13:11:15 x1 gnome-session[1455]: gnome-session-binary[1455]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 11
  Mai 22 13:11:15 x1 gnome-session-binary[1455]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 11
  Mai 22 13:11:15 x1 gnome-session-binary[1455]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Mai 22 13:11:15 x1 kdeconnectd.desktop[1725]: ICE default IO error handler 
doing an exit(), pid = 1725, errno = 11
  Mai 22 13:11:15 x1 org.gnome.SettingsDaemon.Power.desktop[1611]: 
xcb_connection_has_error() returned true
  Mai 22 13:11:15 x1 firefox.desktop[2050]: 

[Touch-packages] [Bug 1773744] Re: Desktop session crash

[Christopher M. Penalver]

Sami Pietila, thank you for reporting this and helping make Ubuntu
better.

1) To clarify, did this issue start after an update? If so, which and
when precisely?

2) Please provide the ouput of the following terminal command (not manually 
attach files):
ls -la /var/crash

3) To verify a WORKAROUND, if you install gnome-session-flashback does
this crash also?

4) To advise, keep in mind that this issue may be due to upgrade cruft
being left behind from your OS upgrade. Hence, testing
http://cdimage.ubuntu.com/daily-live/current/ would help rule this out.

** Tags added: bios-outdated-02.71

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

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

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

Title:
  Desktop session crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I connect third monitor to my Ubuntu PC, the whole graphical
  display session crashes. Additionally, the login does not show texts
  correctly. The texts are mostly missing.

  The errors happend with both Wayland and X.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 28 10:15:54 2018
  DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [103c:90b8]
  InstallationDate: Installed on 2016-11-22 (551 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.18
  dmi.board.asset.tag: CZC3427KBP
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3427KBP
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-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

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

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

[Touch-packages] [Bug 1771340] Re: sshd failed on config reload

[Marcos Paulo de Souza]

I can confirm this is working in Xenial. After change the sshd_config
config and execute a systemctl restart it worked. The ssh.service file
have only one ExecReload clause:

...
[Service]
EnvironmentFile=-/etc/default/ssh
ExecStart=/usr/sbin/sshd -D $SSHD_OPTS
ExecReload=/bin/kill -HUP $MAINPID
...

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

Title:
  sshd failed on config reload

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  After adding some lines to /etc/ssh/sshd_config I tried to reload the
  configuration with the command:

  ```
  sudo systemctl reload sshd
  ```

  No error message was returned. So I assumed that the sshd was running
  with the current config. But `sudo systemctl status sshd` told me that
  the service failed due to a wrong option in /etc/ssh/sshd_config.
  Please see the following output:

  ~~~
  :~$ sudo vim /etc/ssh/sshd_config
  :~$ sudo systemctl reload sshd
  :~$ sudo systemctl status sshd
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s 
ago
Process: 12089 ExecReload=/bin/kill -HUP $MAINPID (code=exited, 
status=0/SUCCESS)
Process: 7536 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 7536 (code=exited, status=255)
  ~~~

  I would expect that a warning or error message is returned when the
  service fails while reloading it's configuration.

  A fix for this behaviour would be appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Tue May 15 10:18:25 2018
  InstallationDate: Installed on 2013-01-10 (1950 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to xenial on 2017-03-12 (428 days ago)
  mtime.conffile..etc.pam.d.sshd: 2017-03-13T19:59:01.965420

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

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

[Touch-packages] [Bug 1773687] Re: [bionic] no unattended installation

[Dirk Eddelbuettel]

Hi Steve,

On 28 May 2018 at 22:47, Steve Langasek wrote:
| This was going to be my recommended approach, as it's the authoritative
| way to have a noninteractive install.  I haven't had a chance to look
| into the package yet given the holiday weekend.  Do you think there is a
| bug here that still warrants investigating, or do you think this was a
| configuration regression on your side?

I have the feeling that one important variable setting may have gotten
dropped at your end because if I look at my GH repo here:

   https://github.com/rocker-org/rocker/tree/master/r-apt

you will see essentially identical Dockerfile setups that worked for

   precise
   trusty
   wily
   xenial
   yakkety
   zesty
   artful

and then all of a sudden failed for

   bionic

I will add the setting, but methinks you guys set it before. Or maybe one of
the Debian packages involved did.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

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

Title:
  [bionic] no unattended installation

Status in tzdata package in Ubuntu:
  New

Bug description:
  Package: tzdata
  Version: 2018d-1
  Ubuntu release: 18.04

  There appears to be a regression with the preseeding data for tzdata in the 
18.04 release.
  When running 

 apt-get install tzdata

  I now _always_ drop into an interactive selection of the timezone
  'area' and 'zone'. This was not the case before; it is also not the
  case in Debian 'unstable' right now.

  I looked into the postinst script, but I can't figure out where the
  preseeded info would be. I tried debconf-set-selections with a preseed
  file, but no luck.

  This blocks usage of tzdata in Docker containers and is there for a
  bit annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: tzdata 2017c-0ubuntu0.17.10
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 13:17:42 2018
  InstallationDate: Installed on 2017-12-31 (147 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773860] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 24

[Mike Doherty]

Public bug reported:

I'll let someone else figure out if this is a duplicate with the other
"failed to install/upgrade" bugs

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Mon May 28 16:47:29 2018
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 24
InstallationDate: Installed on 2016-04-27 (761 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
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: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 24
UpgradeStatus: Upgraded to bionic on 2018-05-29 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 24

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  I'll let someone else figure out if this is a duplicate with the other
  "failed to install/upgrade" bugs

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Mon May 28 16:47:29 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 24
  InstallationDate: Installed on 2016-04-27 (761 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 24
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (0 days ago)

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

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

[Touch-packages] [Bug 1593924] Re: systemd-shim was not installed in 16.10 and now cannot purge or remove

[Kees Cook]

** Package changed: libjpeg-turbo (Ubuntu) => systemd-shim (Ubuntu)

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

Title:
  systemd-shim was not installed in 16.10 and now cannot purge or remove

Status in systemd-shim package in Ubuntu:
  Invalid

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

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

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

[Touch-packages] [Bug 1773859] [NEW] upgrades to 18.04 fail

[Kees Cook]

Public bug reported:

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

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

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

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

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

** Affects: systemd-shim (Ubuntu Bionic)
 Importance: Undecided
 Status: New

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

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

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

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  New
Status in systemd-shim package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd-shim source package in Bionic:
  New

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

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

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

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

[Touch-packages] [Bug 1773516] Re: [Lenovo Yoga 300-11IBY] Right click not working

[Christopher M. Penalver]

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

Phill, if you install gnome-tweak-tool and configure GNOME Tweak Tool >
Keyboard & Mouse > Mouse Click Emulation > Area checked then it is a
configuration issue, and in turn, a duplicate.

However, if you have this configured and it still doesn't work, that's a
different issue.

Could you please advise?

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

Title:
  [Lenovo Yoga 300-11IBY] Right click not working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The right click is not working on Lenovo Yoga touch pad after upgrade
  to 18.04, worked minutes before on 17.10.

  I think it works on the Think Pad out-of-the-box (after upgrade from
  17.10), if that helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  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: Sat May 26 10:34:57 2018
  DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
  InstallationDate: Installed on 2018-01-18 (128 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 80M0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J33995WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 300-11IBY
  dmi.modalias: 
dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M0
  dmi.product.version: Lenovo YOGA 300-11IBY
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

[Bump]

It happens with Gnome and Plasma, for gnome apps like synaptics, etc. I
can't even login to Wayland, the screen goes black just after entering
my user's password and clicking enter.

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

Title:
  xserver-xorg-video-nouveau is required with nouveau driver to display
  properly gnome apps

Status in gnome-desktop package in Ubuntu:
  Incomplete
Status in nautilus package in Ubuntu:
  Incomplete
Status in software-properties package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Incomplete

Bug description:
  When I switch from nvidia to nouveau from software-properties-gtk and
  reboot, with the nouveau driver already running, I experience graphic
  glitches on gnome apps. This is due to "xserver-xorg-video-nouveau"
  missing.

  See bugs here:

  https://bugs.freedesktop.org/show_bug.cgi?id=106657
  https://gitlab.gnome.org/GNOME/nautilus/issues/426

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

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

[Touch-packages] [Bug 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

[Bump]

What information do you need to know exactly? It's a nvidia gtx 10
series

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

Title:
  xserver-xorg-video-nouveau is required with nouveau driver to display
  properly gnome apps

Status in gnome-desktop package in Ubuntu:
  Incomplete
Status in nautilus package in Ubuntu:
  Incomplete
Status in software-properties package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Incomplete

Bug description:
  When I switch from nvidia to nouveau from software-properties-gtk and
  reboot, with the nouveau driver already running, I experience graphic
  glitches on gnome apps. This is due to "xserver-xorg-video-nouveau"
  missing.

  See bugs here:

  https://bugs.freedesktop.org/show_bug.cgi?id=106657
  https://gitlab.gnome.org/GNOME/nautilus/issues/426

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

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

[Touch-packages] [Bug 1760113] Re: System does not display video after waking up from sleep

[GilgongoJones]

I also have the same issue using 18.04 (clean install) 4.15.0-22-generic, with 
the following graphics using Nvidia 390
:

01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 
Ti] (rev a2) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. GM107 [GeForce GTX 750 Ti]
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at f600 (32-bit, non-prefetchable) [size=16M]
Memory at e000 (64-bit, prefetchable) [size=256M]
Memory at f000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Legacy Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [250] Latency Tolerance Reporting
Capabilities: [258] L1 PM Substates
Capabilities: [128] Power Budgeting 
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 

Capabilities: [900] #19
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia

Display is a Dell P2415Q connected using displayport. Very occasionally
it comes back after the CPU has suspended, but mostly not.

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

Title:
  System does not display video after waking up from sleep

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm using the latest daily development snapshot iso of Ubuntu Bionic
  Beaver.

  My issue is that after issuing a sleep command with systemctl suspend
  -i, the system cannot doesn't display any video or seems to work at
  all when waking it up. It does detect the keypress of my keyboards,
  because the fans will start spinning up and the HDD LED will flicker,
  confirming that it did wake up, but I can't do anything with it. All I
  could do was to shut off the computer entirely with my hardware
  button.

  As this was my first bug report I'm willing to provide any more
  debugging information, I just don't know how. I'm using a desktop
  computer and I'm certain the motherboard supports this sleep state and
  it worked fine in previous versions of several linux distros. I blamed
  the error to xorg in particular because it seems to be waking up, it
  just won't start up my screens.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/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-13ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 15:47:01 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GM206 [GeForce GTX 950] [1458:36c5]
  InstallationDate: Installed on 2018-03-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=cf158901-6c71-4345-89dd-371337d8426a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88TD-V EVO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  

[Touch-packages] [Bug 1773687] Re: [bionic] no unattended installation

[Steve Langasek]

This was going to be my recommended approach, as it's the authoritative
way to have a noninteractive install.  I haven't had a chance to look
into the package yet given the holiday weekend.  Do you think there is a
bug here that still warrants investigating, or do you think this was a
configuration regression on your side?

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

Title:
  [bionic] no unattended installation

Status in tzdata package in Ubuntu:
  New

Bug description:
  Package: tzdata
  Version: 2018d-1
  Ubuntu release: 18.04

  There appears to be a regression with the preseeding data for tzdata in the 
18.04 release.
  When running 

 apt-get install tzdata

  I now _always_ drop into an interactive selection of the timezone
  'area' and 'zone'. This was not the case before; it is also not the
  case in Debian 'unstable' right now.

  I looked into the postinst script, but I can't figure out where the
  preseeded info would be. I tried debconf-set-selections with a preseed
  file, but no luck.

  This blocks usage of tzdata in Docker containers and is there for a
  bit annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: tzdata 2017c-0ubuntu0.17.10
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 13:17:42 2018
  InstallationDate: Installed on 2017-12-31 (147 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

[Christian Boltz]

Looks like you have a syntax error in /etc/apparmor.d/tunables/multiarch
around line 13. Can you please attach this file? Also, did you modify it
manually?

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

Title:
  Failed to start AppArmor initialization with status=123/n/a

Status in apparmor package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Won't Fix

Bug description:
  AppArmor in Ubuntu 18.04 fails to start every time:

  $ systemctl status apparmor.service 
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2018-03-19 13:47:22 AWST; 56s 
ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 773 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 773 (code=exited, status=123)

  Mar 19 13:47:21 xps15-9560 apparmor[773]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e
  Mar 19 13:47:21 xps15-9560 apparmor[773]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.web
  Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e
  Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 19 13:47:22 xps15-9560 apparmor[773]:...fail!
  Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  Mar 19 13:47:22 xps15-9560 systemd[1]: Failed to start AppArmor 
initialization.

  
  journalctl -xe gives essentially the same lack of information issued after a 
systemctl restart apparmor.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apparmor 2.11.0-2ubuntu19
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Mar 19 13:50:42 2018
  InstallationDate: Installed on 2017-08-16 (214 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-12-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=1
  SourcePackage: apparmor
  Syslog:
   Mar 19 13:47:22 xps15-9560 dbus-daemon[1252]: [system] AppArmor D-Bus 
mediation is enabled
   Mar 19 13:47:23 xps15-9560 dbus-daemon[1491]: [session uid=125 pid=1491] 
AppArmor D-Bus mediation is enabled
   Mar 19 13:47:39 xps15-9560 dbus-daemon[2160]: [session uid=1001 pid=2160] 
AppArmor D-Bus mediation is enabled
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (121 days ago)
  mtime.conffile..etc.apparmor.d.abstractions.nameservice: 
2017-10-24T16:47:24.395996

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

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

[Touch-packages] [Bug 1773484] Re: Login screen not moved to used monitor

[Christopher M. Penalver]

Sending to gnome-shell for review, given monitor does display output
immediately after first configuration via Settings > Devices > Display
(i.e. appears not driver/kernel issue).

** Description changed:

- On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
- the monitor where the mouse pointer is located. On Ubuntu 18.04 login
- dialog and system menues are restricted to the main monitor.
+ What is expected to happen is that with my computer turned off, when I
+ plug in my external VGA monitor into my laptop for the first time, and
+ boot up to the login screen, the display is in mirror mode and I can see
+ the login screen on both the built-in screen, and external monitor.
  
- So if you have a notebook with defect lcd display you can work with it
- using Ubuntu 16.04 and an external monitor, but you cannot work with
- Ubuntu 18.04, because you are not able to login!
- 
- This problem was also asked on:
- 
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04
+ What happens instead is that the login screen is only shown on the
+ built-in screen.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_AT.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_AT.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Summary changed:

- Login screen not moved to used monitor
+ First bootup with external VGA monitor plugged in doesn't display anything at 
login screen

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

Title:
  First bootup with external VGA monitor plugged in doesn't display
  anything at login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  What is expected to happen is that with my computer turned off, when I
  plug in my external VGA monitor into my laptop for the first time, and
  boot up to the login screen, the display is in mirror mode and I can
  see the login screen on both the built-in screen, and external
  monitor.

  What happens instead is that the login screen is only shown on the
  built-in screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: 

[Touch-packages] [Bug 1773484] Re: Login screen not moved to used monitor

[Christopher M. Penalver]

Manfred Steiner, in order to finely scope this report on "one issue",
this report will only focus on the first time one boots up with the
external VGA monitor connected (no Beamer), and is at the login screen
(not after login).

Regarding the behavior above, what is reasonable is either, it does what
it did before in 16.04, or the monitor is properly detected and is in
mirror mode. Either way, one may login.

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

Title:
  First bootup with external VGA monitor plugged in doesn't display
  anything at login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  What is expected to happen is that with my computer turned off, when I
  plug in my external VGA monitor into my laptop for the first time, and
  boot up to the login screen, the display is in mirror mode and I can
  see the login screen on both the built-in screen, and external
  monitor.

  What happens instead is that the login screen is only shown on the
  built-in screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1537338] Re: package apport 2.14.1-0ubuntu3.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package apport 2.14.1-0ubuntu3.19 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Downloading updates after initial install of Ubuntu 14.4lts

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.19
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  ApportLog:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CrashReports:
   664:1000:116:0:2016-01-19 14:42:47.903456298 +0200:2016-01-19 
14:42:47.903456298 
+0200:/var/crash/_usr_share_software-center_software-center.1000.upload
   640:1000:116:31037082:2016-01-19 14:42:46.903456211 +0200:2016-01-22 
08:04:23.182983618 
+0200:/var/crash/_usr_share_software-center_software-center.1000.crash
   640:0:116:284619:2016-01-23 10:41:18.274090528 +0200:2016-01-23 
10:41:19.274090528 +0200:/var/crash/apport.0.crash
  Date: Sat Jan 23 10:41:19 2016
  DuplicateSignature: package:apport:2.14.1-0ubuntu3.19:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-18 (4 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.10
  SourcePackage: apport
  Title: package apport 2.14.1-0ubuntu3.19 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/apport/+bug/1537338/+subscriptions

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

[Touch-packages] [Bug 1773849] Re: wifi connection to an protected EAP, MSCHAPv2 connection drops constantly

[Willem Hobers]

** Description changed:

  Hi all,
  
  My wifi connection disconnects constantly when I am connected to an
  eduroam/govroam access point (protected EAP, MSCHAPv2).
  
  The wifi driver is: rtl8812au-dkms.
  
  Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  
  02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE
  802.11ac PCIe Wireless Network Adapter
  
  Symptoms: the (eduroam) wifi-network is found, the wifi connection is
  set up, it works for a bit and then the connection is dropped.
  
  If I use my Android phone (which connects fine to the eduroam
  connection), to tether my laptop, the connection is fine.
  
  Also my laptop connects flawlessly to my home connection (WPA).
  
  In kern.log I see messages like this (redacted the mac-address):
  May 28 10:30:09 Xubuntu-18-04 kernel: [  157.858664] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:31:56 Xubuntu-18-04 kernel: [  265.191355] wlp2s0: deauthenticating 
from 00:**:**:**:**:** by local choice (Reason: 3=DEAUTH_
  LEAVING)
  May 28 10:32:55 Xubuntu-18-04 kernel: [  324.049168] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:32:57 Xubuntu-18-04 kernel: [  326.168600] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:32:59 Xubuntu-18-04 kernel: [  327.696740] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:33:00 Xubuntu-18-04 kernel: [  329.056596] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:33:01 Xubuntu-18-04 kernel: [  330.449235] wlp2s0: disassociated 
from 00:08:2f:ef:66:51 (Reason: 1=UNSPECIFIED)
  May 28 10:33:03 Xubuntu-18-04 kernel: [  332.448884] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:33:05 Xubuntu-18-04 kernel: [  334.249308] wlp2s0: disassociated 
from 00:08:2f:ef:66:51 (Reason: 1=UNSPECIFIED)
  May 28 10:33:07 Xubuntu-18-04 kernel: [  336.418400] wlp2s0: deauthenticated 
from 00:**:**:**:**:** (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  I have been using 18.04 without problems (and 16.04 before that) until 
recently; so it seems the problem is recent.
  
  If there is any more information I can provide please let me know.
  
  Edit: I came across a thread which seems to describe the same problem;
  and people there have tried analyzing the problem. I don't understand
  what people are saying there, so it may not be helpful, still:
  https://bbs.archlinux.org/viewtopic.php?id=230963
+ 
+ Edit 2: I'm also seeing this in 18.10 (the daily of which I am testing).

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

Title:
  wifi connection to an protected EAP, MSCHAPv2 connection drops
  constantly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi all,

  My wifi connection disconnects constantly when I am connected to an
  eduroam/govroam access point (protected EAP, MSCHAPv2).

  The wifi driver is: rtl8812au-dkms.

  Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16
  12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE
  802.11ac PCIe Wireless Network Adapter

  Symptoms: the (eduroam) wifi-network is found, the wifi connection is
  set up, it works for a bit and then the connection is dropped.

  If I use my Android phone (which connects fine to the eduroam
  connection), to tether my laptop, the connection is fine.

  Also my laptop connects flawlessly to my home connection (WPA).

  In kern.log I see messages like this (redacted the mac-address):
  May 28 10:30:09 Xubuntu-18-04 kernel: [  157.858664] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:31:56 Xubuntu-18-04 kernel: [  265.191355] wlp2s0: deauthenticating 
from 00:**:**:**:**:** by local choice (Reason: 3=DEAUTH_
  LEAVING)
  May 28 10:32:55 Xubuntu-18-04 kernel: [  324.049168] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:32:57 Xubuntu-18-04 kernel: [  326.168600] wlp2s0: deauthenticated 
from 00:**:**:**:**:** (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:32:59 Xubuntu-18-04 kernel: [  327.696740] wlp2s0: deauthenticated 
from 00:**:**:**:**:** (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:33:00 Xubuntu-18-04 kernel: [  329.056596] wlp2s0: deauthenticated 
from 00:**:**:**:**:** (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:33:01 Xubuntu-18-04 kernel: [  330.449235] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:33:03 Xubuntu-18-04 kernel: [  332.448884] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 

[Touch-packages] [Bug 1773850] [NEW] No login prompt when booting bionic with both hdmi and vga monitor

[Neal McBurnett]

Public bug reported:

I'm running bionic on a Lenovo X230 laptop.
It works fine to boot it with either my hdmi monitor or my VGA monitor.
It also works to attach the VGA monitor after booting and logging in with the 
HTMI monitor.

But if both are connected while I boot, the graphical login prompt never
appears, and just the mouse appears in the laptop window on a blue
screen, with the HDMI monitor showing a blank blue screen, and the VGA
monitor getting no signal.

This monitor configuration worked fine with this computer in Trusty.

I ran apport-bug to report the problem, and chose the first option:
"Display (X.org)". I'm not positive what I'm running, but note that
after booting and getting both monitors plugged in and running after
login, I see both an Xwayland process and an Xorg process.  I suggest
also changing apport-bug to appropriately reflect that wayland is
somehow involved, and I hope that the included debug info will include
any appropriate wayland info.  I note that it does seem to be possible
to get some info via `apport-bug xwayland`.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
Date: Mon May 28 11:40:58 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2018-05-01 (26 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 343522U
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=51612d4c-57c8-45d0-b308-86df52604f07 ro
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: GCETA1WW (2.61 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA1WW(2.61):bd02/12/2015:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
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 N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  No login prompt when booting bionic with both hdmi and vga monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm running bionic on a Lenovo X230 laptop.
  It works fine to boot it with either my hdmi monitor or my VGA monitor.
  It also works to attach the VGA monitor after booting and logging in with the 
HTMI monitor.

  But if both are connected while I boot, the graphical login prompt
  never appears, and just the mouse appears in the laptop window on a
  blue screen, with the HDMI monitor showing a blank blue screen, and
  the VGA monitor getting no signal.

  This monitor configuration worked fine with this computer in Trusty.

  I ran apport-bug to report the problem, and chose the first option:
  "Display (X.org)". I'm not positive what I'm running, but note that
  after booting and getting both monitors plugged in and running after
  login, I see both an Xwayland process and an Xorg process.  I suggest
  also changing apport-bug to appropriately reflect that wayland is
  somehow involved, and I hope that the included debug info will include
  any appropriate wayland 

[Touch-packages] [Bug 1773849] Re: wifi connection to an protected EAP, MSCHAPv2 connection drops constantly

[Willem Hobers]

** Description changed:

  Hi all,
  
  My wifi connection disconnects constantly when I am connected to an
  eduroam/govroam access point (protected EAP, MSCHAPv2).
  
  The wifi driver is: rtl8812au-dkms.
  
  Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  
  02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE
  802.11ac PCIe Wireless Network Adapter
  
  Symptoms: the (eduroam) wifi-network is found, the wifi connection is
  set up, it works for a bit and then the connection is dropped.
  
  If I use my Android phone (which connects fine to the eduroam
  connection), to tether my laptop, the connection is fine.
  
  Also my laptop connects flawlessly to my home connection (WPA).
  
  In kern.log I see messages like this (redacted the mac-address):
  May 28 10:30:09 Xubuntu-18-04 kernel: [  157.858664] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:31:56 Xubuntu-18-04 kernel: [  265.191355] wlp2s0: deauthenticating 
from 00:**:**:**:**:** by local choice (Reason: 3=DEAUTH_
  LEAVING)
  May 28 10:32:55 Xubuntu-18-04 kernel: [  324.049168] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:32:57 Xubuntu-18-04 kernel: [  326.168600] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:32:59 Xubuntu-18-04 kernel: [  327.696740] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:33:00 Xubuntu-18-04 kernel: [  329.056596] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:33:01 Xubuntu-18-04 kernel: [  330.449235] wlp2s0: disassociated 
from 00:08:2f:ef:66:51 (Reason: 1=UNSPECIFIED)
  May 28 10:33:03 Xubuntu-18-04 kernel: [  332.448884] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:33:05 Xubuntu-18-04 kernel: [  334.249308] wlp2s0: disassociated 
from 00:08:2f:ef:66:51 (Reason: 1=UNSPECIFIED)
  May 28 10:33:07 Xubuntu-18-04 kernel: [  336.418400] wlp2s0: deauthenticated 
from 00:**:**:**:**:** (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  I have been using 18.04 without problems (and 16.04 before that) until 
recently; so it seems the problem is recent.
  
  If there is any more information I can provide please let me know.
+ 
+ Edit: I came across a thread which seems to describe the same problem;
+ and people there have tried analyzing the problem. I don't understand
+ what people are saying there, so it may not be helpful, still:
+ https://bbs.archlinux.org/viewtopic.php?id=230963

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

Title:
  wifi connection to an protected EAP, MSCHAPv2 connection drops
  constantly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi all,

  My wifi connection disconnects constantly when I am connected to an
  eduroam/govroam access point (protected EAP, MSCHAPv2).

  The wifi driver is: rtl8812au-dkms.

  Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16
  12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE
  802.11ac PCIe Wireless Network Adapter

  Symptoms: the (eduroam) wifi-network is found, the wifi connection is
  set up, it works for a bit and then the connection is dropped.

  If I use my Android phone (which connects fine to the eduroam
  connection), to tether my laptop, the connection is fine.

  Also my laptop connects flawlessly to my home connection (WPA).

  In kern.log I see messages like this (redacted the mac-address):
  May 28 10:30:09 Xubuntu-18-04 kernel: [  157.858664] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:31:56 Xubuntu-18-04 kernel: [  265.191355] wlp2s0: deauthenticating 
from 00:**:**:**:**:** by local choice (Reason: 3=DEAUTH_
  LEAVING)
  May 28 10:32:55 Xubuntu-18-04 kernel: [  324.049168] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:32:57 Xubuntu-18-04 kernel: [  326.168600] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:32:59 Xubuntu-18-04 kernel: [  327.696740] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:33:00 Xubuntu-18-04 kernel: [  329.056596] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:33:01 Xubuntu-18-04 kernel: [  330.449235] wlp2s0: disassociated 
from 00:08:2f:ef:66:51 (Reason: 1=UNSPECIFIED)
  May 28 10:33:03 Xubuntu-18-04 kernel: [  332.448884] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:33:05 Xubuntu-18-04 kernel: [  334.249308] wlp2s0: 

[Touch-packages] [Bug 1773849] Re: wifi connection to an protected EAP, MSCHAPv2 connection drops constantly

[Willem Hobers]

** Description changed:

  Hi all,
  
  My wifi connection disconnects constantly when I am connected to an
  eduroam/govroam access point (protected EAP, MSCHAPv2).
  
  The wifi driver is: rtl8812au-dkms.
  
  Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  
  02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE
  802.11ac PCIe Wireless Network Adapter
  
  Symptoms: the (eduroam) wifi-network is found, the wifi connection is
  set up, it works for a bit and then the connection is dropped.
  
  If I use my Android phone (which connects fine to the eduroam
  connection), to tether my laptop, the connection is fine.
  
  Also my laptop connects flawlessly to my home connection (WPA).
  
  In kern.log I see messages like this (redacted the mac-address):
  May 28 10:30:09 Xubuntu-18-04 kernel: [  157.858664] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:31:56 Xubuntu-18-04 kernel: [  265.191355] wlp2s0: deauthenticating 
from 00:**:**:**:**:** by local choice (Reason: 3=DEAUTH_
  LEAVING)
  May 28 10:32:55 Xubuntu-18-04 kernel: [  324.049168] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
- May 28 10:32:57 Xubuntu-18-04 kernel: [  326.168600] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
+ May 28 10:32:57 Xubuntu-18-04 kernel: [  326.168600] wlp2s0: deauthenticated 
from 00:**:**:**:**:** (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
- May 28 10:32:59 Xubuntu-18-04 kernel: [  327.696740] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
+ May 28 10:32:59 Xubuntu-18-04 kernel: [  327.696740] wlp2s0: deauthenticated 
from 00:**:**:**:**:** (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
- May 28 10:33:00 Xubuntu-18-04 kernel: [  329.056596] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
+ May 28 10:33:00 Xubuntu-18-04 kernel: [  329.056596] wlp2s0: deauthenticated 
from 00:**:**:**:**:** (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
- May 28 10:33:01 Xubuntu-18-04 kernel: [  330.449235] wlp2s0: disassociated 
from 00:08:2f:ef:66:51 (Reason: 1=UNSPECIFIED)
+ May 28 10:33:01 Xubuntu-18-04 kernel: [  330.449235] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:33:03 Xubuntu-18-04 kernel: [  332.448884] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
- May 28 10:33:05 Xubuntu-18-04 kernel: [  334.249308] wlp2s0: disassociated 
from 00:08:2f:ef:66:51 (Reason: 1=UNSPECIFIED)
+ May 28 10:33:05 Xubuntu-18-04 kernel: [  334.249308] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:33:07 Xubuntu-18-04 kernel: [  336.418400] wlp2s0: deauthenticated 
from 00:**:**:**:**:** (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  I have been using 18.04 without problems (and 16.04 before that) until 
recently; so it seems the problem is recent.
  
  If there is any more information I can provide please let me know.
  
  Edit: I came across a thread which seems to describe the same problem;
  and people there have tried analyzing the problem. I don't understand
  what people are saying there, so it may not be helpful, still:
  https://bbs.archlinux.org/viewtopic.php?id=230963
  
  Edit 2: I'm also seeing this in 18.10 (the daily of which I am testing).

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

Title:
  wifi connection to an protected EAP, MSCHAPv2 connection drops
  constantly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi all,

  My wifi connection disconnects constantly when I am connected to an
  eduroam/govroam access point (protected EAP, MSCHAPv2).

  The wifi driver is: rtl8812au-dkms.

  Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16
  12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE
  802.11ac PCIe Wireless Network Adapter

  Symptoms: the (eduroam) wifi-network is found, the wifi connection is
  set up, it works for a bit and then the connection is dropped.

  If I use my Android phone (which connects fine to the eduroam
  connection), to tether my laptop, the connection is fine.

  Also my laptop connects flawlessly to my home connection (WPA).

  In kern.log I see messages like this (redacted the mac-address):
  May 28 10:30:09 Xubuntu-18-04 kernel: [  157.858664] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:31:56 Xubuntu-18-04 kernel: [  265.191355] wlp2s0: deauthenticating 
from 00:**:**:**:**:** by local choice (Reason: 3=DEAUTH_
  LEAVING)
  May 28 10:32:55 Xubuntu-18-04 kernel: [  324.049168] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:32:57 

[Touch-packages] [Bug 1773849] [NEW] wifi connection to an protected EAP, MSCHAPv2 connection drops constantly

[Willem Hobers]

Public bug reported:

Hi all,

My wifi connection disconnects constantly when I am connected to an
eduroam/govroam access point (protected EAP, MSCHAPv2).

The wifi driver is: rtl8812au-dkms.

Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE
802.11ac PCIe Wireless Network Adapter

Symptoms: the (eduroam) wifi-network is found, the wifi connection is
set up, it works for a bit and then the connection is dropped.

If I use my Android phone (which connects fine to the eduroam
connection), to tether my laptop, the connection is fine.

Also my laptop connects flawlessly to my home connection (WPA).

In kern.log I see messages like this (redacted the mac-address):
May 28 10:30:09 Xubuntu-18-04 kernel: [  157.858664] wlp2s0: disassociated from 
00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
May 28 10:31:56 Xubuntu-18-04 kernel: [  265.191355] wlp2s0: deauthenticating 
from 00:**:**:**:**:** by local choice (Reason: 3=DEAUTH_
LEAVING)
May 28 10:32:55 Xubuntu-18-04 kernel: [  324.049168] wlp2s0: disassociated from 
00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
May 28 10:32:57 Xubuntu-18-04 kernel: [  326.168600] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
OC_STA)
May 28 10:32:59 Xubuntu-18-04 kernel: [  327.696740] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
OC_STA)
May 28 10:33:00 Xubuntu-18-04 kernel: [  329.056596] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
OC_STA)
May 28 10:33:01 Xubuntu-18-04 kernel: [  330.449235] wlp2s0: disassociated from 
00:08:2f:ef:66:51 (Reason: 1=UNSPECIFIED)
May 28 10:33:03 Xubuntu-18-04 kernel: [  332.448884] wlp2s0: disassociated from 
00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
May 28 10:33:05 Xubuntu-18-04 kernel: [  334.249308] wlp2s0: disassociated from 
00:08:2f:ef:66:51 (Reason: 1=UNSPECIFIED)
May 28 10:33:07 Xubuntu-18-04 kernel: [  336.418400] wlp2s0: deauthenticated 
from 00:**:**:**:**:** (Reason: 7=CLASS3_FRAME_FROM_NONASS
OC_STA)
I have been using 18.04 without problems (and 16.04 before that) until 
recently; so it seems the problem is recent.

If there is any more information I can provide please let me know.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  wifi connection to an protected EAP, MSCHAPv2 connection drops
  constantly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi all,

  My wifi connection disconnects constantly when I am connected to an
  eduroam/govroam access point (protected EAP, MSCHAPv2).

  The wifi driver is: rtl8812au-dkms.

  Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16
  12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE
  802.11ac PCIe Wireless Network Adapter

  Symptoms: the (eduroam) wifi-network is found, the wifi connection is
  set up, it works for a bit and then the connection is dropped.

  If I use my Android phone (which connects fine to the eduroam
  connection), to tether my laptop, the connection is fine.

  Also my laptop connects flawlessly to my home connection (WPA).

  In kern.log I see messages like this (redacted the mac-address):
  May 28 10:30:09 Xubuntu-18-04 kernel: [  157.858664] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:31:56 Xubuntu-18-04 kernel: [  265.191355] wlp2s0: deauthenticating 
from 00:**:**:**:**:** by local choice (Reason: 3=DEAUTH_
  LEAVING)
  May 28 10:32:55 Xubuntu-18-04 kernel: [  324.049168] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:32:57 Xubuntu-18-04 kernel: [  326.168600] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:32:59 Xubuntu-18-04 kernel: [  327.696740] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:33:00 Xubuntu-18-04 kernel: [  329.056596] wlp2s0: deauthenticated 
from 00:08:2f:ef:66:51 (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  May 28 10:33:01 Xubuntu-18-04 kernel: [  330.449235] wlp2s0: disassociated 
from 00:08:2f:ef:66:51 (Reason: 1=UNSPECIFIED)
  May 28 10:33:03 Xubuntu-18-04 kernel: [  332.448884] wlp2s0: disassociated 
from 00:**:**:**:**:** (Reason: 1=UNSPECIFIED)
  May 28 10:33:05 Xubuntu-18-04 kernel: [  334.249308] wlp2s0: disassociated 
from 00:08:2f:ef:66:51 (Reason: 1=UNSPECIFIED)
  May 28 10:33:07 Xubuntu-18-04 kernel: [  336.418400] wlp2s0: deauthenticated 
from 00:**:**:**:**:** (Reason: 7=CLASS3_FRAME_FROM_NONASS
  OC_STA)
  I have been using 18.04 without problems (and 16.04 before 

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Christopher M. Penalver]

Krishnan Sreenivas:

Regarding using PPAs, PPAs are not supported in Ubuntu. Hence, if a PPA
is used, and it brakes the system, it is out of scope for a bug report.

In regard to the scope of this report, given the history of what changed
and how wasn't documented and provided, you kept making large,
unsupported, and undocumented changes after the break that appeared to
cause additional breakage, there isn't anything this report can be
scoped to. Hence, it is being closed.

Thank you again for taking the time to report this and helping to make
Ubuntu better. Please submit any future bugs you may find.

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

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~touch-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]

In the meantime I ran the test from the bug description.

Before the update:
ubuntu@xenial-slaps-segfault-1688575:~/test$  export LDAPSASL_SECPROPS=none
ubuntu@xenial-slaps-segfault-1688575:~/test$ ./sasltest 
rc = -6 (Unknown authentication method)
sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
rc = -6 (Unknown authentication method)
rc = -6 (Unknown authentication method)
sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
Aborted (core dumped)


After the update:
ubuntu@xenial-slaps-segfault-1688575:~/test$ apt-cache policy libldap-2.4-2
libldap-2.4-2:
  Installed: 2.4.42+dfsg-2ubuntu3.3
  Candidate: 2.4.42+dfsg-2ubuntu3.3
  Version table:
 *** 2.4.42+dfsg-2ubuntu3.3 500
500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 2.4.42+dfsg-2ubuntu3.2 500
500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://br.archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 2.4.42+dfsg-2ubuntu3 500
500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

ubuntu@xenial-slaps-segfault-1688575:~/test$ echo $LDAPSASL_SECPROPS
none
ubuntu@xenial-slaps-segfault-1688575:~/test$ ./sasltest 
ubuntu@xenial-slaps-segfault-1688575:~/test$ echo $?
0

@kunalija, once your test is done, and if the new packages worked,
please replace the "verification-needed-xenial" tag with "verification-
done-xenial", following instructions from comment #28. 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
Status in openldap source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Concurrent SASL authentications could trigger a segfault. This was observed 
by the bug reporter during replication from a master to a slave, and can be 
reproduced with a test program.

  The fix is applied upstream, see comment #13.

  [Test Case]
  * Create a fresh xenial VM or container and login. Update the apt 
repositories:
  sudo apt update

  * Create a local directory and cd into it:
  mkdir test && cd test

  * Download the test attachments from this bug: Makefile, sasltest.c and 
testscript:
  wget 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript

  * Build with
$ apt install libsasl2-dev libldap2-dev
$ make

  * Execute the testscript with sudo once. It shall fail at the very end with a 
core dump:
  sudo sh ./testscript
  (...)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Export this var:
  export LDAPSASL_SECPROPS=none

  * Run the actual test script a few more times to confirm the crasH:
  $ ./sasltest
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Install the updated packages from proposed

  * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported:
  $ echo $LDAPSASL_SECPROPS
  none

  $ ./sasltest
  $

  This time the test completes without crashing.

  [Regression Potential]
  This is SASL authentication, and with kerberos nonetheless (in the case of 
the bug reporter). I suspect not many people deploy this due to its complexity. 
The ones that have such a setup, however, tend to know what they are doing, so 
if they say the problem is fixed for them, I believe it is.

  About this particular change, it's committed upstream and also in
  debian, and @rtandy was kind enough to provide a sample test script
  that exhibits the problem.

  [Other Info]
  Since the fix is applied upstream and in Debian, there shouldn't be 
additional surprises here.

  [Original 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 

[Touch-packages] [Bug 1773844] [NEW] [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all

[Fernando André]

Public bug reported:

This issue happens on xubuntu 17.10 and also ubuntu.
It may be related to this bug 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/802998
802998 , but since I'm using a new version I reported it again.

1)
lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

2)
apt-cache policy alsa-base
alsa-base:
  Instalado: 1.0.25+dfsg-0ubuntu5
  Candidato: 1.0.25+dfsg-0ubuntu5
  Tabela de versão:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://br.archive.ubuntu.com/ubuntu artful/main i386 Packages
100 /var/lib/dpkg/status

5)
uname -a
Linux patricia-NH4CU03 4.16.12 #1 SMP Sun May 27 16:56:57 -03 2018 x86_64 
x86_64 x86_64 GNU/Linux
Also happens on normal kernel version of 17.10 xubuntu and ubuntu
3)
I would expect it to play sound.

4)
It doesn't play any sound.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.16.12 x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andref 1587 F pulseaudio
CurrentDesktop: XFCE
Date: Mon May 28 16:05:23 2018
InstallationDate: Installed on 2018-01-25 (123 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Áudio interno - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andref 1587 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/16/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.00W
dmi.board.name: NH4CU03
dmi.board.vendor: Digiboard
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: Digibras
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00W:bd04/16/2013:svnDigibras:pnNH4CU03:pvr1.0:rvnDigiboard:rnNH4CU03:rvr1.0:cvnDigibras:ct10:cvr1.0:
dmi.product.name: NH4CU03
dmi.product.version: 1.0
dmi.sys.vendor: Digibras
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-26T21:36:27.395468

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1773844

Title:
  [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This issue happens on xubuntu 17.10 and also ubuntu.
  It may be related to this bug 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/802998
  802998 , but since I'm using a new version I reported it again.

  1)
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2)
  apt-cache policy alsa-base
  alsa-base:
Instalado: 1.0.25+dfsg-0ubuntu5
Candidato: 1.0.25+dfsg-0ubuntu5
Tabela de versão:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://br.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  5)
  uname -a
  Linux patricia-NH4CU03 4.16.12 #1 SMP Sun May 27 16:56:57 -03 2018 x86_64 
x86_64 x86_64 GNU/Linux
  Also happens on normal kernel version of 17.10 xubuntu and ubuntu
  3)
  I would expect it to play sound.

  4)
  It doesn't play any sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.16.12 x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andref 1587 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May 28 16:05:23 2018
  InstallationDate: Installed on 2018-01-25 (123 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andref 1587 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [NH4CU03, Realtek ALC269VB, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Touch-packages] [Bug 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions

[Cristian Aravena Romero]

** Attachment added: "$sudo dpkg -l"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1770725/+attachment/5145634/+files/dpkg_-l.txt

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

Title:
  [i915 SNB] You can not see the image of the movie in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions

[Cristian Aravena Romero]

Hello Daniel,

With mpv it works well

Regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  [i915 SNB] You can not see the image of the movie in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Jeff Carr]

I vote for changing it from "Low" to "Insanely broken and wrong".

Even the workaround to set DNS in resolved.conf is still wrong. There is
a reason that every dhcp server on earth is configured to provide a DNS
server for a reason.

Jeff Carr
CEO WIT.COM Inc.
Formerly co-founder Digital Ocean

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Krishnan Sreenivas]

Complete reinstall after disk format without dual boot works fine

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

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] No sound at all after kernel upgrade

[DSHR]

Currently this quirk seems to make things worse - at least for me with
the current firmware release on the headphones.

** Attachment added: "Relevant entry from sound/usb/quirks-table.h"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1773697/+attachment/5145652/+files/bw-px-quirk-table-entry.h

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions

[Cristian Aravena Romero]

** Attachment added: "Description of the movie"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1770725/+attachment/5145633/+files/Captura%20de%20pantalla%20de%202018-05-28%2013-35-01.png

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

Title:
  [i915 SNB] You can not see the image of the movie in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1773516] Re: [Lenovo Yoga 300-11IBY] Right click not working

[Phill]

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

Although the buttons are integral to the touchpad, they are clearly
marked with a dividing line. Having read the proposed duplicate, while
this issue may have the same underlying cause, this is not a mere
configuration preference on this device because it has clearly
identified buttons, albeit with nothing more than a coloured dividing
line.

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

Title:
  [Lenovo Yoga 300-11IBY] Right click not working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The right click is not working on Lenovo Yoga touch pad after upgrade
  to 18.04, worked minutes before on 17.10.

  I think it works on the Think Pad out-of-the-box (after upgrade from
  17.10), if that helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  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: Sat May 26 10:34:57 2018
  DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
  InstallationDate: Installed on 2018-01-18 (128 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 80M0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J33995WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 300-11IBY
  dmi.modalias: 
dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M0
  dmi.product.version: Lenovo YOGA 300-11IBY
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade

[DSHR]

** Summary changed:

- [USB-Audio - PX USB, playback] No sound at all after kernel upgrade
+ [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with 
error -22 after kernel upgrade

** Description changed:

  Bug report has been generated on a partially working configuration. That
  allows ubuntu-bug to do more work.
  
  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started
  working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly
  stopped working again on newer kernels. The bug report has been
  generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
- sample rates to 48 kHz. The quirk seems not to be working correctly - it
- seems to hinder the audio system to recognize the USB-device as a sound
- device.
+ sample rates to 48 kHz. The quirk seems not to be working correctly and
+ hinder the audio system to recognize the USB-device as a sound device.
  
  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.
  
  PX Headphones are on the newest firmware level.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  dshr   2729 F pulseaudio
-  /dev/snd/controlC1:  dshr   2729 F pulseaudio
-  /dev/snd/controlC0:  dshr   2729 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  dshr   2729 F pulseaudio
+  /dev/snd/controlC1:  dshr   2729 F pulseaudio
+  /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/zsh
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  dshr   2729 F pulseaudio
-  /dev/snd/controlC1:  dshr   2729 F pulseaudio
-  /dev/snd/controlC0:  dshr   2729 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  dshr   2729 F pulseaudio
+  /dev/snd/controlC1:  dshr   2729 F pulseaudio
+  /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio 

[Touch-packages] [Bug 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions

[Cristian Aravena Romero]

** Attachment added: "totem"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1770725/+attachment/5145653/+files/Captura%20de%20pantalla%20de%202018-05-28%2013-43-34.png

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

Title:
  [i915 SNB] You can not see the image of the movie in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1770725] Re: [i915 SNB] You can not see the image of the movie in Wayland sessions

[Cristian Aravena Romero]

** Attachment added: "$sudo vainfo"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1770725/+attachment/5145632/+files/vainfo.txt

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

Title:
  [i915 SNB] You can not see the image of the movie in Wayland sessions

Status in Gstreamer1.0:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  You can not see the image of the movie.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.0-1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.10-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri May 11 15:35:17 2018
  InstallationDate: Installed on 2017-10-13 (210 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions

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

[Touch-packages] [Bug 1773687] Re: [bionic] no unattended installation

[Dirk Eddelbuettel]

Update:

A friend just pointed out that setting `export DEBIAN_FRONTEND=noninteractive` 
helps,
and I verified that in Docker. So _maybe_ we just dropped that setting?

edd@rob:~$ docker run --rm -ti ubuntu:bionic
root@cf1720b38f97:/# apt-get update 
Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] 
 
Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
 
Get:3 http://security.ubuntu.com/ubuntu bionic-security/universe Sources [3783 
B]
Get:4 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 
[18.8 kB]
Get:5 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 
Packages [1066 B]   
Get:6 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 
[88.7 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [83.2 kB]   
 
Get:8 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [65.5 kB] 
 
Get:9 http://archive.ubuntu.com/ubuntu bionic/universe Sources [11.5 MB]
 
Get:10 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 
kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 
MB] 
Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1344 kB]
 
Get:13 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [13.5 
kB]   
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [28.7 
kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 
Packages [1660 B]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 
[79.3 kB] 
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [127 
kB]  
Fetched 25.2 MB in 4s (5655 kB/s)   
 
Reading package lists... Done   
root@cf1720b38f97:/# export DEBIAN_FRONTEND=noninteractive  
 
root@cf1720b38f97:/# apt-get install -y tzdata  
Reading package lists... Done   
Building dependency tree
Reading state information... Done   
The following NEW packages will be installed:   
  tzdata
0 upgraded, 1 newly installed, 0 to remove and 11 not upgraded. 
 
Need to get 188 kB of archives. 
After this operation, 3088 kB of additional disk space will be used.
 
Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 tzdata all 2018d-1 
[188 kB] 
Fetched 188 kB in 1s (271 kB/s) 
debconf: delaying package configuration, since apt-utils is not installed   
 
Selecting previously unselected package tzdata. 
(Reading database ... 4035 files and directories currently installed.)  
 
Preparing to unpack .../tzdata_2018d-1_all.deb ...  
Unpacking tzdata (2018d-1) ...  
Setting up tzdata (2018d-1) ... 

Current default time zone: 'Etc/UTC'
Local time is now:  Mon May 28 17:10:20 UTC 2018.   
 
Universal Time is now:  Mon May 28 17:10:20 UTC 2018.   
 
Run 'dpkg-reconfigure tzdata' if you wish to change it. 
 

root@cf1720b38f97:/#

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

Title:
  [bionic] no unattended installation

Status in tzdata package in Ubuntu:
  New

Bug description:
  Package: tzdata
  Version: 2018d-1
  Ubuntu release: 18.04

  There appears to be a regression with the preseeding data for tzdata in the 
18.04 release.
  When running 

 apt-get install tzdata

  I now _always_ drop into an interactive selection of the timezone
  'area' and 'zone'. This was not the case before; it is also not the
  case in Debian 'unstable' right now.

  I looked into the postinst script, but I can't figure out where the
  preseeded info would be. I tried debconf-set-selections with a preseed
  file, but no luck.

  This blocks usage of tzdata in Docker containers and is there for a
  bit annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: tzdata 2017c-0ubuntu0.17.10
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

[David Coronel]

I confirm the "toram" workaround from Woodrow allows me to PXE netboot
the most recent Ubuntu 18.04 Desktop amd64 ISO image.

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[JR]

I tried it with mainline 4.16.12 and 4.17-rc7 on the Dell Latitude and
the problem still exists.

-- 
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 The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
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 1773484] Re: Login screen not moved to used monitor

[Manfred Steiner]

"Beamer" is another display device connected to VGA connector.

The behavior on Ubuntu 16.04 was perfect.
a) the system menu was visible on each screen
b) the login dialog follows the mouse
c) configurations were automatically detected (i guess depending on device 
ids). and former configurations restored.
d) if no configuration available screens were automatically mirrored (not sure 
if I remember correct)

That behavior is also desired for Ubuntu 18.04

The current behavior:

.. Connected ... Internal LCD ... VGA...GOOD?
-
First time ... Monitor on VGA .. L+S  E ... No  -> 
1)
After Login .. Monitor on VGA .. S .. E ... No  -> 
2)
After reconfiguration  Monitor on VGA .. Off  S ... Yes
After Restart  Monitor on VGA .. L+S  E ... No  -> 
1)
After Login .. Monitor on VGA .. Off  S ... Yes -> 
3)

-> 1) Login Dialog not following mouse. Without internal LCD no login possible.
-> 2) Screen on VGA monitor is empty
-> 3) After Login former monitor configuration automatically detected and 
restored.

As soon as I can connect another VGA monitor I will describe the
behavior again (at the moment not available).

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
  the monitor where the mouse pointer is located. On Ubuntu 18.04 login
  dialog and system menues are restricted to the main monitor.

  So if you have a notebook with defect lcd display you can work with it
  using Ubuntu 16.04 and an external monitor, but you cannot work with
  Ubuntu 18.04, because you are not able to login!

  This problem was also asked on:
  
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

[Suho Meso]

Hello Brian,

I've updated 2 servers with the new package. Let me test few days, and
I'll get back to you with the results.

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
Status in openldap source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Concurrent SASL authentications could trigger a segfault. This was observed 
by the bug reporter during replication from a master to a slave, and can be 
reproduced with a test program.

  The fix is applied upstream, see comment #13.

  [Test Case]
  * Create a fresh xenial VM or container and login. Update the apt 
repositories:
  sudo apt update

  * Create a local directory and cd into it:
  mkdir test && cd test

  * Download the test attachments from this bug: Makefile, sasltest.c and 
testscript:
  wget 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript

  * Build with
$ apt install libsasl2-dev libldap2-dev
$ make

  * Execute the testscript with sudo once. It shall fail at the very end with a 
core dump:
  sudo sh ./testscript
  (...)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Export this var:
  export LDAPSASL_SECPROPS=none

  * Run the actual test script a few more times to confirm the crasH:
  $ ./sasltest
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Install the updated packages from proposed

  * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported:
  $ echo $LDAPSASL_SECPROPS
  none

  $ ./sasltest
  $

  This time the test completes without crashing.

  [Regression Potential]
  This is SASL authentication, and with kerberos nonetheless (in the case of 
the bug reporter). I suspect not many people deploy this due to its complexity. 
The ones that have such a setup, however, tend to know what they are doing, so 
if they say the problem is fixed for them, I believe it is.

  About this particular change, it's committed upstream and also in
  debian, and @rtandy was kind enough to provide a sample test script
  that exhibits the problem.

  [Other Info]
  Since the fix is applied upstream and in Debian, there shouldn't be 
additional surprises here.

  [Original 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 

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Krishnan Sreenivas]

My UEFI has two entries of Ubuntu. Both boot into the same errors. Upon
running the sudo apt-get install intel-microcode i get the login screen
but the login screen loops. I tried Xauthority edit and that did not
work. I will try formatting my entire hard disk and check for the error

** Attachment added: "IMG_20180528_143949594_HDR[1].jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5145566/+files/IMG_20180528_143949594_HDR%5B1%5D.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/1773235

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1773235] Re: [ASUS R554LA] I get booted into recovery mode every third boot or from sleep when on battery

[Krishnan Sreenivas]

I am sorry for the incorrect information, I meant to say that upon installing 
ubuntu over ubuntu budgie by wiping the partition, The ubuntu 18.04 did not 
detect my windows 10. 
bcdedit/enum gave this

Windows Boot Manager

identifier  {bootmgr}
device  partition=\Device\HarddiskVolume1
path\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale  en-US
inherit {globalsettings}
default {current}
resumeobject{7fca1564-23ab-11e6-9bda-2c56dc800fdf}
displayorder{current}
toolsdisplayorder   {memdiag}
timeout 0

Windows Boot Loader
---
identifier  {current}
device  partition=C:
path\WINDOWS\system32\winload.efi
description Windows 10
locale  en-US
inherit {bootloadersettings}
recoverysequence{6daa28e6-cc99-11e7-9be1-ebc6dd63c46c}
displaymessageoverride  Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x1575
osdevicepartition=C:
systemroot  \WINDOWS
resumeobject{7fca1564-23ab-11e6-9bda-2c56dc800fdf}
nx  OptIn
bootmenupolicy  Standard

2) Fast start up is dissabled and so is secure boot
3) I did this.
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair

4) currently i got an error as
[0.00] [Firmware Bug]: TSC_Deadline disabled due to errata: please update 
microcode to version 0x25 (or later)
[0.032537] error parsing PCC subspaces from PCCT
[0.830839] Couldn`t get size: 0x8e
[0.830859] MODSIGN: Couldn`t get UEFI db list
[1.305933] usb 1-4: string descriptor 0 read error: -22

5) I got the attached error while running sudo apt-get install intel-
microcode for the first time and the program error stopped after the
code was executed after a reboot

** Attachment added: "IMG_20180528_140001_DRO.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773235/+attachment/5145565/+files/IMG_20180528_140001_DRO.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/1773235

Title:
  [ASUS R554LA] I get booted into recovery mode every third boot or from
  sleep when on battery

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubutnu version 18.04, Plymouth version 0.9.3-1ubuntu7

  The splash screen comes up and then the system boots into recovery
  mode every 3-7 boots/boot from sleep when on battery [battery at 30%
  minimum and healthy], login screen is disabled as the login screen
  does not come up if an external monitor is not connected (System
  autologs in).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 24 20:34:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-05-05 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6223fa3c-4cdd-4c83-a634-5b5182e7f476 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.504:bd08/28/2015:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  

[Touch-packages] [Bug 1769920] Re: [SRU] Enable support for Rocky Cloud Archive

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.32.3

---
software-properties (0.96.24.32.3) bionic; urgency=medium

  * cloudarchive: Enable support for the Rocky Ubuntu Cloud Archive on
18.04 (LP: #1769920).

 -- Corey Bryant   Tue, 08 May 2018 10:58:48
-0400

** Changed in: software-properties (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Enable support for Rocky Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Released
Status in software-properties source package in Cosmic:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:rocky
 cloud-archive:rocky-proposed

  This will also need to be SRU'ed back to bionic.

  [Impact]
  End users have to manually enable the rocky cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:rocky
  sudo add-apt-repository cloud-archive:rocky-proposed

  [Regression potential]
  Limited - just a data item addition

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

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

[Touch-packages] [Bug 1769920] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for software-properties
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Enable support for Rocky Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Released
Status in software-properties source package in Cosmic:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:rocky
 cloud-archive:rocky-proposed

  This will also need to be SRU'ed back to bionic.

  [Impact]
  End users have to manually enable the rocky cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:rocky
  sudo add-apt-repository cloud-archive:rocky-proposed

  [Regression potential]
  Limited - just a data item addition

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

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

[Touch-packages] [Bug 1739948] Re: Missing French-Belgian keyboard layout

[Loic TRUCHOT]

In order to find French(Belgian) keyboard in the first list, you have to  
install "french" first, as a supported language (bottom button "Managed 
Installed Languages").
Then you will see every french options like "French(Canada)", 
"French(Belgium)", etc in the main list of inputs.

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

Title:
  Missing French-Belgian keyboard layout

Status in ibus package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 17.10
  Release:  17.10

  ibus:
Installed: 1.5.14-2ubuntu1
Candidate: 1.5.14-2ubuntu1
Version table:
   *** 1.5.14-2ubuntu1 500
  500 http://be.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  After my update on 17.10 I couldn't get a french Belgian keyboard in the 
input sources.
  During install time I have tried to find my keyboard layout by using the 
"Type this key process" without success.
  I have also tried all the French keyboard but none of them allow me to type 
"@" or "-"... sut to mention main missing keys.

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

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

[Touch-packages] [Bug 1773803] [NEW] Memory leak in cv::VideoCapture

[Jacopo Carravieri]

Public bug reported:

I am developing a custom C++ programs which continuously processes a
huge number of short videos, so several instances of cv::VideoCapture
are endlessly created and destroyed. I noticed that the memory
consumption keeps growing, until after some days the process gets killed
by the operating system.

After careful testing I tracked down the memory leak in
cv::VideoCapture. Commenting only this object, leaving the rest of the
program untouched, with the exception of those parts where this object
is used, which are changed so that the job done is as close as possible
(ex. using a zero-initialized cv::Mat object instead of a video frame)
leads to no memory leak after hours of execution.

This is portion of code where the error occurs:

void procressVideo(boost::filesystem::path name) {
VideoCapture video(name.string());
if(!video.isOpened()) {
return;
}
size_t width = video.get(CV_CAP_PROP_FRAME_WIDTH);
size_t height = video.get(CV_CAP_PROP_FRAME_HEIGHT);
// Process frames
Mat prev(height, width, CV_8UC3, Scalar(0));
Mat frame;
for(long i = 0; video.read(frame); i++)
{
cvtColor(frame, frame, CV_BGR2RGB);
frame.convertTo(frame, CV_8UC3);
...
...
frame.copyTo(prev);
}
video.release();
boost::filesystem::remove(name);
}

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libopencv-videoio3.2 3.2.0+dfsg-4build2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon May 28 15:02:47 2018
InstallationDate: Installed on 2018-05-24 (3 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: opencv
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Memory leak in cv::VideoCapture

Status in opencv package in Ubuntu:
  New

Bug description:
  I am developing a custom C++ programs which continuously processes a
  huge number of short videos, so several instances of cv::VideoCapture
  are endlessly created and destroyed. I noticed that the memory
  consumption keeps growing, until after some days the process gets
  killed by the operating system.

  After careful testing I tracked down the memory leak in
  cv::VideoCapture. Commenting only this object, leaving the rest of the
  program untouched, with the exception of those parts where this object
  is used, which are changed so that the job done is as close as
  possible (ex. using a zero-initialized cv::Mat object instead of a
  video frame) leads to no memory leak after hours of execution.

  This is portion of code where the error occurs:

  void procressVideo(boost::filesystem::path name) {
  VideoCapture video(name.string());
  if(!video.isOpened()) {
  return;
  }
  size_t width = video.get(CV_CAP_PROP_FRAME_WIDTH);
  size_t height = video.get(CV_CAP_PROP_FRAME_HEIGHT);
  // Process frames
  Mat prev(height, width, CV_8UC3, Scalar(0));
  Mat frame;
  for(long i = 0; video.read(frame); i++)
  {
  cvtColor(frame, frame, CV_BGR2RGB);
  frame.convertTo(frame, CV_8UC3);
  ...
  ...
  frame.copyTo(prev);
  }
  video.release();
  boost::filesystem::remove(name);
  }

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libopencv-videoio3.2 3.2.0+dfsg-4build2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 28 15:02:47 2018
  InstallationDate: Installed on 2018-05-24 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: opencv
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1766974] Re: /dev/dri/card0

[VinsS]

I confirm this bug.

I join the Apport log.


** Attachment added: "_usr_lib_xorg_Xorg.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1766974/+attachment/5145498/+files/_usr_lib_xorg_Xorg.0.crash

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

Title:
  /dev/dri/card0

Status in xorg package in Ubuntu:
  New

Bug description:
  There are very many bugs reported recently against xorg with a commmon
  theme

  the following are just 2 examples from the various xorg logs

  (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission 
denied
  (EE) intel(0): [drm] failed to set drm interface version: Permission denied 
[13].

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

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

[Touch-packages] [Bug 1773744] Re: Desktop session crash

[Sami Pietila]

I can see error messages like this in the log: "CRITICAL: We failed, but
the fail whale is dead. Sorry"

touko 28 10:05:38 elite gsd-clipboard[5250]: gsd-clipboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :0.
touko 28 10:05:38 elite gsd-xsettings[5224]: gsd-xsettings: Fatal IO error 11 
(Resource temporarily unavailable) on X server :0.
touko 28 10:05:38 elite unknown[5232]: gsd-wacom: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1
touko 28 10:05:38 elite unknown[5210]: gsd-power: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
touko 28 10:05:38 elite gsd-color[5245]: gsd-color: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
touko 28 10:05:38 elite gnome-shell[5099]: gnome-shell: Fatal IO error 0 
(Success) on X server :0.
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
touko 28 10:05:38 elite polkitd(authority=local)[1476]: Unregistered 
Authentication Agent for unix-session:5 (system bus name :1.247, object path 
/org/freedesktop/PolicyKit1/AuthenticationAge
touko 28 10:05:38 elite gsd-color[2275]: failed to connect to device: Failed to 
connect to missing device 
/org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2515H_9X2VY5CG12LL_sami_
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1
touko 28 10:05:38 elite gnome-control-c[5869]: gnome-control-center: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
touko 28 10:05:38 elite gnome-session-binary[4955]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
touko 28 10:05:38 elite gnome-session[4955]: gnome-session-binary[4955]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
touko 28 10:05:38 elite gnome-session-binary[4955]: CRITICAL: We failed, but 
the fail whale is dead. Sorry
touko 28 10:05:38 elite kernel: rfkill: input handler enabled
touko 28 10:05:38 elite at-spi-bus-launcher[5057]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
touko 28 10:05:38 elite at-spi-bus-launcher[5057]:   after 69 requests (69 
known processed) with 0 events remaining.
touko 28 10:05:38 elite gdm-password][4897]: pam_unix(gdm-password:session): 
session closed for user sami
touko 28 10:05:38 elite gnome-shell[2080]: Object St.Icon (0x55f7781d71a0), has 
been already finalized. Impossible to set any property to it.
touko 28 10:05:38 elite gnome-shell[2080]: Object St.BoxLayout 
(0x55f7781d5c10), has been already finalized. Impossible to set any property to 
it.
touko 28 10:05:38 elite org.gnome.Shell.desktop[2080]: == Stack trace for 
context 0x55f7776c9320 ==
touko 28 10:05:38 elite org.gnome.Shell.desktop[2080]: #0 0x55f777a77fe0 i   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7feaa42c96f8 @ 231)
touko 28 10:05:38 elite org.gnome.Shell.desktop[2080]: #1 0x7ffd8bc93230 b   

[Touch-packages] [Bug 1557704] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()

[Launchpad Bug Tracker]

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

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

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

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

Title:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  crashed on login

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: udev 229-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar 15 14:56:09 2016
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2016-02-23 (20 days ago)
  InstallationMedia:
   
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=69b2a3c4-09ad-4737-8a48-67b5f2362690 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __open_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61MA-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61MA-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[Brian Candler]

> no matter if we succeed/fail there one can at least later remove open-
iscsid if he wants without taking out the ubuntu-server meta.

That's perfect - thank you!

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[ Christian Ehrhardt ]

So for this bug we need:
1. make it a recommends
2. ubuntu-meta update for cosmic

For #1 I opened [1] and #2 can only follow after that is merged.

And this can be done independent to bug 1755858 - so no matter if we
succeed/fail there one can at least later remove open-iscsid if he wants
without taking out the ubuntu-server meta.

[1]: https://code.launchpad.net/~paelzer/ubuntu-
seeds/+git/ubuntu/+merge/346948

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/ubuntu/+merge/346948

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1763584] Re: ureadahead service fails with error Error while tracing: No such file or directory

[demon]

My system is being affected as well, I'm running Ubuntu 16.04.4 having
the same service failing to start.

There are a few reports of this on stackexchange as well with one
particular solution about patching the kernel:

https://unix.stackexchange.com/questions/308801/ureadahead-error-while-
tracing-possible-kernel-patch-problem.

I've also filed a bug with kernel.org :
https://bugzilla.kernel.org/show_bug.cgi?id=199861


Running ureadahead with strace directly from terminal yields:


# strace ureadahead --verbose --force-trace /

[..]
openat(3, "events/fs/do_sys_open/enable", O_RDWR) = -1 ENOENT (No such file or 
directory)
close(3)= 0
write(2, "ureadahead: Error while tracing:"..., 59ureadahead: Error while 
tracing: No such file or directory
[..]


and "/sys/kernel/debug/tracing/events/fs/do_sys_open/enable" does not exist.


** Bug watch added: Linux Kernel Bug Tracker #199861
   https://bugzilla.kernel.org/show_bug.cgi?id=199861

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

Title:
  ureadahead service fails with error Error while tracing: No such file
  or directory

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  I'm reporting this as duplicate of #1176536 to provide more info.

  dmig@dmig-Inspiron-5379:~$ systemctl status ureadahead.service 
  ● ureadahead.service - Read required files in advance
 Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Fri 2018-04-13 13:09:41 +07; 
10min ago
   Main PID: 379 (code=exited, status=5)

  Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: ureadahead: Error while 
tracing: No such file or directory
  Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: Counted 8 CPUs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ureadahead 0.100.0-20
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 13 13:13:26 2018
  InstallationDate: Installed on 2018-03-27 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1763584] Re: ureadahead service fails with error Error while tracing: No such file or directory

[Launchpad Bug Tracker]

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

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

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

Title:
  ureadahead service fails with error Error while tracing: No such file
  or directory

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  I'm reporting this as duplicate of #1176536 to provide more info.

  dmig@dmig-Inspiron-5379:~$ systemctl status ureadahead.service 
  ● ureadahead.service - Read required files in advance
 Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Fri 2018-04-13 13:09:41 +07; 
10min ago
   Main PID: 379 (code=exited, status=5)

  Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: ureadahead: Error while 
tracing: No such file or directory
  Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: Counted 8 CPUs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ureadahead 0.100.0-20
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 13 13:13:26 2018
  InstallationDate: Installed on 2018-03-27 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773744] [NEW] Desktop session crash

[Sami Pietila]

Public bug reported:

If I connect third monitor to my Ubuntu PC, the whole graphical display
session crashes. Additionally, the login does not show texts correctly.
The texts are mostly missing.

The errors happend with both Wayland and X.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May 28 10:15:54 2018
DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X OEM] 
[103c:90b8]
InstallationDate: Installed on 2016-11-22 (551 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago)
dmi.bios.date: 09/09/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.18
dmi.board.asset.tag: CZC3427KBP
dmi.board.name: 18E4
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC3427KBP
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP EliteDesk 800 G1 TWR
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-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

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


** Tags: amd64 apport-bug bionic crash 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/1773744

Title:
  Desktop session crash

Status in xorg package in Ubuntu:
  New

Bug description:
  If I connect third monitor to my Ubuntu PC, the whole graphical
  display session crashes. Additionally, the login does not show texts
  correctly. The texts are mostly missing.

  The errors happend with both Wayland and X.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 28 10:15:54 2018
  DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [103c:90b8]
  InstallationDate: Installed on 2016-11-22 (551 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to 

[Touch-packages] [Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[ Christian Ehrhardt ]

@Scott, I agree and I'm already on a much better fix by bug 1755858
After this there is not much reason left to remove it anywhere (there is but 
not as much as now).

On top - going forward we can make is a recommends instead of a Depends
which help those that want to remove it later.

TL;DR:
- "why is this daemon running" will be addressed by 1755858
- I wan't to be able to remove open-iscsid is this bug
- no need to un-unify images for this anymore

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

[Timo Aaltonen]

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390
(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/1773637

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a: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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  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 1:1.0.15-2

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

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

[Touch-packages] [Bug 1762122] Re: drm_kms_helper.edid_firmware not working anymore on Ubuntu 18.04

[Timo Aaltonen]

it's called 'drm.edid_firmware' these days

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

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

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

Title:
  drm_kms_helper.edid_firmware not working anymore on Ubuntu 18.04

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I installed today Ubuntu 18.04. I have a secondary monitor (Acer
  AL1914), which does not provide a EDID, so I created one and usually
  loaded directly from the kernel at startup.

  The EDID is located here:
  /lib/firmware/edid/al1914.bin

  The kernel command line is this:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash 
drm_kms_helper.edid_firmware=VGA-1:edid/al1914.bin"

  On Ubuntu 16.04, this worked perfectly. Now, the additional mode from
  the edid is not present among the resolutions available (I have to
  create a new one and add it with cvt and xrandr once the system is
  loaded).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  8 08:27:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  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:c0d8]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-04-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/351V5C/3540VC/3440VC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=088e46ca-c64d-43c6-8c68-0f92cb2917b6 ro quiet splash 
drm_kms_helper.edid_firmware=VGA-1:edid/al1914.bin vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09ABE
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP350V5C-S08IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  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:bvnAmericanMegatrendsInc.:bvrP09ABE:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/351V5C/3540VC/3440VC:pvrP09ABE.012.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S08IT:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: Eureka
  dmi.product.name: 350V5C/351V5C/3540VC/3440VC
  dmi.product.version: P09ABE.012.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Pete]

Correction: I did not see the .1 in your version number.

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * More captive portals have been discovered that do not handle DNS requests 
with D0 set.
   * Thus extend previous aruba-networks fix from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all 
NXDOMAIN results with lower feature levels just in case.

  [Test Case]

   * systemd-resolved something-nonexistant.ubuntu.com
   * monitor the logs, and check that the transaction has been downgraded 
multiple times and tried at least once at a feature level below D0. There 
should be a downgrade message in the log.
   * Note, it will be cached, thus one may need to call $ systemd-resolved 
--flush-caches

  [Regression Potential]

   * Legitimate NXDOMAIN queries will now take longer, as they will be
  retried multiple times with different features sets until an answer is
  found. At that point the query will be cached and will return quickly.
  This is needed to work-around bad captive portals that do not support
  dns queries with D0. Post-captive portal, the feature level can
  usually be cranked back up and it does after a grace period.

  [Other Info]
   
   * Original bug report

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Pete]

@Tom: Than it's not the same issue. As this is the version the bug was
reported with.

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * More captive portals have been discovered that do not handle DNS requests 
with D0 set.
   * Thus extend previous aruba-networks fix from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all 
NXDOMAIN results with lower feature levels just in case.

  [Test Case]

   * systemd-resolved something-nonexistant.ubuntu.com
   * monitor the logs, and check that the transaction has been downgraded 
multiple times and tried at least once at a feature level below D0. There 
should be a downgrade message in the log.
   * Note, it will be cached, thus one may need to call $ systemd-resolved 
--flush-caches

  [Regression Potential]

   * Legitimate NXDOMAIN queries will now take longer, as they will be
  retried multiple times with different features sets until an answer is
  found. At that point the query will be cached and will return quickly.
  This is needed to work-around bad captive portals that do not support
  dns queries with D0. Post-captive portal, the feature level can
  usually be cranked back up and it does after a grace period.

  [Other Info]
   
   * Original bug report

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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