date:20170907

Well LP seems to have added it to wtaches, just adding another task with it 
doesn't work.
Waiting for Artful to migrate properly now.

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

Title:
  mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race
  leaving ntp dead on reboot

Status in ntp package in Ubuntu:
  Confirmed
Status in ntp source package in Xenial:
  Confirmed
Status in ntp source package in Zesty:
  Fix Released
Status in ntp source package in Artful:
  Confirmed
Status in ntp package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The locks of ntpdate the ifup hook and the ntp service start do not 
 match, therefore installation of ntpdate can harmstring the start of 
 ntp at boot.

   * The change ports back what Debian added later and we merged in Zesty.
 It does two things:
 1. it makes the lock paths actually match
 2. it drops the usage of lockfile-progs which never was a dependency 
and uses flock directly.
 
  [Test Case]

   * Prep
 - Taking a Xenial VM (to avoid all the time set rejects in a container 
   from cluttering the view)
 - Installing ntp
 - Check status of ntp
 - Reboot the VM
 - Check status of ntp
   # Until now all should be good
   * Break it
 - install ntpdate
 - reboot
 - Check status of ntp
   - It (likely) is failed for "blocked known address being busy"
 - This is somewhat of a race, adding more extra network devices in 
   libvirt to your guest increases the chance if you can't reproduce.
   * Fix it
 - install the fix from proposed (or the ppa in c#14)
 - reboot
 - ntp is now running correctly after reboot

  [Regression Potential]

   * It was locking before as well, just on a lock never contended and 
 potentially failing to have the lockfile-progs calls available.
 Due to the change the init now of ntp can take longer (until the 
 ntpdate calls are out of the way)
   * For a fallback in case locking goes crazy in unexpected ways the 
 timeout of the flock (180s) is intentionally not checked for bad return 
 codes. That way in those cases ntp still tries to initialize and if it 
 fails for an ntpdate blocking the port it didn't "loose" anything by 
 being stalled.
 Therefor I'd consider that the actual regression potential rather 
 low  and safe.

  [Other Info]
   
   * This is kind of a bug-zombie, fixed in zesty but resurrected in Debian 
 (and Ubuntu by our merge) due to the addition of a native systemd 
 service. Now that Dev is finally (again) good it is time to tackle the 
 Xenial SRU.

  ---

  ntpdate and ntp conflict on the NTP well-known-socket. If ntp and
  ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there
  are 2 static interfaces configured, most often we find that ntpd is
  not running after a reboot.

  When the ntp service is started by systemd, ntp fails to bind the NTP
  socket because ntpdate is running in the background. It's intended
  that ntp and ntpdate try to avoid this conflict with a lock file, but
  the locking mechanism was changed in ntpdate.if-up (from lockfile to
  flock), but it was not changed in ntp.init. Previously the file
  locking prevented ntp from trying to start when ntpdate was running.
  Not any more.

  Having multiple interfaces causes a much longer period of the socket
  being unavailable, because the 2 ntpdate processes will get serialized
  by the lock, while the ntp service is looking for a different lock, so
  it just plows right in.  Attempts by netdate.if-up to stop and start
  ntp seem to overlap and when the final start is invoked, systemd seems
  to thing ntp is already running, though it has failed.

  In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made:
    debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock 
now.
  Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream.

  This change diverged locking between ntpdate.if-up and ntp.init. This
  was rectified in rev 451 of ntp.init, to use compatible locking, but
  that doesn't appear in the Ubuntu version.

  System Information:

   lsb_release -rd:
     Description:Ubuntu 16.04.2 LTS
     Release:16.04

   apt-cache policy ntpdate:

     ntpdate:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
     100 /var/lib/dpkg/status

   apt-cache policy ntp:

     ntp:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
     100 /var/lib/dpkg/status

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

-- 
Mailing list: htt

[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot

Review is good, pushed the artful fix and added an SRU Template.
Also reported the follow on bug to Debian as 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874540 (I can't link two 
Debian bugs on the same paackage can I?)

** Description changed:

+ [Impact]
+ 
+  * The locks of ntpdate the ifup hook and the ntp service start do not 
+match, therefore installation of ntpdate can harmstring the start of 
+ntp at boot.
+ 
+  * The change ports back what Debian added later and we merged in Zesty.
+It does two things:
+1. it makes the lock paths actually match
+2. it drops the usage of lockfile-progs which never was a dependency 
+   and uses flock directly.
+
+ [Test Case]
+ 
+  * Prep
+- Taking a Xenial VM (to avoid all the time set rejects in a container 
+  from cluttering the view)
+- Installing ntp
+- Check status of ntp
+- Reboot the VM
+- Check status of ntp
+  # Until now all should be good
+  * Break it
+- install ntpdate
+- reboot
+- Check status of ntp
+  - It (likely) is failed for "blocked known address being busy"
+- This is somewhat of a race, adding more extra network devices in 
+  libvirt to your guest increases the chance if you can't reproduce.
+  * Fix it
+- install the fix from proposed (or the ppa in c#14)
+- reboot
+- ntp is now running correctly after reboot
+ 
+ [Regression Potential]
+ 
+  * It was locking before as well, just on a lock never contended and 
+potentially failing to have the lockfile-progs calls available.
+Due to the change the init now of ntp can take longer (until the 
+ntpdate calls are out of the way)
+  * For a fallback in case locking goes crazy in unexpected ways the 
+timeout of the flock (180s) is intentionally not checked for bad return 
+codes. That way in those cases ntp still tries to initialize and if it 
+fails for an ntpdate blocking the port it didn't "loose" anything by 
+being stalled.
+Therefor I'd consider that the actual regression potential rather 
+low  and safe.
+ 
+ [Other Info]
+  
+  * This is kind of a bug-zombie, fixed in zesty but resurrected in Debian 
+(and Ubuntu by our merge) due to the addition of a native systemd 
+service. Now that Dev is finally (again) good it is time to tackle the 
+Xenial SRU.
+ 
+ ---
+ 
  ntpdate and ntp conflict on the NTP well-known-socket. If ntp and
  ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are
  2 static interfaces configured, most often we find that ntpd is not
  running after a reboot.
  
  When the ntp service is started by systemd, ntp fails to bind the NTP
  socket because ntpdate is running in the background. It's intended that
  ntp and ntpdate try to avoid this conflict with a lock file, but the
  locking mechanism was changed in ntpdate.if-up (from lockfile to flock),
  but it was not changed in ntp.init. Previously the file locking
  prevented ntp from trying to start when ntpdate was running. Not any
  more.
  
  Having multiple interfaces causes a much longer period of the socket
  being unavailable, because the 2 ntpdate processes will get serialized
  by the lock, while the ntp service is looking for a different lock, so
  it just plows right in.  Attempts by netdate.if-up to stop and start ntp
  seem to overlap and when the final start is invoked, systemd seems to
  thing ntp is already running, though it has failed.
  
  In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made:
-   debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock 
now.
+   debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock 
now.
  Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream.
  
  This change diverged locking between ntpdate.if-up and ntp.init. This
  was rectified in rev 451 of ntp.init, to use compatible locking, but
  that doesn't appear in the Ubuntu version.
  
- 
  System Information:
  
-  lsb_release -rd:
-Description:Ubuntu 16.04.2 LTS
-Release:16.04
+  lsb_release -rd:
+    Description:Ubuntu 16.04.2 LTS
+    Release:16.04
  
+  apt-cache policy ntpdate:
  
-  apt-cache policy ntpdate:
+    ntpdate:
+  Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
+  Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
+  Version table:
+ *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
+    100 /var/lib/dpkg/status
  
-ntpdate:
-  Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
-  Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
-  Version table:
- *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
-100 /var/lib/dpkg/status
+  apt-cache policy ntp:
  
-  apt-cache policy ntp:
- 
-ntp:
-  Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
-  Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
-  Version table:
- *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
-100 /var/lib/dpkg/status
+    ntp:
+  Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
+  Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
+  Ve

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

2017-09-07 Thread max moro

confirmed on 
HP ProLiant ML10 Gen9, Xeon E3-1225 v5
Intel Raid Bios set to RAID1 (4 drives, 2xraid1)

Shutdowen/reboot hangs (kworkers) and Raid is rebuilt on every "reset"


Linux w11 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
Description:Ubuntu 16.04.3 LTS
Release:16.04

Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] 
[raid10]
md124 : active raid1 sdc[1] sdd[0]
  2930264064 blocks super external:/md125/0 [2/2] [UU]
  [=>...]  resync = 27.1% (795895744/2930264196) 
finish=190.3min speed=186838K/sec

md125 : inactive sdd[1](S) sdc[0](S)
  4776 blocks super external:imsm

md126 : active raid1 sda[1] sdb[0]
  976759808 blocks super external:/md127/0 [2/2] [UU]
  [===>.]  resync = 75.0% (733104704/976759940) 
finish=28.2min speed=143955K/sec

md127 : inactive sda[1](S) sdb[0](S)
  5288 blocks super external:imsm

unused devices: 

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kerne

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE network shares in file chooser

Here is a debdiff with that patch integrated. I hope it'll help.

** Patch added: "Package patch"

https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1714518/+attachment/4945764/+files/gtk+3.0-fix-FUSE-mounts.debdiff

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

Title:
GTK+3 doesn't show FUSE network shares in file chooser

Status in gtk+3.0 package in Ubuntu:
Confirmed

Bug description:
GTK+3 doesn't show FUSE network shares in file chooser - it used to do
so in GTK+2, and the GTK+3 documentation still mentions it should do
it.

In the mean time, every user of every application switching to GTK+3
-- including Chromium, at some point between 58 and 60 -- (a change
which happened in 16.04 LTS!!), loses the functionality to open or
save directly to a network share.

I had chosen 16.04 LTS for deploying our workstations at work, and my 50
users have been suddenly unable to do a simple operation they have to do dozens
of times a day.
They now have to "buffer" these files to their local filesystem when saving
them and before uploading them, and then copy them to the company's network
shares.
They were already a little bit grumpy when it stopped working with Firefox,
and are now really side-eyeing me when they apply updates and find Chromium
broken.

I have reported the bug upstream and provided a patch to fix this. I
hope you'll be able and willing to include it to Ubuntu's GTK+3
package.

Thanks in advance.

Colin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1714518/+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 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

2017-09-07 Thread max moro

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+attachment/4945763/+files/reached_target.png

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not
  help either.

  More information below:

[Touch-packages] [Bug 1568897] Re: Disable Guest Access by default.

2017-09-07 Thread AsciiWolf

Looks like this issue is finally "fixed" in Ubuntu 17.10 where the guest
session is no longer available.

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

Title:
  Disable Guest Access by default.

Status in lightdm package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Triaged

Bug description:
  "Guest Access" should be disabled by default. It is an unexpected
  "feature", on an otherwise secure system. Until a GUI option is added
  (https://bugs.launchpad.net/ubuntu/+source/gnome-control-
  center/+bug/886415), it is also an un-intuitive feature to disable.

  I've found it only invites trouble. For me, trouble had the face of my
  children while I was at work. =) They found that they were able to use
  my laptop, without logging in.

  Then on their PC they found that, while logged into their account,
  using the "Guest Access" bypassed the proxy settings setup in their
  Firefox profile.

  Please consider defaulting both pre-logon and post-logon Guest Access
  to off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1568897/+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 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot

This bug was fixed in the package ntp - 1:4.2.8p10+dfsg-5ubuntu2

---
ntp (1:4.2.8p10+dfsg-5ubuntu2) artful; urgency=medium

  * d/ntp-systemd-wrapper protect systemd service startup from concurrent
ntpdate processes the same way it was protected on sysv-init (LP: #1706818)

 -- Christian Ehrhardt   Tue, 05 Sep
2017 15:09:08 +0200

** Changed in: ntp (Ubuntu Artful)
   Status: Confirmed => Fix Released

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

Title:
  mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race
  leaving ntp dead on reboot

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Confirmed
Status in ntp source package in Zesty:
  Fix Released
Status in ntp source package in Artful:
  Fix Released
Status in ntp package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The locks of ntpdate the ifup hook and the ntp service start do not 
 match, therefore installation of ntpdate can harmstring the start of 
 ntp at boot.

   * The change ports back what Debian added later and we merged in Zesty.
 It does two things:
 1. it makes the lock paths actually match
 2. it drops the usage of lockfile-progs which never was a dependency 
and uses flock directly.
 
  [Test Case]

   * Prep
 - Taking a Xenial VM (to avoid all the time set rejects in a container 
   from cluttering the view)
 - Installing ntp
 - Check status of ntp
 - Reboot the VM
 - Check status of ntp
   # Until now all should be good
   * Break it
 - install ntpdate
 - reboot
 - Check status of ntp
   - It (likely) is failed for "blocked known address being busy"
 - This is somewhat of a race, adding more extra network devices in 
   libvirt to your guest increases the chance if you can't reproduce.
   * Fix it
 - install the fix from proposed (or the ppa in c#14)
 - reboot
 - ntp is now running correctly after reboot

  [Regression Potential]

   * It was locking before as well, just on a lock never contended and 
 potentially failing to have the lockfile-progs calls available.
 Due to the change the init now of ntp can take longer (until the 
 ntpdate calls are out of the way)
   * For a fallback in case locking goes crazy in unexpected ways the 
 timeout of the flock (180s) is intentionally not checked for bad return 
 codes. That way in those cases ntp still tries to initialize and if it 
 fails for an ntpdate blocking the port it didn't "loose" anything by 
 being stalled.
 Therefor I'd consider that the actual regression potential rather 
 low  and safe.

  [Other Info]
   
   * This is kind of a bug-zombie, fixed in zesty but resurrected in Debian 
 (and Ubuntu by our merge) due to the addition of a native systemd 
 service. Now that Dev is finally (again) good it is time to tackle the 
 Xenial SRU.

  ---

  ntpdate and ntp conflict on the NTP well-known-socket. If ntp and
  ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there
  are 2 static interfaces configured, most often we find that ntpd is
  not running after a reboot.

  When the ntp service is started by systemd, ntp fails to bind the NTP
  socket because ntpdate is running in the background. It's intended
  that ntp and ntpdate try to avoid this conflict with a lock file, but
  the locking mechanism was changed in ntpdate.if-up (from lockfile to
  flock), but it was not changed in ntp.init. Previously the file
  locking prevented ntp from trying to start when ntpdate was running.
  Not any more.

  Having multiple interfaces causes a much longer period of the socket
  being unavailable, because the 2 ntpdate processes will get serialized
  by the lock, while the ntp service is looking for a different lock, so
  it just plows right in.  Attempts by netdate.if-up to stop and start
  ntp seem to overlap and when the final start is invoked, systemd seems
  to thing ntp is already running, though it has failed.

  In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made:
    debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock 
now.
  Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream.

  This change diverged locking between ntpdate.if-up and ntp.init. This
  was rectified in rev 451 of ntp.init, to use compatible locking, but
  that doesn't appear in the Ubuntu version.

  System Information:

   lsb_release -rd:
     Description:Ubuntu 16.04.2 LTS
     Release:16.04

   apt-cache policy ntpdate:

     ntpdate:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
     100 /var/lib/dpkg/status

   apt-cache policy ntp:

     ntp:
   Installed: 1:4.2.8p4+dfsg-3

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE network shares in file chooser

2017-09-07 Thread Daniel van Vugt

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => Colin Leroy (colin-colino)

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => In Progress

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=787128
   Importance: Unknown
   Status: Unknown

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

Title:
  GTK+3 doesn't show FUSE network shares in file chooser

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day. 
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares. 
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+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 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot

Artful is done (the systemd version of it), Xenial now has the backport
of the fix we had in zesty for SRU consideration in xenial-unapproved.

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

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

Title:
  mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race
  leaving ntp dead on reboot

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  In Progress
Status in ntp source package in Zesty:
  Fix Released
Status in ntp source package in Artful:
  Fix Released
Status in ntp package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The locks of ntpdate the ifup hook and the ntp service start do not 
 match, therefore installation of ntpdate can harmstring the start of 
 ntp at boot.

   * The change ports back what Debian added later and we merged in Zesty.
 It does two things:
 1. it makes the lock paths actually match
 2. it drops the usage of lockfile-progs which never was a dependency 
and uses flock directly.
 
  [Test Case]

   * Prep
 - Taking a Xenial VM (to avoid all the time set rejects in a container 
   from cluttering the view)
 - Installing ntp
 - Check status of ntp
 - Reboot the VM
 - Check status of ntp
   # Until now all should be good
   * Break it
 - install ntpdate
 - reboot
 - Check status of ntp
   - It (likely) is failed for "blocked known address being busy"
 - This is somewhat of a race, adding more extra network devices in 
   libvirt to your guest increases the chance if you can't reproduce.
   * Fix it
 - install the fix from proposed (or the ppa in c#14)
 - reboot
 - ntp is now running correctly after reboot

  [Regression Potential]

   * It was locking before as well, just on a lock never contended and 
 potentially failing to have the lockfile-progs calls available.
 Due to the change the init now of ntp can take longer (until the 
 ntpdate calls are out of the way)
   * For a fallback in case locking goes crazy in unexpected ways the 
 timeout of the flock (180s) is intentionally not checked for bad return 
 codes. That way in those cases ntp still tries to initialize and if it 
 fails for an ntpdate blocking the port it didn't "loose" anything by 
 being stalled.
 Therefor I'd consider that the actual regression potential rather 
 low  and safe.

  [Other Info]
   
   * This is kind of a bug-zombie, fixed in zesty but resurrected in Debian 
 (and Ubuntu by our merge) due to the addition of a native systemd 
 service. Now that Dev is finally (again) good it is time to tackle the 
 Xenial SRU.

  ---

  ntpdate and ntp conflict on the NTP well-known-socket. If ntp and
  ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there
  are 2 static interfaces configured, most often we find that ntpd is
  not running after a reboot.

  When the ntp service is started by systemd, ntp fails to bind the NTP
  socket because ntpdate is running in the background. It's intended
  that ntp and ntpdate try to avoid this conflict with a lock file, but
  the locking mechanism was changed in ntpdate.if-up (from lockfile to
  flock), but it was not changed in ntp.init. Previously the file
  locking prevented ntp from trying to start when ntpdate was running.
  Not any more.

  Having multiple interfaces causes a much longer period of the socket
  being unavailable, because the 2 ntpdate processes will get serialized
  by the lock, while the ntp service is looking for a different lock, so
  it just plows right in.  Attempts by netdate.if-up to stop and start
  ntp seem to overlap and when the final start is invoked, systemd seems
  to thing ntp is already running, though it has failed.

  In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made:
    debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock 
now.
  Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream.

  This change diverged locking between ntpdate.if-up and ntp.init. This
  was rectified in rev 451 of ntp.init, to use compatible locking, but
  that doesn't appear in the Ubuntu version.

  System Information:

   lsb_release -rd:
     Description:Ubuntu 16.04.2 LTS
     Release:16.04

   apt-cache policy ntpdate:

     ntpdate:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
     100 /var/lib/dpkg/status

   apt-cache policy ntp:

     ntp:
   Installed: 1:4.2.8p4+dfsg-3ubuntu5.5
   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5
   Version table:
  *** 1:4.2.8p4+dfsg-3ubuntu5.5 100
     100 /var/lib/dpkg/status

To manage notifications about this bug go to:
http

[Touch-packages] [Bug 1715599] [NEW] 2.26-0ubuntu1 breaks compliation of several KDE sources

You have been subscribed to a public bug:

2.26-0ubuntu1 breaks compliation of several KDE sources.

Including so far, but maybe not limited to is autotests:

kde4libs
kio
kopete

with the error

In file included from /usr/include/libxslt/xsltInternals.h:24:0,
 from /usr/include/libxslt/xsltutils.h:23,
 from 
/tmp/autopkgtest.U99BLh/build.W2l/kde4libs-4.14.34/kdoctools/kio_help.cpp:61:
/usr/include/libxslt/xsltlocale.h:20:10: fatal error: xlocale.h: No such file 
or directory
 #include 
  ^~~
compilation terminated.

Confirmed also in kio package rebuild in our staging ppa

https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-
frameworks/+sourcepub/8240685/+listing-archive-extra

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

-- 
2.26-0ubuntu1 breaks compliation of several KDE sources
https://bugs.launchpad.net/bugs/1715599
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to libxslt 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 1715599] Re: 2.26-0ubuntu1 breaks compliation of several KDE sources

2017-09-07 Thread Rik Mills

** Description changed:

- 2.26-0ubuntu1 breaks compliation of several KDE sources.
+ gblic 2.26-0ubuntu1 which removed xlocale.h:  breaks compliation of
+ several KDE sources, but libxslt still requires that header.
  
  Including so far, but maybe not limited to is autotests:
  
  kde4libs
  kio
  kopete
  
  with the error
  
  In file included from /usr/include/libxslt/xsltInternals.h:24:0,
-  from /usr/include/libxslt/xsltutils.h:23,
-  from 
/tmp/autopkgtest.U99BLh/build.W2l/kde4libs-4.14.34/kdoctools/kio_help.cpp:61:
+  from /usr/include/libxslt/xsltutils.h:23,
+  from 
/tmp/autopkgtest.U99BLh/build.W2l/kde4libs-4.14.34/kdoctools/kio_help.cpp:61:
  /usr/include/libxslt/xsltlocale.h:20:10: fatal error: xlocale.h: No such file 
or directory
-  #include 
-   ^~~
+  #include 
+   ^~~
  compilation terminated.
  
  Confirmed also in kio package rebuild in our staging ppa
  
  https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-
  frameworks/+sourcepub/8240685/+listing-archive-extra

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

Title:
  2.26-0ubuntu1 breaks compliation of several KDE sources

Status in libxslt package in Ubuntu:
  New

Bug description:
  gblic 2.26-0ubuntu1 which removed xlocale.h:  breaks compliation of
  several KDE sources, but libxslt still requires that header.

  Including so far, but maybe not limited to is autotests:

  kde4libs
  kio
  kopete

  with the error

  In file included from /usr/include/libxslt/xsltInternals.h:24:0,
   from /usr/include/libxslt/xsltutils.h:23,
   from 
/tmp/autopkgtest.U99BLh/build.W2l/kde4libs-4.14.34/kdoctools/kio_help.cpp:61:
  /usr/include/libxslt/xsltlocale.h:20:10: fatal error: xlocale.h: No such file 
or directory
   #include 
    ^~~
  compilation terminated.

  Confirmed also in kio package rebuild in our staging ppa

  https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-
  frameworks/+sourcepub/8240685/+listing-archive-extra

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1715599/+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 1715599] Re: 2.26-0ubuntu1 breaks compliation of several KDE sources

xlocale.h is no longer shipped or required; use locale.h instead.

** Package changed: glibc (Ubuntu) => libxslt (Ubuntu)

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

Title:
  2.26-0ubuntu1 breaks compliation of several KDE sources

Status in libxslt package in Ubuntu:
  New

Bug description:
  gblic 2.26-0ubuntu1 which removed xlocale.h:  breaks compliation of
  several KDE sources, but libxslt still requires that header.

  Including so far, but maybe not limited to is autotests:

  kde4libs
  kio
  kopete

  with the error

  In file included from /usr/include/libxslt/xsltInternals.h:24:0,
   from /usr/include/libxslt/xsltutils.h:23,
   from 
/tmp/autopkgtest.U99BLh/build.W2l/kde4libs-4.14.34/kdoctools/kio_help.cpp:61:
  /usr/include/libxslt/xsltlocale.h:20:10: fatal error: xlocale.h: No such file 
or directory
   #include 
    ^~~
  compilation terminated.

  Confirmed also in kio package rebuild in our staging ppa

  https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-
  frameworks/+sourcepub/8240685/+listing-archive-extra

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1715599/+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 1714518] Re: GTK+3 doesn't show FUSE network shares in file chooser

2017-09-07 Thread Jeremy Bicha

Why do you think showing network shares is supposed to be the default in
GTK+ 3?

My understanding is that it is documented that only local files are shown:
https://developer.gnome.org/gtk3/stable/GtkFileChooser.html#gtk-file-chooser-set-local-only

I think the comment about FUSE was more of "on some systems, you may get
network files showing anyway even though we try to follow the setting."

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

Title:
  GTK+3 doesn't show FUSE network shares in file chooser

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day. 
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares. 
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+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 1324728] Re: ibus-daemon high memory usage

2017-09-07 Thread silviot

With 91 days uptime, ibus-daemon I get:

ps -C ibus-daemon -o %cpu,%mem,vsz,rss,time,cmd
%CPU %MEMVSZ   RSS TIME CMD
 0.4  6.9 1560844 1134516 09:08:07 /usr/bin/ibus-daemon --daemonize --xim 
--address unix:tmpdir=/tmp/ibus

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

Title:
  ibus-daemon high memory usage

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  After surfing the web in firefox for a while, I observed that ibus-
  daemon was occupying a surprisingly large amount of memory (smem
  reports its unique set size [USS] as 107 MiB). This is much higher
  than the usage observed shortly after login (about 1.3 MiB USS).

  Not sure yet if there's anything in particular needed to trigger this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu May 29 20:02:38 2014
  ExecutablePath: /usr/bin/ibus-daemon
  SourcePackage: ibus
  UpgradeStatus: Upgraded to trusty on 2014-04-15 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1324728/+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 1715599] Re: 2.26-0ubuntu1 breaks compliation of several KDE sources

** Changed in: libxslt (Ubuntu)
   Status: New => Fix Committed

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

Title:
  2.26-0ubuntu1 breaks compliation of several KDE sources

Status in libxslt package in Ubuntu:
  Fix Committed

Bug description:
  gblic 2.26-0ubuntu1 which removed xlocale.h:  breaks compliation of
  several KDE sources, but libxslt still requires that header.

  Including so far, but maybe not limited to is autotests:

  kde4libs
  kio
  kopete

  with the error

  In file included from /usr/include/libxslt/xsltInternals.h:24:0,
   from /usr/include/libxslt/xsltutils.h:23,
   from 
/tmp/autopkgtest.U99BLh/build.W2l/kde4libs-4.14.34/kdoctools/kio_help.cpp:61:
  /usr/include/libxslt/xsltlocale.h:20:10: fatal error: xlocale.h: No such file 
or directory
   #include 
    ^~~
  compilation terminated.

  Confirmed also in kio package rebuild in our staging ppa

  https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-
  frameworks/+sourcepub/8240685/+listing-archive-extra

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1715599/+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 1714518] Re: GTK+3 doesn't show FUSE network shares in file chooser

Hi,

No - I think the default is to show everything accessible via POSIX
paths.

There is some code in GTK+2 that specifically verifies if volumes are
accessible via POSIX paths in local only mode, and adds them if they
are. This includes FUSE-mounted network shares.

in gtk/gtkfilechooserdefault.c: shortcuts_add_volumes() for example.

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

Title:
  GTK+3 doesn't show FUSE network shares in file chooser

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day. 
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares. 
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+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 1715621] [NEW] package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return co

2017-09-07 Thread mmesh

Public bug reported:

Tried to purge broken packages.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 linux-image-extra-4.10.0-27-generic: Remove
 linux-image-extra-4.10.0-30-generic: Remove
 initramfs-tools: Configure
 linux-firmware: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Sep  7 14:03:03 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2017-03-02 (188 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 failed 
to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited 
with return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check 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/1715621

Title:
  package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Tried to purge broken packages.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   linux-image-extra-4.10.0-27-generic: Remove
   linux-image-extra-4.10.0-30-generic: Remove
   initramfs-tools: Configure
   linux-firmware: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Sep  7 14:03:03 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2017-03-02 (188 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1715621/+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 1713984] Re: started raise network interfaces - times out

2017-09-07 Thread Davide

Sony VAIO VPCEB1M1E
Ubuntu 17.10
systemd 234-2ubuntu6 -> boot time: 47 sec
systemd 234-2ubuntu9 -> boot time: 72 sec

Is it normal?

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

Title:
  started raise network interfaces - times out

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  Ubuntu Budgie 17.10 Beta 1 32bit virtualbox install

  Test Case AutoResize

  choose to encrypt home drive, install all updates and non free codecs
  for the installation options

  On boot (and every subsequent boot) I see in the boot sequence

  started raise network interfaces
  networking.service

  this sits there for 1 minute 30 seconds before resuming.

  
  On login, fired up chromium and connected to google so the networking is ok.

  Question - why the 1 minute 30 seconds delay?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: Budgie:GNOME
  Date: Wed Aug 30 12:24:23 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha i386 
(20170829)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=cfd3c5b9-deb1-4d8f-8d6a-98996d260029 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713984/+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 1715633] [NEW] nvidia drivers...

2017-09-07 Thread Juan Carlos Carvajal Bermúdez

Public bug reported:

I'm trying to install the nvidia driver since days. I'm afraid that one
of the "displays" (the intel VGA one) is not working anymore. At least
it appears unclaimed with or without the nvidia driver.


*** ANY HELP IS HIGHLY APPREACIATED, THANK YOU ***


ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.26.13  Wed Aug 16 04:02:47 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME-Flashback:Unity
Date: Thu Sep  7 14:54:16 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
 nvidia-381, 381.26.13, 4.4.0-93-generic, x86_64: installed
 webcamstudio, 0.73, 3.13.0-101-generic, x86_64: installed
 webcamstudio, 0.73, 4.4.0-92-generic, x86_64: installed
 webcamstudio, 0.73, 4.4.0-93-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GconfCompiz:
 /apps/compiz-1/plugins:
   /apps/compiz-1/plugins/unityshell:
/apps/compiz-1/plugins/unityshell/screen0:
 /apps/compiz-1/plugins/unityshell/screen0/options:
  devices_option = 0
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1113]
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM108M [GeForce 840M] 
[1462:1113]
InstallationDate: Installed on 2015-01-23 (958 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Micro-Star International Co., Ltd. GP60 2PE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=da904324-ef1b-4408-8fe7-543a661e7464 ro nomodeset=1 splash quiet
SourcePackage: xorg
UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 5: Error: GLX is not available on the system
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16GHIMS.10B
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16GH
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GHIMS.10B:bd10/23/2014:svnMicro-StarInternationalCo.,Ltd.:pnGP602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GH:rvrREV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: GP60 2PE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
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 N/A
xserver.bootTime: Thu Sep  7 14:46:28 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.3

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


** Tags: amd64 apport-bug possible-manual-nvidia-install ubuntu xenial

** Description changed:

  I'm trying to install the nvidia driver since days. I'm afraid that one
  of the "displays" (the intel VGA one) is not working anymore. At least
  it appears unclaimed with or without the nvidia driver.
+ 
+ 
+ *** ANY HELP IS HIGHLY APPREACIATED, THANK YOU ***
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0:

[Touch-packages] [Bug 1715627] Re: apport-gtk crashed with SIGSEGV

2017-09-07 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1552577, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1715627/+attachment/4945870/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1715627/+attachment/4945872/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1715627/+attachment/4945876/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1715627/+attachment/4945877/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1715627/+attachment/4945878/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1715627/+attachment/4945879/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1715627/+attachment/4945880/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1552577
   apport-gtk crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with SIGSEGV

Status in apport package in Ubuntu:
  New

Bug description:
  Crash in Ubuntu 17.10 while other bug was trying to report

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: apport-gtk 2.20.7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashReports:
   640:1000:116:7008543:2017-09-07 14:19:56.744469881 +0200:2017-09-07 
14:19:57.744469881 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:123:116:21181674:2017-09-07 14:21:00.996262726 +0200:2017-09-07 
14:20:26.924434598 +0200:/var/crash/_usr_bin_gnome-shell.123.crash
   640:1000:116:922735:2017-09-07 14:21:32.340234887 +0200:2017-09-07 
14:21:31.056235982 +0200:/var/crash/_usr_bin_update-notifier.1000.crash
   640:1000:116:735360:2017-09-07 14:19:51.720478663 +0200:2017-09-07 
14:19:49.272482489 
+0200:/var/crash/_opt_teamviewer_tv_bin_TVGuiSlave.64.1000.crash
   640:1000:116:2252403:2017-09-07 14:17:46.189757823 +0200:2017-09-07 
14:17:47.189757823 
+0200:/var/crash/_usr_lib_x86_64-linux-gnu_unity_unity-panel-service.1000.crash
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Sep  7 14:19:52 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2
  SegvAnalysis:
   Segfault happened at: 0x7fa5738a5c99:mov(%rbx),%rdi
   PC (0x7fa5738a5c99) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1715627/+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 1714518] Re: GTK+3 doesn't show FUSE network shares in file chooser

I would also add that even though asking for GTK3 applications like
Chromium, Firefox, Thunderbird to call
gtk_file_chooser_set_local_only(FALSE) seems like an easy fix, it is
not:

when such applications then call for gtk_file_chooser_get_filename()
(and _get_filenames), they could end up with NULL for remote files that
are not fuse-mounted.

Similarly, gtk_file_chooser_get_uri() (and _get_uris) behaves
differently when local-only is set or not. With local-only set,
_get_uri() returns a native file:/// path, without it returns a normal
uri (smb:// ...)

My understanding of the "show FUSE mounts in local-only mode" is that it
helps numerous applications easily handle I/O with remote volumes
without having to use GIO everywhere.

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

Title:
  GTK+3 doesn't show FUSE network shares in file chooser

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day. 
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares. 
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+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 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

2017-09-07 Thread Eric Desrochers

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

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

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

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

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

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

** No longer affects: rsyslog (Ubuntu Yakkety)

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

Title:
  Add a trigger to reload rsyslog when a new configuration file is
  dropped in /etc/rsyslog.d

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Trusty:
  In Progress
Status in rsyslog source package in Xenial:
  In Progress
Status in rsyslog source package in Zesty:
  In Progress
Status in rsyslog source package in Artful:
  Fix Released
Status in rsyslog package in Debian:
  Fix Released

Bug description:
  [Impact]
  Servers or cloud instances will not log important messages after initial 
deployment. Manual reboot or restart of services is necessary to get expected 
behaviour.

  [Test Case]
  1) Install, enable and start haproxy
  2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed
  3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT 
created
  4) Restart rsyslog service
  5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created
  6) Restart haproxy service and observe that log now is filled with entries

  With the patched deb steps 3,4 and 6 becomes irrelevant and everything
  works out of the box.

  [Regression Potential]
  Minimal.

  This patch merges a patch from Debian where a trigger is added to the
  rsyslog package that fires when other debs drop files into
  /etc/rsyslog.d.

  
  [Original Bug Description]
  rsyslog should reload its configuration when other packages drop 
configuration in /etc/rsyslog.d

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337

  https://anonscm.debian.org/cgit/collab-
  maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+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 1715642] [NEW] displey problem

2017-09-07 Thread Nima Dolatabadi

Public bug reported:

when I run a program through wine that needs to reduce the resolution to 
windows xp basic (800 x 600), wine program stopping unexpectedly and my desktop 
changes resolution so every time I need to restart my ubuntu.
for more information pls check the photo I sent.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-93.116~14.04.1-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
 GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep  7 17:33:30 2017
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 4.4.0-93-generic, x86_64: installed
 nvidia-381, 381.22, 4.4.0-93-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d]
 NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d]
InstallationDate: Installed on 2016-12-06 (274 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Micro-Star International Co., Ltd. GE620/GE620DX/FX620DX
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=f01602a0-6076-4436-9a4b-e05e01b6cdc5 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16G5IMS V1.0F
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16G5
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16G5IMSV1.0F:bd05/26/2011:svnMicro-StarInternationalCo.,Ltd.:pnGE620/GE620DX/FX620DX:pvrTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16G5:rvrTobefilledbyO.E.M.:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrTobefilledbyO.E.M.:
dmi.product.name: GE620/GE620DX/FX620DX
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Sep  7 17:29:53 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3~trusty2

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


** Tags: amd64 apport-bug corruption possible-manual-nvidia-install trusty 
ubuntu

** Attachment added: "Screenshot from 2017-09-07 17:31:10.png"
   
https://bugs.launchpad.net/bugs/1715642/+attachment/4945927/+files/Screenshot%20from%202017-09-07%2017%3A31%3A10.png

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

Title:
  displey problem

Status in xorg package in Ubuntu:
  New

Bug description:
  when I run a program through wine that needs to reduce the resolution to 
windows xp basic (800 x 600), wine program stopping unexpectedly and my desktop 
changes resolution so every time I need to restart my ubuntu.
  for more information pls check the photo I sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116~14.04.1-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0u

[Touch-packages] [Bug 1715641] [NEW] network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc

Public bug reported:

network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet
doesn't depend on recent enough glibc

# cat debian/network-manager.substvars 
misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
misc:Depends=init-system-helpers (>= 1.18~)
misc:Pre-Depends=
shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)


# grep GLIBC_2.25 -r .
Binary file ./debian/tmp/usr/sbin/NetworkManager matches
Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
Binary file ./src/NetworkManager matches
Binary file ./src/nm-iface-helper matches
Binary file ./src/devices/wifi/tests/test-general matches
Binary file ./src/devices/tests/test-lldp matches
Binary file ./src/dhcp/tests/test-dhcp-utils matches
Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
Binary file ./src/tests/test-resolvconf-capture matches
Binary file ./src/tests/test-ip4-config matches
Binary file ./src/tests/test-ip6-config matches
Binary file ./src/tests/test-general matches
Binary file ./src/tests/test-systemd matches
Binary file ./src/tests/config/test-config matches
Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

# ldd /usr/sbin/NetworkManager   
/usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' 
not found (required by /usr/sbin/NetworkManager)

I will add a manual dep to network-manager but this is weird.

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

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

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

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

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

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

Title:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

Status in debhelper package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

  # cat debian/network-manager.substvars 
  misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
  misc:Depends=init-system-helpers (>= 1.18~)
  misc:Pre-Depends=
  shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)

  
  # grep GLIBC_2.25 -r .
  Binary file ./debian/tmp/usr/sbin/NetworkManager matches
  Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
  Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
  Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
  Binary file ./src/NetworkManager matches
  Binary file ./src/nm-iface-helper matches
  Binary file ./src/devices/wifi/tests/test-general matches
  Binary file ./src/devices/tests/test-lldp matches
  Binary file ./src/dhcp/tests/test-dhcp-utils matches
  Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
  Binary file ./src/tests/test-resolvconf-capture matches
  Binary file ./src/tests/test-ip4-config matches
  Binary file ./src/tests/test-ip6-config matches
  Binary file ./src/tests/test-general matches
  Binary file ./src/tests/test-systemd matches
  Binary file ./src/tests/config/test-config matches
  Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

  # ldd /usr/sbin/NetworkManager   
  /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version 
`GLIBC_2.25' not found (required by /usr/sbin/NetworkManager)

  I will add a manual dep to network-manager but this is weird.

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

-- 
Mailing l

[Touch-packages] [Bug 1715641] Re: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc

Inspecting with readelf I see this:

Version needs section '.gnu.version_r' contains 9 entries:
 Addr: 0x00010a80  Offset: 0x010a80  Link: 6 (.dynstr)
  00: Version: 1  File: ld-linux-x86-64.so.2  Cnt: 1
  0x0010:   Name: GLIBC_2.3  Flags: none  Version: 20
  0x0020: Version: 1  File: libuuid.so.1  Cnt: 1
  0x0030:   Name: UUID_1.0  Flags: none  Version: 18
  0x0040: Version: 1  File: libdl.so.2  Cnt: 1
  0x0050:   Name: GLIBC_2.2.5  Flags: none  Version: 13
  0x0060: Version: 1  File: libudev.so.1  Cnt: 1
  0x0070:   Name: LIBUDEV_183  Flags: none  Version: 8
  0x0080: Version: 1  File: libsystemd.so.0  Cnt: 1
  0x0090:   Name: LIBSYSTEMD_209  Flags: none  Version: 7
  0x00a0: Version: 1  File: libcurl-gnutls.so.4  Cnt: 1
  0x00b0:   Name: CURL_GNUTLS_3  Flags: none  Version: 6
  0x00c0: Version: 1  File: libgnutls.so.30  Cnt: 1
  0x00d0:   Name: GNUTLS_3_4  Flags: none  Version: 5
  0x00e0: Version: 1  File: libpthread.so.0  Cnt: 1
  0x00f0:   Name: GLIBC_2.2.5  Flags: none  Version: 3
  0x0100: Version: 1  File: libc.so.6  Cnt: 11
  0x0110:   Name: GLIBC_2.9  Flags: none  Version: 19
  0x0120:   Name: GLIBC_2.17  Flags: none  Version: 17
  0x0130:   Name: GLIBC_2.14  Flags: none  Version: 16
  0x0140:   Name: GLIBC_2.8  Flags: none  Version: 15
  0x0150:   Name: GLIBC_2.3.4  Flags: none  Version: 14
  0x0160:   Name: GLIBC_2.3.2  Flags: none  Version: 12
  0x0170:   Name: GLIBC_2.25  Flags: none  Version: 11
  0x0180:   Name: GLIBC_2.7  Flags: none  Version: 10
  0x0190:   Name: GLIBC_2.3  Flags: none  Version: 9
  0x01a0:   Name: GLIBC_2.2.5  Flags: none  Version: 4
  0x01b0:   Name: GLIBC_2.4  Flags: none  Version: 2


Maybe shlibdeps doesn't process .gnu.version_r sections?

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

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

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

Title:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

Status in binutils package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

  # cat debian/network-manager.substvars 
  misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
  misc:Depends=init-system-helpers (>= 1.18~)
  misc:Pre-Depends=
  shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)

  
  # grep GLIBC_2.25 -r .
  Binary file ./debian/tmp/usr/sbin/NetworkManager matches
  Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
  Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
  Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
  Binary file ./src/NetworkManager matches
  Binary file ./src/nm-iface-helper matches
  Binary file ./src/devices/wifi/tests/test-general matches
  Binary file ./src/devices/tests/test-lldp matches
  Binary file ./src/dhcp/tests/test-dhcp-utils matches
  Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
  Binary file ./src/tests/test-resolvconf-capture matches
  Binary file ./src/tests/test-ip4-config matches
  Binary file ./src/tests/test-ip6-config matches
  Binary file ./src/tests/test-general matches
  Binary file ./src/tests/test-systemd matches
  Binary file ./src/tests/config/test-config matches
  Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

  # ldd /usr/sbin/NetworkManager   
  /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version 
`GLIBC_2.25' not found (required by /usr/sbin/NetworkManager)

  I will add a manual dep to network-manager but this is weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1715641/+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 1715641] Re: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc

maybe Dpkg/Shlibs/Objdump.pm doesn't parse that section?

Or maybe objdump output changed, hence the parsing fails?

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

Title:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

Status in binutils package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

  # cat debian/network-manager.substvars 
  misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
  misc:Depends=init-system-helpers (>= 1.18~)
  misc:Pre-Depends=
  shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)

  
  # grep GLIBC_2.25 -r .
  Binary file ./debian/tmp/usr/sbin/NetworkManager matches
  Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
  Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
  Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
  Binary file ./src/NetworkManager matches
  Binary file ./src/nm-iface-helper matches
  Binary file ./src/devices/wifi/tests/test-general matches
  Binary file ./src/devices/tests/test-lldp matches
  Binary file ./src/dhcp/tests/test-dhcp-utils matches
  Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
  Binary file ./src/tests/test-resolvconf-capture matches
  Binary file ./src/tests/test-ip4-config matches
  Binary file ./src/tests/test-ip6-config matches
  Binary file ./src/tests/test-general matches
  Binary file ./src/tests/test-systemd matches
  Binary file ./src/tests/config/test-config matches
  Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

  # ldd /usr/sbin/NetworkManager   
  /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version 
`GLIBC_2.25' not found (required by /usr/sbin/NetworkManager)

  I will add a manual dep to network-manager but this is weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1715641/+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 1715641] Re: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc

I believe this is a bug in dpkg, since it does not parse 'Version
References:' paragraph of data.

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

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

Title:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

Status in binutils package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  Triaged
Status in glibc package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

  # cat debian/network-manager.substvars 
  misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
  misc:Depends=init-system-helpers (>= 1.18~)
  misc:Pre-Depends=
  shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)

  
  # grep GLIBC_2.25 -r .
  Binary file ./debian/tmp/usr/sbin/NetworkManager matches
  Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
  Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
  Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
  Binary file ./src/NetworkManager matches
  Binary file ./src/nm-iface-helper matches
  Binary file ./src/devices/wifi/tests/test-general matches
  Binary file ./src/devices/tests/test-lldp matches
  Binary file ./src/dhcp/tests/test-dhcp-utils matches
  Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
  Binary file ./src/tests/test-resolvconf-capture matches
  Binary file ./src/tests/test-ip4-config matches
  Binary file ./src/tests/test-ip6-config matches
  Binary file ./src/tests/test-general matches
  Binary file ./src/tests/test-systemd matches
  Binary file ./src/tests/config/test-config matches
  Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

  # ldd /usr/sbin/NetworkManager   
  /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version 
`GLIBC_2.25' not found (required by /usr/sbin/NetworkManager)

  I will add a manual dep to network-manager but this is weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1715641/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2017-09-07 Thread mc

@andrea-lazzarotto thank you for your information. I saw, that it is
fixed in 17.04, but I would like to stay on long-term-support version
and I still hope that it will be fixed for 16.04 too. I understand that
it cannot be fixed for all possible versions, but IMHO LTS version
should have this privilege.

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

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

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1715621] Re: package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code

2017-09-07 Thread 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/1715621

Title:
  package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Tried to purge broken packages.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   linux-image-extra-4.10.0-27-generic: Remove
   linux-image-extra-4.10.0-30-generic: Remove
   initramfs-tools: Configure
   linux-firmware: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Sep  7 14:03:03 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2017-03-02 (188 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1715621/+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 1714518] Re: GTK+3 doesn't show FUSE network shares in file chooser

Hello,

Here is a (different) patch to fix the problem on Artful's GTK 3.22.

The difference with the previous patch for GTK 3.18 is that there is now
an "Other Locations" entry in the sidebar, which displays mounts via
GtkPlacesView. This puts them in the correct place.

** Patch added: "Patch against GTK+3.22 for Artful"

https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1714518/+attachment/4946007/+files/gtk-3.22-add-fuse-mounts-in-placesview.debdiff

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

Title:
GTK+3 doesn't show FUSE network shares in file chooser

Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
In Progress

Bug description:
GTK+3 doesn't show FUSE network shares in file chooser - it used to do
so in GTK+2, and the GTK+3 documentation still mentions it should do
it.

I have reported the bug upstream and provided a patch to fix this. I
hope you'll be able and willing to include it to Ubuntu's GTK+3
package.

Thanks in advance.

Colin

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+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 1715641] Re: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc

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

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

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

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

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

Title:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

Status in binutils package in Ubuntu:
  Invalid
Status in debhelper package in Ubuntu:
  Invalid
Status in dpkg package in Ubuntu:
  Triaged
Status in glibc package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

  # cat debian/network-manager.substvars 
  misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
  misc:Depends=init-system-helpers (>= 1.18~)
  misc:Pre-Depends=
  shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)

  
  # grep GLIBC_2.25 -r .
  Binary file ./debian/tmp/usr/sbin/NetworkManager matches
  Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
  Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
  Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
  Binary file ./src/NetworkManager matches
  Binary file ./src/nm-iface-helper matches
  Binary file ./src/devices/wifi/tests/test-general matches
  Binary file ./src/devices/tests/test-lldp matches
  Binary file ./src/dhcp/tests/test-dhcp-utils matches
  Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
  Binary file ./src/tests/test-resolvconf-capture matches
  Binary file ./src/tests/test-ip4-config matches
  Binary file ./src/tests/test-ip6-config matches
  Binary file ./src/tests/test-general matches
  Binary file ./src/tests/test-systemd matches
  Binary file ./src/tests/config/test-config matches
  Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

  # ldd /usr/sbin/NetworkManager   
  /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version 
`GLIBC_2.25' not found (required by /usr/sbin/NetworkManager)

  I will add a manual dep to network-manager but this is weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1715641/+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 1715641] Re: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc

** Bug watch added: Debian Bug tracker #874585
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874585

** Also affects: dpkg (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874585
   Importance: Unknown
   Status: Unknown

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

Title:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

Status in binutils package in Ubuntu:
  Invalid
Status in debhelper package in Ubuntu:
  Invalid
Status in dpkg package in Ubuntu:
  Triaged
Status in glibc package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged
Status in dpkg package in Debian:
  Unknown

Bug description:
  network-manager built against glibc-2.26 requires GLIBC_2.25 symbol
  yet doesn't depend on recent enough glibc

  # cat debian/network-manager.substvars 
  misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~)
  misc:Depends=init-system-helpers (>= 1.18~)
  misc:Pre-Depends=
  shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 
2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 
3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), 
libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 
(>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 
(>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), 
libuuid1 (>= 2.16)

  
  # grep GLIBC_2.25 -r .
  Binary file ./debian/tmp/usr/sbin/NetworkManager matches
  Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches
  Binary file ./debian/network-manager/usr/sbin/NetworkManager matches
  Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper 
matches
  Binary file ./src/NetworkManager matches
  Binary file ./src/nm-iface-helper matches
  Binary file ./src/devices/wifi/tests/test-general matches
  Binary file ./src/devices/tests/test-lldp matches
  Binary file ./src/dhcp/tests/test-dhcp-utils matches
  Binary file ./src/dhcp/tests/test-dhcp-dhclient matches
  Binary file ./src/tests/test-resolvconf-capture matches
  Binary file ./src/tests/test-ip4-config matches
  Binary file ./src/tests/test-ip6-config matches
  Binary file ./src/tests/test-general matches
  Binary file ./src/tests/test-systemd matches
  Binary file ./src/tests/config/test-config matches
  Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches

  # ldd /usr/sbin/NetworkManager   
  /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version 
`GLIBC_2.25' not found (required by /usr/sbin/NetworkManager)

  I will add a manual dep to network-manager but this is weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1715641/+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 1715278] Re: [FFe] LXC 2.1

2017-09-07 Thread Hans Joachim Desserud

** Tags added: upgrade-software-version

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

Title:
  [FFe] LXC 2.1

Status in lxc package in Ubuntu:
  New

Bug description:
  LXC upstream just released LXC 2.1. This was meant to happen right
  before the Ubuntu feature freeze but we ran a bit late due to last
  minute bugfixes and cleanups.

  LXC 2.1 is generally backward compatible all the way down to LXC 1.0
  and higher, including at the ABI level (new symbols got added but none
  were changed or removed since LXC 1.0). So getting LXC 2.1 in Ubuntu
  17.04 wouldn't require any porting or changes to any downstream
  software in the archive.

  
  This release is meant as a transitional release between the 2.0 and 3.0 
series of LXC. A great number of configuration options were changed and a 
number of tools and commands have now been marked as deprecated. But all this 
without actually removing any of those, instead LXC 2.1 is issuing warnings and 
providing tooling to automatically convert the needed configuration files.

  This will give some time for our users to notice anything that needs
  updating and get it done before they upgrade to LXC 3.0 and things
  will stop working until they do those changes then.

  
  Detailed on the LXC 2.1 release are here: 
https://discuss.linuxcontainers.org/t/lxc-2-1-has-been-released/487

  We have packages ready to upload to artful and that have been used
  during development in our various PPAs. We therefore don't expect any
  significant issues with this hitting the Ubuntu archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1715278/+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 1714518] Re: GTK+3 doesn't show FUSE network shares in file chooser

2017-09-07 Thread Bug Watch Updater

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

** Changed in: gtk
   Importance: Unknown => Medium

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

Title:
  GTK+3 doesn't show FUSE network shares in file chooser

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day. 
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares. 
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+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 1713536] Re: udev: boot script does not trigger subsystem coldplug

Hello bugproxy, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu6
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-zesty

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

Title:
  udev: boot script does not trigger subsystem coldplug

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  subsystems udev rules are not processed on boot, thus resulting in missing 
devices on boot / before rootfs is mounted.

  [Solution]
  trigger udev subsystems and devices, in the initramfs, in that order.

  [Testcase]
  Boot s390x system with chzdev configured devices, and cio_ignore=all kernel 
command line parameter. The chzdev configured devices should still be 
discovered on boot.

  [Original Bug report]

  The udev initramfs-tools boot script does not trigger subsystem "add"
  uevents. As a result, udev rules that listen to subsystem "add" events
  are never activated. This problem exists on at least Ubuntu 16.04 and
  17.10.

  On s390, this results in a boot failure if the kernel is configured to
  start with an active device black list (kernel parameter
  cio_ignore=all,!condev). An example for an affected udev rule looks
  like this:

  ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
  RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
  /proc/cio_ignore'"

  A proposed fix would be:

  Modify /usr/share/initramfs-tools/scripts/init-top/udev:

  Replace line
  udevadm trigger --action=add
  with
  udevadm trigger --type=subsystems --action=add
  udevadm trigger --type=devices --action=add

  This would also be consistent with the steps that the systemd udev
  coldplug unit file performs (see /lib/systemd/system/systemd-udev-
  trigger.service).

  [Regression Potential]
  More udev rules will be now triggered, earlier, during initramfs stage of 
boot rather than post-pivot-root. However, this is inline with current rootfs 
behaviour and thus should not regress behaviour - simply some rules will get 
triggered earlier.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713536/+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 1710410] Re: Must run systemd-resolve --status before DNS resolving is operative

Hello WoJ, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu6
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-zesty

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

Title:
  Must run systemd-resolve --status before DNS resolving is operative

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  systemd-resolved is not enabled by default, therefore relies on dbus 
activation to become active and operatable and update resolvconf with resolved 
stub resolver

  [Fix]
  Enable systemd-resolved in the src:systemd package by default, even when 
libnss-resolve is not installed

  [Regression Potential]
  Minimal, simply the service is now started earlier in the boot, as part of 
the multi-user.targer, rather than awaiting for dbus activation from command 
line tool or the nss-resolved module.

  [Testcase]
  Debootstrap minimal zesty, without libnss-resolve package installed, boot and 
check that 127.0.0.53 is present in /etc/resolv.conf and that 
systemd-resolved.service is running

  Context: fresh install of zesty via

  debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1
  http://fr.archive.ubuntu.com/ubuntu

  ran via asystemd-nspawn with a static IP

  1. Upon first connexion, a ping fails:

  root@zesty1:~# ping google.com
  ping: google.com: Temporary failure in name resolution

  2. The content of /etc/resolv.conf:

  root@zesty1:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  3. When running systemd-resolve --status:

  root@zesty1:~# systemd-resolve --status
  Global
   DNS Servers: 8.8.8.8
    8.8.4.4
    2001:4860:4860::
    2001:4860:4860::8844
    DNSSEC NTA: 10.in-addr.arpa
    16.172.in-addr.arpa
    168.192.in-addr.arpa
  (...)

  4. After running this command the resolution is miraculously restored:

  root@zesty1:~# ping google.com
  PING google.com (172.217.22.142) 56(84) bytes of data.
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710410/+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 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload

Hello ChristianEhrhardt, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu6
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-zesty

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

Title:
  Systemd fails to serialize tasks correctly on daemon-reload

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  A unit with multiple Exec stanzas will loose execution state (which stanzas, 
out of multiple, have executed or not) upon systemd daemon-reload during the 
execution of these stanzas. This results in lost data/state, and units 
potentially failing to start/restart in unpredictable manner

  [Testcase]
  Setup a race of a unit with multiple exec stanzas (e.g. echo, sleep, echo) 
and execute daemon-reload whilst that is in progress. The execution state 
should persist across daemon-reload with all exec stanzas completing, in order, 
without duplicates.

  [Original Bug report]

  Hi,
  I was initially tracking down a libvirt bug [1], but happened to realize it 
is actually a general systemd issue.
  From there I got to file, discuss and test [2].

  For now I file the bug to be ablte to do my tests correctly, but if it
  really fixes the issue I'd like to suggest to fix it in the release -
  so better file upfront and do even my test patches right.

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
  [2]: https://github.com/systemd/systemd/issues/6299.

  [Regression Potential]
  Minimal, this is a fix for incorrect upstream behaviour which resolves a racy 
condition. The code changes are upstream reviewed cherry-pick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1702823/+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 1703393] Re: TCP offloads disabled by default

Hello Dimitri, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu6
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-zesty

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

Title:
  TCP offloads disabled by default

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  Regression in systemd v232 resulted in IPv4 TCP segmentation offload ("tso" 
in ethtool) to be disabled by default, yet previously it was enabled.

  [Fix]
  Backport upstream patch to fix the regression

  [Testcase]
  Use ethtool to verify that tso is enabled on e.g. e1000e card with fixed 
package.

  [Regression Potential]
  Link features were incorrectly initialised, this fix changes the 
initialisation code back to the correct default values. This changes the 
defaults back to what they are in all other releases. Users on zesty release 
may have been accustomed to the wrong defaults and may need to adjust .link 
files to e.g. disable tso if that is the behavior they want.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1703393/+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 1682154] Re: loginctl ignoring user given sessions IDs at command-line

Hello slodki, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu6
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-zesty

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

Title:
  loginctl ignoring user given sessions IDs at command-line

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  loginctl command does not process session IDs given on the command-line, like 
the documentation suggests. This makes it impossible to use simple command-line 
calls to check properties of a given session. 

  [Fix]
  Backport upstream patch to fix the issue

  [Testcase]
  Use loginctl command and specify multiple session IDs at the command-line and 
verify that details about these sessons are brought up in the output.

  [Regression Potential]
  Minimal, current behaviour is not sane at all, and it is a typpo fix from '1' 
to 'i' meaning that first argument was always used, instead of the current 
iterated one.

  
  Kubuntu zesty, 232-21ubuntu2

  See upstream bug https://github.com/systemd/systemd/issues/5733 with
  patch attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1682154/+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 1449001] Re: systemd-resolved: please do not use Google public DNS by default

Hello Malcolm, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu6
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-zesty

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

Title:
  systemd-resolved: please do not use Google public DNS by default

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in the 
absence of other configured DNS servers.

  systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
  installed by default and will behave in this way if enabled by the
  user.

  $ cat /etc/systemd/resolved.conf
  (...)
  # Entries in this file show the compile time defaults.
  (...)
  #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

  This raises privacy concerns since in the event of accidental
  misconfiguration DNS queries will be sent unencrypted across the
  internet, and potentially also security concerns given systemd-
  resolved does not perform DNSSEC validation and is not particularly
  well hardened against malicious responses e.g. from a MITM
  (http://www.openwall.com/lists/oss-security/2014/11/12/5).

  I believe that it would be better to fail safe if no DNS server is
  configured -- i.e. have DNS lookups fail; it's better that the user is
  aware of their misconfiguration, rather than silently sending their
  queries to Google.  The user can intentionally opt to use Google
  public DNS if they wish.

  [Testcase]
  Steps to reproduce:
  1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
  2. Reboot, or otherwise clear relevant state
  3. sudo service systemd-resolved start
  4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
  5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by 
default), observe that DNS lookups probably still work, and queries are being 
sent to one of Google's servers

  Possible workaround/bugfix: ship a resolved.conf which clears the
  FallbackDNS parameter.

  [Solution]
  In ubuntu, we disable fallback DNS at build time, via build system 
configuration flags.

  This issue has been discussed in the Debian BTS
  (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My
  interpretation of the Debian package maintainer's position is that a
  user concerned with the privacy implications shouldn't let systemd get
  into a state where it uses the fallback DNS servers (quoting Marco
  d'Itri: "Short summary: have a resolv.conf file or use DHCP").  I
  would argue that it's safest not to have fallback DNS servers
  configured at all by default.

  [Regression Potential]
  Missconfigured networks, that do not have a DNS server would previously 
magically work due to having Google DNS preconfigured regardless. With this 
change, such network configurations will fail to work, and one will have to 
properly fix network config to point at the right/existing name server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1449001/+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 1715716] [NEW] package gnome-icon-theme (not installed) failed to install/upgrade: unable to open '/usr/share/icons/gnome/48x48/status/battery-caution.png.dpkg-new': Operation no

2017-09-07 Thread James Lipscomb

Public bug reported:

Routine Software Update.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gnome-icon-theme (not installed)
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering:
 gdebi-core:amd64: Install
 gnome-icon-theme:amd64: Install
 gdebi:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Aug 31 18:31:01 2017
DuplicateSignature:
 package:gnome-icon-theme:(not installed)
 Unpacking gnome-icon-theme (3.12.0-2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/gnome-icon-theme_3.12.0-2_all.deb (--unpack):
  unable to open 
'/usr/share/icons/gnome/48x48/status/battery-caution.png.dpkg-new': Operation 
not permitted
ErrorMessage: unable to open 
'/usr/share/icons/gnome/48x48/status/battery-caution.png.dpkg-new': Operation 
not permitted
InstallationDate: Installed on 2016-08-29 (373 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gnome-icon-theme
Title: package gnome-icon-theme (not installed) failed to install/upgrade: 
unable to open 
'/usr/share/icons/gnome/48x48/status/battery-caution.png.dpkg-new': Operation 
not permitted
UpgradeStatus: Upgraded to zesty on 2017-04-18 (141 days ago)

** Affects: gnome-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package gnome-icon-theme (not installed) failed to install/upgrade:
  unable to open '/usr/share/icons/gnome/48x48/status/battery-
  caution.png.dpkg-new': Operation not permitted

Status in gnome-icon-theme package in Ubuntu:
  New

Bug description:
  Routine Software Update.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gnome-icon-theme (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   gdebi-core:amd64: Install
   gnome-icon-theme:amd64: Install
   gdebi:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Aug 31 18:31:01 2017
  DuplicateSignature:
   package:gnome-icon-theme:(not installed)
   Unpacking gnome-icon-theme (3.12.0-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/gnome-icon-theme_3.12.0-2_all.deb (--unpack):
unable to open 
'/usr/share/icons/gnome/48x48/status/battery-caution.png.dpkg-new': Operation 
not permitted
  ErrorMessage: unable to open 
'/usr/share/icons/gnome/48x48/status/battery-caution.png.dpkg-new': Operation 
not permitted
  InstallationDate: Installed on 2016-08-29 (373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gnome-icon-theme
  Title: package gnome-icon-theme (not installed) failed to install/upgrade: 
unable to open 
'/usr/share/icons/gnome/48x48/status/battery-caution.png.dpkg-new': Operation 
not permitted
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (141 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1715716/+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 1715716] Re: package gnome-icon-theme (not installed) failed to install/upgrade: unable to open '/usr/share/icons/gnome/48x48/status/battery-caution.png.dpkg-new': Operation not

2017-09-07 Thread 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 gnome-icon-theme in
Ubuntu.
https://bugs.launchpad.net/bugs/1715716

Title:
  package gnome-icon-theme (not installed) failed to install/upgrade:
  unable to open '/usr/share/icons/gnome/48x48/status/battery-
  caution.png.dpkg-new': Operation not permitted

Status in gnome-icon-theme package in Ubuntu:
  New

Bug description:
  Routine Software Update.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gnome-icon-theme (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   gdebi-core:amd64: Install
   gnome-icon-theme:amd64: Install
   gdebi:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Aug 31 18:31:01 2017
  DuplicateSignature:
   package:gnome-icon-theme:(not installed)
   Unpacking gnome-icon-theme (3.12.0-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/gnome-icon-theme_3.12.0-2_all.deb (--unpack):
unable to open 
'/usr/share/icons/gnome/48x48/status/battery-caution.png.dpkg-new': Operation 
not permitted
  ErrorMessage: unable to open 
'/usr/share/icons/gnome/48x48/status/battery-caution.png.dpkg-new': Operation 
not permitted
  InstallationDate: Installed on 2016-08-29 (373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gnome-icon-theme
  Title: package gnome-icon-theme (not installed) failed to install/upgrade: 
unable to open 
'/usr/share/icons/gnome/48x48/status/battery-caution.png.dpkg-new': Operation 
not permitted
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (141 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1715716/+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 1715719] [NEW] systemd v232+ journals aren't compatible with journalctrl from 229

2017-09-07 Thread Ken VanDine

Public bug reported:

systemd v232+ journals aren't compatible with journalctrl from 229

This normally isn't a problem, but in trying to create a snap for gnome-
logs I've run into a situation where we need to build the snap for 16.04
which has libsystemd0=229.  This snap works fine if the host is running
16.04 as well.  But on an artful host, the snap fails to access the
journal.  I've tested backporting v232 from zesty to xenial and building
my snap with libsystem0 232.  This works fine on 16.04 and 17.10 hosts.

@xnox suggested v232+ journals are built with more features enabled.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Assignee: Dimitri John Ledkov (xnox)
 Status: New

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  systemd v232+ journals aren't compatible with journalctrl from 229

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd v232+ journals aren't compatible with journalctrl from 229

  This normally isn't a problem, but in trying to create a snap for
  gnome-logs I've run into a situation where we need to build the snap
  for 16.04 which has libsystemd0=229.  This snap works fine if the host
  is running 16.04 as well.  But on an artful host, the snap fails to
  access the journal.  I've tested backporting v232 from zesty to xenial
  and building my snap with libsystem0 232.  This works fine on 16.04
  and 17.10 hosts.

  @xnox suggested v232+ journals are built with more features enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1715719/+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 1715719] Re: systemd v232+ journals aren't compatible with journalctrl from 229

2017-09-07 Thread Ken VanDine

** Description changed:

- systemd v232+ journals aren't compatible with journalctrl from 229
+ In my attempt to snap gnome-logs, I've run into an issue where gnome-
+ logs fails to get the journal when run on an artful host.  The snap is
+ built in a xenial chroot against xenial + gnome-3-24 backports PPA.  The
+ same snap does work when run on a 16.04 host.
  
- This normally isn't a problem, but in trying to create a snap for gnome-
- logs I've run into a situation where we need to build the snap for 16.04
- which has libsystemd0=229.  This snap works fine if the host is running
- 16.04 as well.  But on an artful host, the snap fails to access the
- journal.  I've tested backporting v232 from zesty to xenial and building
- my snap with libsystem0 232.  This works fine on 16.04 and 17.10 hosts.
+ artful has libsystemd0 234 and xenial has libsystemd0 229.  I took a
+ stab at building libsystemd0 232 on xenial then build the snap with
+ libsystemd0 232.  The resulting snap works fine on 16.04 and 17.10
+ hosts.
+ 
+ To summarize, we need a libsystemd0 built for xenial bundled in the
+ gnome-logs snap that is compatible with the running systemd on the host.
+ The basic rebuild of 232 for xenial is compatible with systemd from
+ xenial through artful.  But we want to be sure backporting that in a
+ supported PPA is not a bad idea.  Ideally we would just cherry pick
+ whatever 229 is lacking in our PPA.
  
  @xnox suggested v232+ journals are built with more features enabled.

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

Title:
  systemd v232+ journals aren't compatible with journalctrl from 229

Status in systemd package in Ubuntu:
  New

Bug description:
  In my attempt to snap gnome-logs, I've run into an issue where gnome-
  logs fails to get the journal when run on an artful host.  The snap is
  built in a xenial chroot against xenial + gnome-3-24 backports PPA.
  The same snap does work when run on a 16.04 host.

  artful has libsystemd0 234 and xenial has libsystemd0 229.  I took a
  stab at building libsystemd0 232 on xenial then build the snap with
  libsystemd0 232.  The resulting snap works fine on 16.04 and 17.10
  hosts.

  To summarize, we need a libsystemd0 built for xenial bundled in the
  gnome-logs snap that is compatible with the running systemd on the
  host.  The basic rebuild of 232 for xenial is compatible with systemd
  from xenial through artful.  But we want to be sure backporting that
  in a supported PPA is not a bad idea.  Ideally we would just cherry
  pick whatever 229 is lacking in our PPA.

  @xnox suggested v232+ journals are built with more features enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1715719/+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 1709536] Missing SRU information

Thanks for uploading the fix for this bug report to -proposed.  However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process.  You can find full details at
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially
this bug is missing some of the following: a statement of impact, a test
case and details regarding the regression potential.  Thanks in advance!

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

Title:
  snapd 2.26.14 on ubuntu-core won't start in containers anymore

Status in Snap Layer:
  New
Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Artful:
  Fix Released

Bug description:
  It looks like snapd in ubuntu-core (2.26.14 here) has been modified to
  use a negative Nice value in systemd. Systemd seems to treat a failure
  to apply the requested Nice value as critical to unit startup.

  Unprivileged LXD containers do not allow the use of negative nice
  values as those are restricted to the real root user. I believe the
  optimal fix would be for systemd to ignore permission errors when
  attempting to setup such custom nice values in containers but if that
  can't be resolved quickly, then it means that snapd will now fail to
  start inside containers.

  
  Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, 
code=exited, status=201/NICE
  Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state.
  Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 
'exit-code'.

  
  I have confirmed that setting up a unit override by hand which sets Nice=0 
does resolve the problem, confirming that the negative Nice value is the 
problem (snapd.service has Nice=-5 here).

To manage notifications about this bug go to:
https://bugs.launchpad.net/layer-snap/+bug/1709536/+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 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot

Hello Josh, or anyone else affected,

Accepted ntp into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p4+dfsg-
3ubuntu5.7 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ntp (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race
  leaving ntp dead on reboot

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Fix Committed
Status in ntp source package in Zesty:
  Fix Released
Status in ntp source package in Artful:
  Fix Released
Status in ntp package in Debian:
  Fix Released

Bug description:
  [Impact]

   * The locks of ntpdate the ifup hook and the ntp service start do not 
 match, therefore installation of ntpdate can harmstring the start of 
 ntp at boot.

   * The change ports back what Debian added later and we merged in Zesty.
 It does two things:
 1. it makes the lock paths actually match
 2. it drops the usage of lockfile-progs which never was a dependency 
and uses flock directly.
 
  [Test Case]

   * Prep
 - Taking a Xenial VM (to avoid all the time set rejects in a container 
   from cluttering the view)
 - Installing ntp
 - Check status of ntp
 - Reboot the VM
 - Check status of ntp
   # Until now all should be good
   * Break it
 - install ntpdate
 - reboot
 - Check status of ntp
   - It (likely) is failed for "blocked known address being busy"
 - This is somewhat of a race, adding more extra network devices in 
   libvirt to your guest increases the chance if you can't reproduce.
   * Fix it
 - install the fix from proposed (or the ppa in c#14)
 - reboot
 - ntp is now running correctly after reboot

  [Regression Potential]

   * It was locking before as well, just on a lock never contended and 
 potentially failing to have the lockfile-progs calls available.
 Due to the change the init now of ntp can take longer (until the 
 ntpdate calls are out of the way)
   * For a fallback in case locking goes crazy in unexpected ways the 
 timeout of the flock (180s) is intentionally not checked for bad return 
 codes. That way in those cases ntp still tries to initialize and if it 
 fails for an ntpdate blocking the port it didn't "loose" anything by 
 being stalled.
 Therefor I'd consider that the actual regression potential rather 
 low  and safe.

  [Other Info]
   
   * This is kind of a bug-zombie, fixed in zesty but resurrected in Debian 
 (and Ubuntu by our merge) due to the addition of a native systemd 
 service. Now that Dev is finally (again) good it is time to tackle the 
 Xenial SRU.

  ---

  ntpdate and ntp conflict on the NTP well-known-socket. If ntp and
  ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there
  are 2 static interfaces configured, most often we find that ntpd is
  not running after a reboot.

  When the ntp service is started by systemd, ntp fails to bind the NTP
  socket because ntpdate is running in the background. It's intended
  that ntp and ntpdate try to avoid this conflict with a lock file, but
  the locking mechanism was changed in ntpdate.if-up (from lockfile to
  flock), but it was not changed in ntp.init. Previously the file
  locking prevented ntp from trying to start when ntpdate was running.
  Not any more.

  Having multiple interfaces causes a much longer period of the socket
  being unavailable, because the 2 ntpdate processes will get serialized
  by the lock, while the ntp service is looking for a different lock, so
  it just plows right in.  Attempts by netdate.if-up to stop and start
  ntp seem to overlap and when the final start is invoked, systemd seems
  to thing ntp is already running, though it has failed.

  In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made:
    debian/ntpdate.if

[Touch-packages] [Bug 1715131] Missing SRU information

Thanks for uploading the fix for this bug report to -proposed.  However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process.  You can find full details at
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially
this bug is missing some of the following: a statement of impact, a test
case and details regarding the regression potential.  Thanks in advance!

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

Title:
  networkd add support for Bridge Priority, AgeingTimeSec and
  DefaultPVID

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  networkd add support for Bridge Priority, AgeingTimeSec and
  DefaultPVID

  cherrypick these settings for better supportability of networkd on
  xenial with netplan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1715131/+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 1600000] Missing SRU information

Thanks for uploading the fix for this bug report to -proposed.  However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process.  You can find full details at
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially
this bug is missing some of the following: a statement of impact, a test
case and details regarding the regression potential.  Thanks in advance!

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

Title:
  libnss-resolve treats two trailing dots on a domain name incorrectly

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM  
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ resolve dns/ dns/' 
/etc/nsswitch.conf 
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ dns/ resolve dns/' 
/etc/nsswitch.conf 
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM  
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$ 

  This is responsible for the new regression in glibc:

  --
  FAIL: posix/tst-getaddrinfo5
  original exit status 1
  resolving "localhost." worked, proceeding to test
  resolving "localhost.." failed, test passed
  resolving "www.gnu.org." worked, proceeding to test
  resolving "www.gnu.org.." worked, test failed
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/160/+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 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

2017-09-07 Thread Doug McMahon

This is a screenshot of the recoverable hang mentioned above, just sits
there forever. crtl+c bumps it going, then 3 lines & a proper
shutdown/resart

** Attachment added: "IMG_20170907_104227.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939/+attachment/4946144/+files/IMG_20170907_104227.jpg

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939/+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 1715453] Re: compis makes desktop slow

** Information type changed from Private Security to Public

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

Title:
  compis makes desktop slow

Status in xorg package in Ubuntu:
  New

Bug description:
  i need more than 60 sec for start X... ?!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Sep  6 19:57:20 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:0655]
  InstallationDate: Installed on 2016-11-02 (307 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Notebook W65_67SZ
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed 
root=UUID=7aaeecb0-efd9-4bcf-a22b-296c637d59ed ro quiet splash plymouth:debug 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd02/26/2014:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715453/+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 1714943] Re: com.ubuntu-apport-gtk-root

Thank you for taking the time to report this bug and helping to
 make Ubuntu better. Unfortunately we can't fix it, because your description did
n't include enough information. You may find it helpful to read 'How to report b
ugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be 
grateful if you would then provide a more complete description of the problem.  
We have instructions on debugging some types of problems at http://wiki.ubuntu.c
om/DebuggingProcedures. At a minimum, we need: 1. the specific steps or actions 
you took that caused you to encounter the problem, 2. the behavior you expected,
 and 3. the behavior you actually encountered (in as much detail as possible). T
hanks!

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

** Information type changed from Private Security to Public

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

Title:
  com.ubuntu-apport-gtk-root

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  O programa responsável por relatar erros do sistema parece estar
  instalado e gerenciado de forma diferente da original.

  The program responsible for reporting system errors appears to be
  installed and generated differently from the original.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83
  Uname: Linux 4.4.0-94-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep  4 09:09:54 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-08-30 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic 
root=UUID=60cc7eaf-5cb0-4280-87d6-deb942ed3dbf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
  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: Mon Sep  4 09:01:45 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714943/+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 1714590] Re: dpkg

** Information type changed from Private Security to Public

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

Title:
  dpkg

Status in xorg package in Ubuntu:
  New

Bug description:
  Não consigo instalar de forma satisfatória o aplicativo e nem
  desinstalá-lo completamente. O que está ocorrendo?

  
  I can not install the application satisfactorily and can not uninstall it 
completely. What is happening?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83
  Uname: Linux 4.4.0-94-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Sep  1 17:59:34 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-08-30 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic 
root=UUID=60cc7eaf-5cb0-4280-87d6-deb942ed3dbf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
  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: Fri Sep  1 17:36:23 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714590/+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 1702319] Re: package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

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

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

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

Title:
  package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 127

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I tried so many alternatives i didn't found relevant bug to fix it.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CrashReports: 600:0:116:180223:2017-07-04 20:24:38.287366390 +0530:2017-07-04 
20:24:39.287366390 +0530:/var/crash/apport.0.crash
  Date: Tue Jul  4 20:24:38 2017
  DpkgTerminalLog:
   Preparing to unpack .../apport_2.20.1-0ubuntu2.4_all.deb ...
   /var/lib/dpkg/info/apport.prerm: 19: /var/lib/dpkg/info/apport.prerm: 
pyclean: not found
   dpkg: error processing archive 
/var/cache/apt/archives/apport_2.20.1-0ubuntu2.4_all.deb (--unpack):
subprocess installed pre-removal script returned error exit status 127
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.5
   Preparing to unpack .../apport_2.20.1-0ubuntu2.4_all.deb ...
   /var/lib/dpkg/info/apport.prerm: 19: /var/lib/dpkg/info/apport.prerm: 
pyclean: not found
   dpkg: error processing archive 
/var/cache/apt/archives/apport_2.20.1-0ubuntu2.4_all.deb (--unpack):
subprocess installed pre-removal script returned error exit status 127
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
  InstallationDate: Installed on 2017-03-30 (95 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1702319/+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 1714521] Re: package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

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

** Information type changed from Private Security to Public

** This bug has been marked a duplicate of bug 1702319
   package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127

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

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

Status in apport package in Ubuntu:
  New

Bug description:
  Hi,i m not that mch technical expert in linux system.i try to update
  and upgrade the package of my ubuntu machine and its showing error.pls
  check.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportLog:
   ERROR: apport (pid 5509) Thu Aug 31 19:15:40 2017: called for pid 4324, 
signal 6, core limit 0
   ERROR: apport (pid 5509) Thu Aug 31 19:15:40 2017: executable: 
/usr/bin/unity-scope-loader (command line "/usr/bin/unity-scope-loader 
applications/applications.scope applications/scopes.scope commands.scope")
   ERROR: apport (pid 5509) Thu Aug 31 19:15:40 2017: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 5509) Thu Aug 31 19:15:43 2017: wrote report 
/var/crash/_usr_bin_unity-scope-loader.1000.crash
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CrashReports:
   640:1000:116:54657:2017-08-31 19:15:44.251554445 +0530:2017-08-31 
19:26:44.559352537 +0530:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:116:1540867:2017-08-31 19:15:43.011923730 +0530:2017-08-31 
19:15:43.555761915 +0530:/var/crash/_usr_bin_unity-scope-loader.1000.crash
   600:0:116:315855:2017-09-01 19:38:18.263080358 +0530:2017-09-01 
19:38:19.263080358 +0530:/var/crash/apport.0.crash
  Date: Fri Sep  1 19:38:19 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-08-31 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1714521/+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 1713041] Re: Ubuntu Software app doesn't display

** Information type changed from Private Security to Public

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

Title:
  Ubuntu Software app doesn't display

Status in xorg package in Ubuntu:
  New

Bug description:
  Release: 17.04
  Version of package: Zesty (?)

  I am unable to open the Ubuntu Software application.
  The display after selecting it is the working symbol, however the window 
doesn't display.

  Please advise on a remedy.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Aug 25 12:53:06 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-06-14 (72 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 3542
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=e1a860ac-fd98-4751-9bea-7a369a86fe22 ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0V25HW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0V25HW:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1713041/+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 1713528] Re: PCI/internal sound card not detected

** Information type changed from Private Security to Public

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller (rev 01)
Subsystem: Lenovo NM10/ICH7 Family High Definition Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 28
Memory at feaf8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Aug 28 11:53:56 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-28 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5HKT43AUS
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: LENOVO
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr5HKT43AUS:bd09/07/2009:svnLENOVO:pn7298E1A:pvrThinkCentreM58e:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 7298E1A
  dmi.product.version: ThinkCentre M58e
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1713528/+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 1707222] Re: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean

This bug was fixed in the package cloud-init - 0.7.9-267-g922c3c5c-
0ubuntu1

---
cloud-init (0.7.9-267-g922c3c5c-0ubuntu1) artful; urgency=medium

  * New upstream snapshot.
- Ec2: only attempt to operate at local mode on known platforms.
  (LP: #1715128)
- Use /run/cloud-init for tempfile operations. (LP: #1707222)
- ds-identify: Make OpenStack return maybe on arch other than intel.
  (LP: #1715241)
- tests: mock missed openstack metadata uri network_data.json
  [Chad Smith] (LP: #1714376)
- relocate tests/unittests/helpers.py to cloudinit/tests
  [Lars Kellogg-Stedman]
- tox: add nose timer output [Joshua Powers]
- upstart: do not package upstart jobs, drop ubuntu-init-switch module.
- tests: Stop leaking calls through unmocked metadata addresses
  [Chad Smith] (LP: #1714117)

 -- Scott Moser   Thu, 07 Sep 2017 16:59:04 -0400

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  usage of /tmp during boot is not safe due to systemd-tmpfiles-clean

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Earlier this week on Zesty on Azure I saw a cloud-init failure in its 
'mount_cb' function.
  That function esentially does:
   a.) make a tmp directory for a mount point
   b.)  mount some filesystem to that mount point
   c.) call a function
   d.) unmount the directory

  What I recall was that access to a file inside the mount point failed during 
'c'.
  This seems possible as systemd-tmpfiles-clean may be running at the same time 
as cloud-init (cloud-init.service in this example).

  
  It seems that this service basically inhibits *any* other service from using 
tmp files.
  It's ordering statements are only:

After=local-fs.target time-sync.target
Before=shutdown.target

  So while in most cases only services that run early in the boot
  process like cloud-init will be affected, any service could have its
  tmp files removed.  this service could take quite a long time to run
  if /tmp/ had been filled with lots of files in the previous boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1707222/+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 1715749] [NEW] Intermittent black screen on HP EliteBook 840 G1

2017-09-07 Thread Michael von Glasow

Public bug reported:

Occasionally, the internal laptop display goes black for a few seconds,
then comes back to life. The external display stays on. It looks as if
power management were kicking in by error but affecting only the
internal display.

When I’m working with the external display, I need to move the mouse
into the area managed by the internal display to wake it up again; else
it seems to remain black (though I haven’t tested that behavior
thoroughly).

Most tests with the external display were made with the port replicator
and an external display plugged into one of the DP ports via a DP–DVI
adapter. I cannot tell for sure what the behavior is with the external
display plugged directly into the laptop.

The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
finally moved to the EliteBook 840 G1.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Sep  8 00:53:24 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-12-09 (1002 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  New

Bug description:
  Occasionally, the internal laptop display goes black for a few
  seconds, then comes back to life. The external display stays on. It
  looks as if power management were kicking in by error but affecting
  only the internal display.

  When I’m working with the external display, I need to move the mouse
  into the area managed by the internal display to wake it up again;
  else it seems to remain black (though I haven’t tested that behavior
  thoroughly).

  Most tests with the external display were made with the port
  replicator and an external display plugged into one of the DP ports
  via a DP–DVI adapter. I cannot tell for sure what the behavior is with
  the external display plugged directly into the laptop.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 1715750] [NEW] cursor not blinking when editing a file

2017-09-07 Thread Facundo Batista

Public bug reported:

Happens with a lot of different files, if not all.

You move the cursor around, maybe it blinks a couple of times, then it
disappears.

I could record a video, if needed, to show it.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: vim-gnome 2:8.0.0095-1ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Sep  7 19:01:51 2017
InstallationDate: Installed on 2016-07-29 (404 days ago)
InstallationMedia: Ubuntu 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.
PackageArchitecture: all
SourcePackage: vim
UpgradeStatus: Upgraded to zesty on 2017-07-09 (60 days ago)

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


** Tags: amd64 apport-bug zesty

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

Title:
  cursor not blinking when editing a file

Status in vim package in Ubuntu:
  New

Bug description:
  Happens with a lot of different files, if not all.

  You move the cursor around, maybe it blinks a couple of times, then it
  disappears.

  I could record a video, if needed, to show it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: vim-gnome 2:8.0.0095-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Sep  7 19:01:51 2017
  InstallationDate: Installed on 2016-07-29 (404 days ago)
  InstallationMedia: Ubuntu 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.
  PackageArchitecture: all
  SourcePackage: vim
  UpgradeStatus: Upgraded to zesty on 2017-07-09 (60 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1715750/+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 1715753] [NEW] ln --relative broken on u14, works on u16

2017-09-07 Thread Scott Mcdermott

Public bug reported:

in ubuntu14, the behavior of "ln --relative" seems to be quite broken.
on ubuntu 16 it works as expected.  can we please backport whatever fix
from u16 or update coreutils? 8.15 is where they started including the
'realpath' binary, maybe they fixed "ln --relative" too.

u14 INCORRECT:

$ loop=0; nloops=4; base=/tmp/lntest; rm -rf $base/ && mkdir -p $base/dir &&
touch $base/dir/file && while ((loop++ < nloops)); do ln -frs $base/dir/file 
$base/link; readlink -f $base/link; sleep 1; done
/tmp/lntest/dir/file
/tmp/lntest/file
/tmp/lntest/dir/file
/tmp/lntest/file

u16 CORRECT:

$ loop=0; nloops=4; base=/tmp/lntest; rm -rf $base/ && mkdir -p $base/dir &&
touch $base/dir/file && while ((loop++ < nloops)); do ln -frs $base/dir/file 
$base/link; readlink -f $base/link; sleep 1; done
/tmp/lntest/dir/file
/tmp/lntest/dir/file
/tmp/lntest/dir/file
/tmp/lntest/dir/file

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

** Description changed:

  in ubuntu14, the behavior of "ln --relative" seems to be quite broken.
  on ubuntu 16 it works as expected.  can we please backport whatever fix
  from u16 or update coreutils? 8.15 is where they started including the
  'realpath' binary, maybe they fixed "ln --relative" too.
  
  u14 INCORRECT:
  
- $ loop=0; nloops=4; base=/tmp/lntest; rm -rf $base/ && mkdir -p $base/dir && 
touch $base/dir/file && while ((loop++ < nloops)); do ln <-frs $base/dir/file 
$base/link; readlink -f $base/link; sleep 1; done
+ $ loop=0; nloops=4; base=/tmp/lntest; rm -rf $base/ && mkdir -p $base/dir &&
+ touch $base/dir/file && while ((loop++ < nloops)); do ln -frs $base/dir/file 
$base/link; readlink -f $base/link; sleep 1; done
  /tmp/lntest/dir/file
  /tmp/lntest/file
  /tmp/lntest/dir/file
  /tmp/lntest/file
  
  u16 CORRECT:
  
- $ loop=0; nloops=4; base=/tmp/lntest; rm -rf $base/ && mkdir -p $base/dir && 
touch $base/dir/file && while ((loop++ < nloops)); do ln <-frs $base/dir/file 
$base/link; readlink -f $base/link; sleep 1; done
+ $ loop=0; nloops=4; base=/tmp/lntest; rm -rf $base/ && mkdir -p $base/dir &&
+ touch $base/dir/file && while ((loop++ < nloops)); do ln -frs $base/dir/file 
$base/link; readlink -f $base/link; sleep 1; done
  /tmp/lntest/dir/file
  /tmp/lntest/dir/file
  /tmp/lntest/dir/file
  /tmp/lntest/dir/file

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

Title:
  ln --relative broken on u14, works on u16

Status in coreutils package in Ubuntu:
  New

Bug description:
  in ubuntu14, the behavior of "ln --relative" seems to be quite broken.
  on ubuntu 16 it works as expected.  can we please backport whatever
  fix from u16 or update coreutils? 8.15 is where they started including
  the 'realpath' binary, maybe they fixed "ln --relative" too.

  u14 INCORRECT:

  $ loop=0; nloops=4; base=/tmp/lntest; rm -rf $base/ && mkdir -p $base/dir &&
  touch $base/dir/file && while ((loop++ < nloops)); do ln -frs $base/dir/file 
$base/link; readlink -f $base/link; sleep 1; done
  /tmp/lntest/dir/file
  /tmp/lntest/file
  /tmp/lntest/dir/file
  /tmp/lntest/file

  u16 CORRECT:

  $ loop=0; nloops=4; base=/tmp/lntest; rm -rf $base/ && mkdir -p $base/dir &&
  touch $base/dir/file && while ((loop++ < nloops)); do ln -frs $base/dir/file 
$base/link; readlink -f $base/link; sleep 1; done
  /tmp/lntest/dir/file
  /tmp/lntest/dir/file
  /tmp/lntest/dir/file
  /tmp/lntest/dir/file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1715753/+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 1715761] [NEW] My sound system does not work no matter what.

2017-09-07 Thread Joshua Sulentic

Public bug reported:

My computer originally ran Windows 10.  I recently put Ubuntu on it,
thinking it would go onto my thumb drive, but it didn't.  It has messed
up my login process, but I can still eventually get to Ubuntu.  But I
try playing videos and I cannot hear the audio, from YouTube and
advertisements.  My computer has been designed to run B&O Play, but
maybe downloading a new OS screwed it up.

1) Ubuntu 17.04
2) Unknown
3) Play any sound requested
4) Silence

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   legend 1761 F...m pulseaudio
 /dev/snd/controlC0:  legend 1761 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Thu Sep  7 17:01:30 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-09-07 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   legend 1761 F...m pulseaudio
 /dev/snd/controlC0:  legend 1761 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [HP Pavilion Notebook, Realtek ALC295, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.02
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 820B
dmi.board.vendor: HP
dmi.board.version: 82.17
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd03/14/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820B:rvr82.17:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug zesty

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

Title:
  My sound system does not work no matter what.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My computer originally ran Windows 10.  I recently put Ubuntu on it,
  thinking it would go onto my thumb drive, but it didn't.  It has
  messed up my login process, but I can still eventually get to Ubuntu.
  But I try playing videos and I cannot hear the audio, from YouTube and
  advertisements.  My computer has been designed to run B&O Play, but
  maybe downloading a new OS screwed it up.

  1) Ubuntu 17.04
  2) Unknown
  3) Play any sound requested
  4) Silence

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   legend 1761 F...m pulseaudio
   /dev/snd/controlC0:  legend 1761 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Sep  7 17:01:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-07 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   legend 1761 F...m pulseaudio
   /dev/snd/controlC0:  legend 1761 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP Pavilion Notebook, Realtek ALC295, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 820B
  dmi.board.vendor: HP
  dmi.board.version: 82.17
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd03/14/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820B:rvr82.17:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductCon

[Touch-packages] [Bug 1715764] [NEW] Flickering Screen

2017-09-07 Thread George Salomon

Public bug reported:

Screen flickers particularly when I use Discord but have also
experienced it with Minecraft. Occasionally have issues with misplaced
pixels in slack and mozilla firefox, but much less frequently with
firefox. Only have experienced pixels being misplayed whilst being on
vox and maybe one or two others I'm forgetting, have not had any issues
when using most websites.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Sep  8 00:19:34 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80a1]
InstallationDate: Installed on 2016-09-01 (371 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed 
root=UUID=93999ca7-5b83-4851-969c-5482f1b9ee8d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.77
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80A1
dmi.board.vendor: HP
dmi.board.version: 91.1C
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A1:rvr91.1C:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
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: Tue Sep  5 00:34:29 2017
xserver.configfile: default
xserver.errors:
 intel(0): Failed to submit rendering commands (No such file or directory), 
disabling acceleration.
 intel(0): When reporting this, please include /sys/class/drm/card0/error and 
the full dmesg.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   20049 
 vendor SDC
xserver.version: 2:1.18.4-0ubuntu0.3

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

Title:
  Flickering Screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Screen flickers particularly when I use Discord but have also
  experienced it with Minecraft. Occasionally have issues with misplaced
  pixels in slack and mozilla firefox, but much less frequently with
  firefox. Only have experienced pixels being misplayed whilst being on
  vox and maybe one or two others I'm forgetting, have not had any
  issues when using most websites.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Sep  8 00:19:34 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCa

[Touch-packages] [Bug 1704508] Re: add-apt-repository traceback when hitting ctrl-c

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

---
software-properties (0.96.24.16) artful; urgency=medium

  * add-apt-repository: Don't raise a Traceback when Ctrl-c is used to cancel
an operation. Thanks to Launchpad user Yeison Valero fo the initial patch.
(LP: #1704508)

 -- Brian Murray   Wed, 06 Sep 2017 15:36:51 -0700

** Changed in: software-properties (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  add-apt-repository traceback when hitting ctrl-c

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  add-apt-repository says to hit ctrl-c to cancel adding a PPA.  Then it
  tracebacks when you do:

  ubuntu@bysen:~$ sudo add-apt-repository ppa:maas/next
   This PPA holds new upstream development releases, usually development 
releases. Currently, it is holding the 2.2 series.
   More info: https://launchpad.net/~maas/+archive/ubuntu/next
  Press [ENTER] to continue or ctrl-c to cancel adding it
  ^CTraceback (most recent call last):
File "/usr/bin/add-apt-repository", line 143, in 
  sys.stdin.readline()
  KeyboardInterrupt

  
  I understand why the trace is generated, but this is ugly (users should never 
see tracebacks for known conditions, IMO).  

  The KeyboardInterrupt exception should be handled properly like any
  other exception.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.20.7
  ProcVersionSignature: User Name 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Fri Jul 14 23:17:57 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1704508/+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 1703393] Re: TCP offloads disabled by default

2017-09-07 Thread Zach Marano

GCE has confirmed this fixes the bug in question. Please proceed!

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

Title:
  TCP offloads disabled by default

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  Regression in systemd v232 resulted in IPv4 TCP segmentation offload ("tso" 
in ethtool) to be disabled by default, yet previously it was enabled.

  [Fix]
  Backport upstream patch to fix the regression

  [Testcase]
  Use ethtool to verify that tso is enabled on e.g. e1000e card with fixed 
package.

  [Regression Potential]
  Link features were incorrectly initialised, this fix changes the 
initialisation code back to the correct default values. This changes the 
defaults back to what they are in all other releases. Users on zesty release 
may have been accustomed to the wrong defaults and may need to adjust .link 
files to e.g. disable tso if that is the behavior they want.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1703393/+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 1714301] Re: systemd-networkd hangs my boot (wireless)

2017-09-07 Thread André

what does 'unconditional enablement' mean? just enable the 'systemd-
networkd' service?

bug #1697730 could be a duplicate of this (or the other way around)

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

Title:
  systemd-networkd hangs my boot (wireless)

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  Since that systemd-networkd is enabled, my laptop doesn't boot (hangs)
  until I plug in an ethernet cable.

  Here is the journal from this boot, note the hang up until I connect my cable 
at 17:51:35:
  aoÃ»t 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  aoÃ»t 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo
  aoÃ»t 31 17:50:08 tidus systemd[1]: emergency-tmp.service: Cannot add 
dependency job, ignoring: Unit emergency-tmp.service is not loaded properly: 
Inva
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3836]: no servers can be used, exiting
  aoÃ»t 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Start request repeated too quickly.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Failed to start 
systemd-resolved-update-resolvconf.service.
  aoÃ»t 31 17:50:08 tidus systemd[1]: 
systemd-resolved-update-resolvconf.service: Failed with result 
'start-limit-hit'.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:3 'up' [virbr0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/Ne
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0]: start 
running ordered scripts...
  aoÃ»t 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6148] 
dispatcher: (6) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 0.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 1.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 2.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host 3.ubuntu.pool.ntp.org: 
Name or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: Can't find host ntp.ubuntu.com: Name 
or service not known (-2)
  aoÃ»t 31 17:50:08 tidus ntpdate[3908]: no servers can be used, exiting
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting.
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], 
"/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script 
'/etc/N
  aoÃ»t 31 17:50:08 tidus NetworkManager[2340]:   [1504194608.6612] 
dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat
  aoÃ»t 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22.
  aoÃ»t 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22.
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: 
/usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
  aoÃ»t 31 17:50:08 tidus nm-dispatcher[2511]: run-parts:

[Touch-packages] [Bug 882147] Re: overlayfs does not implement inotify interfaces correctly

2017-09-07 Thread Serge Hallyn

I've seen reports that this is fixed in 4.10?

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

Title:
  overlayfs does not implement inotify interfaces correctly

Status in coreutils package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in coreutils source package in Precise:
  Confirmed
Status in linux source package in Precise:
  Triaged

Bug description:
  When using tail on the liveCD some updates are not reported.  This
  seems to be triggered by tail using inotify to identify modified
  files.  Overlayfs does not appear to be implementing inotify quite the
  way you might hope reporting only against the underlying filesystems.

  Related bugs:
   * bug 1213925:  upstart should notice "/etc" inode change

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 0/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apw2296 F pulseaudio
   /dev/snd/pcmC0D0c:   apw2296 F...m pulseaudio
   /dev/snd/pcmC0D0p:   apw2296 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc70 irq 47'
     Mixer name : 'Intel Cantiga HDMI'
     Components : 'HDA:111d7675,1028029f,00100103 
HDA:80862802,80860101,0010'
     Controls  : 20
     Simple ctrls  : 11
  Date: Wed Oct 26 17:46:16 2011
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d8328455-deac-4bae-877d-c408d371cefe
  MachineType: Dell Inc. Studio 1537
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=cf503727-25f2-4ecd-b0f3-2b894523bcba ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (9 days ago)
  WpaSupplicantLog:

  dmi.bios.date: 09/22/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Studio 1537
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/882147/+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 882147] Re: overlayfs does not implement inotify interfaces correctly

2017-09-07 Thread Serge Hallyn

Nope, tail -f is still broken at least in 4.12.

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

Title:
  overlayfs does not implement inotify interfaces correctly

Status in coreutils package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in coreutils source package in Precise:
  Confirmed
Status in linux source package in Precise:
  Triaged

Bug description:
  When using tail on the liveCD some updates are not reported.  This
  seems to be triggered by tail using inotify to identify modified
  files.  Overlayfs does not appear to be implementing inotify quite the
  way you might hope reporting only against the underlying filesystems.

  Related bugs:
   * bug 1213925:  upstart should notice "/etc" inode change

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 0/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apw2296 F pulseaudio
   /dev/snd/pcmC0D0c:   apw2296 F...m pulseaudio
   /dev/snd/pcmC0D0p:   apw2296 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc70 irq 47'
     Mixer name : 'Intel Cantiga HDMI'
     Components : 'HDA:111d7675,1028029f,00100103 
HDA:80862802,80860101,0010'
     Controls  : 20
     Simple ctrls  : 11
  Date: Wed Oct 26 17:46:16 2011
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d8328455-deac-4bae-877d-c408d371cefe
  MachineType: Dell Inc. Studio 1537
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=cf503727-25f2-4ecd-b0f3-2b894523bcba ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (9 days ago)
  WpaSupplicantLog:

  dmi.bios.date: 09/22/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Studio 1537
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/882147/+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 1715792] [NEW] GTK file picker dialogue shows too many mount points

2017-09-07 Thread naught101

Public bug reported:

I'm running kubuntu 17.10 beta, and the GTK file picker dialogue (for
all GTK apps - e.g. firefox, thunderbird, GIMP, agave) is listing a
tonne of useless mount points in the left-most panel:

https://i.stack.imgur.com/TrJYy.png

Is there any way to hide these? Other posts suggest adding commands to
/etc/fstab, but none of these mount points are listed in fstab to begin
with..

These entries do not appear in the Qt file picker dialogue.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libgtk-3-0 3.22.19-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-12.13-lowlatency 4.12.8
Uname: Linux 4.12.0-12-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Sep  8 13:33:19 2017
InstallationDate: Installed on 2017-08-19 (19 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  GTK file picker dialogue shows too many mount points

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I'm running kubuntu 17.10 beta, and the GTK file picker dialogue (for
  all GTK apps - e.g. firefox, thunderbird, GIMP, agave) is listing a
  tonne of useless mount points in the left-most panel:

  https://i.stack.imgur.com/TrJYy.png

  Is there any way to hide these? Other posts suggest adding commands to
  /etc/fstab, but none of these mount points are listed in fstab to
  begin with..

  These entries do not appear in the Qt file picker dialogue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgtk-3-0 3.22.19-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-lowlatency 4.12.8
  Uname: Linux 4.12.0-12-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Sep  8 13:33:19 2017
  InstallationDate: Installed on 2017-08-19 (19 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1715792/+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 1715804] [NEW] system crash

2017-09-07 Thread Kaustubh

Public bug reported:

I dont know why but in between my os crashes and some orange line comes on my 
screen then i have to restart my pc it is hard when i am doing my projects i 
have to do it all again  please help
and i am new tu ubuntu linux

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Fri Sep  8 10:43:01 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
InstallationDate: Installed on 2017-09-06 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 13ee:0001 MosArt Optical Mouse
 Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Gigabyte Technology Co., Ltd. M68MT-D3
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=40de3290-6e3a-40dc-b4a2-40c6893c2d94 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/14/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: M68MT-D3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd06/14/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: M68MT-D3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Fri Sep  8 10:38:46 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 crash ubuntu zesty

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

Title:
  system crash

Status in xorg package in Ubuntu:
  New

Bug description:
  I dont know why but in between my os crashes and some orange line comes on my 
screen then i have to restart my pc it is hard when i am doing my projects i 
have to do it all again  please help
  and i am new tu ubuntu linux

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Fri Sep  8 10:43:01 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
  InstallationDate: Installed on 2017-09-06 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Touch-packages] [Bug 1715805] [NEW] system crash

2017-09-07 Thread Kaustubh

Public bug reported:

I dont know why but in between my os crashes and some orange line comes on my 
screen then i have to restart my pc it is hard when i am doing my projects i 
have to do it all again  please help
and i am new tu ubuntu linux

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Fri Sep  8 10:43:01 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
InstallationDate: Installed on 2017-09-06 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 13ee:0001 MosArt Optical Mouse
 Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Gigabyte Technology Co., Ltd. M68MT-D3
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=40de3290-6e3a-40dc-b4a2-40c6893c2d94 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/14/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: M68MT-D3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd06/14/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: M68MT-D3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Fri Sep  8 10:38:46 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 crash ubuntu zesty

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

Title:
  system crash

Status in xorg package in Ubuntu:
  New

Bug description:
  I dont know why but in between my os crashes and some orange line comes on my 
screen then i have to restart my pc it is hard when i am doing my projects i 
have to do it all again  please help
  and i am new tu ubuntu linux

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Fri Sep  8 10:43:01 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
  InstallationDate: Installed on 2017-09-06 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Touch-packages] [Bug 1652586] Re: package python3-cryptography 1.2.3-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1