[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Magnus Helander]

Insane amounts in /var/log/syslog

Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:usb: Ignored relative path
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:devices: Ignored relative 
path
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:1-1.3:1.0: Ignored 
relative path
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:..: Ignored relative path
Jun 10 19:52:56 think420 ureadahead[273]: message repeated 2 times: [ 
ureadahead:..: Ignored relative path]
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:devices: Ignored relative 
path
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:pci:00: Ignored 
relative path
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead::00:1a.0: Ignored 
relative path
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:usb1: Ignored relative path
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:1-1: Ignored relative path
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:1-1.3: Ignored relative 
path
Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:1-1.3:1.0: Ignored 
relative path

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

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1579580/+subscriptions

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

[Touch-packages] [Bug 1719038] Re: X Server crashes during log in VM since 16.04.2

[ Christian Ehrhardt ]

** Also affects: spice (Ubuntu)
   Importance: Undecided
   Status: 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/1719038

Title:
  X Server crashes during log in VM since 16.04.2

Status in X.Org X server:
  Unknown
Status in qemu package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1719038/+subscriptions

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

[Touch-packages] [Bug 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop

[Aleksandr Panzin]

Still here with Ubuntu 18.04 on ThinkPad P51s

$ cat /proc/asound/card*/codec* | grep Codec
Codec: Realtek ALC298
Codec: Intel Kabylake HDMI

$  sudo lspci -vvv | grep -A 40 -i audio

00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
Subsystem: Lenovo Sunrise Point-LP HD Audio
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1737614

Title:
  Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP
  15-BS576TX laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a new laptop HP-15-BS576TX which has this Intel Corporation
  Sunrise Point-LP HD Audio.

  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD
  Audio [8086:9d71] (rev 21)

  The laptop sound works perfectly fine in Windows 10 with realtek
  drivers. However, in Ubuntu 17.10, the volume is significantly low,
  that I've to scroll the volume slider above 100% mark in pulseaudio to
  the maximum to get acceptable level of sound. I suspect the sound
  quality also is low (mono-like), may be not coming from all speakers
  (perhaps subwoofer exist for this model). Also alsamixer shows the
  speaker volume at the maximum.

   Details about the audio hardware are below:

  :~$ sudo lspci -vvv | grep -A 40 -i audio
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Hewlett-Packard Company Device 832b
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  /proc/asound/card0/codec#0 <==
  Codec: Realtek ALC3227

  ==> /proc/asound/card0/codec#2 <==
  Codec: Intel Kabylake HDMI

  :~$  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  I have gone through Linux kernel sources ALSA and Snd-HDA lists and
  unable to find any optimizations for this laptop.

  Here is the relevant dmesg details:

  [   15.502856] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [   16.310503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3227: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [   16.310506] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   16.310507] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [   16.310508] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [   16.310509] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [   16.310510] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x19
  [   16.310512] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
  [   16.451397] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input9
  [   16.451451] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input10
  [   16.451496] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input11
  [   16.451538] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input12
  [   16.451581] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input13
  [   16.451624] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input14
  [   16.451687] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input15

  Any further information needed, please let me know. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5 [modified: 
usr/share/alsa-base/alsa-info.sh]
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: ndiswrapper
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  admin2018   1246 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 12 00:46:12 2017
  InstallationDate: Installed on 2017-11-22 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
 

[Touch-packages] [Bug 1762314] Re: Sound output too low

[Vanja D]

Identical symptoms, package version, distro version, also ALC298, also
tried windows, only difference is computer model (Lenovo T570).
Confirmed on two identical computers with identical setups. Sorry, don't
know how to generate a new report or add debug info.

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

Title:
  Sound output too low

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound output on lenovo p51s is too low. No option to go above 100% in volume 
settings. Download pulse audio volume control to raise application and output 
volume to 153%, which helps to some extent, but then leads to distortion. 
  Was running windows 10 on same system and audio was loud enough!
  Also after this morning
  s update, the volume keys no longer work, even after re-mapping them in 
shortcuts.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jatin  2098 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr  8 22:50:04 2018
  InstallationDate: Installed on 2018-03-23 (17 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [20HCS06601, Realtek ALC298, Speaker, Internal] Background noise or 
low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1VET36W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HCS06601
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1VET36W(1.26):bd10/03/2017:svnLENOVO:pn20HCS06601:pvrThinkPadP51s:rvnLENOVO:rn20HCS06601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51s
  dmi.product.name: 20HCS06601
  dmi.product.version: ThinkPad P51s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1602536] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives

[Balint Reczey]

U-u is fixed in version 1.2.

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

** Description changed:

  [Impact]
  
-  * Unattended-upgrades fails to autoremove packages after installing
+  * Unattended-upgrades fails to autoremove packages after installing
  updates or fails to install updates due to a parallel process acquiring
  apt or dpkg lock while u-u is running.
  
  [Test Case]
  
-  * Set up a system with packages (> 30) to be upgraded. In case of
+  * Set up a system with packages (> 30) to be upgraded. In case of
  Bionic -security has a low number of updates, thus set up the system to
  install -updates to have more packages for u-u to upgrade:
  
-  echo 'Unattended-Upgrade::Allowed-Origins::
+  echo 'Unattended-Upgrade::Allowed-Origins::
  "${distro_id}:${distro_codename}-updates";' >
  /etc/apt/apt.conf.d/51-updates
  
-  * Set up two shells to run commands in parallel
-  * In shell "A" run sudo apt update && sudo unattended-upgrade --dry-run 
--verbose --debug
-  * After u-u started run the following command in shell "B":
-  while sleep 1; do python3 -c 'import apt; import apt_pkg; 
print(apt_pkg.pkgsystem_lock())' ; done
-  * Observe the following exception repeated while running u-u and True being 
printed after u-u is finished:
+  * Set up two shells to run commands in parallel
+  * In shell "A" run sudo apt update && sudo unattended-upgrade --dry-run 
--verbose --debug
+  * After u-u started run the following command in shell "B":
+  while sleep 1; do python3 -c 'import apt; import apt_pkg; 
print(apt_pkg.pkgsystem_lock())' ; done
+  * Observe the following exception repeated while running u-u and True being 
printed after u-u is finished:
  ...
  Traceback (most recent call last):
-   File "", line 1, in 
+   File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  Traceback (most recent call last):
-   File "", line 1, in 
+   File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  True
  Traceback (most recent call last):
-   File "", line 1, in 
+   File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  True
  True
  True
  True
  ...
  
  [Regression Potential WIP]
  
-  * Unattended-upgrade may crash
+  * Unattended-upgrade may crash
+ 
+ [Other Info]
+ 
+ It looks like python-apt also releases the lock sometimes unexpectedly
+ thus the both packages need to be fixed to avoid loosing the lock.
  
  [Original Bug Text]
  
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unattended-upgrades.  This problem was most recently seen with
  version 0.90, the problem page at
  https://errors.ubuntu.com/problem/19f99745d7dce5aea118eb31bfffcbdcdf238c4f
  contains more details.

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

** Also affects: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Fix Released

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

** Also affects: unattended-upgrades (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 python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1602536

Title:
  /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin
  /unattended-
  upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives

Status in python-apt package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in unattended-upgrades source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in unattended-upgrades source package in Bionic:
  New

Bug description:
  [Impact]

   * Unattended-upgrades fails to autoremove packages after installing
  updates or fails to install updates due to a parallel process
  acquiring apt or dpkg lock while u-u is running.

  [Test Case]

   * Set up a system with packages (> 30) to be upgraded. In case of
  Bionic -security has a low number of updates, thus set up the system
  to install -updates to have more packages for u-u to upgrade:

   echo 'Unattended-Upgrade::Allowed-Origins::
  "${distro_id}:${distro_codename}-updates";' >
  /etc/apt/apt.conf.d/51-updates

   * Set up two shells to run commands in parallel
   * In shell "A" run sudo ap

[Touch-packages] [Bug 1762314] Re: Sound output too low

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  Sound output too low

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound output on lenovo p51s is too low. No option to go above 100% in volume 
settings. Download pulse audio volume control to raise application and output 
volume to 153%, which helps to some extent, but then leads to distortion. 
  Was running windows 10 on same system and audio was loud enough!
  Also after this morning
  s update, the volume keys no longer work, even after re-mapping them in 
shortcuts.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jatin  2098 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr  8 22:50:04 2018
  InstallationDate: Installed on 2018-03-23 (17 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [20HCS06601, Realtek ALC298, Speaker, Internal] Background noise or 
low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1VET36W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HCS06601
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1VET36W(1.26):bd10/03/2017:svnLENOVO:pn20HCS06601:pvrThinkPadP51s:rvnLENOVO:rn20HCS06601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51s
  dmi.product.name: 20HCS06601
  dmi.product.version: ThinkPad P51s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11

[Bug Watch Updater]

Launchpad has imported 31 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=151521.

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


On 2016-08-05T07:04:52+00:00 timo.jyrinki wrote:

Created attachment 227601
dmesg

It's a Braswell 14nm platform with Coreboot and SeaBIOS as a payload to
boot Ubuntu 16.10 (+ mainline 4.7 kernel). Sound does not work and the
UIs don't show any devices either since pulseaudio fails so start with
"failed to detect any sound hardware".

According to Chromebook community person, there might be some required
initialization missing that the ChromeOS payload ("depthcharge") is
usually responsible for.

alsa-info at: http://www.alsa-
project.org/db/?f=c193a12f53608b68d259f574b4791d18a522a000

dmesg, dmidecode, lshw, lspci as attachments.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/20


On 2016-08-05T07:05:21+00:00 timo.jyrinki wrote:

Created attachment 227611
dmidecode

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/21


On 2016-08-05T07:05:44+00:00 timo.jyrinki wrote:

Created attachment 227621
lshw

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/22


On 2016-08-05T07:06:03+00:00 timo.jyrinki wrote:

Created attachment 227631
lspci

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/23


On 2016-08-08T14:06:46+00:00 timo.jyrinki wrote:

It seems these should get merged?

https://github.com/plbossart/sound/branches/all?query=byt-cht

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/24


On 2016-08-09T20:03:04+00:00 tiwai wrote:

The relevant codes have been already merged to upstream recently.
Could you try 4.8-rc1?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/25


On 2016-08-10T13:57:03+00:00 timo.jyrinki wrote:

Created attachment 228161
dmesg 4.8rc1

No change, no sound and cht-bsw-max98090 cht-bsw-max98090:
snd_soc_register_card failed -517

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/26


On 2016-08-22T09:49:19+00:00 vinod.koul wrote:

(In reply to Timo Jyrinki from comment #6)
> Created attachment 228161 [details]
> dmesg 4.8rc1
> 
> No change, no sound and cht-bsw-max98090 cht-bsw-max98090:
> snd_soc_register_card failed -517

SST driver seems to initialze well. This i2c seems to fail..

[   19.972195] cht-bsw-max98090 cht-bsw-max98090: ASoC: i2c-104C227E:00 not 
registered
[   19.972207] cht-bsw-max98090 cht-bsw-max98090: snd_soc_register_card failed 
-517

I will check the codec on this device, if you know please do let me
know...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/27


On 2016-08-24T08:21:35+00:00 vinod.koul wrote:

okay I checked. With coreboot this seems to work fine.

Cna you check the SeaBIOS used and get it to create the I2C device
104C227E so codec can be loaded thus completing the sound card

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/28


On 2016-08-24T09:27:31+00:00 timo.jyrinki wrote:

Thank you, sounds like a very useful bit of information. I've passed on
the info to the G+ coreboot on Chromebooks community where the people
creating the SeaBIOS images are.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/29


On 2016-08-24T10:51:23+00:00 timo.jyrinki wrote:

And copy-pasting here (from
https://plus.google.com/u/0/+TimoJyrinki/posts/R1AqYCSPru8 ):

"SeaBIOS doesn't do hardware initialisation, that's down to coreboot, so
no, I can't. Obviously, the sound hardware works under the ChromeOS
kernel so I would guess they need to figure out what the ChromeOS kernel
is doing that upstream isn't."

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1609750/comments/30


On 2016-08-26T09:07:20+00:00 timo.jyrinki wrot

[Touch-packages] [Bug 1772094] Re: Surface Pro 4: Keyboard not functional during LUKS password prompt

[Paul White]

** Package changed: ubuntu => initramfs-tools (Ubuntu)

** Tags added: bionic

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

Title:
  Surface Pro 4: Keyboard not functional during LUKS password prompt

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 18.04 desktop edition on a Microsoft Surface Pro 4,
  using LVM and full disk encryption.  When LUKS prompts for the
  password, however, the type cover keyboard does not work.  I had to
  plug in a USB keyboard to type in the password and boot.

  However, the solution is simple.  Edit the /etc/initramfs-
  tools/modules file, add "hid_multitouch" to a line on its own, then
  run "update-initramfs -u".  Now the typecover keyboard can be used to
  enter the LUKS password on boot.

  The Ubuntu 18.04 desktop installer should be modified to detect if it
  is running on Surface Pro hardware, and add the module, above, as
  needed.

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

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

[Touch-packages] [Bug 1772094] [NEW] Surface Pro 4: Keyboard not functional during LUKS password prompt

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I installed Ubuntu 18.04 desktop edition on a Microsoft Surface Pro 4,
using LVM and full disk encryption.  When LUKS prompts for the password,
however, the type cover keyboard does not work.  I had to plug in a USB
keyboard to type in the password and boot.

However, the solution is simple.  Edit the /etc/initramfs-tools/modules
file, add "hid_multitouch" to a line on its own, then run "update-
initramfs -u".  Now the typecover keyboard can be used to enter the LUKS
password on boot.

The Ubuntu 18.04 desktop installer should be modified to detect if it is
running on Surface Pro hardware, and add the module, above, as needed.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
Surface Pro 4: Keyboard not functional during LUKS password prompt
https://bugs.launchpad.net/bugs/1772094
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools in Ubuntu.

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

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

[Steve Langasek]

Thanks, that confirms that the file existed before the upgrade.  I would
still need a copy of this file to try to understand where it came from.

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  New
Status in systemd-shim package in Ubuntu:
  Incomplete
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 19353] Re: Tools relying on /etc/debian_version get confused

[themusicgod1]

** Tags added: cosmic

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

Title:
  Tools relying on /etc/debian_version get confused

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  /etc/debian_version appears to be carried unmodified from Debian on Ubuntu 
systems. 
  This means that things like reportbug that use the information there to 
identify the 
  version of Debian that they are running on will identify Unbuntu systems as a 
Debian 
  version.

  Another approach would be to modify all the tools like reportbug to add their 
own 
  information or read /etc/ubuntu_version and prefer that.

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

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

[Touch-packages] [Bug 1269840] Re: ubuntu-bug ubuntu-bug doesn't work

[themusicgod1]

** Tags added: cosmic

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

Title:
  ubuntu-bug ubuntu-bug doesn't work

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-bug doesn't make program lookup when package lookup failed.
  This is inconvenient for users, who don't know about `which` command.
  Is it possible to automate lookup and continue search until something
  matches?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport 2.12.5-0ubuntu2.2
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CrashReports:
   640:1000:122:1423125:2014-01-09 20:22:25.104739665 +0300:2014-01-09 
20:22:26.104739665 
+0300:/var/crash/_usr_lib_i386-linux-gnu_bamf_bamfdaemon.1000.crash
   640:1000:122:157297300:2014-01-09 20:56:44.036795854 +0300:2014-01-09 
20:56:45.036795854 +0300:/var/crash/_usr_bin_compiz.1000.crash
   640:0:122:4884804:2014-01-10 13:10:06.891414880 +0300:2014-01-10 
13:10:07.891414880 +0300:/var/crash/_usr_bin_Xorg.0.crash
  Date: Thu Jan 16 18:10:59 2014
  InstallationDate: Installed on 2012-03-12 (675 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (87 days ago)

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

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

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

[Shane Synan]

Apologies for the double-comment.

Following the guide from here...
https://askubuntu.com/questions/838491/systemd-shim-error-after-upgrading-from-16-04-to-16-10/838673#838673

I was able to continue upgrading with these commands:

[let upgrader bail out and run dpkg configure]
sudo mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak
sudo apt-get install -f
sudo apt dist-upgrade
sudo apt autoremove

Then, to optionally finish cleaning up, check what packages are no longer 
supported using the command from...
https://askubuntu.com/questions/691051/how-to-get-the-list-of-the-unsupported-packages-mentioned-during-the-os-upgrade

awk -F\' '/demoted/ {gsub(/ /,"\n",$2); print $2}' /var/log/dist-
upgrade/main.log

The system in question appears to work fine now, just the usual cleanup
of changes for any major OS upgrade.

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  New
Status in systemd-shim package in Ubuntu:
  Incomplete
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

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

[Steve Langasek]

On Sun, Jun 10, 2018 at 07:38:26PM -, Shane Synan wrote:
> I just ran into this situation myself.  After I received the error
> report and let the upgrade recover, running the dpkg command gives me...

> diversion by systemd-shim from: 
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
> diversion by systemd-shim to: 
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> systemd: /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service

Thanks for the information.  And does the file
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service exist on
your system?  If so, please attach it to the bug report so we can see its
contents and try to figure out where it came from.

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  New
Status in systemd-shim package in Ubuntu:
  Incomplete
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 1776106] Re: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  it my

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.11
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Sun Jun 10 22:09:32 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-06-10 (0 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-12-09T18:41:30

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

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

[Touch-packages] [Bug 1776106] [NEW] package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[nauj nille-odarit]

Public bug reported:

it my

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.11
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
Date: Sun Jun 10 22:09:32 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-06-10 (0 days ago)
mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-12-09T18:41:30

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  it my

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.11
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Sun Jun 10 22:09:32 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-06-10 (0 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-12-09T18:41:30

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

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

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

[Shane Synan]

I just ran into this situation myself.  After I received the error
report and let the upgrade recover, running the dpkg command gives me...

diversion by systemd-shim from: 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
diversion by systemd-shim to: 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
systemd: /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  New
Status in systemd-shim package in Ubuntu:
  Incomplete
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 1771749] Re: Ethernet connection lost after few minutes since starting

[Victor Marin]

I don't know which kernel version I did use in Xenial (initially I used
the normal one, the kernel installed by default, but then I installed
UKUU so couldn't remember, but I never had this problem with previous
versions of Kubuntu nor any other flavor of Ubuntu nor in any Linux
distro, for the case.

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/co

[Touch-packages] [Bug 1775380] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked.
  invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed.
  ● lvm2-lvmetad.service - LVM2 metadata daemon
 Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor 
preset: enabled)
 Active: inactive (dead)
   Docs: man:lvmetad(8)
  dpkg: error processing package lvm2 (--configure):
   installed lvm2 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic
  Errors were encountered while processing:
   lvm2
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  all time that I try to update or remove or install something receive
  error like above

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu3
  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
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jun  6 13:19:37 2018
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  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: lvm2
  Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess 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/lvm2/+bug/1775380/+subscriptions

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

[Touch-packages] [Bug 1776075] Re: Bluetooth Problem

[Paul White]

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

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

Title:
  Bluetooth Problem

Status in bluez package in Ubuntu:
  New

Bug description:
  Ich kann Bluetooth nicht Aktivieren

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jun 10 14:59:59 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7400G] [1002:9994] 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7400G] [144d:c660]
  InstallationDate: Installed on 2015-11-17 (935 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed 
root=UUID=5b7ab83e-d739-434f-afc7-78ed793a51a1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04RAS.W68.121025.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U3C-A03DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04RAS.W68.121025.LEO:bd10/25/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U3C:pvrP04RAS:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U3C-A03DE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U3C
  dmi.product.version: P04RAS
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Jun 10 14:07:04 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 905147] Re: QPrinterDialog ignores default settings from CUPS

[Bug Watch Updater]

** Changed in: qt
   Status: Unknown => Won't Fix

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

Title:
  QPrinterDialog ignores default settings from CUPS

Status in Qt:
  Won't Fix
Status in qt4-x11 package in Ubuntu:
  Fix Released

Bug description:
  KDE as well as many QT-Applications use QPrinterDialog as their
  printing dialog. Thing is: This dialog ignores default settings
  defined in CUPS - it doesn't even remember that last settings that
  were chosen. I know this is a QT issue but I kindly ask you not to
  close this bug as upstream and here's why:

  1. This bug has been around for years now - the first report to Nokia about 
was back in 2008 if I recall correctly. 
  2. A user doesn't know and doesn't care about whose fault it is. He just 
knows, that he set his printer settings to default to duplex in CUPS and that 
his QT applications don't print duplex. At first he might shrug and set duplex 
in the dialog. Next time the setting is back to simplex. The same is true for 
other options like collate and color settings. It's just a huge usability 
issue. 
  3. The fix below has been adopted by other major distributions for quite some 
time now. It works for duplex, collate and color settings. 
  4. It saves lots and lots of trees!

  I think it does not work for paper size and in general it doesn't fix
  the problem that QT can't remember the settings you choose in the
  print dialog. The paper size may be read from the configured defaults
  easily, too, but settings saving may be a bit harder. However, you'd
  implement this fix, you'd do something VERY good for Ubuntu -
  especially since 12.04 is meant to be an LTS release! If you could
  even improve the fix that would be huge!

  Here's the fix from the KDE bug tracker:
  https://bugs.kde.org/attachment.cgi?id=41187

  More info:
  https://bugs.kde.org/show_bug.cgi?id=180051
  https://bugreports.qt.nokia.com//browse/QTBUG-6471 (and 
https://bugreports.qt.nokia.com/browse/QTBUG-23037) and other bug reports from 
the comments there.

  For Oneiric I've made a patched version in a PPA of mine that you
  could look at. You'll see it's really a minor modification that
  doesn't take any effort at all to implement. You can find it here:
  https://launchpad.net/~dhertel/+archive/myfixes

  As a side note: I know that KDE is not the default environment in
  Ubuntu, but it's getting more important for people since Gnome2
  officially is no more and Unity isn't exactly better when one doesn't
  even like Gnome3 to begin with.

  So I hope this makes it into Precise...

  Cheers,
  Dominik

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

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

[Touch-packages] [Bug 1616148] Re: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 101

[Launchpad Bug Tracker]

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

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

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

Title:
  package python-gi 3.20.0-0ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 101

Status in pygobject package in Ubuntu:
  Confirmed

Bug description:
  No way to install the package python-gi 3.20.0-0ubuntu1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-gi 3.20.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Tue Aug 23 16:53:08 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 101
  InstallationDate: Installed on 2016-04-02 (143 days ago)
  InstallationMedia: Lubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: pygobject
  Title: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 101
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 905147]

[Michael Weghorn]

The issue that a printer's default CUPS options are not properly
initialized in the print dialog has been fixed upstream in Qt now, along
with several other improvements of the Qt print dialog.

Most of the improvements will be contained in Qt version 5.11 already
(s. [1] for more details), while the proper initialization of the duplex
option -- which is mentioned in this bug report pretty often -- will be
implemented in Qt 5.12 (s. [2]).

I therefore suggest to close this bug as RESOLVED UPSTREAM - and will do
so soon unless any objections are brought up here in the meantime.

[1] https://www.kdab.com/better-support-for-cups-features-in-qt-5-11/
[2] https://codereview.qt-project.org/#/c/226881/

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

Title:
  QPrinterDialog ignores default settings from CUPS

Status in Qt:
  Won't Fix
Status in qt4-x11 package in Ubuntu:
  Fix Released

Bug description:
  KDE as well as many QT-Applications use QPrinterDialog as their
  printing dialog. Thing is: This dialog ignores default settings
  defined in CUPS - it doesn't even remember that last settings that
  were chosen. I know this is a QT issue but I kindly ask you not to
  close this bug as upstream and here's why:

  1. This bug has been around for years now - the first report to Nokia about 
was back in 2008 if I recall correctly. 
  2. A user doesn't know and doesn't care about whose fault it is. He just 
knows, that he set his printer settings to default to duplex in CUPS and that 
his QT applications don't print duplex. At first he might shrug and set duplex 
in the dialog. Next time the setting is back to simplex. The same is true for 
other options like collate and color settings. It's just a huge usability 
issue. 
  3. The fix below has been adopted by other major distributions for quite some 
time now. It works for duplex, collate and color settings. 
  4. It saves lots and lots of trees!

  I think it does not work for paper size and in general it doesn't fix
  the problem that QT can't remember the settings you choose in the
  print dialog. The paper size may be read from the configured defaults
  easily, too, but settings saving may be a bit harder. However, you'd
  implement this fix, you'd do something VERY good for Ubuntu -
  especially since 12.04 is meant to be an LTS release! If you could
  even improve the fix that would be huge!

  Here's the fix from the KDE bug tracker:
  https://bugs.kde.org/attachment.cgi?id=41187

  More info:
  https://bugs.kde.org/show_bug.cgi?id=180051
  https://bugreports.qt.nokia.com//browse/QTBUG-6471 (and 
https://bugreports.qt.nokia.com/browse/QTBUG-23037) and other bug reports from 
the comments there.

  For Oneiric I've made a patched version in a PPA of mine that you
  could look at. You'll see it's really a minor modification that
  doesn't take any effort at all to implement. You can find it here:
  https://launchpad.net/~dhertel/+archive/myfixes

  As a side note: I know that KDE is not the default environment in
  Ubuntu, but it's getting more important for people since Gnome2
  officially is no more and Unity isn't exactly better when one doesn't
  even like Gnome3 to begin with.

  So I hope this makes it into Precise...

  Cheers,
  Dominik

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

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

[Touch-packages] [Bug 905147]

[Michael Weghorn]

(In reply to Michael Weghorn from comment #105)
> [...] 
> I therefore suggest to close this bug as RESOLVED UPSTREAM - and will do so
> soon unless any objections are brought up here in the meantime.

I'm doing this now, since nobody raised any objections.

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

Title:
  QPrinterDialog ignores default settings from CUPS

Status in Qt:
  Won't Fix
Status in qt4-x11 package in Ubuntu:
  Fix Released

Bug description:
  KDE as well as many QT-Applications use QPrinterDialog as their
  printing dialog. Thing is: This dialog ignores default settings
  defined in CUPS - it doesn't even remember that last settings that
  were chosen. I know this is a QT issue but I kindly ask you not to
  close this bug as upstream and here's why:

  1. This bug has been around for years now - the first report to Nokia about 
was back in 2008 if I recall correctly. 
  2. A user doesn't know and doesn't care about whose fault it is. He just 
knows, that he set his printer settings to default to duplex in CUPS and that 
his QT applications don't print duplex. At first he might shrug and set duplex 
in the dialog. Next time the setting is back to simplex. The same is true for 
other options like collate and color settings. It's just a huge usability 
issue. 
  3. The fix below has been adopted by other major distributions for quite some 
time now. It works for duplex, collate and color settings. 
  4. It saves lots and lots of trees!

  I think it does not work for paper size and in general it doesn't fix
  the problem that QT can't remember the settings you choose in the
  print dialog. The paper size may be read from the configured defaults
  easily, too, but settings saving may be a bit harder. However, you'd
  implement this fix, you'd do something VERY good for Ubuntu -
  especially since 12.04 is meant to be an LTS release! If you could
  even improve the fix that would be huge!

  Here's the fix from the KDE bug tracker:
  https://bugs.kde.org/attachment.cgi?id=41187

  More info:
  https://bugs.kde.org/show_bug.cgi?id=180051
  https://bugreports.qt.nokia.com//browse/QTBUG-6471 (and 
https://bugreports.qt.nokia.com/browse/QTBUG-23037) and other bug reports from 
the comments there.

  For Oneiric I've made a patched version in a PPA of mine that you
  could look at. You'll see it's really a minor modification that
  doesn't take any effort at all to implement. You can find it here:
  https://launchpad.net/~dhertel/+archive/myfixes

  As a side note: I know that KDE is not the default environment in
  Ubuntu, but it's getting more important for people since Gnome2
  officially is no more and Unity isn't exactly better when one doesn't
  even like Gnome3 to begin with.

  So I hope this makes it into Precise...

  Cheers,
  Dominik

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

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

[Touch-packages] [Bug 1776013] Re: systemd-networkd: DHCP lease lost (Ubuntu 18.04)

[Dimitri John Ledkov]

netwokrd backend documentation:

https://www.freedesktop.org/software/systemd/man/systemd.network.html#CriticalConnection=

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

Title:
  systemd-networkd: DHCP lease lost (Ubuntu 18.04)

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I have a Linux router whose external Ethernet interface is configured from 
ISP's DHCP server.
  After its migration from Ubuntu 16.04 + ifupdown + isc-dhcp-client to Ubuntu 
18.04 + netplan.io + systemd-networkd, I noticed that systemd-networkd plays 
overly fairly when it can not get a timely renew response from ISP's DHCP 
server: it honestly removes the dynamic IP from the interface and restores 
(often the same) IP only when ISP's DHCP server gives it a proper response 
again. Which causes 1..5-minute pauses in Internet availability since my ISP's 
DHCP server is for some reason flaky, i.e. it can become unresponsive for some 
periods of time. I never noticed this problem with isc-dhcp-client, and started 
noticing it only after migrating DHCP client role to systemd-networkd.
  The question is, can I (or you) make systemd-networkd DHCP client behave more 
relaxedly ?
  I know that most DHCP clients (isc-, pump, dhcpcd) at some stage of their 
development decided to implement such relaxed logic, i.e. to keep 
last-configured dynamic IP on the interface despite the lack of responses from 
DHCP server. As this is easier to implement than to make ISP staff fix their 
services, I would suppose there should be some knob in systemd-networkd 
settings. Or, at least, an idea to implement something similar in the future.

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

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

[Touch-packages] [Bug 1776013] Re: systemd-networkd: DHCP lease lost (Ubuntu 18.04)

[Dimitri John Ledkov]

Yes, the critical connection is the option to use in this case.

You may also check the leases themselves in /run/systemd/netif/leases
and check if the T1/T2/Lifetime are sensible, with each subsequent one
higher than the prior. And if not, contact your ISP support to correct
those.


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

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

Title:
  systemd-networkd: DHCP lease lost (Ubuntu 18.04)

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I have a Linux router whose external Ethernet interface is configured from 
ISP's DHCP server.
  After its migration from Ubuntu 16.04 + ifupdown + isc-dhcp-client to Ubuntu 
18.04 + netplan.io + systemd-networkd, I noticed that systemd-networkd plays 
overly fairly when it can not get a timely renew response from ISP's DHCP 
server: it honestly removes the dynamic IP from the interface and restores 
(often the same) IP only when ISP's DHCP server gives it a proper response 
again. Which causes 1..5-minute pauses in Internet availability since my ISP's 
DHCP server is for some reason flaky, i.e. it can become unresponsive for some 
periods of time. I never noticed this problem with isc-dhcp-client, and started 
noticing it only after migrating DHCP client role to systemd-networkd.
  The question is, can I (or you) make systemd-networkd DHCP client behave more 
relaxedly ?
  I know that most DHCP clients (isc-, pump, dhcpcd) at some stage of their 
development decided to implement such relaxed logic, i.e. to keep 
last-configured dynamic IP on the interface despite the lack of responses from 
DHCP server. As this is easier to implement than to make ISP staff fix their 
services, I would suppose there should be some knob in systemd-networkd 
settings. Or, at least, an idea to implement something similar in the future.

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

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

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[aka2006]

Same issue.
When I used git clone, it shows:
git-remote-https: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version 
`CURL_OPENSSL_3' not found (required by git-remote-https)
But when I installed libcurl3, it shows:
The following packages will be REMOVED:
  libcurl4 virtualbox-5.2
>From the above comments, I don't get satisfied solution.
Will Ubuntu release the patch?

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

[Touch-packages] [Bug 1776075] [NEW] Bluetooth Problem

[Parolari Enrico]

Public bug reported:

Ich kann Bluetooth nicht Aktivieren

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Jun 10 14:59:59 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7400G] [1002:9994] 
(prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7400G] [144d:c660]
InstallationDate: Installed on 2015-11-17 (935 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed 
root=UUID=5b7ab83e-d739-434f-afc7-78ed793a51a1 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/25/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P04RAS.W68.121025.LEO
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP535U3C-A03DE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04RAS.W68.121025.LEO:bd10/25/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U3C:pvrP04RAS:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U3C-A03DE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 535U3C
dmi.product.version: P04RAS
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Jun 10 14:07:04 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: radeon

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


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

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

Title:
  Bluetooth Problem

Status in xorg package in Ubuntu:
  New

Bug description:
  Ich kann Bluetooth nicht Aktivieren

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jun 10 14:59:59 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7400G] [1002:9994] 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7400G] [144d:c660]
  InstallationDate: Installed on 2015-11-17 (935 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed 
root=UUID=5b7ab83e-d739-434f-afc7-78ed793a51a1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04RAS.W68.121025.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U3C-A03DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
 

[Touch-packages] [Bug 1776074] [NEW] indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead)

[Mantas Kriaučiūnas]

Public bug reported:

indicator-datetime package has big ubuntu-touch-sounds package in
Recommends field even in latest Ubuntu Bionic release.

gnome-panel recommends indicator-applet-complete and indicator-applet-
complete recommends indicator-datetime, so big and not useful ubuntu-
touch-sounds is installed in all desktop systems, where gnome-flashback
(gnome-panel) desktop environment is used.

I think ubuntu-touch-sounds should be removed from Recommends field and
if there are some cases, where ubuntu-touch-sounds is usefull for
indicator-datetime, then Suggests should be used instead.

** Affects: baltix-default-settings
 Importance: Undecided
 Status: New

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: baltix-default-settings
   Importance: Undecided
   Status: New

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

Title:
  indicator-datetime shouldn't recommend big ubuntu-touch-sounds package
  (maybe Suggests should be used instead)

Status in Default settings and artwork for Baltix OS:
  New
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  indicator-datetime package has big ubuntu-touch-sounds package in
  Recommends field even in latest Ubuntu Bionic release.

  gnome-panel recommends indicator-applet-complete and indicator-applet-
  complete recommends indicator-datetime, so big and not useful ubuntu-
  touch-sounds is installed in all desktop systems, where gnome-
  flashback (gnome-panel) desktop environment is used.

  I think ubuntu-touch-sounds should be removed from Recommends field
  and if there are some cases, where ubuntu-touch-sounds is usefull for
  indicator-datetime, then Suggests should be used instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1776074/+subscriptions

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

[Touch-packages] [Bug 1577042] Re: SIGSEGV in SoundTouch 1.9.2

[Daniel Schürmann]

> Why not simply increasing the minimum required version from 1.8.0 to
2.0.0?

Yes, that is the way to go here. Trusty for example has Soundtouch 1.7
so we build it with our own static library anyway. If Ubuntu has 2.0.0
one day, it will uses the system provided version again.

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

Title:
  SIGSEGV in SoundTouch 1.9.2

Status in Mixxx:
  Confirmed
Status in soundtouch package in Ubuntu:
  Confirmed

Bug description:
  OS: Fedora 23 x86_64
  Lib: soundtouch-1.9.2-3.fc23.x86_64

  Branch: master (2.1.0-alpha-pre x64)
  Key Lock enabled
  Pitch at 0.00
    - not moved during the whole session (AutoDJ background music @home)
  File plays fine after restart
    - same results
    - waveform generation is skipped now

  Warning [AnalyzerQueue 1]: Recoverable MP3 frame decoding error: lost 
synchronization
  Debug [AnalyzerQueue 1]: Waveform generation for track 92614 done 6 s
  Debug [AnalyzerQueue 1]: ReplayGain 2.0 (libebur128) result is -2.78099 dB 
for "/home/uk/Music/Collection/nico/chelsea girl/01-02 nico these days.mp3"
  Debug [AnalyzerQueue 1]: Beat Calculation complete
  Debug [AnalyzerQueue 1]: Key Detection complete
  Debug [AnalyzerQueue 1]: Key Histogram
  Debug [AnalyzerQueue 1]: 6 : "F" 7.93267e+06
  Debug [AnalyzerQueue 1]: 11 : "B♭" 1.47456e+06

  Program received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7ffee22d2700 (LWP 16845)]
  0x77891e90 in soundtouch::TDStretch::overlapStereo(float*, float 
const*) const () from /usr/lib64/libSoundTouch.so.1
  (gdb) bt
  #0  0x77891e90 in soundtouch::TDStretch::overlapStereo(float*, float 
const*) const () at /usr/lib64/libSoundTouch.so.1
  #1  0x77893037 in soundtouch::TDStretch::processSamples() ()
  at /usr/lib64/libSoundTouch.so.1
  #2  0x77891490 in soundtouch::SoundTouch::putSamples(float const*, 
unsigned int) () at /usr/lib64/libSoundTouch.so.1
  #3  0x007cfc82 in EngineBufferScaleST::getScaled(float*, int) 
(this=0x20a9d00, pOutput=, buf_size=2048)
  at src/engine/enginebufferscalest.cpp:164
  #4  0x007cba11 in EngineBuffer::process(float*, int) (this=0x1fa1be0, 
pOutput=0x7fffc8792010, iBufferSize=2048) at src/engine/enginebuffer.cpp:983
  #5  0x007d1310 in EngineDeck::process(float*, int) (this=0x1f759d0, 
pOut=0x7fffc8792010, iBufferSize=2048) at src/engine/enginedeck.cpp:98
  #6  0x007dff4e in EngineMaster::processChannels(int) 
(this=this@entry=0x14fe100, iBufferSize=iBufferSize@entry=2048) at 
src/engine/enginemaster.cpp:318
  #7  0x007e8b50 in EngineMaster::process(int) (this=0x14fe100, 
iBufferSize=iBufferSize@entry=2048) at src/engine/enginemaster.cpp:350
  #8  0x00b47d5b in SoundManager::onDeviceOutputCallback(unsigned int) 
(this=, iFramesPerBuffer=iFramesPerBuffer@entry=1024)
  at src/soundio/soundmanager.cpp:548
  #9  0x00b44a36 in 
SoundDevicePortAudio::callbackProcessClkRef(unsigned int, float*, float const*, 
PaStreamCallbackTimeInfo const*, unsigned long) (this=0x1e337c0, 
framesPerBuffer=1024, out=0x4de4f2a0, in=, timeInfo= to continue, or q  to quit---
  ptimized out>, statusFlags=)
  at src/soundio/sounddeviceportaudio.cpp:949
  #10 0x77459454 in AdaptingOutputOnlyProcess ()
  at /usr/lib64/libportaudio.so.2
  #11 0x7745aded in PaUtil_EndBufferProcessing ()
  at /usr/lib64/libportaudio.so.2
  #12 0x7746391b in CallbackThreadFunc () at 
/usr/lib64/libportaudio.so.2
  #13 0x71d1e60a in start_thread () at /usr/lib64/libpthread.so.0
  #14 0x7fffeeeb5a4d in clone () at /usr/lib64/libc.so.6

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

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

[Touch-packages] [Bug 1772941] Re: isc-dhcp-server does not listen network interfaces

[Launchpad Bug Tracker]

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

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  isc-dhcp-server does not listen network interfaces

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  System: Ubuntu 16.04.4 LTS x64 XFCE desktop
  Version of package: isc-dhcp-server
  Uname: 4.4.0-127-generic
  Result spected: service isc-dhcp-server status returning that service is 
active, running and OK.
  Network interfaces: 2, enp0s3 (static, main), en0s8 not configured yet.
  Current result:
  service isc-dhcp-server status returns an error message, which says that 
there is no network interface listening.

  In /etc/default/isc-dhcp-server I have configured this line:
  INTERFACES="enp0s3" but still giving the same error. Links to an ask ubuntu 
question:https://askubuntu.com/questions/536531/dhcp-server-wont-start-gives-not-configured-to-listen-on-any-interfaces-eve

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

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

[Touch-packages] [Bug 1772941] Re: isc-dhcp-server does not listen network interfaces

[Wladimir Mutel]

On my system (Ubuntu 18.04 configured with netplan.io and systemd-networkd 
where possible), dhcpd is configured by default, so it just enumerates 
currently-available IP subnets on interfaces to determine on which interface to 
listen.
The only interface it is normally listening on my system is br0, which 
currently includes only wlan0 interface managed by hostapd.
On one reboot I had a race condition between dhcpd and hostapd : on its 
startup, hostapd did 'country update' on wlan0 which temporarily brought it 
down, and br0 went down as well, then systemd-networkd temporarily removed its 
IP address. Right at this moment, dhcpd had begun to start, looking matching 
IPs on interfaces and failing to find any of them. After that I got working 
hostapd (WiFi network visible to clients), but clients unable to configure 
their IPs after WiFi authentication.

So, yes, 'sleep 30' can be a solution, but it is better to implement
some dependency on the systemd level. Like, start dhcpd not earlier than
hostapd is started and operating. Or maybe start hostapd not earlier
than dhcpd has found its subnet and interface (if dhcpd is capable to
survive through temporary drop-down of its interface during normal
operation).

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

Title:
  isc-dhcp-server does not listen network interfaces

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  System: Ubuntu 16.04.4 LTS x64 XFCE desktop
  Version of package: isc-dhcp-server
  Uname: 4.4.0-127-generic
  Result spected: service isc-dhcp-server status returning that service is 
active, running and OK.
  Network interfaces: 2, enp0s3 (static, main), en0s8 not configured yet.
  Current result:
  service isc-dhcp-server status returns an error message, which says that 
there is no network interface listening.

  In /etc/default/isc-dhcp-server I have configured this line:
  INTERFACES="enp0s3" but still giving the same error. Links to an ask ubuntu 
question:https://askubuntu.com/questions/536531/dhcp-server-wont-start-gives-not-configured-to-listen-on-any-interfaces-eve

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

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

[Touch-packages] [Bug 1091663] Re: Support for Infineon modems

[Bug Watch Updater]

** Changed in: modemmanager
   Status: Confirmed => Unknown

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

Title:
  Support for Infineon modems

Status in ModemManager:
  Unknown
Status in ubuntu-nexus7:
  Invalid
Status in modemmanager package in Ubuntu:
  Triaged

Bug description:
  Repeated attempts to get 3G connectivity on my Nexus 7 fail. The same
  SIM worked fine under Android.

  Very occasionally, a notification pops up saying that I have
  connected, but I am then immediately disconnected again. Most of the
  time, though, I get a 'disconnected' notification and nothing else.

  My provider is giffgaff (UK). The mobile broadband hardware is
  definitely detected by Ubuntu, given that it appears in the network
  menu.

  I can do further testing if asked.

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

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

[Touch-packages] [Bug 1091663]

[Gitlab-migration]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-
broadband/ModemManager/issues/2.

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

Title:
  Support for Infineon modems

Status in ModemManager:
  Unknown
Status in ubuntu-nexus7:
  Invalid
Status in modemmanager package in Ubuntu:
  Triaged

Bug description:
  Repeated attempts to get 3G connectivity on my Nexus 7 fail. The same
  SIM worked fine under Android.

  Very occasionally, a notification pops up saying that I have
  connected, but I am then immediately disconnected again. Most of the
  time, though, I get a 'disconnected' notification and nothing else.

  My provider is giffgaff (UK). The mobile broadband hardware is
  definitely detected by Ubuntu, given that it appears in the network
  menu.

  I can do further testing if asked.

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

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

[Touch-packages] [Bug 1770961] Re: Add options to set the snappy refresh schedule

[Ads20000]

'For example if you can use the option to download updates and prompt
the user to upgrade but don't do it until the user confirms it.'

This is not a feature that snappy supports but I suppose Software &
Updates could do this in a hacky way if it wanted to do so.

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://snapdocs.labix.org/configuration-options/87

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

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

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

[Touch-packages] [Bug 1770961] Re: Add options to set the snappy refresh schedule

[Nikolaos Perrakis]

I 'd prefer it if software and updates functionality could be used to
fully control how snaps update. For example if you can use the option to
download updates and prompt the user to upgrade but don't do it until
the user confirms it.

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://snapdocs.labix.org/configuration-options/87

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

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

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

[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Vlad K.]

Solution per comment #3 fixed the problem for me as well, ureadahead is
no longer spammy.

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

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1579580/+subscriptions

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

[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Vlad K.]

92454 entries here, Ubuntu 18.04, fresh installation.

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

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1579580/+subscriptions

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

[Touch-packages] [Bug 1771749] Re: Ethernet connection lost after few minutes since starting

[Kai-Heng Feng]

What's kernel version do you use in Xenial LTS?

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   ifa

[Touch-packages] [Bug 1762384] Re: libgpgme-dev installs libgpgme-pthread.so in /usr/lib/${DEB_HOST_MULTIARCH}, literally

[Launchpad Bug Tracker]

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

** Changed in: gpgme1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  libgpgme-dev installs libgpgme-pthread.so in
  /usr/lib/${DEB_HOST_MULTIARCH}, literally

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  In Bionic, libgpgme-pthread.so it is installed in
  /usr/lib/${DEB_HOST_MULTIARCH} instead of /usr/lib/x86_64-linux-gnu
  (the variable is not replaced)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1762384/+subscriptions

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

[Touch-packages] [Bug 1767321] Re: Xorg freeze

[Ads20000]

Sebastien would
https://wiki.ubuntu.com/DebuggingProgramCrash#The_Xorg_server catch
this? This doesn't seem to be a 'crash'? So how should this be debugged?

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.04, display freezes for ~1-5 seconds at seemingly random
  intervals. When it resumes, gnome shell's dock flickers as if the
  problem was caused by it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:02:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
   Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 
radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.asset.tag: 5CG6351LQL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP
  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/1767321/+subscriptions

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