date:20171128

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

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

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

Title:
  Limiting queue disk space does not work, upgrade needed

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  # lsb_release -rd
  Description:Ubuntu 14.04.1 LTS
  Release:14.04
  # apt-cache policy rsyslog
  rsyslog:
Installed: 7.4.4-1ubuntu2.3
Candidate: 7.4.4-1ubuntu2.3
Version table:
   [...]

  When rsyslog is run with a config to save/cache log to disk, e.g when the 
host that
  it is forwarding log to is not responding, it fails to respect the
  maxdiskspace parameter. This is a known bug and 7.4.7 of v7-stable has
  been released to fix this, see 
http://www.rsyslog.com/changelog-for-7-4-7-v7-stable/

  
  Config for testing:

  global(
workDirectory="/tmp"
  )

  module(load="imudp")
  module(load="omrelp")

  input(type="imudp"
port="514"
  )

  action(type="omrelp"
target="localhost"
port="2514"
action.resumeRetryCount="-1"
queue.saveonshutdown="on"
queue.type="LinkedList"
queue.filename="omrelp"

queue.maxfilesize="100M"
queue.maxdiskspace="1M"

queue.checkpointinterval="100"
queue.highwatermark="10"
  )

  Then just log more than 1MB of messages to UDP to see that it doesn't
  stop at 1MB but just continues forever.

  Please upgrade the package to 7.4.7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1380976/+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 1734858] [NEW] Xorg crash - Xwayland

2017-11-28 Thread Pavel Studeník

Public bug reported:

I am using two monitors for work. And when I moved aplication rhythmbox
from first to second monitor, the screen session was logout and I have
to login again. After it I found following error by dmesg

>> dmesg
[ 2753.218761] BUG: unable to handle kernel paging request at 09fffb9d8290
[ 2753.218811] IP: __radix_tree_lookup+0x0/0x130
[ 2753.218826] PGD 0 
[ 2753.218827] P4D 0 

[ 2753.218852] Oops:  [#1] SMP
[ 2753.218865] Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle xfrm_user xfrm_algo 
xt_addrtype ipt_MASQUERADE br_netfilter nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp aufs llc ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter binfmt_misc uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel snd_hda_codec_hdmi snd_hda_codec_conexant 
arc4 snd_hda_codec_generic aes_x86_64 crypto_simd glue_helper cryptd 
intel_cstate snd_hda_intel joydev snd_hda_codec input_leds iwldvm snd_hda_core
[ 2753.219080]  serio_raw snd_hwdep mac80211 snd_seq_midi snd_seq_midi_event 
snd_rawmidi iwlwifi snd_seq wmi_bmof snd_pcm intel_ips cfg80211 thinkpad_acpi 
nvram mei_me lpc_ich mei shpchp snd_seq_device snd_timer snd soundcore mac_hid 
nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre nf_nat 
nf_conntrack libcrc32c parport_pc ppdev lp parport ip_tables x_tables autofs4 
hid_generic usbhid hid i915 i2c_algo_bit mxm_wmi drm_kms_helper firewire_ohci 
psmouse syscopyarea sysfillrect firewire_core sysimgblt ahci fb_sys_fops 
libahci e1000e drm sdhci_pci sdhci crc_itu_t ptp pps_core video wmi
[ 2753.219250] CPU: 3 PID: 9728 Comm: Web Content Tainted: G   OE   
4.13.0-17-generic #20-Ubuntu
[ 2753.219277] Hardware name: LENOVO 4384BR2/4384BR2, BIOS 6MET81WW (1.41 ) 
10/26/2010
[ 2753.219300] task: 8fc0a893ac00 task.stack: a27dc2e1
[ 2753.219320] RIP: 0010:__radix_tree_lookup+0x0/0x130
[ 2753.219336] RSP: :a27dc2e13cd8 EFLAGS: 00010246
[ 2753.219353] RAX:  RBX: 09fffb9d8288 RCX: a27dc2e13ce0
[ 2753.219375] RDX:  RSI: 0003fffe3f010f91 RDI: 09fffb9d8288
[ 2753.219397] RBP: a27dc2e13cf0 R08: 8fc04cd94000 R09: 7f95eec25010
[ 2753.219418] R10: 0083 R11: 7f95eec84290 R12: 0003fffe3f010f91
[ 2753.219440] R13: 09fffb9d8280 R14: 0003fffe3f010f91 R15: 8fc04cd94000
[ 2753.219463] FS:  7f9626bed1c0() GS:8fc0bbd8() 
knlGS:
[ 2753.219487] CS:  0010 DS:  ES:  CR0: 80050033
[ 2753.219505] CR2: 09fffb9d8290 CR3: 0001b618c000 CR4: 06e0
[ 2753.219527] Call Trace:
[ 2753.219539]  ? radix_tree_lookup_slot+0x22/0x50
[ 2753.219559]  find_get_entry+0x1e/0xd0
[ 2753.219573]  pagecache_get_page+0x2c/0x210
[ 2753.219590]  lookup_swap_cache+0x43/0x90
[ 2753.219605]  do_swap_page+0x95/0x700
[ 2753.219618]  ? do_wp_page+0x157/0x500
[ 2753.219632]  __handle_mm_fault+0x70c/0x1020
[ 2753.219647]  handle_mm_fault+0xb1/0x200
[ 2753.219663]  __do_page_fault+0x24d/0x4d0
[ 2753.219677]  do_page_fault+0x22/0x30
[ 2753.219693]  page_fault+0x28/0x30

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 28 11:04:19 2017
DistUpgraded: 2017-10-03 22:32:45,006 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
InstallationDate: Installed on 2015-11-01 (757 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
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.
MachineType: LENOVO 4384BR2
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vml

[Touch-packages] [Bug 1734662] Re: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

2017-11-28 Thread natraj

i had linked python to python3 and updated the python link to python2

mv /usr/bin/python /usr/bin/python2

ln -s /usr/bin/python /usr//bin/python3

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

Title:
  package python-setuptools 3.3-1ubuntu2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in python-setuptools package in Ubuntu:
  Invalid

Bug description:
  Somethign is messed up after linking python to python 3 and after this
  all these issues started cropping up.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-setuptools 3.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Mon Nov 27 16:19:13 2017
  Dependencies: python-pkg-resources 3.3-1ubuntu2
  DuplicateSignature: package:python-setuptools:3.3-1ubuntu2:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-11-16 (10 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python-setuptools
  Title: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to trusty on 2017-11-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1734662/+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 1385410] Re: hook into system-image updates to precompile policy prior to reboot

** No longer affects: ubuntu-ux

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

Title:
  hook into system-image updates to precompile policy prior to reboot

Status in click-apparmor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Occasionally users will receive and OTA update that requires apparmor
  policy to be recompiled. Recompiling apparmor policy can take quite a
  bit of time (minutes) depending on how many applications the user has
  installed. While this is only expected to happen on major OTA OS
  upgrades (eg, 14.10 to 15.04), it is possible it could happen at other
  times. This would improve the user experience for developers
  considerably since policy recompiles can be relatively frequent when
  running the development release.

  : "On start
  apparmor profiles need to be regenerated which means the first boot
  after the upgrade might take long depending on the number of installed
  applications (even up to 30 minutes). Currently there will be no
  visual indication of the profile regeneration, so please be patient
  and wait until you see the UI appearing."

  To improve the user experience, we should detect and recompile
  apparmor profiles prior to reboot but after system-image updates has
  downloaded the new update. This always for the possibility of using a
  progress meter when compiling policy (which we currently cannot).

  :
  "Therefore, every step of the system update should show a progress
  bar, that fills once across all the steps ... Subtask Recompiling
  apparmor profiles; Allocation 45%; Resulting range 0~45%"

  See also bug 1350598, about caching compiled policies more often.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1385410/+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 1357548] Re: [toolkit] Empty PIN/password/passphrase field appears to contain 4 characters

** No longer affects: ubuntu-ux

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

Title:
  [toolkit] Empty PIN/password/passphrase field appears to contain 4
  characters

Status in Canonical System Image:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu RTM:
  Fix Released

Bug description:
  minor interrelated issues & probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 "bullets" implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the "bullets" remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a "show password" would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1357548/+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 1378350] Re: Need to allow multiple apps to handle the same url patterns

** No longer affects: ubuntu-ux

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

Title:
  Need to allow multiple apps to handle the same url patterns

Status in Canonical System Image:
  Confirmed
Status in content-hub package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Triaged
Status in url-dispatcher package in Ubuntu:
  Triaged

Bug description:
  Steps:
  * install gmail and dekko apps

  Expected:
  * when using a mailto: URL (see bug #1351222) URL, the user should be asked 
which app to open (and cache the response optionally?)

  Current:
  * not sure what would happen ;)

  Design resolution _

  Case 1: If no email client is installed and a user clicks on a 'mail
  to' link, the user should be prompted to download the Dekko app.

  Case 2: If the user has Dekko installed, then clicking on the 'mail
  to' link should open the Dekko client --> compose mail screen to the
  'mail to' address.

  Case 3: If the user has Dekko and Gmail installed, the 'mail to' link
  by default should open in the Dekko client. However, the user can
  change their mail client preferences in system settings.

  Case 4: If the user has Gmail and another mail client installed, the
  'mail to' link should default to the first client that was installed
  on their device (which would be the default mail client preference in
  system settings -  this can be changed by the user via system
  settings).

  Notes:
  1. Wherever the user has not actively changed a mail client preference and 
Dekko is installed on their device, the default 'mail to' client should be 
Dekko.
  2. When clicking on a 'mail to' link, the user's expectation is to have this 
link open in a relevant client (unless it is case 1), therefore this should be 
the case and any mail preference choices the user can perform via system 
settings rather than being presented with multiple choice options of which 
client to open the URL in.

  : "Whenever the URL dispatcher
  is called on to open an address that multiple apps have registered
  for, it should open a “Use App” dialog, with a centered grid of
  labelled buttons with the icon for each applicable app, followed by a
  “Cancel” button."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1378350/+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 1370008] Re: URL Dispatcher Should Prompt on Bad URL

** No longer affects: ubuntu-ux

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

Title:
  URL Dispatcher Should Prompt on Bad URL

Status in Canonical System Image:
  Confirmed
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gallery-app.  This problem was most recently seen with
  version 13.10.0+14.10.20140908.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/b1f16000af092461aeb85b5c7edfd3dc3f1271c8
  contains more details.

  : "Whenever
  the URL dispatcher is called on to open an address of a protocol that
  it does not understand (url-dispatcher-bad-url), it should open an
  alert with the title “Unrecognized Address”, text of the form ‘Ubuntu
  can’t open addresses of type “{protocol:}”.’, and an “OK” button. To
  prevent denial of UI service, however, the alert should not open if it
  has already opened more than three times in the past minute."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1370008/+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 1364452] Re: People's own phone number isn't where they expect to find it

** No longer affects: ubuntu-ux

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

Title:
  People's own phone number isn't where they expect to find it

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Twenty people were given an Ubuntu phone and asked to find their own
  phone number. (10 were iPhone users, 8 Android, 1 Windows Phone, and 1
  feature phone user.)

  The first place they looked:
  - 9 in the Contacts app
  - 5 in System Settings "Phone" screen
  - 3 in System Settings "About" screen
  - 2 in the Dialer app contacts screen
  - 1 in System Settings "Cellular" screen.

  So, our current placement of the phone number in the "About" screen
  (bug 1221908) is suboptimal.

  Instead it should be in the Contacts app, and possibly in the "Phone" screen.
  Where the phone is dual SIM, both phone numbers should be shown.

  Only once that is done, it should be removed from the "About" screen.

  : "Address Book should always contain one
  special contact representing you as the user of the phone ... To
  indicate its purpose and resilience, the “Me” contact should be
  denoted by the word “Me” as a caption at the trailing end (with a
  translation hint stating that it should be extremely short); and the
  contact’s visual design should be subtly different from other
  contacts. Apart from those two differences, the contact should be
  displayed and ordered the same as any other contacts in the list..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1364452/+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 1268097] Re: [System settings] Can't set user-supplied ring tone

** No longer affects: ubuntu-ux

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

Title:
  [System settings] Can't set user-supplied ring tone

Status in Canonical System Image:
  Fix Released
Status in content-hub package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  AFAICS I can't set a custom ring tone without using a writable image.
  (http://askubuntu.com/questions/372759/ringtones-in-ubuntu-touch)

  : "In the “Ringtone”
  screen, immediately before “None” should be a “Custom Ringtone…”
  item..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1268097/+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)

This morning I found out that if I boot
linux-image-4.13.0-17-generic
I get a hang at
Nov 23 07:12:47 lakshmi NetworkManager[1795]:   [1511439167.0455] 
manager: rfkill: WWAN hardware radio set enabled
Nov 23 07:14:30 lakshmi systemd-networkd-wait-online[1454]: Event loop failed: 
Connection timed out

But if I boot
linux-image-4.14.2-041402-generic
there is no two minute delay.

-- 
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:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

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]: Se

[Touch-packages] [Bug 1317860] Re: the phone should switch itself off before completely draining battery

** No longer affects: ubuntu-ux

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  Fix Released
Status in indicator-power package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Invalid

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+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 1732172] Re: [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

2017-11-28 Thread Andreas Hasenack

Marking as incomplete given the response in comment #3

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

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

Title:
  [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Does anyone know when the following OpenSSH venerabilities will be
  patched on Ubuntu 14.04

  CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012,
  CVE-2016-8858

  As these are coming up repeatedly on or security scans

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1732172/+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 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged

This morning I found out that if I boot
linux-image-4.13.0-17-generic
I get a hang at
Nov 23 07:12:47 lakshmi NetworkManager[1795]:  [1511439167.0455] manager: 
rfkill: WWAN hardware radio set enabled
Nov 23 07:14:30 lakshmi systemd-networkd-wait-online[1454]: Event loop failed: 
Connection timed out

But if I boot
linux-image-4.14.2-041402-generic
there is no two minute delay.

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

Title:
  systemd-networkd-wait-online waits when devices are unmanaged

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I started a system with cloud-init disabled, etc. and a single real
  network interface (ens3) that could be configured.

  That VM has no configuration whatsoever for systemd-networkd, as that
  would have to have been written by netplan, and cloud-init did not
  generate netplan config (because it was disabled).

  So:

  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  d-networkd-wait-online --ignore=lo
  ignoring: lo
  Event loop failed: Connection timed out
  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl
  IDX LINK TYPE   OPERATIONAL SETUP 
1 lo   loopback   carrier unmanaged 
2 ens3 ether  off unmanaged 
3 sit0 sitoff unmanaged 

  3 links listed.
  root@ubuntu:/etc/systemd/system/network-online.target.wants# 

  
  The system took 120 seconds to complete boot, because wait-online had to 
finish; and running wait-online from the system afterwards also waits 120 
seconds (its default timeout). If there is no configuration for an interface, 
it's unmanaged (as shown by networkctl), so wait-online should not wait, and 
simply report that all interfaces are unmanaged, possibly returning an error so 
we don't reach network-online.

  FWIW, having wait-online look up configuration might later be useful
  also to figure out if an interface was configured, but marked as
  optional (such that it is explicitly not required to be up at boot),
  or if we want to configure network devices but specify that networkd
  should *not* bring them online (like "administratively disabled"
  interfaces in Cisco world using the "shutdown" command).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+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 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-28 Thread imachine

Cool,

Fixed as Woko wrote, cheers man.

However, firefox still happens to show _some_ fonts incorrectly -
possibly, bitmap fonts?

Some fonts downloaded from the web (like on Gmail) work fine.

Others don't.

See attached SSots.

** Attachment added: "messed up lack of hinting"
   
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+attachment/5015637/+files/Screenshot-2017-11-28%20Zazzle%20com%20Unsubscribe.png

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

Title:
  Font hinting appears broken on 17.10 beta

Status in Qt:
  New
Status in freetype package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed
Status in qtbase-opensource-src source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/1722508/+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 1722508] Re: Font hinting appears broken on 17.10 beta

2017-11-28 Thread imachine

Then see here the correctly displayed fonts on Gmail (also downloaded
from Gmail's server, no local font).

Works fine and hints correctly.

What gives?

Running last stable firefox (56.0, 57 all messed up, so locked 56 with
apt-lock)

Ubuntu 17.10

** Attachment added: "Screenshot-2017-11-28 Ubuntu One Forgotten Password - m 
jedrasik gmail com - Gmail.png"
   
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+attachment/5015638/+files/Screenshot-2017-11-28%20Ubuntu%20One%20Forgotten%20Password%20-%20m%20jedrasik%20gmail%20com%20-%20Gmail.png

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

Title:
  Font hinting appears broken on 17.10 beta

Status in Qt:
  New
Status in freetype package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed
Status in qtbase-opensource-src source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/1722508/+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 1734660] Re: package python-six 1.5.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-11-28 Thread Andreas Hasenack

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

** This bug has been marked a duplicate of bug 1734661
   package python-requests 2.2.1-1ubuntu0.3 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration

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

Title:
  package python-six 1.5.2-1ubuntu1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in six package in Ubuntu:
  New

Bug description:
  Something is messed up after linking python to python 3 and after this
  all these issues started cropping up.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-six 1.5.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Mon Nov 27 16:11:12 2017
  Dependencies:
   
  DuplicateSignature: package:python-six:1.5.2-1ubuntu1:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-11-16 (10 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: six
  Title: package python-six 1.5.2-1ubuntu1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to trusty on 2017-11-27 (0 days ago)

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

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

Re: [Touch-packages] [Bug 1724233] Re: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()

2017-11-28 Thread Craig Stein

It is on the GNOME software/extension center so I assume that is a yes

On Nov 27, 2017 11:50 PM, "Matthias Klose"  wrote:

> is this a packaged extension?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1724233
>
> Title:
>   python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
>
> Status in python2.7 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Booted into stock Ubuntu 17.10 release candidate from October 15, 2017
>   and this error message simply came up.
>
>   apt-cache policy python
>   python:
> Installed: 2.7.14-2ubuntu1
> Candidate: 2.7.14-2ubuntu1
> Version table:
>*** 2.7.14-2ubuntu1 500
>   500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64
> Packages
>   100 /var/lib/dpkg/status
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 17.10
>   Package: python2.7-minimal 2.7.14-2ubuntu2
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Oct 17 06:15:41 2017
>   ExecutablePath: /usr/bin/python2.7
>   InstallationDate: Installed on 2017-10-17 (0 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015)
>   ProcCmdline: python accountable2you.pyc --username
>   ProcEnviron:
>LANGUAGE=en_CA:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_CA.UTF-8
>SHELL=/bin/bash
>   Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal,
> 3.6.3-0ubuntu2
>   PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal,
> 2.7.14-2ubuntu1
>   SegvAnalysis:
>Segfault happened at: 0x7f84d920daa9 :
> movzwl 0xa(%rdi),%r15d
>PC (0x7f84d920daa9) ok
>source "0xa(%rdi)" (0x64007d) not located in a known VMA region
> (needed readable region)!
>destination "%r15d" ok
>Stack memory exhausted (SP below stack segment)
>   SegvReason: reading unknown VMA
>   Signal: 11
>   SourcePackage: python2.7
>   StacktraceTop:
>ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6
>ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
>   Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/
> 1724233/+subscriptions
>

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

Title:
  python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()

Status in python2.7 package in Ubuntu:
  Incomplete

Bug description:
  Booted into stock Ubuntu 17.10 release candidate from October 15, 2017
  and this error message simply came up.

  apt-cache policy python
  python:
Installed: 2.7.14-2ubuntu1
Candidate: 2.7.14-2ubuntu1
Version table:
   *** 2.7.14-2ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: python2.7-minimal 2.7.14-2ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 06:15:41 2017
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2017-10-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015)
  ProcCmdline: python accountable2you.pyc --username
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f84d920daa9 : movzwl 
0xa(%rdi),%r15d
   PC (0x7f84d920daa9) ok
   source "0xa(%rdi)" (0x64007d) not located in a known VMA region (needed 
readable region)!
   destination "%r15d" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: python2.7
  StacktraceTop:
   ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.

[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged

This bug may be a duplicate of LP #1717152

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

Title:
  systemd-networkd-wait-online waits when devices are unmanaged

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I started a system with cloud-init disabled, etc. and a single real
  network interface (ens3) that could be configured.

  That VM has no configuration whatsoever for systemd-networkd, as that
  would have to have been written by netplan, and cloud-init did not
  generate netplan config (because it was disabled).

  So:

  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  d-networkd-wait-online --ignore=lo
  ignoring: lo
  Event loop failed: Connection timed out
  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl
  IDX LINK TYPE   OPERATIONAL SETUP 
1 lo   loopback   carrier unmanaged 
2 ens3 ether  off unmanaged 
3 sit0 sitoff unmanaged 

  3 links listed.
  root@ubuntu:/etc/systemd/system/network-online.target.wants# 

  
  The system took 120 seconds to complete boot, because wait-online had to 
finish; and running wait-online from the system afterwards also waits 120 
seconds (its default timeout). If there is no configuration for an interface, 
it's unmanaged (as shown by networkctl), so wait-online should not wait, and 
simply report that all interfaces are unmanaged, possibly returning an error so 
we don't reach network-online.

  FWIW, having wait-online look up configuration might later be useful
  also to figure out if an interface was configured, but marked as
  optional (such that it is explicitly not required to be up at boot),
  or if we want to configure network devices but specify that networkd
  should *not* bring them online (like "administratively disabled"
  interfaces in Cisco world using the "shutdown" command).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+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 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged

I'm not using cloud-init. My network devices are not managed because I disabled 
NetworkManager.service shortly after installing 17.10 on bare metal Nov 5, 2017 
9:44 AM EDT.  I think there were too many fires then and I didn't want to try 
to convince NetworkManager to use a bridge.  I just lived with the two minute 
delay while working on the four minute delay LP 1731566
and the "BUG: unable to handle kernel NULL pointer dereference at (null)" LP 
1730374 until work on that last issue lead to the two minute delay clearing up 
as a side-effect.

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

Title:
  systemd-networkd-wait-online waits when devices are unmanaged

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I started a system with cloud-init disabled, etc. and a single real
  network interface (ens3) that could be configured.

  That VM has no configuration whatsoever for systemd-networkd, as that
  would have to have been written by netplan, and cloud-init did not
  generate netplan config (because it was disabled).

  So:

  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  d-networkd-wait-online --ignore=lo
  ignoring: lo
  Event loop failed: Connection timed out
  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl
  IDX LINK TYPE   OPERATIONAL SETUP 
1 lo   loopback   carrier unmanaged 
2 ens3 ether  off unmanaged 
3 sit0 sitoff unmanaged 

  3 links listed.
  root@ubuntu:/etc/systemd/system/network-online.target.wants# 

  
  The system took 120 seconds to complete boot, because wait-online had to 
finish; and running wait-online from the system afterwards also waits 120 
seconds (its default timeout). If there is no configuration for an interface, 
it's unmanaged (as shown by networkctl), so wait-online should not wait, and 
simply report that all interfaces are unmanaged, possibly returning an error so 
we don't reach network-online.

  FWIW, having wait-online look up configuration might later be useful
  also to figure out if an interface was configured, but marked as
  optional (such that it is explicitly not required to be up at boot),
  or if we want to configure network devices but specify that networkd
  should *not* bring them online (like "administratively disabled"
  interfaces in Cisco world using the "shutdown" command).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+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)

If you are looking for newer bug reports with this issue try
LP: #1717152
LP: #1728181

-- 
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:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

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: 
/etc/network/if-up.d/ubuntu-fan exited with return code 2
  aoÃ»

[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

2017-11-28 Thread Dimitri John Ledkov

** Also affects: makedumpfile (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Canonical Foundations Team (canonical-foundations)
   Status: Confirmed

** Also affects: systemd (Ubuntu Bionic)
   Importance: High
 Assignee: Canonical Foundations Team (canonical-foundations)
   Status: Triaged

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Triaged
Status in makedumpfile source package in Artful:
  New
Status in systemd source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+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 1734038] Re: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty)

2017-11-28 Thread Michael Vogt

We merged https://github.com/snapcore/snapd/pull/4306 which fixes this.

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

Title:
  utils don't understand «include "/where/ever"» (was: Potential
  regression found with apparmor test on Xenial/Zesty)

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  Issue found with Xenial kernel 4.4.0-102 and Zesty kernel 4.10.0-41,
  across different architectures

  Multiple tests from ubuntu_qrt_apparmor test suite failed with the same error 
message:
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,

  (BTW the include and this ld.so.cache are not in the same line, please
  refer to comment #3 for attachment)

  This issue will gone if you downgrade the snapd and ubuntu-core-launcher 
package:
  sudo apt-get install snapd=2.28.5 ubuntu-core-launcher=2.28.5

  Debug information:
  ubuntu@kernel01:~$ snap version
  snap2.29.3
  snapd   2.29.3
  series  16
  ubuntu  16.04
  kernel  4.4.0-102-generic

  ubuntu@kernel01:~$ apt list snapd
  Listing... Done
  snapd/xenial-proposed,now 2.29.3 s390x [installed]
  N: There are 2 additional versions. Please use the '-a' switch to see them.

  ubuntu@kernel01:~$ apt list apparmor -a
  Listing... Done
  apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 s390x [installed]
  apparmor/xenial-security 2.10.95-0ubuntu2.6 s390x
  apparmor/xenial 2.10.95-0ubuntu2 s390x

  Steps to run the Apparmor test from QA Regression testing suite:
1. git clone --depth 1 https://git.launchpad.net/qa-regression-testing
2. sudo ./qa-regression-testing/scripts/test-apparmor.py

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-102-generic 4.4.0-102.125
  ProcVersionSignature: Ubuntu 4.4.0-102.125-generic 4.4.98
  Uname: Linux 4.4.0-102-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Thu Nov 23 01:36:31 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-102-generic N/A
   linux-backports-modules-4.4.0-102-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1734038/+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 1734890] [NEW] pulse audio does not load because "module-switch-on-connect" should be loaded once at most

2017-11-28 Thread janl

Public bug reported:

This laptop was initially loaded with kubuntu 17.04. Yesterday I used
do-release-upgrade to update to 17.10.

This morning I noticed that the pulse audio mixer was broken while
chrome and amarok could still play sound.  Cold booted just in case.

Still no pulse mixing.  But alsamixer was working.  Found that no pulse
processes are running.


  $ ps auxww | grep pulse
  niclangf  9666  0.0  0.0  15900  1180 pts/3S+   15:13   0:00 grep 
--color=auto pulse
  $ pulseaudio 
  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. 
  Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.
  $ ps auxww | grep pulse
  niclangf  9833  0.0  0.0  15900  1036 pts/3S+   15:16   0:00 grep 
--color=auto pulse

Removed .config/pulse and .gconf/system/pulseaudio

  $ pulseaudio 
  W: [pulseaudio] authkey.c: Failed to open cookie file 
'/home/niclangf/.config/pulse/cookie': No such file or directory
  W: [pulseaudio] authkey.c: Failed to load authentication key 
'/home/niclangf/.config/pulse/cookie': No such file or directory
  W: [pulseaudio] authkey.c: Failed to open cookie file 
'/home/niclangf/.pulse-cookie': No such file or directory
  W: [pulseaudio] authkey.c: Failed to load authentication key 
'/home/niclangf/.pulse-cookie': No such file or directory
  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  $ pulseaudio 
  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most.  Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

Nicolai

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Nov 28 15:11:06 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-07-18 (133 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to artful on 2017-11-27 (1 days ago)
dmi.bios.date: 12/27/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET25W (1.04 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HGS1C200
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET25W(1.04):bd12/27/2016:svnLENOVO:pn20HGS1C200:pvrThinkPadT470s:rvnLENOVO:rn20HGS1C200:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HGS1C200
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO

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

Title:
  pulse audio does not load because "module-switch-on-connect" should be
  loaded once at most

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This laptop was initially loaded with kubuntu 17.04. Yesterday I used
  do-release-upgrade to update to 17.10.

  This morning I noticed that the pulse audio mixer was broken while
  chrome and amarok could still play sound.  Cold booted just in case.

  Still no pulse mixing.  But alsamixer was working.  Found that no
  pulse processes are running.

  
$ ps auxww | grep pulse
niclangf  9666  0.0  0.0  15900  1180 pts/3S+   15:13   0:00 grep 
--color=auto pulse
$ pulseaudio 
E: [pulseaudio] module.c: Module "module-switch-on-connect" should be 
loaded once at most. 
Refusing to load.
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Failed to initialize daemon.
$ ps auxww | grep pulse
niclangf  9833  0.0  0.0  15900  1036 pts/3S+   15:16   0:00 grep 
--color=auto pulse

  Removed .config/pulse and .gconf/system/pulseaudio

$ pulseaudio 
W: [pulseaudio] authkey.c: Failed to open cookie file 
'/home/niclangf/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key 
'/home/niclangf/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to open cookie file 
'/home/niclangf/.pulse-cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key 
'/home/niclangf/.pulse-cookie': No such file or directory
E: [puls

[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression

2017-11-28 Thread Dariusz Gadomski

Seth: those values were somehow calculated from a number of runs. A
single pyperformance benchmark run took ~20 minutes and I repeated each
of them 3 times.

I still have the 'raw' outputs of pyperformance if needed. From those I
see that there are at least 3 values for each test and also there is
also time named 'warmup' for each of the tests.

Attaching one of them as example.

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

Title:
Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
Fix Released
Status in python2.7 source package in Xenial:
Confirmed

Bug description:
I work on the OpenStack-Ansible project and we've noticed that testing
jobs on 16.04 take quite a bit longer to complete than on 14.04. They
complete within an hour on 14.04 but they normally take 90 minutes or
more on 16.04. We use the same version of Ansible with both versions
of Ubuntu.

After more digging, I tested python performance (using the
'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There
is a significant performance difference between each version of
python. That is detailed in a spreadsheet[0].

I began using perf to dig into the differences when running the python
performance module and when using Ansible playbooks. CPU migrations
(as measured by perf) are doubled in Ubuntu 16.04 when running the
same python workloads.

I tried changing some of the kerne.sched sysctl configurables but they
had very little effect on the results.

I compiled python 2.7.12 from source on 14.04 and found the
performance to be unchanged there. I'm not entirely sure where the
problem might be now.

We also have a bug open in OpenStack-Ansible[1] that provides
additional detail. Thanks in advance for any help you can provide!

[0]
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
[1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+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 1638695] Re: Python 2.7.12 performance regression

2017-11-28 Thread Dariusz Gadomski

Xenial pyperformance results with -fstack-protector-strong changed to
-fstack-protector.

** Attachment added: "xenial-fsp-01.json"

https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+attachment/5015696/+files/xenial-fsp-01.json

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

Title:
Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
Fix Released
Status in python2.7 source package in Xenial:
Confirmed

I tried changing some of the kerne.sched sysctl configurables but they
had very little effect on the results.

I compiled python 2.7.12 from source on 14.04 and found the
performance to be unchanged there. I'm not entirely sure where the
problem might be now.

We also have a bug open in OpenStack-Ansible[1] that provides
additional detail. Thanks in advance for any help you can provide!

[0]
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
[1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+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 1734904] [NEW] bugwith 2 screens

2017-11-28 Thread Marc Ayber

Public bug reported:

I've connected a graphical card to connect a second screen. The major
one is connected to the graphical port of my motherboard.

When I try to connect to my user ID, the computer boots 2 or 3 times
before I can use it.

I've a dual boot with a 16.04 UBUNTU STUDIO.

This problem appears only when I try to connect to UBUNTU 16.04

Thanks for the help

Marc

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Nov 28 16:03:03 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
 Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] RV610 [Radeon HD 2400 
PRO] [1462:1041]
InstallationDate: Installed on 2017-07-17 (134 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: ASUS All Series
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=d343bedd-832e-437a-845d-08005d563f63 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
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 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: Tue Nov 28 11:53:32 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
xserver.video_driver: modeset

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

Title:
  bugwith 2 screens

Status in xorg package in Ubuntu:
  New

Bug description:
  I've connected a graphical card to connect a second screen. The major
  one is connected to the graphical port of my motherboard.

  When I try to connect to my user ID, the computer boots 2 or 3 times
  before I can use it.

  I've a dual boot with a 16.04 UBUNTU STUDIO.

  This problem appears only when I try to connect to UBUNTU 16.04

  Thanks for the help

  Marc

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Nov 28 16:03:03 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-i

[Touch-packages] [Bug 1734908] [NEW] systemd-rfkill service times out when a new rfkill device is added

2017-11-28 Thread Kleber Sacilotto de Souza

Public bug reported:

1. Issue

Package version: systemd=234-2ubuntu12.1

The following issue was observed while running network-
manager=1.8.4-1ubuntu3 autopkgtest on Artful:

---
Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation 
timed out. Terminating.
Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill 
Switch Status.
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered 
failed state.
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with 
result 'timeout'.
---

This happens after the testcase inserts the fake-rfkill module (a module
shipped with network-manager tests that registers a new fake device with
the rfkill subsystem).

2. How to reproduce

2.1. Download network-manager package source code
$ apt-get source network-manager

2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill

3. Fix

The issue is fixed by the following systemd upstream patches:

---
https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac

commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f
Author: S. Fan 
Date:   Mon Jul 31 05:10:10 2017 -0500

rfkill: fix erroneous behavior when polling the udev monitor (#6489)

Comparing udev_device_get_sysname(device) and sysname will always return
true. We need to check the device received from udev monitor instead.

Also, fd_wait_for_event() sometimes never exits. Better set a timeout
here.
---

---
https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac

commit c7f6ca9379279affa8f22d15fa13063491f86a49
Author: Xiang Fan 
Date:   Wed Aug 9 05:51:53 2017 -0500

rfkill: fix typo (#6574)
---

With the fixed, the output from systemd-rfkill is:

---
Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev 
monitor.
Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch Status.
---

The patches are needed to fix the ADT tests observed with Artful tests on 
ppc64el architecture:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

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

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

Title:
  systemd-rfkill service times out when a new rfkill device is added

Status in systemd package in Ubuntu:
  New

Bug description:
  1. Issue

  Package version: systemd=234-2ubuntu12.1

  The following issue was observed while running network-
  manager=1.8.4-1ubuntu3 autopkgtest on Artful:

  ---
  Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start 
operation timed out. Terminating.
  Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill 
Switch Status.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered 
failed state.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with 
result 'timeout'.
  ---

  This happens after the testcase inserts the fake-rfkill module (a
  module shipped with network-manager tests that registers a new fake
  device with the rfkill subsystem).

  2. How to reproduce

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  3. Fix

  The issue is fixed by the following systemd upstream patches:

  ---
  
https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac

  commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f
  Author: S. Fan 
  Date:   Mon Jul 31 05:10:10 2017 -0500

  rfkill: fix erroneous behavior when polling the udev monitor
  (#6489)

  Comparing udev

[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added

2017-11-28 Thread Kleber Sacilotto de Souza

** Description changed:

1. Issue
+
+ Package version: systemd=234-2ubuntu12.1

The following issue was observed while running network-
manager=1.8.4-1ubuntu3 autopkgtest on Artful:

---
Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch
Status...
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start
operation timed out. Terminating.
Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill
Switch Status.
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered
failed state.
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with
result 'timeout'.
---

This happens after the testcase inserts the fake-rfkill module (a module
shipped with network-manager tests that registers a new fake device with
the rfkill subsystem).

2. How to reproduce

2.1. Download network-manager package source code
$ apt-get source network-manager

2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill

3. Fix

The issue is fixed by the following systemd upstream patches:

---

https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac

commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f
Author: S. Fan
Date: Mon Jul 31 05:10:10 2017 -0500

- rfkill: fix erroneous behavior when polling the udev monitor (#6489)
-
- Comparing udev_device_get_sysname(device) and sysname will always return
- true. We need to check the device received from udev monitor instead.
-
- Also, fd_wait_for_event() sometimes never exits. Better set a timeout
- here.
+ rfkill: fix erroneous behavior when polling the udev monitor (#6489)
+
+ Comparing udev_device_get_sysname(device) and sysname will always return
+ true. We need to check the device received from udev monitor instead.
+
+ Also, fd_wait_for_event() sometimes never exits. Better set a timeout
+ here.
---

---

https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac

commit c7f6ca9379279affa8f22d15fa13063491f86a49
Author: Xiang Fan
Date: Wed Aug 9 05:51:53 2017 -0500

- rfkill: fix typo (#6574)
+ rfkill: fix typo (#6574)
---

With the fixed, the output from systemd-rfkill is:

---
Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch
Status...
Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev
monitor.
Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch
Status.
---

The patches are needed to fix the ADT tests observed with Artful tests on
ppc64el architecture:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

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

Title:
systemd-rfkill service times out when a new rfkill device is added

Status in systemd package in Ubuntu:
New

Bug description:
1. Issue

Package version: systemd=234-2ubuntu12.1

The following issue was observed while running network-
manager=1.8.4-1ubuntu3 autopkgtest on Artful:

This happens after the testcase inserts the fake-rfkill module (a
module shipped with network-manager tests that registers a new fake
device with the rfkill subsystem).

2. How to reproduce

2.1. Download network-manager package source code
$ apt-get source network-manager

2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill

3. Fix

The issue is fixed by the foll

[Touch-packages] [Bug 1722564] Re: apport question will not accept multi-character responses

2017-11-28 Thread Brian Murray

These are now in the SRU queue again and awaiting review by a team
member of mine.

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

Title:
  apport question will not accept multi-character responses

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  New
Status in apport source package in Zesty:
  New
Status in apport source package in Artful:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Packages which provide apport integration with more than 9 options in a 
choice will not be able to select options numbered >= 10 on the commandline 
using 'ubuntu-bug '

  
  [Test Case]
  Overview:
   1. Update to proposed versions of cloud-init v. 17.1 and apport v. 
   2. Run 'ubuntu-bug cloud-init' attempt to report a bug on a cloud choice 
greater than 9
   3. View report and make sure the proper cloud is reported


  Script:
  if [ ! -f './lxc-proposed-snapshot' ]; then
wget 
https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot;
chmod 755 lxc-proposed-snapshot;
  fi

  for release in xenial artful; do
  ref=$release-proposed;
  echo "$release START --";
  lxc-proposed-snapshot --proposed --publish $release $ref;
  lxc init $ref test-$release;
  lxc start test-$release;
  lxc exec test-$release -- apt install apport;
  lxc exec test-$release -- dpkg-query --show apport;
  lxc exec test-$release -- ubuntu-bug cloud-init;
  done

  [Regression Potential]
  Minimal. This bug only affects packages with >9 bug filing options for a 
given choice. Worst case, is bugs filed would incorrectly represent option 1 of 
a selection instead of option 1X.

  
  === End SRU Template ===

  === original description ===
  the newly added cloud-init apport support shows a list of cloud providers and 
asks the user to select one.  There are currently 18 options.  For any option > 
10, apport will just take the '1' that is typed as the answer.

  It should obviously wait for more than one character or a carriage
  return.

  *** Please select the cloud vendor or environment in which this
  instance is running

  Choices:
    1: Amazon - Ec2
    2: AliYun
    3: AltCloud
    4: Azure
    5: Bigstep
    6: CloudSigma
    7: CloudStack
    8: DigitalOcean
    9: GCE - Google Compute Engine
    10: MAAS
    11: NoCloud
    12: OpenNebula
    13: OpenStack
    14: OVF
    15: Scaleway
    16: SmartOS
    17: VMware
    18: Other
    C: Cancel
  Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 10 15:21:48 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1722564/+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 1502173] Re: Python warnings: modules imported without specifying a version first

2017-11-28 Thread Brian Murray

I was unable to recreate this problem on Ubuntu 17.10. Can you provide
some more details about the version of apport you have installed or what
exactly you are seeing?

bdmurray@impulse:~$ apt-cache policy apport
apport:
  Installed: 2.20.7-0ubuntu3.5
  Candidate: 2.20.7-0ubuntu3.5
  Version table:
 *** 2.20.7-0ubuntu3.5 500
500 http://192.168.10.7/ubuntu artful-updates/main amd64 Packages
500 http://192.168.10.7/ubuntu artful-updates/main i386 Packages
500 http://192.168.10.7/ubuntu artful-security/main amd64 Packages
500 http://192.168.10.7/ubuntu artful-security/main i386 Packages
100 /var/lib/dpkg/status
 2.20.7-0ubuntu3 500
500 http://192.168.10.7/ubuntu artful/main amd64 Packages
500 http://192.168.10.7/ubuntu artful/main i386 Packages
bdmurray@impulse:~$ /usr/share/apport/apport-gtk

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

Title:
  Python warnings: modules imported without specifying a version first

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Released

Bug description:
  [Description]
  Users receive warnings about importing of python modules without a version 
being specified.  While this isn't a big deal in itself we get lots of bug 
reports from people about this issue since it is so obvious.  Given that Ubuntu 
16.04 is an LTS release we should fix this and prevent further reporting of the 
issue.

  [Test Case]
  1) run /usr/share/apport/apport-gtk in a terminal
  2) Observe the following

  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
    from gi.repository import GLib, Wnck, GdkX11, Gdk
  /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without 
specifying a version first. Use gi.require_version('GdkX11', '3.0') before 
import to ensure that the right version gets loaded.
    from gi.repository import GLib, Wnck, GdkX11, Gdk

  with the version of apport in -proposed you'll no longer receive the
  warning.

  [Regression Potential]As with any SRU this could cause a regression in
  the software if the fix is typo'ed so review it carefully.  If there
  isn't a typo and then the chance of a regression is very very very
  low.

  Original Description
  

  Hi,

  here is the problem:

  $ /usr/share/apport/apport-gtk
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
    from gi.repository import GLib, Wnck, GdkX11, Gdk
  /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without 
specifying a version first. Use gi.require_version('GdkX11', '3.0') before 
import to ensure that the right version gets loaded.
    from gi.repository import GLib, Wnck, GdkX11, Gdk

  ProblemType: BugDistroRelease: Ubuntu 15.10
  Package: apport-gtk 2.19-0ubuntu1
  Uname: Linux 4.2.2-040202-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Oct  2 16:17:14 2015
  EcryptfsInUse: Yes
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1502173/+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 1380976] Re: Limiting queue disk space does not work, upgrade needed

2017-11-28 Thread Malte Schmidt

I confirmed this bug as it still affects 7.4.4-1ubuntu2.7 from trusty-
updates.

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

Title:
  Limiting queue disk space does not work, upgrade needed

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  # lsb_release -rd
  Description:Ubuntu 14.04.1 LTS
  Release:14.04
  # apt-cache policy rsyslog
  rsyslog:
Installed: 7.4.4-1ubuntu2.3
Candidate: 7.4.4-1ubuntu2.3
Version table:
   [...]

  When rsyslog is run with a config to save/cache log to disk, e.g when the 
host that
  it is forwarding log to is not responding, it fails to respect the
  maxdiskspace parameter. This is a known bug and 7.4.7 of v7-stable has
  been released to fix this, see 
http://www.rsyslog.com/changelog-for-7-4-7-v7-stable/

  
  Config for testing:

  global(
workDirectory="/tmp"
  )

  module(load="imudp")
  module(load="omrelp")

  input(type="imudp"
port="514"
  )

  action(type="omrelp"
target="localhost"
port="2514"
action.resumeRetryCount="-1"
queue.saveonshutdown="on"
queue.type="LinkedList"
queue.filename="omrelp"

queue.maxfilesize="100M"
queue.maxdiskspace="1M"

queue.checkpointinterval="100"
queue.highwatermark="10"
  )

  Then just log more than 1MB of messages to UDP to see that it doesn't
  stop at 1MB but just continues forever.

  Please upgrade the package to 7.4.7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1380976/+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 1734922] [NEW] Ubuntu releases its IP during system reboot/shutdown

You have been subscribed to a public bug:

Hi,

I got a weird problem in our setup. Every time I reboot Ubuntu systems
it is releasing its IP from the DHCP server. So the IP is getting free
in DHCP. Therefore in some cases DHCP is offering the same IP to other
system. And its then difficult to find the new IP assigned to the system
as it is located at remote location.  IP reservation may help, but we
cannot go for reservation as we have huge number of system.

I checked with other distributions(RHEL/CentOS/Fedora/Windows), those
systems does not release IP during system reboot/shutdown

And the IP release is happening when the interface is added in
/etc/network/interfaces file with dhcp options.


Kindly suggest how can I prevent IP release during system shutdown/reboot in 
Ubuntu

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
Ubuntu releases its IP during system reboot/shutdown
https://bugs.launchpad.net/bugs/1734922
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to isc-dhcp 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 1734922] Re: Ubuntu releases its IP during system reboot/shutdown

2017-11-28 Thread Sourav Maity

** Package changed: ubuntu => isc-dhcp (Ubuntu)

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

Title:
  Ubuntu releases its IP during system reboot/shutdown

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Hi,

  I got a weird problem in our setup. Every time I reboot Ubuntu systems
  it is releasing its IP from the DHCP server. So the IP is getting free
  in DHCP. Therefore in some cases DHCP is offering the same IP to other
  system. And its then difficult to find the new IP assigned to the
  system as it is located at remote location.  IP reservation may help,
  but we cannot go for reservation as we have huge number of system.

  I checked with other distributions(RHEL/CentOS/Fedora/Windows), those
  systems does not release IP during system reboot/shutdown

  And the IP release is happening when the interface is added in
  /etc/network/interfaces file with dhcp options.

  
  Kindly suggest how can I prevent IP release during system shutdown/reboot in 
Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1734922/+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 1730395] Re: ibus pinyin preference not working

2017-11-28 Thread KANGOD

@walterclozet I wish so, but on Ubuntu 17.10, I just got

$ sudo apt install python-ibus
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package python-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/1730395

Title:
  ibus pinyin preference not working

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  System is Ubuntu 17.10 amd64
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  
  select sunpinyin from gtk3 menu, click preference, nothing happens. trying 
cli mode, error shows:
  /usr/lib/ibus/ibus-setup-sunpinyin
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid 
string constant "murrine-scrollbar", expected valid string constant
  Traceback (most recent call last):
File "/usr/share//ibus-sunpinyin/setup/main.py", line 42, in 
  import ibus
  ImportError: No module named ibus

  it seems python-ibus is missing, but trying to install python-ibus
  shows the package does not exists. seems only exists in trusty and
  trusty-update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1730395/+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 1734503] Re: In Xfce, Gnome3, Ubuntu Studio, and Mate Desktop the pulse audio gui application is corrupted, I can't switch outputs.

2017-11-28 Thread c_smooth

I took all the other DE's from my system, I think a lot of the problems
stemmed from running KDE Plasma from a backport. It pretty much
conflicted with every DE theme except cinnamon. There where still some
problems even after I removed it, but at least cinnamon works.

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

Title:
  In Xfce, Gnome3, Ubuntu Studio, and Mate Desktop the pulse audio gui
  application is corrupted, I can't switch outputs.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.3 LTS
  1.8.0
  I expected to be able to switch to different outputs of my sound hardware. 
That list is gone and all I have is a volume circle knob. This doesn't effect 
the cinnamon DE but it does effect Gnome3, Mate, Xfce, and Xfce ubuntu studio 
edition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.4
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Sat Nov 25 22:12:43 2017
  InstallationDate: Installed on 2017-09-29 (57 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: Z87-M8
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd11/07/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87-M8:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-10-18T18:43:48.348315

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1734503/+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 1734942] [NEW] package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

2017-11-28 Thread Venkatasubramanian R

Public bug reported:

my laptop detected this issue

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: hicolor-icon-theme 0.15-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
Date: Tue Nov 28 19:20:13 2017
Dependencies:
 
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2017-10-12 (47 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: hicolor-icon-theme
Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

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

Bug description:
  my laptop detected this issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Tue Nov 28 19:20:13 2017
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-10-12 (47 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1734942/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

2017-11-28 Thread Scott Moser

I've verified that this is reproducible within lxc, and then filed a bug i
saw (bug 1734939) as a result.

Heres a trivial reproduce:

## just showing content of the url.
$ curl --silent https://hastebin.com/raw/coladicuva
#!/bin/sh
cat /proc/uptime | tee /run/user-script-uptime

$ name=btest
$ lxc launch ubuntu-daily:bionic $name \
   "--config=user.user-data=#include https://hastebin.com/raw/coladicuva";

$ sleep 20
$ lxc exec b4 grep WARN /var/log/cloud-init.log
2017-11-28 16:49:12,251 - user_data.py[WARNING]: 
HTTPSConnectionPool(host='hastebin.com', port=443): Max retries exceeded with 
url: /raw/coladicuva (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary 
failure in name resolution',)) for url: https://hastebin.com/raw/coladicuva



** Changed in: cloud-init (Ubuntu Bionic)
   Importance: High => Critical

** Changed in: cloud-init (Ubuntu Artful)
   Importance: High => Critical

** Changed in: systemd (Ubuntu Bionic)
   Importance: High => Critical

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

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Confirmed
Status in cloud-init source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://";

  And https is not going to work for a raw IP address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1734942] Re: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

2017-11-28 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 hicolor-icon-theme in
Ubuntu.
https://bugs.launchpad.net/bugs/1734942

Title:
  package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

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

Bug description:
  my laptop detected this issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Tue Nov 28 19:20:13 2017
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-10-12 (47 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1734942/+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 1734943] [NEW] no internet access, from any wi-fi network or wired network

2017-11-28 Thread Alex Manea

Public bug reported:

Today, when i started Ubuntu. In bar, on the network icon appear a "?"
symbol. I tried to connect Ubuntu to internet with a wired cable and
another wi-fi network. He's connect to wi-fi and wired cable network but
appears a "?" symbol in the network icon and i don't have access on the
internet. Sorry for my bad english  :))) Thank you!

P.S. i use Ubuntu 17.10

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Assignee: Alex Manea (manea101)
 Status: New

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Alex Manea (manea101)

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

Title:
  no internet access, from any wi-fi network or wired network

Status in systemd package in Ubuntu:
  New

Bug description:
  Today, when i started Ubuntu. In bar, on the network icon appear a "?"
  symbol. I tried to connect Ubuntu to internet with a wired cable and
  another wi-fi network. He's connect to wi-fi and wired cable network
  but appears a "?" symbol in the network icon and i don't have access
  on the internet. Sorry for my bad english  :))) Thank you!

  P.S. i use Ubuntu 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734943/+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 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

2017-11-28 Thread Manoj Iyer

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => High

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

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

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for ppaid...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080 : 0080
  [   42.323969570,7] HBRT: OCC common base 00200080 : 0080
  [   42.330941943,7] HBRT: OCC common base 00200080 : 0080
  [5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
  [6.017413373,7] HBRT: OCC Load requested
  [6.017414365,7] HBRT: Calling loadOCC() homer 00200140, 
occ_common_area 00200080, chip 
  [6.017553013,7] HBRT: Calling loadOCC() homer 3a00, 
occ_common_area 00200080, chip 0001
  [6.017666150,7] HBRT: Calling loadOCC() homer 00280040, 
occ_common_area 00200080, chip 0010
  [6.017790110,7] HBRT: Calling loadOCC() homer 00100040, 
occ_common_area 00200080, chip 0011
  [

[Touch-packages] [Bug 1699759] Re: LXC Alpine template broken on ppc64le

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  LXC Alpine template broken on ppc64le

Status in The Ubuntu-power-systems project:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-06-14 07:36:33 ==
  LXC Alpine template is broken on Ubuntu 17.10, since it does not support 
ppc64le.

  It shows the following message:

  # Unknown architecture.

  == Comment: #1 - Breno Leitao  - 2017-06-14 07:37:50 ==
  Patch sent to upstream and accepted already:

  https://github.com/lxc/lxc/pull/1621#issuecomment-307887344

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1699759/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-11-28 Thread Greg Lutostanski

Confirmed with Drew that this bug has not been hit since the pacemaker
fix released.

Can remove field-high team, but keep for the discussion on init-system-
helpers.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in pacemaker package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  Confirmed
Status in pacemaker source package in Xenial:
  Fix Released
Status in init-system-helpers source package in Zesty:
  Confirmed
Status in pacemaker source package in Zesty:
  Fix Released
Status in init-system-helpers source package in Artful:
  Confirmed
Status in pacemaker source package in Artful:
  Fix Released
Status in init-system-helpers source package in Bionic:
  Confirmed
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1652466] Re: Totem can't play videos on Gallium graphics without mesa-va-drivers

2017-11-28 Thread Amr Ibrahim

I have tested the version in xenial-proposed and it works well as in the
test case.

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

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

Title:
  Totem can't play videos on Gallium graphics without mesa-va-drivers

Status in One Hundred Papercuts:
  Fix Committed
Status in libva package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid
Status in libva source package in Xenial:
  Fix Committed
Status in totem source package in Xenial:
  Invalid

Bug description:
  Impact
  ---
  Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium 
graphics in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.

  Here is the dependency chain in Xenial:
  gstreamer1.0-vaapi Depends on libva1
  libva1 Recommends va-driver-all
  va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers)

  This is fixed in version 1.7.0-2 in Debian and Yakkety.
  libva (1.7.0-2) unstable; urgency=medium

* debian/control:
  - Add mesa-va-drivers as alternative to Depends of va-driver-all.
  - Bump Standards-Versions.

   -- Sebastian Ramacher   Wed, 11 May 2016
  17:32:06 +0200

  
  Test case
  --
  - Purge va-driver-all and mesa-va-drivers if already installed
  - Install va-driver-all from xenial-proposed
  - Make sure that mesa-va-drivers is pulled in
  - Play videos in Totem with gstreamer1.0-vaapi installed and make sure that 
videos play nicely.

  Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and 
no mesa-va-drivers):
  :~$ totem
  Stream with high frequencies VQ coding
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0

  When mesa-va-drivers is installed, Totem plays videos just fine.

  
  Regression potential
  -
  Since there are no code changes at all, I cannot think of any regressions.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: va-driver-all 1.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 24 21:54:20 2016
  InstallationDate: Installed on 2016-04-26 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libva
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1652466/+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 1708409] Re: kdump service does not start after configure/reboot

** Tags added: ppc64el-kdump

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Triaged
Status in makedumpfile source package in Artful:
  New
Status in systemd source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+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 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

2017-11-28 Thread Khaled El Mously

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in bluez source package in Zesty:
  New
Status in linux source package in Zesty:
  Fix Committed
Status in bluez source package in Artful:
  New
Status in linux source package in Artful:
  Fix Committed

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+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 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

2017-11-28 Thread Khaled El Mously

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-zesty

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in bluez source package in Zesty:
  New
Status in linux source package in Zesty:
  Fix Committed
Status in bluez source package in Artful:
  New
Status in linux source package in Artful:
  Fix Committed

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+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 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

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

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

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

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for ppaid...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080 : 0080
  [   42.323969570,7] HBRT: OCC common base 00200080 : 0080
  [   42.330941943,7] HBRT: OCC common base 00200080 : 0080
  [5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
  [6.017413373,7] HBRT: OCC Load requested
  [6.017414365,7] HBRT: Calling loadOCC() homer 00200140, 
occ_common_area 00200080, chip 
  [6.017553013,7] HBRT: Calling loadOCC() homer 3a00, 
occ_common_area 00200080, chip 0001
  [6.017666150,7] HBRT: Calling loadOCC() homer 00280040, 
occ_common_area 00200080, chip 0010
  [6.017790110,7] HBRT: Calling loadOCC() homer 00100040, 
occ_common_area 00200080, chip 0011
  [

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

2017-11-28 Thread Manoj Iyer

** Changed in: ubuntu-power-systems
 Assignee: David Britton (davidpbritton) => Canonical Server Team 
(canonical-server)

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  New

Bug description:
  Attn. Canonical:  Please make sure that the existing iproute2 package
  gets updated with the two referenced patches as the missing
  information is impacting our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data
   
  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-42A 
   
  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
   
  == Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

  I found upstream already had patches that fix this problem:

  1) https://www.spinics.net/lists/netdev/msg415009.html
  commit 530903dd9003492edb0714e937ad4a5d1219e376
  Author: Petr Vorel 
  Date:   Tue Jan 17 00:25:50 2017 +0100

  ip: fix igmp parsing when iface is long

  Entries with long vhost names in /proc/net/igmp have no whitespace
  between name and colon, so sscanf() adds it to vhost and
  'ip maddr show iface' doesn't include inet result.

  Signed-off-by: Petr Vorel 

  
  2) https://www.spinics.net/lists/netdev/msg461479.html
  commit 21503ed2af233ffe795926f6641ac84ec1b15bf9
  Author: Michal Kubecek 
  Date:   Thu Oct 19 10:21:08 2017 +0200

  ip maddr: fix filtering by device

  Commit 530903dd9003 ("ip: fix igmp parsing when iface is long") uses
  variable len to keep trailing colon from interface name comparison.  This
  variable is local to loop body but we set it in one pass and use it in
  following one(s) so that we are actually using (pseudo)random length for
  comparison. This became apparent since commit b48a1161f5f9 ("ipmaddr: 
Avoid
  accessing uninitialized data") always initializes len to zero so that the
  name comparison is always true. As a result, "ip maddr show dev eth0" 
shows
  IPv4 multicast addresses for all interfaces.

  Instead of keeping the length, let's simply replace the trailing colon 
with
  a null byte. The bonus is that we get correct interface name in ma.name.

  Fixes: 530903dd9003 ("ip: fix igmp parsing when iface is long")
  Signed-off-by: Michal Kubecek 
  Acked-by: Phil Sutter 
  Acked-by: Petr Vorel 

  The fix is in the same place, but different way.
  This is the current implementation In ip/ipmaddr.c file:
  struct ma_info *ma;

  if (buf[0] != '\t') {
  size_t len;

  sscanf(buf, "%d%s", &m.index, m.name);
  len = strlen(m.name);
  if (m.name[len - 1] == ':')
  m.name[len - 1] = '\0';
  continue;
  }

  
  The existing "ip" command that shows the problem:
  [root@coral-sriov-host1 ip]# /usr/sbin/ip maddr show dev enP1p12s0f0   /* <-- 
We do NOT see the IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet6 ff02::1
  inet6 ff01::1

  I clone the latest "ip" utility from upstream to the same test box.
  [root@coral-sriov-host1 git_iproute2]# git clone 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git

  I build the "ip" utility on same test box, which has the above 2
  patches included.

  [root@coral-sriov-host1 ip]# /root/git_iproute2/iproute2/ip/ip maddr show dev 
enP1p12s0f0  /* <--- shows correct IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet  224.0.0.1/* <--- */
  inet6 ff02::1
  inet6 ff01::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pow

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

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

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  New

Bug description:
  Attn. Canonical:  Please make sure that the existing iproute2 package
  gets updated with the two referenced patches as the missing
  information is impacting our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data
   
  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-42A 
   
  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
   
  == Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

  I found upstream already had patches that fix this problem:

  1) https://www.spinics.net/lists/netdev/msg415009.html
  commit 530903dd9003492edb0714e937ad4a5d1219e376
  Author: Petr Vorel 
  Date:   Tue Jan 17 00:25:50 2017 +0100

  ip: fix igmp parsing when iface is long

  Entries with long vhost names in /proc/net/igmp have no whitespace
  between name and colon, so sscanf() adds it to vhost and
  'ip maddr show iface' doesn't include inet result.

  Signed-off-by: Petr Vorel 

  
  2) https://www.spinics.net/lists/netdev/msg461479.html
  commit 21503ed2af233ffe795926f6641ac84ec1b15bf9
  Author: Michal Kubecek 
  Date:   Thu Oct 19 10:21:08 2017 +0200

  ip maddr: fix filtering by device

  Commit 530903dd9003 ("ip: fix igmp parsing when iface is long") uses
  variable len to keep trailing colon from interface name comparison.  This
  variable is local to loop body but we set it in one pass and use it in
  following one(s) so that we are actually using (pseudo)random length for
  comparison. This became apparent since commit b48a1161f5f9 ("ipmaddr: 
Avoid
  accessing uninitialized data") always initializes len to zero so that the
  name comparison is always true. As a result, "ip maddr show dev eth0" 
shows
  IPv4 multicast addresses for all interfaces.

  Instead of keeping the length, let's simply replace the trailing colon 
with
  a null byte. The bonus is that we get correct interface name in ma.name.

  Fixes: 530903dd9003 ("ip: fix igmp parsing when iface is long")
  Signed-off-by: Michal Kubecek 
  Acked-by: Phil Sutter 
  Acked-by: Petr Vorel 

  The fix is in the same place, but different way.
  This is the current implementation In ip/ipmaddr.c file:
  struct ma_info *ma;

  if (buf[0] != '\t') {
  size_t len;

  sscanf(buf, "%d%s", &m.index, m.name);
  len = strlen(m.name);
  if (m.name[len - 1] == ':')
  m.name[len - 1] = '\0';
  continue;
  }

  
  The existing "ip" command that shows the problem:
  [root@coral-sriov-host1 ip]# /usr/sbin/ip maddr show dev enP1p12s0f0   /* <-- 
We do NOT see the IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet6 ff02::1
  inet6 ff01::1

  I clone the latest "ip" utility from upstream to the same test box.
  [root@coral-sriov-host1 git_iproute2]# git clone 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git

  I build the "ip" utility on same test box, which has the above 2
  patches included.

  [root@coral-sriov-host1 ip]# /root/git_iproute2/iproute2/ip/ip maddr show dev 
enP1p12s0f0  /* <--- shows correct IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet  224.0.0.1/* <--- */
  inet6 ff02::1
  inet6 ff01::1

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

-- 
Mailing list: ht

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

2017-11-28 Thread David Britton

** Changed in: iproute2 (Ubuntu)
 Assignee: David Britton (davidpbritton) => Andreas Hasenack (ahasenack)

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  New

Bug description:
  Attn. Canonical:  Please make sure that the existing iproute2 package
  gets updated with the two referenced patches as the missing
  information is impacting our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data
   
  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-42A 
   
  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
   
  == Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

  I found upstream already had patches that fix this problem:

  1) https://www.spinics.net/lists/netdev/msg415009.html
  commit 530903dd9003492edb0714e937ad4a5d1219e376
  Author: Petr Vorel 
  Date:   Tue Jan 17 00:25:50 2017 +0100

  ip: fix igmp parsing when iface is long

  Entries with long vhost names in /proc/net/igmp have no whitespace
  between name and colon, so sscanf() adds it to vhost and
  'ip maddr show iface' doesn't include inet result.

  Signed-off-by: Petr Vorel 

  
  2) https://www.spinics.net/lists/netdev/msg461479.html
  commit 21503ed2af233ffe795926f6641ac84ec1b15bf9
  Author: Michal Kubecek 
  Date:   Thu Oct 19 10:21:08 2017 +0200

  ip maddr: fix filtering by device

  Commit 530903dd9003 ("ip: fix igmp parsing when iface is long") uses
  variable len to keep trailing colon from interface name comparison.  This
  variable is local to loop body but we set it in one pass and use it in
  following one(s) so that we are actually using (pseudo)random length for
  comparison. This became apparent since commit b48a1161f5f9 ("ipmaddr: 
Avoid
  accessing uninitialized data") always initializes len to zero so that the
  name comparison is always true. As a result, "ip maddr show dev eth0" 
shows
  IPv4 multicast addresses for all interfaces.

  Instead of keeping the length, let's simply replace the trailing colon 
with
  a null byte. The bonus is that we get correct interface name in ma.name.

  Fixes: 530903dd9003 ("ip: fix igmp parsing when iface is long")
  Signed-off-by: Michal Kubecek 
  Acked-by: Phil Sutter 
  Acked-by: Petr Vorel 

  The fix is in the same place, but different way.
  This is the current implementation In ip/ipmaddr.c file:
  struct ma_info *ma;

  if (buf[0] != '\t') {
  size_t len;

  sscanf(buf, "%d%s", &m.index, m.name);
  len = strlen(m.name);
  if (m.name[len - 1] == ':')
  m.name[len - 1] = '\0';
  continue;
  }

  
  The existing "ip" command that shows the problem:
  [root@coral-sriov-host1 ip]# /usr/sbin/ip maddr show dev enP1p12s0f0   /* <-- 
We do NOT see the IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet6 ff02::1
  inet6 ff01::1

  I clone the latest "ip" utility from upstream to the same test box.
  [root@coral-sriov-host1 git_iproute2]# git clone 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git

  I build the "ip" utility on same test box, which has the above 2
  patches included.

  [root@coral-sriov-host1 ip]# /root/git_iproute2/iproute2/ip/ip maddr show dev 
enP1p12s0f0  /* <--- shows correct IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet  224.0.0.1/* <--- */
  inet6 ff02::1
  inet6 ff01::1

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

[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

2017-11-28 Thread David Britton

** Changed in: util-linux (Ubuntu)
 Assignee: David Britton (davidpbritton) => Patricia Gaughen (gaughen)

** Changed in: ubuntu-power-systems
 Assignee: Canonical Server Team (canonical-server) => (unassigned)

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

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

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for ppaid...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080 : 0080
  [   42.323969570,7] HBRT: OCC common base 00200080 : 0080
  [   42.330941943,7] HBRT: OCC common base 00200080 : 0080
  [5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
  [6.017413373,7] HBRT: OCC Load requested
  [6.017414365,7] HBRT: Calling loadOCC() homer 00200140, 
occ_common_area 00200080, chip 
  [6.017553013,7] HBRT: Calling loadOCC() homer 3a00, 
occ_common_area 00200080, chip 0001
  [6.017666150,7] HBRT: Calling loadOCC() homer 00280040, 
occ_common

[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-11-28 Thread David Britton

** No longer affects: init-system-helpers (Ubuntu Bionic)

** No longer affects: init-system-helpers (Ubuntu Artful)

** No longer affects: init-system-helpers (Ubuntu Zesty)

** No longer affects: init-system-helpers (Ubuntu Xenial)

** Changed in: init-system-helpers (Ubuntu)
   Status: Confirmed => Opinion

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Opinion
Status in pacemaker package in Ubuntu:
  Fix Released
Status in pacemaker source package in Xenial:
  Fix Released
Status in pacemaker source package in Zesty:
  Fix Released
Status in pacemaker source package in Artful:
  Fix Released
Status in pacemaker source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.

  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker

  pacemaker daemons will not be restarted.

  [Regression Potential]
  Minimal, earlier and later versions provide the defaults in the lsb header.

  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1734960] [NEW] Bluetooth headset profile HSP/HFP doesn't work

2017-11-28 Thread pl7ofit

Public bug reported:

My bluetooth headphones Bluedio T2S has a microphone and support HSP/HFP 
profile, but when i try change sound profile in blueman-manager to HSP/HFP - 
then i get error "Failed to change profile to headset_head_unit".
With profile a2dp headphones work good(clementine, chromium etc..), but I could 
not get work output headphones in steam games, i listen only silence(i think 
it's problem of pulseaudio)

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
 /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
CurrentDesktop: MATE
Date: Tue Nov 28 19:51:59 2017
InstallationDate: Installed on 2016-06-22 (524 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: Bluedio
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
 /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
Symptom_Type: No sound at all
Title: [Bluedio, recording] No sound at all
UpgradeStatus: Upgraded to zesty on 2017-11-24 (4 days ago)
dmi.bios.date: 07/08/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: L2.38
dmi.board.name: AM2NF6G-VSTA
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL2.38:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2017-11-24T19:23:23.458810

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


** Tags: amd64 apport-bug third-party-packages zesty

** Attachment added: "Снимок экрана в 2017-11-28 20-06-41.png"
   
https://bugs.launchpad.net/bugs/1734960/+attachment/5015793/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%B2%202017-11-28%2020-06-41.png

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

Title:
  Bluetooth headset profile HSP/HFP doesn't work

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  My bluetooth headphones Bluedio T2S has a microphone and support HSP/HFP 
profile, but when i try change sound profile in blueman-manager to HSP/HFP - 
then i get error "Failed to change profile to headset_head_unit".
  With profile a2dp headphones work good(clementine, chromium etc..), but I 
could not get work output headphones in steam games, i listen only silence(i 
think it's problem of pulseaudio)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Nov 28 19:51:59 2017
  InstallationDate: Installed on 2016-06-22 (524 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Bluedio
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  Symptom_Type: No sound at all
  Title: [Bluedio, recording] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-11-24 (4 days ago)
  dmi.bios.date: 07/08/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L2.38
  dmi.board.name: AM2NF6G-VSTA
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL2.38:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Fi

[Touch-packages] [Bug 1734967] [NEW] tzdata info for WGT/WGST broken

2017-11-28 Thread Thomas M Steenholdt

Public bug reported:

Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed from
date command but instead just "-03". Problem is evident in PHP
applications too, which now think we're in Sao Paolo.

This appears to have changed with latest tzdata update or perhaps in
combination with change from DST.

Same problem on 16.04, 17.10 and Debian 9.

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

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

Title:
  tzdata info for WGT/WGST broken

Status in tzdata package in Ubuntu:
  New

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1734967/+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 1708409] Re: kdump service does not start after configure/reboot

2017-11-28 Thread Thadeu Lima de Souza Cascardo

It seems this has been reverted on systemd 235. However, as this might
come to bite us back again in the future (it was mentioned that
dependencies should not be added to aliases), and as Steve has pointed
out, it makes more sense to use multi-user.target, I am going to fix it
in a future release to come soon.

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Triaged
Status in makedumpfile source package in Artful:
  New
Status in systemd source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+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 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

2017-11-28 Thread Tres Finocchiaro

Sorry to bump a closed bug report, but what is the proposed solution?

On 17.10, I've enabled the "proposed" through Software & Updates, but
"ubuntu-themes" is not a valid package name.  Since "ubuntu-artwork" is
listed as a binary build from this package, I've updated that to no
avail.

Preparing to unpack 
.../ubuntu-artwork_1%3a16.10+17.10.20171115-0ubuntu1_all.deb ...
Unpacking ubuntu-artwork (1:16.10+17.10.20171115-0ubuntu1) over 
(1:16.10+17.10.20171115-0ubuntu1) ...
Setting up ubuntu-artwork (1:16.10+17.10.20171115-0ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-1) ...

But the original error ** "murrine-scrollbar", expected valid string
constant  ** still exists.

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1723422/+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 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

2017-11-28 Thread Tres Finocchiaro

Please disregard the above message.  Like @huerben, I have similar
symptom but a separate issue after updating.  The murrine-scrollbar
error has disappeared with the above steps.

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1723422/+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 1722313] Re: Enable auditing in util-linux.

version of package verified on artful,
 
ubuntu@artfulguest:~$ dpkg -l | grep util-linux
ii  util-linux 2.30.1-0ubuntu4.1
amd64miscellaneous system utilities

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

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress
Status in util-linux source package in Zesty:
  In Progress
Status in util-linux source package in Artful:
  Fix Committed
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.
   
  Only the hwclock and the login commands within util-linux package have source 
code for auditing. But that source code is disabled by default and requires the 
config option, --with-audit to enable it. The login command is not built nor 
shipped in util-linux. Ubuntu uses the login command from shadow instead. Thus, 
only hwclock command would be affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged if auditd daemon is running.
  Otherwise, nothing gets logged.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+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 1722313] Re: Enable auditing in util-linux.

Generated an artful VM and verified that this is fixed in artful.

ubuntu@artfulguest:~$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="17.10 (Artful Aardvark)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 17.10"
VERSION_ID="17.10"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=artful
UBUNTU_CODENAME=artful

altered the hwclock via "sudo hwclock --set --date "1/1/2000 00:00:00"

received following audit log message in appropriate log files when applicable.
type=USER_CMD msg=audit(1511896792.291:29): pid=3008 uid=1000 auid=1000 ses=2 
msg='cwd="/home/ubuntu" cmd="hwclock" terminal=pts/0 res=success'

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

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress
Status in util-linux source package in Zesty:
  In Progress
Status in util-linux source package in Artful:
  Fix Committed
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.
   
  Only the hwclock and the login commands within util-linux package have source 
code for auditing. But that source code is disabled by default and requires the 
config option, --with-audit to enable it. The login command is not built nor 
shipped in util-linux. Ubuntu uses the login command from shadow instead. Thus, 
only hwclock command would be affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged if auditd daemon is running.
  Otherwise, nothing gets logged.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+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 1722313] Re: Enable auditing in util-linux.

Sorry, comment #13 had a cut-and-paste issue.

log message is, 
type=USYS_CONFIG msg=audit(1511898182.500:184): pid=3305 uid=0 auid=1000 ses=2 
msg='op=change-system-time exe="/sbin/hwclock" hostname=artfulguest addr=? 
terminal=pts/0 res=success'

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

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress
Status in util-linux source package in Zesty:
  In Progress
Status in util-linux source package in Artful:
  Fix Committed
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.
   
  Only the hwclock and the login commands within util-linux package have source 
code for auditing. But that source code is disabled by default and requires the 
config option, --with-audit to enable it. The login command is not built nor 
shipped in util-linux. Ubuntu uses the login command from shadow instead. Thus, 
only hwclock command would be affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged if auditd daemon is running.
  Otherwise, nothing gets logged.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+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 1552792] Re: gnome software leaves dependencies installed

2017-11-28 Thread AsciiWolf

** Bug watch added: GNOME Bug Tracker #790956
   https://bugzilla.gnome.org/show_bug.cgi?id=790956

** Also affects: gnome-software via
   https://bugzilla.gnome.org/show_bug.cgi?id=790956
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome software leaves dependencies installed

Status in GNOME Software:
  Unknown
Status in Release Notes for Ubuntu:
  Fix Released
Status in aptdaemon package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  Triaged
Status in packagekit package in Ubuntu:
  New

Bug description:
  Using gnome software to install an application - removal of that
  package leaves behind dependencies

  Installing an application with ubuntu software centre only leaves
  behind config files (seen in synaptic labelled for complete removal).

  After installing and then removing alarm clock with USC -

  
  sudo apt-get autoremove 
  [sudo] password for wolf: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  
  After cleaning up and then reinstalling with gnome software, followed by the 
removal

  sudo apt-get autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
libappindicator1 libindicator7
  0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade.
  After this operation, 184 kB disk space will be freed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar  3 16:23:45 2016
  InstallationDate: Installed on 2015-10-29 (126 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1552792/+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 1722313] Re: Enable auditing in util-linux.

** Tags added: verification-done-artful

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

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress
Status in util-linux source package in Zesty:
  In Progress
Status in util-linux source package in Artful:
  Fix Committed
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.
   
  Only the hwclock and the login commands within util-linux package have source 
code for auditing. But that source code is disabled by default and requires the 
config option, --with-audit to enable it. The login command is not built nor 
shipped in util-linux. Ubuntu uses the login command from shadow instead. Thus, 
only hwclock command would be affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged if auditd daemon is running.
  Otherwise, nothing gets logged.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+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 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on

2017-11-28 Thread Ken VanDine

** Also affects: nux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Copy-paste and text selection doesn't work when caps-lock is on

Status in nux package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  New

Bug description:
  [Impact]
  Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps 
Lock is on

  [Test case]
  0) Set Caps-Lock on in your keyboard
  1) Open dash, and write something
  2) Ctrl+A should select all the text, Ctrl+C should copy,
     Ctrl+V should paste and Ctrl+X should cut

  Currently they don't work unless caps-lock is turned off

  [Possible regression]
  Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling 
won't work anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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 961679] Re: gtkrc is producing light menus from dark elements

2017-11-28 Thread Ken VanDine

** Also affects: ubuntu-themes (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  gtkrc is producing light menus from dark elements

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  New

Bug description:
  Examples - 
  Right click on any window's title bar
  In app window menus of gtk 2 apps, examples -  synaptic, browsers where 
global menus aren't used, vlc with no global menu, ect.
  Right click in a browser's  menu bar
  Systray right click menus

  The in app window  context menu of gtk2 windows is correctly light,
  maybe there is no way to have both, ie., it's either all dark or all
  light?

  The choice here would be to go with all dark if there is no other way

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: light-themes 0.1.8.31-0ubuntu1 [modified: 
usr/share/themes/Ambiance/gtk-2.0/gtkrc 
usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css 
usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css 
usr/share/themes/Ambiance/gtk-3.0/gtk.css 
usr/share/themes/Ambiance/gtk-3.0/settings.ini 
usr/share/themes/Ambiance/metacity-1/close.png 
usr/share/themes/Ambiance/metacity-1/close_focused_normal.png 
usr/share/themes/Ambiance/metacity-1/close_focused_prelight.png 
usr/share/themes/Ambiance/metacity-1/close_focused_pressed.png 
usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml]
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
  Uname: Linux 3.2.0-19-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Wed Mar 21 17:42:27 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: light-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/961679/+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 1735000] [NEW] package python3.4-minimal 3.4.3-1ubuntu1~14.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134

2017-11-28 Thread Aldert Piersma

Public bug reported:

Update stops.
update 2 week ago same problem.(was a update with new kernal, big update)
lately many problems with ubuntu:Often stops.

thanks in advance,
Sincerely
Aldert

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python3.4-minimal 3.4.3-1ubuntu1~14.04.6
ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
Date: Tue Nov 28 21:45:05 2017
DuplicateSignature: package:python3.4-minimal:3.4.3-1ubuntu1~14.04.6:subprocess 
installed post-installation script returned error exit status 134
ErrorMessage: subprocess installed post-installation script returned error exit 
status 134
InstallationDate: Installed on 2015-06-04 (908 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: python3.4
Title: package python3.4-minimal 3.4.3-1ubuntu1~14.04.6 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 134
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3.4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package python3.4-minimal 3.4.3-1ubuntu1~14.04.6 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 134

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Update stops.
  update 2 week ago same problem.(was a update with new kernal, big update)
  lately many problems with ubuntu:Often stops.

  thanks in advance,
  Sincerely
  Aldert

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python3.4-minimal 3.4.3-1ubuntu1~14.04.6
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Tue Nov 28 21:45:05 2017
  DuplicateSignature: 
package:python3.4-minimal:3.4.3-1ubuntu1~14.04.6:subprocess installed 
post-installation script returned error exit status 134
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 134
  InstallationDate: Installed on 2015-06-04 (908 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python3.4
  Title: package python3.4-minimal 3.4.3-1ubuntu1~14.04.6 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 134
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1735000/+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 1712921] Re: enabling networkd appears to eat up entropy

2017-11-28 Thread Mathieu Trudel-Lapierre

nplan 0.32~16.04.2 fails to build because I mismerged 0.32 and broke the
code skipping the test_routes_v6 test in the NetworkManager case.
Therefore, it can't possibly pass SRU verification.

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

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

Title:
  enabling networkd appears to eat up entropy

Status in nplan package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in nplan source package in Xenial:
  Fix Committed
Status in openssh source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in nplan source package in Zesty:
  Fix Committed
Status in openssh source package in Zesty:
  New
Status in systemd source package in Zesty:
  New
Status in nplan source package in Artful:
  In Progress
Status in openssh source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Triaged
Status in nplan source package in Bionic:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged

Bug description:
  [Impact]
  Booting systems have a limited amount of entropy, especially in some of the 
cloud cases. We should avoid using it up unnecessarily.

  [Test cases]

  == netplan ==
  1) Boot system with netplan config; using networkd renderer
  2) Validate that it starts and does not cause undue delay.
  2b) strace nplan at boottime (the netplan generator at 
/lib/systemd/system-generators/netplan) and validate it does not call 
get_random() / uuid_generate().
  3) Validate that config with NetworkManager renderer generates UUIDs.

  [Regression potential]
  Netplan depends on UUID generation to create correct networkManager 
configuration for VLANs. This is a specific use-case that is typically not hit, 
but any failure to generate valid NetworkManager configuration would be a 
regression from this SRU.

  ---

  enabling networkd appears to eat up entropy

  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.

  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1712921/+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 1717471] Re: networkd does not accept / set advertised mtu

2017-11-28 Thread Mathieu Trudel-Lapierre

nplan 0.32~16.04.2 fails to build because I mismerged 0.32 and broke the
code skipping the test_routes_v6 test in the NetworkManager case.
Therefore, it can't possibly pass SRU verification.

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

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

Title:
  networkd does not accept / set advertised mtu

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

Bug description:
  [Impact]
  Hosts may require a specific MTU to be set as passed by DHCP options. We 
should honor these settings to ensure proper communication of the host with the 
rest of the network.

  [Test case]
  1) Run netplan on a system that should receive MTU settings from DHCP.
  2) Validate that the MTU configuration provided by DHCP is applied to the 
right interface.

  [Regression Potential]
  If DHCP settings specify an invalid MTU setting which is currently being 
ignored and letting the systems communicate correctly with the network, then 
these systems would regress.

  ---

   Right, so as far as I can tell the neutron-api on lcy01 is
  configured to advertise an instance interface MTU of 1400, though
  that's lower than it has to be, and the new DHCP setup with networkd
  just doesn't respect that DHCP option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+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 1709135] Re: add bond primary parameter

2017-11-28 Thread Mathieu Trudel-Lapierre

nplan 0.32~16.04.2 fails to build because I mismerged 0.32 and broke the
code skipping the test_routes_v6 test in the NetworkManager case.
Therefore, it can't possibly pass SRU verification.

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

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

Title:
  add bond primary parameter

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

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+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 1735000] Re: package python3.4-minimal 3.4.3-1ubuntu1~14.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134

2017-11-28 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 python3.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1735000

Title:
  package python3.4-minimal 3.4.3-1ubuntu1~14.04.6 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 134

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Update stops.
  update 2 week ago same problem.(was a update with new kernal, big update)
  lately many problems with ubuntu:Often stops.

  thanks in advance,
  Sincerely
  Aldert

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python3.4-minimal 3.4.3-1ubuntu1~14.04.6
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Tue Nov 28 21:45:05 2017
  DuplicateSignature: 
package:python3.4-minimal:3.4.3-1ubuntu1~14.04.6:subprocess installed 
post-installation script returned error exit status 134
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 134
  InstallationDate: Installed on 2015-06-04 (908 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python3.4
  Title: package python3.4-minimal 3.4.3-1ubuntu1~14.04.6 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 134
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1735000/+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 1552792] Re: gnome software leaves dependencies installed

2017-11-28 Thread Bug Watch Updater

** Changed in: gnome-software
   Status: Unknown => Confirmed

** Changed in: gnome-software
   Importance: Unknown => High

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

Title:
  gnome software leaves dependencies installed

Status in GNOME Software:
  Confirmed
Status in Release Notes for Ubuntu:
  Fix Released
Status in aptdaemon package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  Triaged
Status in packagekit package in Ubuntu:
  New

Bug description:
  Using gnome software to install an application - removal of that
  package leaves behind dependencies

  Installing an application with ubuntu software centre only leaves
  behind config files (seen in synaptic labelled for complete removal).

  After installing and then removing alarm clock with USC -

  
  sudo apt-get autoremove 
  [sudo] password for wolf: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  
  After cleaning up and then reinstalling with gnome software, followed by the 
removal

  sudo apt-get autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
libappindicator1 libindicator7
  0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade.
  After this operation, 184 kB disk space will be freed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar  3 16:23:45 2016
  InstallationDate: Installed on 2015-10-29 (126 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1552792/+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 1735002] [NEW] Allow configuring Wi-Fi MAC Randomization feature from GUI

2017-11-28 Thread Jeremy Bicha

Public bug reported:

Recent versions of NetworkManager have a feature enabled by default to
use a random MAC address when scanning for available Wi-Fi networks for
privacy. My understanding is that the spoofed MAC address is not used
when actually connecting to a network.

This feature was disabled in Ubuntu 17.10 because it broke scanning with
some Wi-Fi drivers. My understanding is that there is a bug in some
drivers when attempting to change the MAC address. See LP: #1681513.

The bug might not be as big of an issue with the latest version of 
NetworkManager because
1) There are helpful commits like this (it was not backported to 17.04):
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=46d53e1
2) It is also possible now to selectively disable Wi-Fi MAC Randomization for 
specific drivers.
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b869d9

However, I'm really hesitant to re-enable this feature as long as
A) we don't know for sure which drivers are affected,
B) and more importantly, there is no GUI way to turn the feature on or off. 
Asking users to edit config files isn't very nice.

The MAC Address Randomization feature is really nice (Windows 10 has a
similar feature) but I think we need a GUI on/off switch in Settings >
Wi-Fi or Settings > Privacy.

** Affects: gnome-control-center
 Importance: Unknown
 Status: Unknown

** Affects: network-manager
 Importance: Unknown
 Status: Unknown

** Affects: gnome-control-center (Ubuntu)
 Importance: Wishlist
 Status: Triaged

** Affects: network-manager (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: bionic

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

** Bug watch added: GNOME Bug Tracker #781295
   https://bugzilla.gnome.org/show_bug.cgi?id=781295

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=781295
   Importance: Unknown
   Status: Unknown

** Bug watch added: GNOME Bug Tracker #790961
   https://bugzilla.gnome.org/show_bug.cgi?id=790961

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=790961
   Importance: Unknown
   Status: Unknown

** Tags added: bionic

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

Title:
  Allow configuring Wi-Fi MAC Randomization feature from GUI

Status in gnome-control-center:
  Unknown
Status in NetworkManager:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Recent versions of NetworkManager have a feature enabled by default to
  use a random MAC address when scanning for available Wi-Fi networks
  for privacy. My understanding is that the spoofed MAC address is not
  used when actually connecting to a network.

  This feature was disabled in Ubuntu 17.10 because it broke scanning
  with some Wi-Fi drivers. My understanding is that there is a bug in
  some drivers when attempting to change the MAC address. See LP:
  #1681513.

  The bug might not be as big of an issue with the latest version of 
NetworkManager because
  1) There are helpful commits like this (it was not backported to 17.04):
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=46d53e1
  2) It is also possible now to selectively disable Wi-Fi MAC Randomization for 
specific drivers.
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b869d9

  However, I'm really hesitant to re-enable this feature as long as
  A) we don't know for sure which drivers are affected,
  B) and more importantly, there is no GUI way to turn the feature on or off. 
Asking users to edit config files isn't very nice.

  The MAC Address Randomization feature is really nice (Windows 10 has a
  similar feature) but I think we need a GUI on/off switch in Settings >
  Wi-Fi or Settings > Privacy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1735002/+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 769874] Re: Naming restrictions in UFL considered non-free by Debian

2017-11-28 Thread Bug Watch Updater

** Changed in: debian
   Status: New => Fix Committed

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

Title:
  Naming restrictions in UFL considered non-free by Debian

Status in Ubuntu Font Family:
  Invalid
Status in Ubuntu Font Licence:
  Incomplete
Status in ubuntu-font-family-sources package in Ubuntu:
  Invalid
Status in Debian:
  Fix Committed

Bug description:
  The Debian ftpmaster consider the Ubuntu Font License to be non-free:

    "After discussion in the FTP Team, we consider the font naming restrictions
    to restrictive and unclear for main."

http://lists.alioth.debian.org/pipermail/pkg-fonts-
  devel/2011-April/006515.html

  Debian ITP:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603157

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/769874/+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 1735002] Re: Allow configuring Wi-Fi MAC Randomization feature from GUI

2017-11-28 Thread Bug Watch Updater

** Changed in: gnome-control-center
   Status: Unknown => Confirmed

** Changed in: gnome-control-center
   Importance: Unknown => Wishlist

** Changed in: network-manager
   Status: Unknown => Confirmed

** Changed in: network-manager
   Importance: Unknown => Wishlist

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

Title:
  Allow configuring Wi-Fi MAC Randomization feature from GUI

Status in gnome-control-center:
  Confirmed
Status in NetworkManager:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Recent versions of NetworkManager have a feature enabled by default to
  use a random MAC address when scanning for available Wi-Fi networks
  for privacy. My understanding is that the spoofed MAC address is not
  used when actually connecting to a network.

  This feature was disabled in Ubuntu 17.10 because it broke scanning
  with some Wi-Fi drivers. My understanding is that there is a bug in
  some drivers when attempting to change the MAC address. See LP:
  #1681513.

  The bug might not be as big of an issue with the latest version of 
NetworkManager because
  1) There are helpful commits like this (it was not backported to 17.04):
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=46d53e1
  2) It is also possible now to selectively disable Wi-Fi MAC Randomization for 
specific drivers.
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b869d9

  However, I'm really hesitant to re-enable this feature as long as
  A) we don't know for sure which drivers are affected,
  B) and more importantly, there is no GUI way to turn the feature on or off. 
Asking users to edit config files isn't very nice.

  The MAC Address Randomization feature is really nice (Windows 10 has a
  similar feature) but I think we need a GUI on/off switch in Settings >
  Wi-Fi or Settings > Privacy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1735002/+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 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

2017-11-28 Thread Andreas Hasenack

** Changed in: iproute2 (Ubuntu)
   Status: New => In Progress

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  In Progress

Bug description:
  Attn. Canonical:  Please make sure that the existing iproute2 package
  gets updated with the two referenced patches as the missing
  information is impacting our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data
   
  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-42A 
   
  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
   
  == Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

  I found upstream already had patches that fix this problem:

  1) https://www.spinics.net/lists/netdev/msg415009.html
  commit 530903dd9003492edb0714e937ad4a5d1219e376
  Author: Petr Vorel 
  Date:   Tue Jan 17 00:25:50 2017 +0100

  ip: fix igmp parsing when iface is long

  Entries with long vhost names in /proc/net/igmp have no whitespace
  between name and colon, so sscanf() adds it to vhost and
  'ip maddr show iface' doesn't include inet result.

  Signed-off-by: Petr Vorel 

  
  2) https://www.spinics.net/lists/netdev/msg461479.html
  commit 21503ed2af233ffe795926f6641ac84ec1b15bf9
  Author: Michal Kubecek 
  Date:   Thu Oct 19 10:21:08 2017 +0200

  ip maddr: fix filtering by device

  Commit 530903dd9003 ("ip: fix igmp parsing when iface is long") uses
  variable len to keep trailing colon from interface name comparison.  This
  variable is local to loop body but we set it in one pass and use it in
  following one(s) so that we are actually using (pseudo)random length for
  comparison. This became apparent since commit b48a1161f5f9 ("ipmaddr: 
Avoid
  accessing uninitialized data") always initializes len to zero so that the
  name comparison is always true. As a result, "ip maddr show dev eth0" 
shows
  IPv4 multicast addresses for all interfaces.

  Instead of keeping the length, let's simply replace the trailing colon 
with
  a null byte. The bonus is that we get correct interface name in ma.name.

  Fixes: 530903dd9003 ("ip: fix igmp parsing when iface is long")
  Signed-off-by: Michal Kubecek 
  Acked-by: Phil Sutter 
  Acked-by: Petr Vorel 

  The fix is in the same place, but different way.
  This is the current implementation In ip/ipmaddr.c file:
  struct ma_info *ma;

  if (buf[0] != '\t') {
  size_t len;

  sscanf(buf, "%d%s", &m.index, m.name);
  len = strlen(m.name);
  if (m.name[len - 1] == ':')
  m.name[len - 1] = '\0';
  continue;
  }

  
  The existing "ip" command that shows the problem:
  [root@coral-sriov-host1 ip]# /usr/sbin/ip maddr show dev enP1p12s0f0   /* <-- 
We do NOT see the IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet6 ff02::1
  inet6 ff01::1

  I clone the latest "ip" utility from upstream to the same test box.
  [root@coral-sriov-host1 git_iproute2]# git clone 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git

  I build the "ip" utility on same test box, which has the above 2
  patches included.

  [root@coral-sriov-host1 ip]# /root/git_iproute2/iproute2/ip/ip maddr show dev 
enP1p12s0f0  /* <--- shows correct IPv4 maddr */
  2:  enP1p12s0f0
  link  01:00:5e:00:00:01
  inet  224.0.0.1/* <--- */
  inet6 ff02::1
  inet6 ff01::1

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

-- 
Mailing

[Touch-packages] [Bug 1722564] Re: apport question will not accept multi-character responses

2017-11-28 Thread Adam Conrad

Hello Scott, or anyone else affected,

Accepted apport into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.1-0ubuntu2.14 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: apport (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

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

** Tags added: verification-needed-zesty

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

Title:
  apport question will not accept multi-character responses

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Zesty:
  Fix Committed
Status in apport source package in Artful:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Packages which provide apport integration with more than 9 options in a 
choice will not be able to select options numbered >= 10 on the commandline 
using 'ubuntu-bug '

  
  [Test Case]
  Overview:
   1. Update to proposed versions of cloud-init v. 17.1 and apport v. 
   2. Run 'ubuntu-bug cloud-init' attempt to report a bug on a cloud choice 
greater than 9
   3. View report and make sure the proper cloud is reported


  Script:
  if [ ! -f './lxc-proposed-snapshot' ]; then
wget 
https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot;
chmod 755 lxc-proposed-snapshot;
  fi

  for release in xenial artful; do
  ref=$release-proposed;
  echo "$release START --";
  lxc-proposed-snapshot --proposed --publish $release $ref;
  lxc init $ref test-$release;
  lxc start test-$release;
  lxc exec test-$release -- apt install apport;
  lxc exec test-$release -- dpkg-query --show apport;
  lxc exec test-$release -- ubuntu-bug cloud-init;
  done

  [Regression Potential]
  Minimal. This bug only affects packages with >9 bug filing options for a 
given choice. Worst case, is bugs filed would incorrectly represent option 1 of 
a selection instead of option 1X.

  
  === End SRU Template ===

  === original description ===
  the newly added cloud-init apport support shows a list of cloud providers and 
asks the user to select one.  There are currently 18 options.  For any option > 
10, apport will just take the '1' that is typed as the answer.

  It should obviously wait for more than one character or a carriage
  return.

  *** Please select the cloud vendor or environment in which this
  instance is running

  Choices:
    1: Amazon - Ec2
    2: AliYun
    3: AltCloud
    4: Azure
    5: Bigstep
    6: CloudSigma
    7: CloudStack
    8: DigitalOcean
    9: GCE - Google Compute Engine
    10: MAAS
    11: NoCloud
    12: OpenNebula
    13: OpenStack
    14: OVF
    15: Scaleway
    16: SmartOS
    17: VMware
    18: Other
    C: Cancel
  Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 10 15:21:48 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1722564/+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 1722564] Please test proposed package

2017-11-28 Thread Adam Conrad

Hello Scott, or anyone else affected,

Accepted apport into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.7-0ubuntu3.6 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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. 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!

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

Title:
  apport question will not accept multi-character responses

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Zesty:
  Fix Committed
Status in apport source package in Artful:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Packages which provide apport integration with more than 9 options in a 
choice will not be able to select options numbered >= 10 on the commandline 
using 'ubuntu-bug '

  
  [Test Case]
  Overview:
   1. Update to proposed versions of cloud-init v. 17.1 and apport v. 
   2. Run 'ubuntu-bug cloud-init' attempt to report a bug on a cloud choice 
greater than 9
   3. View report and make sure the proper cloud is reported


  Script:
  if [ ! -f './lxc-proposed-snapshot' ]; then
wget 
https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot;
chmod 755 lxc-proposed-snapshot;
  fi

  for release in xenial artful; do
  ref=$release-proposed;
  echo "$release START --";
  lxc-proposed-snapshot --proposed --publish $release $ref;
  lxc init $ref test-$release;
  lxc start test-$release;
  lxc exec test-$release -- apt install apport;
  lxc exec test-$release -- dpkg-query --show apport;
  lxc exec test-$release -- ubuntu-bug cloud-init;
  done

  [Regression Potential]
  Minimal. This bug only affects packages with >9 bug filing options for a 
given choice. Worst case, is bugs filed would incorrectly represent option 1 of 
a selection instead of option 1X.

  
  === End SRU Template ===

  === original description ===
  the newly added cloud-init apport support shows a list of cloud providers and 
asks the user to select one.  There are currently 18 options.  For any option > 
10, apport will just take the '1' that is typed as the answer.

  It should obviously wait for more than one character or a carriage
  return.

  *** Please select the cloud vendor or environment in which this
  instance is running

  Choices:
    1: Amazon - Ec2
    2: AliYun
    3: AltCloud
    4: Azure
    5: Bigstep
    6: CloudSigma
    7: CloudStack
    8: DigitalOcean
    9: GCE - Google Compute Engine
    10: MAAS
    11: NoCloud
    12: OpenNebula
    13: OpenStack
    14: OVF
    15: Scaleway
    16: SmartOS
    17: VMware
    18: Other
    C: Cancel
  Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 10 15:21:48 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1722564/+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 1722564] Please test proposed package

2017-11-28 Thread Adam Conrad

Hello Scott, or anyone else affected,

Accepted apport into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.4-0ubuntu4.9 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!

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

Title:
  apport question will not accept multi-character responses

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Zesty:
  Fix Committed
Status in apport source package in Artful:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Packages which provide apport integration with more than 9 options in a 
choice will not be able to select options numbered >= 10 on the commandline 
using 'ubuntu-bug '

  
  [Test Case]
  Overview:
   1. Update to proposed versions of cloud-init v. 17.1 and apport v. 
   2. Run 'ubuntu-bug cloud-init' attempt to report a bug on a cloud choice 
greater than 9
   3. View report and make sure the proper cloud is reported


  Script:
  if [ ! -f './lxc-proposed-snapshot' ]; then
wget 
https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot;
chmod 755 lxc-proposed-snapshot;
  fi

  for release in xenial artful; do
  ref=$release-proposed;
  echo "$release START --";
  lxc-proposed-snapshot --proposed --publish $release $ref;
  lxc init $ref test-$release;
  lxc start test-$release;
  lxc exec test-$release -- apt install apport;
  lxc exec test-$release -- dpkg-query --show apport;
  lxc exec test-$release -- ubuntu-bug cloud-init;
  done

  [Regression Potential]
  Minimal. This bug only affects packages with >9 bug filing options for a 
given choice. Worst case, is bugs filed would incorrectly represent option 1 of 
a selection instead of option 1X.

  
  === End SRU Template ===

  === original description ===
  the newly added cloud-init apport support shows a list of cloud providers and 
asks the user to select one.  There are currently 18 options.  For any option > 
10, apport will just take the '1' that is typed as the answer.

  It should obviously wait for more than one character or a carriage
  return.

  *** Please select the cloud vendor or environment in which this
  instance is running

  Choices:
    1: Amazon - Ec2
    2: AliYun
    3: AltCloud
    4: Azure
    5: Bigstep
    6: CloudSigma
    7: CloudStack
    8: DigitalOcean
    9: GCE - Google Compute Engine
    10: MAAS
    11: NoCloud
    12: OpenNebula
    13: OpenStack
    14: OVF
    15: Scaleway
    16: SmartOS
    17: VMware
    18: Other
    C: Cancel
  Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 10 15:21:48 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1722564/+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 1728617] Re: Scrolled window broken when containing an eventbox

** Branch linked: lp:~ubuntu-desktop/gtk/ubuntugtk3

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

Title:
  Scrolled window broken when containing an eventbox

Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in gtk+3.0 source package in Artful:
  Triaged

Bug description:
  https://github.com/gnumdk/lollypop/issues/1279

  Ubuntu is shipping 074_eventbox_scroll_mask.patch, this patch is
  really strange, it adds a scroll mask on all eventbox breaking all
  applications using eventbox in scrolled windows.

  This patch is not in Debian and should be removed!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1728617/+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 1735020] [NEW] bad resolution

2017-11-28 Thread Freddy Perez

Public bug reported:

check the file

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 29 00:45:03 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 
(rev 10) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:82b0]
InstallationDate: Installed on 2017-10-15 (44 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=d4590d94-84c0-429f-a7bf-2dcf578d7efd ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0403
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: V-P5G31
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 4.01
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0403:bd12/09/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G31:rvr4.01:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful resolution ubuntu wayland-session

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

Title:
  bad resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  check the file

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 29 00:45:03 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:82b0]
  InstallationDate: Installed on 2017-10-15 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=d4590d94-84c0-429f-a7bf-2dcf578d7efd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0403
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P5G31
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 4.01
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0403:bd12/09/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G31:rvr4.01:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-co

[Touch-packages] [Bug 1660619] Re: kernel: [drm:intel_pipe_update_end [i915]] ERROR Atomic update failure on pipe B

2017-11-28 Thread D-nl-k

Got this error, too. 2 year anniversary is near and nobody seems to
care. The best would be to move away from this Intel Graphics crap.

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've a dual monitor setup and I'm running latest version of kubuntu.

  After a few days of uptime the desktop becomes so slow that I've to
  reboot it.

  In the log I find those errors, I don't know if they are related:

  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B (start=150051 end=150052) time 110 us, min 1073, max
  1079, scanline start 1072, end 1080

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 31 14:06:17 2017
  DistUpgraded: 2016-10-16 19:45:53,200 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7978]
  InstallationDate: Installed on 2013-04-25 (1376 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=f848f2e6-9d53-4c75-823a-fa97cfe10aa6 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (106 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnZ170AGAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Jan 28 11:57:37 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619/+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 1735032] [NEW] rebase iproute2 to newer version

2017-11-28 Thread Daniel Borkmann

Public bug reported:

Ubuntu's iproute2 version [1] is still many kernel versions behind. It's
still on 4.9, whereas shipped kernel is on 4.13 in the meantime!

iproute2 is developed alongside the kernel, so new kernel features will
also get updates to iproute2 whenever they change related code. Meaning,
these features cannot be used out of the box if the actual shipped
iproute2 version here is not on par with the kernel version (the release
tags have 1:1 mapping with kernel releases) [2].

Please consider updating iproute2 package, and please also consider
updating it regularly along with officially shipped kernels in Ubuntu,
so that all the added networking features can be used there without
forcing users to do a manual compilation of iproute2.

Thanks,
Daniel

  [1] 
http://changelogs.ubuntu.com/changelogs/pool/main/i/iproute2/iproute2_4.9.0-1ubuntu2/changelog
  [2] 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/refs/tags

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

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

Title:
  rebase iproute2 to newer version

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Ubuntu's iproute2 version [1] is still many kernel versions behind.
  It's still on 4.9, whereas shipped kernel is on 4.13 in the meantime!

  iproute2 is developed alongside the kernel, so new kernel features
  will also get updates to iproute2 whenever they change related code.
  Meaning, these features cannot be used out of the box if the actual
  shipped iproute2 version here is not on par with the kernel version
  (the release tags have 1:1 mapping with kernel releases) [2].

  Please consider updating iproute2 package, and please also consider
  updating it regularly along with officially shipped kernels in Ubuntu,
  so that all the added networking features can be used there without
  forcing users to do a manual compilation of iproute2.

  Thanks,
  Daniel

[1] 
http://changelogs.ubuntu.com/changelogs/pool/main/i/iproute2/iproute2_4.9.0-1ubuntu2/changelog
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/refs/tags

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1735032/+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 1734662] Re: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

2017-11-28 Thread Matthias Klose

just don't do that, or do you that as well?: ln -s /usr/bin/rm
/usr/bin/ls

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

Title:
  package python-setuptools 3.3-1ubuntu2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in python-setuptools package in Ubuntu:
  Invalid

Bug description:
  Somethign is messed up after linking python to python 3 and after this
  all these issues started cropping up.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-setuptools 3.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Mon Nov 27 16:19:13 2017
  Dependencies: python-pkg-resources 3.3-1ubuntu2
  DuplicateSignature: package:python-setuptools:3.3-1ubuntu2:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-11-16 (10 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python-setuptools
  Title: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to trusty on 2017-11-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1734662/+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 1735040] [NEW] Constant scanning for access points makes bluetooth audio (a2dp) unusable; setting bssid fixes this

2017-11-28 Thread Prashant L Rao

Public bug reported:

While using Wi-Fi and Bluetooth A2DP together there was stuttering on my
headset. I noticed that the interruptions were happening at constant
intervals and wondered if it was on account of Network Manager scanning
for access points. Forcing NM to stick to my local AP by using its BSSID
seems to have eliminated the interference/stuttering almost completely.

This is with the iwlwifi driver, the chip is the Intel Wireless 3160. It
could be that the driver is buggy too but since tweaking the NM
configuration appears to fix it, perhaps something could be done there.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Nov 29 07:54:09 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-11-27 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.1.1 dev wlp6s0 proto static metric 600 
 192.168.1.0/24 dev wlp6s0 proto kernel scope link src 192.168.1.101 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE 
 JioFi2_16E4CC   d11872a2-f551-4196-afca-776b92cda1cf  802-11-wireless  
1511922053  Wednesday 29 November 2017 07:50:53 AM IST  yes  0  
   no/org/freedesktop/NetworkManager/Settings/1  yes wlp6s0 
 activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
 Wired connection 1  f3db4b13-14a4-345e-9f62-abde3efe9544  802-3-ethernet   
1511823262  Tuesday 28 November 2017 04:24:22 AM ISTyes  4294966297 
   no/org/freedesktop/NetworkManager/Settings/2  no  -- 
 -- --   --
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   
 
 wlp6s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
JioFi2_16E4CC  d11872a2-f551-4196-afca-776b92cda1cf  
/org/freedesktop/NetworkManager/ActiveConnection/11 
 enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  --   
  ----  

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  Constant scanning for access points makes bluetooth audio (a2dp)
  unusable; setting bssid fixes this

Status in network-manager package in Ubuntu:
  New

Bug description:
  While using Wi-Fi and Bluetooth A2DP together there was stuttering on
  my headset. I noticed that the interruptions were happening at
  constant intervals and wondered if it was on account of Network
  Manager scanning for access points. Forcing NM to stick to my local AP
  by using its BSSID seems to have eliminated the
  interference/stuttering almost completely.

  This is with the iwlwifi driver, the chip is the Intel Wireless 3160.
  It could be that the driver is buggy too but since tweaking the NM
  configuration appears to fix it, perhaps something could be done
  there.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov 29 07:54:09 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-27 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp6s0 proto static metric 600

[Touch-packages] [Bug 1730395] Re: ibus pinyin preference not working

2017-11-28 Thread walterclozet

@KANGOD install python-ibus from trusy-update will solve the problem. i
download one from https://launchpad.net/ubuntu/trusty/amd64/python-
ibus/1.5.5-1ubuntu3.2, and install the deb with dpkg -i

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

Title:
  ibus pinyin preference not working

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  System is Ubuntu 17.10 amd64
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  
  select sunpinyin from gtk3 menu, click preference, nothing happens. trying 
cli mode, error shows:
  /usr/lib/ibus/ibus-setup-sunpinyin
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid 
string constant "murrine-scrollbar", expected valid string constant
  Traceback (most recent call last):
File "/usr/share//ibus-sunpinyin/setup/main.py", line 42, in 
  import ibus
  ImportError: No module named ibus

  it seems python-ibus is missing, but trying to install python-ibus
  shows the package does not exists. seems only exists in trusty and
  trusty-update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1730395/+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 1735032] Re: rebase iproute2 to newer version

2017-11-28 Thread dino99

http://metadata.ftp-
master.debian.org/changelogs/main/i/iproute2/iproute2_4.9.0-2.1_changelog

** Tags added: upgrade-software-version

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

Title:
  rebase iproute2 to newer version

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu's iproute2 version [1] is still many kernel versions behind.
  It's still on 4.9, whereas shipped kernel is on 4.13 in the meantime!

  iproute2 is developed alongside the kernel, so new kernel features
  will also get updates to iproute2 whenever they change related code.
  Meaning, these features cannot be used out of the box if the actual
  shipped iproute2 version here is not on par with the kernel version
  (the release tags have 1:1 mapping with kernel releases) [2].

  Please consider updating iproute2 package, and please also consider
  updating it regularly along with officially shipped kernels in Ubuntu,
  so that all the added networking features can be used there without
  forcing users to do a manual compilation of iproute2.

  Thanks,
  Daniel

[1] 
http://changelogs.ubuntu.com/changelogs/pool/main/i/iproute2/iproute2_4.9.0-1ubuntu2/changelog
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/refs/tags

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1735032/+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 1735032] Re: rebase iproute2 to newer version