[Touch-packages] [Bug 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug

[Colin Law]

It certainly caused me to waste some time trying to work out why it was
not sending them.

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

Title:
  turning off "Send error reports to Canonical" prevents using ubuntu-
  bug

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Bionic:
  Triaged
Status in apport source package in Disco:
  Triaged
Status in apport source package in Eoan:
  Triaged

Bug description:
  Impact
  --
  apport was modified (bug 1778497) to reduce the number of times people have 
to respond to crash reports, however the changes introduced a check to see if 
whoopsie is enabled. That check is done for any type of report, not just 
crashes, and subsequently people can not use ubuntu-bug to report bugs if 
whoopsie is disabled which is wrong as whoopsie is only for uploading crashes 
to the Error Tracker.

  Test Case
  -
  1) On a system with Gnome installed use the Privacy control panel and set 
"Send error reports to Canonical" to Off
  2) In a terminal run 'ubuntu-bug gnome-terminal'
  3) Click "Send" and observe nothing happening (if something does happen 
confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there 
may be a bug in the control panel)

  
  Original Description
  
  Ubuntu 18.04.1 LTS, X11 gnome session.

  For some reason ubuntu-bug  no longer opens a browser
  window, so it is not possible to enter useful bug detauls, or even
  know the bug number.

  After prompting whether or not to Send the report, clicking "Send"
  just closes appport and nothing else ever happens.  The exit status of
  "ubuntu-bug" is zero.

  This worked fine before, but it has been many months since I tried to
  submit a bug.

  strace shows many stat calls on plausible browser paths, including the
  one that is correct (/usr/bin/firefox, which returned a successful
  stat call).  I'll attach the trace output from

     strace -f -o /tmp/strace.log ubuntu-bug apport

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

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

[Touch-packages] [Bug 1862913] [NEW] ubuntu-bug failing silently if Settings > Privacy > Problem Reporting disabled

[Colin Law]

Public bug reported:

On a system running Ubuntu 19.10 (upgraded over several versions) if Settings > 
Privacy > Problem Reporting is disabled then running 
ubuntu-bug 
collects the data and asks if it should send it.  On clicking Send it silently 
terminates and does nothing.
An appropriate response would either be to send the data anyway, since the user 
has been explicitly asked, or to fail with a message explaining why.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apport 2.20.11-0ubuntu8.2
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportLog:
 ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: called for pid 2865, signal 
11, core limit 0, dump mode 1
 ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
 ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: debug: session gdbus call: 
(true,)
 
 ERROR: apport (pid 3384) Mon Feb 10 14:41:31 2020: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 12 09:03:53 2020
InstallationDate: Installed on 2014-10-21 (1939 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  ubuntu-bug failing silently if Settings > Privacy > Problem Reporting
  disabled

Status in apport package in Ubuntu:
  New

Bug description:
  On a system running Ubuntu 19.10 (upgraded over several versions) if Settings 
> Privacy > Problem Reporting is disabled then running 
  ubuntu-bug 
  collects the data and asks if it should send it.  On clicking Send it 
silently terminates and does nothing.
  An appropriate response would either be to send the data anyway, since the 
user has been explicitly asked, or to fail with a message explaining why.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.2
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportLog:
   ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: called for pid 2865, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
   ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3384) Mon Feb 10 14:41:31 2020: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 09:03:53 2020
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Colin Law]

It has only been marked Won't Fix in Yakkety, because Yakkety is well
past it's sell by date.  It is still open on Xenial.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Won't Fix

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1244285] Re: Date/time sometimes doesn’t appear in menu bar, settings greyed out

[Colin Law]

Does this bug still manifest itself?  It is years old. I have not seen
the problem since several Ubuntu versions ago.

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

Title:
  Date/time sometimes doesn’t appear in menu bar, settings greyed out

Status in One Hundred Papercuts:
  Triaged
Status in Indicator Date and Time:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  it does not happen often, and when it happens, just a log out and re-
  log in is enough to restore it.

  http://askubuntu.com/questions/357266/how-to-show-time-in-
  ubuntu-13-10/357280

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

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

[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.

[Colin Law]

I am also seeing very similar effects. The menu doesn't show the wifi
connection points at all and sometimes the network icon in the top panel
disappears completely.  As others have found control via Settings works
fine. Ubuntu 18.04 on a Lenovo Lifebook.

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

Title:
  Ubuntu 18.04 - NetworkManager menu items in top right menu behaves
  very strange.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour 
on my Dell XPS 15.
  This laptop doesn't have an integrated Ethernet port, so I've to use external 
USB 3.0 Ethernet adapters.
  When I boot Ubuntu with the adapter plugged in, the wired connection section 
in the top right menu doesn't show the "Via cavo collegato" section (in 
Italian, sorry... maybe in English it is "Through connected cable") in the 
correct way, often but not every time...
  The menu section title is sometimes " collegato" and expanding the section it 
doesn't list all the defined Ethernet connection profiles I've on my machine.
  To access all profiles and to change it I've to select the "Wired network 
settings" item in the section and so the system settings window appears and all 
defined profiles are there (so I can change connection by clicking here).

  Another strange behaviour occours with the "VPN" section in the same topright 
menu.
  I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN 
type). If I select one of this two profiles, VPN connection is established but 
the switch button in the menu doesn't reflect the state of the connection. To 
see the correct state of the VPN connection I've to open the "system settings" 
window, again.

  It seems there is some trouble in the topright menu communication with
  the NetworkManager subsystem.

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

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

[Touch-packages] [Bug 1713205] Re: Slow suspend when wifi active

[Colin Law]

Still present in 17.10

** Tags added: artful

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

Title:
  Slow suspend when wifi active

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa package in Debian:
  Fix Released

Bug description:
  Running 17.04 (upgraded over several versions) I see a ten second
  additional delay on suspend if wifi is in use. Looking at the journal
  this looks to be debian wpa bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=835648

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: wpasupplicant 2.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 26 08:13:04 2017
  InstallationDate: Installed on 2014-10-21 (1039 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

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

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

[Touch-packages] [Bug 1721116] Re: tracker-extract using 700MB-1GB+ of RAM

[Colin Law]

I am seeing this with Ubuntu 17.04, using Gnome Shell.

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

Title:
  tracker-extract using 700MB-1GB+ of RAM

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  BEHAVIOR
  The tracker service (showing as "tracker-extract" in the GNOME System 
Monitor) shows that it's using anywhere from 700MB to 1.1GB of RAM. This seems 
like a lot.

  EXPECTED BEHAVIOR
  Tracker uses much less RAM.

  Bug reported using:
  Tracker 2.0.0
  Ubuntu 17.10 beta 2
  Linux kernel 4.13.0-12-generic

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

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

[Touch-packages] [Bug 1724756] [NEW] Updates Available pops up when Check set to Never

[Colin Law]

Public bug reported:

In Software & Updates with Automatically Check set to Never and When
Security Updates Available set to Display Immediately the system is
apparently still checking for updates, as the Software Updates Available
is shown when there are updates.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unattended-upgrades 0.93.1ubuntu2.3
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Oct 19 07:26:44 2017
InstallationDate: Installed on 2014-10-21 (1093 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
PackageArchitecture: all
SourcePackage: unattended-upgrades
UpgradeStatus: Upgraded to zesty on 2017-04-26 (175 days ago)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "0";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "0";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-09-17T16:17:23.842448
mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-05-19T08:12:23.274412

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


** Tags: amd64 apport-bug zesty

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

Title:
  Updates Available pops up when Check set to Never

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  In Software & Updates with Automatically Check set to Never and When
  Security Updates Available set to Display Immediately the system is
  apparently still checking for updates, as the Software Updates
  Available is shown when there are updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unattended-upgrades 0.93.1ubuntu2.3
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 19 07:26:44 2017
  InstallationDate: Installed on 2014-10-21 (1093 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (175 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "0";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-09-17T16:17:23.842448
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-05-19T08:12:23.274412

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

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

[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

[Colin Law]

@prefec2 that sounds like a different bug. This one is not intermittent.
If the workaround in comment #6 does not fix it for you then I suggest
filing a new bug.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 1609546] Re: DNS lookup through Netgear DG834G V4 router slow or times out

[Colin Law]

Laurent, if disabling DNSSEC does not fix it then it is not the same
bug. I suggest submitting a new bug.

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

Title:
  DNS lookup through Netgear DG834G V4 router slow or times out

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Update:
  On Zesty I am seeing a timeout both with systemd-resolve and dnslookup rather 
than just a slow resolution. The workaround in comment #6 which disables DNSSEC 
still corrects the problem.
  ---

  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Colin Law]

@litinoveweedle this bug is marked fixed. If you are still seeing a
similar symptom then I suggest opening a new bug.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1713205] [NEW] Slow suspend when wifi active

[Colin Law]

Public bug reported:

Running 17.04 (upgraded over several versions) I see a ten second
additional delay on suspend if wifi is in use. Looking at the journal
this looks to be debian wpa bug https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=835648

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: wpasupplicant 2.4-0ubuntu9
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Aug 26 08:13:04 2017
InstallationDate: Installed on 2014-10-21 (1039 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
SourcePackage: wpa
UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

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


** Tags: amd64 apport-bug zesty

** Description changed:

  Running 17.04 (upgraded over several versions) I see a ten second
  additional delay on suspend if wifi is in use. Looking at the journal
- this looks to be debian wpa bug #835648
+ this looks to be debian wpa bug 835648
  
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835648
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: wpasupplicant 2.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 26 08:13:04 2017
  InstallationDate: Installed on 2014-10-21 (1039 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

** Description changed:

  Running 17.04 (upgraded over several versions) I see a ten second
  additional delay on suspend if wifi is in use. Looking at the journal
- this looks to be debian wpa bug 835648
- 
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835648
+ this looks to be debian wpa bug https://bugs.debian.org/cgi-
+ bin/bugreport.cgi?bug=835648
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: wpasupplicant 2.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 26 08:13:04 2017
  InstallationDate: Installed on 2014-10-21 (1039 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

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

Title:
  Slow suspend when wifi active

Status in wpa package in Ubuntu:
  New

Bug description:
  Running 17.04 (upgraded over several versions) I see a ten second
  additional delay on suspend if wifi is in use. Looking at the journal
  this looks to be debian wpa bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=835648

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: wpasupplicant 2.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 26 08:13:04 2017
  InstallationDate: Installed on 2014-10-21 (1039 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

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

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

[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

[Colin Law]

I can confirm that for me removing /etc/resolv.conf and replacing it
with a link to stub-resolv.conf using

sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

and rebooting (probably I could just have restarted the appropriate
service) restores DNS functionality.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

[Colin Law]

@Willem, since this bug is specifically about invoking the HUD from
firefox, and it seems from your description that you are not using
firefox and you are not seeing the problem specifically when you open
the HUD, I think your problem does not fit the description of this bug.
You would probably be better to start a new bug.

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in firefox source package in Xenial:
  Incomplete
Status in hud source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

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

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

[Touch-packages] [Bug 1609546] Re: DNS lookup through Netgear DG834G V4 router slow or times out

[Colin Law]

This is particularly annoying when installing Ubuntu, as the system
knows the network is connected, but DNS does not work so it can't
actually do anything useful.

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

Title:
  DNS lookup through Netgear DG834G V4 router slow or times out

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Update:
  On Zesty I am seeing a timeout both with systemd-resolve and dnslookup rather 
than just a slow resolution. The workaround in comment #6 which disables DNSSEC 
still corrects the problem.
  ---

  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Colin Law]

@exander77 there is no need for personal abuse here. In that case the
description of this bug should have been updated to include that.
However I see there is debate on that bug about whether it is fixed by
the version of dnsmasq which fixes this bug. If not then it is
definitely a different bug. I suggest opening a new bug. It will not get
duplicated to this one if the dnsmasq fix does not fix the problem.
There is no point commenting further on this bug as it is marked as
fixed so no-one will do anything about it.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Colin Law]

@exander77 this bug is specifically about a failure after
suspend/resume. If your issue does not relate to suspend/resume it is a
different bug.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1609546] Re: DNS lookup through Netgear DG834G V4 router slow or times out

[Colin Law]

** Summary changed:

- Slow DNS lookup through Netgear DG834G V4 router
+ DNS lookup through Netgear DG834G V4 router slow or times out

** Description changed:

+ Update:
+ On Zesty I am seeing a timeout both with systemd-resolve and dnslookup rather 
than just a slow resolution. The workaround in comment #6 which disables DNSSEC 
still corrects the problem.
+ ---
+ 
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com
  
  I do not see the same delay if I run
  nslookup www.google.com
  
  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.
  
  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  DNS lookup through Netgear DG834G V4 router slow or times out

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Update:
  On Zesty I am seeing a timeout both with systemd-resolve and dnslookup rather 
than just a slow resolution. The workaround in comment #6 which disables DNSSEC 
still corrects the problem.
  ---

  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  

[Touch-packages] [Bug 1609546] Re: Slow DNS lookup through Netgear DG834G V4 router

[Colin Law]

I have replied to the upstream comment, however with Zesty I am seeing a
slightly different symptom. Both systemd-resolve and nslookup both
timeout rather than just being slow. Disabling DNSSEC still fixes it
however.

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

Title:
  Slow DNS lookup through Netgear DG834G V4 router

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1609546] Re: nslookup doesn't works

[Colin Law]

@Gannet, I don't understand why you have changed the description. For me
I see a slow lookup, it does eventually resolve. Does the workaround in
#6 fix it? If not then it is a different bug.

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

Title:
  nslookup doesn't works

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1609546] Re: Slow DNS lookup through Netgear DG834G V4 router

[Colin Law]

** Tags added: zesty

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

Title:
  Slow DNS lookup through Netgear DG834G V4 router

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt

[Colin Law]

I don't know whether it is significant but I notice in syslog that for
the second connection to the vpn I see the additional line

systemd-resolved[1001]: Using degraded feature set (UDP+EDNS0+DO) for
DNS server 127.0.1.1.

and I notice that a similar message is present in the log in comment #1

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

Title:
  Network Manager + OpenVPN does not respond to DNS server change on
  second connection attempt

Status in dnsmasq:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Scenario:
  Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I 
only have the one computer to test with, the 16.10 is definitely relevant (I 
did not have this problem on 16.04)  but I can't tell if the upgrade is part of 
it,  (the upgrade may or may not be relevant).

  Have "full time"  wired or wireless connection  (does not matter which used)
  Part time OpenVPN connection set up via NetworkManager.

  Steps to reproduce
  1. Fresh boot
  2.  ping a device on the VPN network  (eg amachine.remotelan ) Result:  
"ping: amachine.remotelan: Name or service not known"
  3.  Connect to the VPN service via Network Manager.
  4. ping amachine.remotelan  -  result:
   PING amachine.remotelan (192.168.68.44) 56(84) bytes of data.
64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 
time=7.75 ms
  5.  Disconnect from the VPN service again.
ping result again "ping: amachine.remotelan: Name or service not known"

  6. Reconnect to the VPN again, and ping again

  Observed: 
 "ping: amachine.remotelan: Name or service not known"

However "ping 192.168.68.44"  responds successfully as expected

  Expected:
  PING ... 192.168 64 bytes from .. etc   to the ping by name

  ---
  Further info I'm going to add in a subsequent comment. (just annotating 
syslog right now!)

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

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

[Touch-packages] [Bug 1617204] Re: NM does not offer VPN options

[Colin Law]

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

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

Title:
  NM does not offer VPN options

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  network-manager-pptp is installed, but when I select "Configure VPN"
  NM offers only Hardware and Virtual options, no VPN options.,

  Observed on two Lubuntu 16.04 and one LXLE 16.04 system; everything
  works as expected on Lubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Aug 26 09:05:44 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-08 (17 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  IpRoute:
   default via 172.16.0.27 dev wlp2s0  proto static  metric 600 
   172.16.0.0/16 dev wlp2s0  proto kernel  scope link  src 172.16.0.182  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
haywiredcce62ca8-d2bd-480e-b67b-f4cf93a54d8b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1609546] Re: Slow DNS lookup through Netgear DG834G V4 router

[Colin Law]

Thanks Martin.

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

Title:
  Slow DNS lookup through Netgear DG834G V4 router

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1609546] Re: Slow DNS lookup through Netgear DG834G V4 router

[Colin Law]

Disabling DNSSEC appears to have solved the problem.
(I had to manually create /etc/systemd/resolved.conf.d/ before the command 
would run)

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

Title:
  Slow DNS lookup through Netgear DG834G V4 router

Status in systemd package in Ubuntu:
  New

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1609546] Re: Slow DNS lookup through Netgear DG834G V4 router

[Colin Law]

** Attachment added: "systemd-resolve debug log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1609546/+attachment/4723282/+files/debug.txt

** Changed in: systemd (Ubuntu)
   Status: Incomplete => 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/1609546

Title:
  Slow DNS lookup through Netgear DG834G V4 router

Status in systemd package in Ubuntu:
  New

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1609546] Re: Slow DNS lookup through Netgear DG834G V4 router

[Colin Law]

I am marking this New again as it has not actually been fixed by
upgrading the router. It now appears that the symptom is intermittent. I
have not been able to determine what it is that triggers it to fail or
work.

** Changed in: systemd (Ubuntu)
   Status: Invalid => 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/1609546

Title:
  Slow DNS lookup through Netgear DG834G V4 router

Status in systemd package in Ubuntu:
  New

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1610907] Re: 60 second hang during shutdown

[Colin Law]

** Attachment added: "Output from journalctl showing hang at Aug 08 09:58:25"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1610907/+attachment/4716539/+files/journal.txt

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

Title:
  60 second hang during shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  On up to date Yaketty I intermittently see a 60 second hang on
  shutdown. In attached logs the hang was at Aug 08 09:58:25

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug  8 10:10:31 2016
  InstallationDate: Installed on 2016-08-02 (5 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1610907] [NEW] 60 second hang during shutdown

[Colin Law]

Public bug reported:

On up to date Yaketty I intermittently see a 60 second hang on shutdown.
In attached logs the hang was at Aug 08 09:58:25

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-1
ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
Uname: Linux 4.4.0-33-generic x86_64
ApportVersion: 2.20.3-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Aug  8 10:10:31 2016
InstallationDate: Installed on 2016-08-02 (5 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
MachineType: Hewlett-Packard Presario CQ57 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.47
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3577
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 24.49
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: Presario CQ57 Notebook PC
dmi.product.version: 068E1220491620100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug yakkety

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

Title:
  60 second hang during shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  On up to date Yaketty I intermittently see a 60 second hang on
  shutdown. In attached logs the hang was at Aug 08 09:58:25

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug  8 10:10:31 2016
  InstallationDate: Installed on 2016-08-02 (5 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1609546] Re: Slow DNS lookup through Netgear DG834G V4 router

[Colin Law]

Having updated the router to the latest firmware (5.01.17) the problem
appears to be resolved (even though the release notes made no mention of
DNS.  Marking this bug as invalid.

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

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

Title:
  Slow DNS lookup through Netgear DG834G V4 router

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1609546] [NEW] Slow DNS lookup through Netgear DG834G V4 router

[Colin Law]

Public bug reported:

On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
systemd-resolve www.google.com
or
wget www.google.com

I do not see the same delay if I run
nslookup www.google.com

A clue may be that in syslog I see
Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

I do not see the issue if I specify an external DNS server.
I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-1
ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
Uname: Linux 4.4.0-33-generic x86_64
ApportVersion: 2.20.3-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Aug  3 21:24:07 2016
InstallationDate: Installed on 2016-08-02 (1 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
MachineType: Hewlett-Packard Presario CQ57 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.47
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3577
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 24.49
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: Presario CQ57 Notebook PC
dmi.product.version: 068E1220491620100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Slow DNS lookup through Netgear DG834G V4 router

Status in systemd package in Ubuntu:
  New

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:

[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded

[Colin Law]

@angel-granados-j This bug is about the wording of the error message, not the 
fact that the error may appear.
For how to avoid it I suggest you ask elsewhere, the ubuntu-users email list 
for example.

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

Title:
  message "The repository is insufficiently signed by key  (weak
  digest)" is poorly worded

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  The title pretty much says it all.

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

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

[Touch-packages] [Bug 1589204] Re: apt-get dist-upgrade and apt full-upgrade not reporting held back package

[Colin Law]

Sorry, it is apt-get upgrade that shows 1 not to upgrade.
Description corrected.

** Description changed:

  I have the situation where a package cannot be upgraded because of missing 
dependencies.  However
  sudo apt-get dist-upgrade
  and
  sudo apt full-upgrade
  and
  sudo apt upgrade
  all show
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
  
  Only
- sudo apt upgrade
+ sudo apt-get upgrade
  shows
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
  
  I believe all of the above commands should show that 1 cannot be
  upgraded.
  
  This bug is not about the particular package I am trying to install, but 
about the way apt reports the problem.
  The details, for reference, are that I am trying to upgrade mosquitto from 
the mosquitto ppa.  After apt-get update I see
  $ apt-cache policy mosquitto
  mosquitto:
-   Installed: 1.4.8-1build1
-   Candidate: 1.4.9-0mosquitto1
-   Version table:
-  1.4.9-0mosquitto1 500
- 500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu 
xenial/main amd64 Packages
-  *** 1.4.8-1build1 500
- 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.4.8-1build1
+   Candidate: 1.4.9-0mosquitto1
+   Version table:
+  1.4.9-0mosquitto1 500
+ 500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu 
xenial/main amd64 Packages
+  *** 1.4.8-1build1 500
+ 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
+ 100 /var/lib/dpkg/status
  
  but if I try to manually install mosquitto I get
  
  The following packages have unmet dependencies.
-  mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable
+  mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable
  
  and
  
  $ apt-cache policy libwebsockets3
  libwebsockets3:
-   Installed: (none)
-   Candidate: (none)
+   Installed: (none)
+   Candidate: (none)
  Due to the fact that libwebsockets3 is not available for Xenial.
  As I said this bug is not about the problem with this particular package but 
about the fact that apt does not report that there is a package to be upgraded, 
but it cannot be done.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun  5 08:45:33 2016
  InstallationDate: Installed on 2014-10-21 (592 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-03-06 (90 days ago)

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

Title:
  apt-get dist-upgrade and apt full-upgrade not reporting held back
  package

Status in apt package in Ubuntu:
  New

Bug description:
  I have the situation where a package cannot be upgraded because of missing 
dependencies.  However
  sudo apt-get dist-upgrade
  and
  sudo apt full-upgrade
  and
  sudo apt upgrade
  all show
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

  Only
  sudo apt-get upgrade
  shows
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  I believe all of the above commands should show that 1 cannot be
  upgraded.

  This bug is not about the particular package I am trying to install, but 
about the way apt reports the problem.
  The details, for reference, are that I am trying to upgrade mosquitto from 
the mosquitto ppa.  After apt-get update I see
  $ apt-cache policy mosquitto
  mosquitto:
    Installed: 1.4.8-1build1
    Candidate: 1.4.9-0mosquitto1
    Version table:
   1.4.9-0mosquitto1 500
  500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu 
xenial/main amd64 Packages
   *** 1.4.8-1build1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  but if I try to manually install mosquitto I get

  The following packages have unmet dependencies.
   mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable

  and

  $ apt-cache policy libwebsockets3
  libwebsockets3:
    Installed: (none)
    Candidate: (none)
  Due to the fact that libwebsockets3 is not available for Xenial.
  As I said this bug is not about the problem with this particular package but 
about the fact that apt does not report that there is a package to be upgraded, 
but it cannot be done.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun  5 08:45:33 2016
  

[Touch-packages] [Bug 1589204] [NEW] apt-get dist-upgrade and apt full-upgrade not reporting held back package

[Colin Law]

Public bug reported:

I have the situation where a package cannot be upgraded because of missing 
dependencies.  However
sudo apt-get dist-upgrade
and
sudo apt full-upgrade
and
sudo apt upgrade
all show
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

Only
sudo apt upgrade
shows
0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

I believe all of the above commands should show that 1 cannot be
upgraded.

This bug is not about the particular package I am trying to install, but about 
the way apt reports the problem.
The details, for reference, are that I am trying to upgrade mosquitto from the 
mosquitto ppa.  After apt-get update I see
$ apt-cache policy mosquitto
mosquitto:
  Installed: 1.4.8-1build1
  Candidate: 1.4.9-0mosquitto1
  Version table:
 1.4.9-0mosquitto1 500
500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu 
xenial/main amd64 Packages
 *** 1.4.8-1build1 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

but if I try to manually install mosquitto I get

The following packages have unmet dependencies.
 mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable

and

$ apt-cache policy libwebsockets3
libwebsockets3:
  Installed: (none)
  Candidate: (none)
Due to the fact that libwebsockets3 is not available for Xenial.
As I said this bug is not about the problem with this particular package but 
about the fact that apt does not report that there is a package to be upgraded, 
but it cannot be done.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.12~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jun  5 08:45:33 2016
InstallationDate: Installed on 2014-10-21 (592 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
SourcePackage: apt
UpgradeStatus: Upgraded to xenial on 2016-03-06 (90 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  apt-get dist-upgrade and apt full-upgrade not reporting held back
  package

Status in apt package in Ubuntu:
  New

Bug description:
  I have the situation where a package cannot be upgraded because of missing 
dependencies.  However
  sudo apt-get dist-upgrade
  and
  sudo apt full-upgrade
  and
  sudo apt upgrade
  all show
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

  Only
  sudo apt upgrade
  shows
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  I believe all of the above commands should show that 1 cannot be
  upgraded.

  This bug is not about the particular package I am trying to install, but 
about the way apt reports the problem.
  The details, for reference, are that I am trying to upgrade mosquitto from 
the mosquitto ppa.  After apt-get update I see
  $ apt-cache policy mosquitto
  mosquitto:
Installed: 1.4.8-1build1
Candidate: 1.4.9-0mosquitto1
Version table:
   1.4.9-0mosquitto1 500
  500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu 
xenial/main amd64 Packages
   *** 1.4.8-1build1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  but if I try to manually install mosquitto I get

  The following packages have unmet dependencies.
   mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable

  and

  $ apt-cache policy libwebsockets3
  libwebsockets3:
Installed: (none)
Candidate: (none)
  Due to the fact that libwebsockets3 is not available for Xenial.
  As I said this bug is not about the problem with this particular package but 
about the fact that apt does not report that there is a package to be upgraded, 
but it cannot be done.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun  5 08:45:33 2016
  InstallationDate: Installed on 2014-10-21 (592 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-03-06 (90 days ago)

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

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

[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded

[Colin Law]

@Mahmoud F.Elshazly (elshazly5) this bug is about the wording of a
message, not about specific repositories.

However, only one of the repositories is an Ubuntu repo, and that one is
for trusty not xenial, so it is not appropriate to be using it at all.
For the non-ubuntu repos you will have to take up the problem with them,
or ask in a more appropriate place.

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

Title:
  message "The repository is insufficiently signed by key  (weak
  digest)" is poorly worded

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  The title pretty much says it all.

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

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

[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early

[Colin Law]

To recent commentators,   unless you are sure this is a problem caused
by dbus stopping too early then it is a different issue.  Even if you
believe it is the same issue it is probably best to open new bug rather
than commenting on a closed one.

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

Title:
  remote file systems hang on shutdown, D-BUS stops too early

Status in D-Bus:
  Won't Fix
Status in dbus package in Ubuntu:
  Fix Released

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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

[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded

[Colin Law]

@Williamforte which one?  Copy/paste the relevant section here from the
terminal.

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

Title:
  message "The repository is insufficiently signed by key  (weak
  digest)" is poorly worded

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  The title pretty much says it all.

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

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

[Touch-packages] [Bug 1228567] Re: at-spi2 daemon error messages in .xsession-errors

[Colin Law]

@Cerin: I believe this bug has little impact.  If your machine is
unusable then it is likely a different problem.

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

Title:
  at-spi2 daemon error messages in .xsession-errors

Status in at-spi2-core package in Ubuntu:
  Fix Released

Bug description:
  Sometimes I get the following messages in .xsession-errors

  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd respawning too fast, stopped

  I use a Lenovo Thinkpad Twist convertible with touch screen, using
  Onboard in tablet mode.

  Can perhaps have a relation with bug 1227173.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+subscriptions

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

[Touch-packages] [Bug 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

[Colin Law]

@va_crone  you have not told us which version you are using now.

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

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

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

[Touch-packages] [Bug 1470748] Re: Corrupted displays when hot plugging second monitor

[Colin Law]

It seems this has been fixed so marking accordingly.

** Changed in: unity
   Status: Triaged => Fix Released

** Changed in: unity (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Corrupted displays when hot plugging second monitor

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  On up to date Wily running on a laptop, when a second monitor is hot
  plugged in, the image on the laptop monitor is cropped so only lower
  two thirds are visible and the second monitor shows a black screen
  with occasional flashes.

  If the machine is booted with both monitors connected the displays
  work as expected.

  Same setup works ok on Vivid.

  This report generated with the system in the error condition.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20150627.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul  2 08:34:19 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2015-07-01 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150609)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 
root=UUID=4ab50317-49e7-45c9-b675-d9391fbfd0e3 ro quiet splash
  SourcePackage: unity
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.60-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.8-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.8-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jul  2 08:25:52 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890 
   vendor SEC
  xserver.version: 2:1.17.1-0ubuntu4

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

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

[Touch-packages] [Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()

[Colin Law]

** Changed in: glib2.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  gedit crashed with SIGABRT in g_assertion_message()

Status in gedit package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Invalid

Bug description:
  Gedit crashed just after opening a (small) text file from nautilus
  with "Open with".

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: gedit 3.10.4-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1
  Uname: Linux 4.2.0-11-lowlatency x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Sep 25 16:05:28 2015
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2014-12-13 (285 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: gedit /home/username/Bureau/Export_cabmnt_329340483152739798.csv
  Signal: 6
  SourcePackage: gedit
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   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: gedit crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago)
  UserGroups: adm audio cdrom dialout dip libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Touch-packages] [Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()

[Colin Law]

Is bug #1499575 (gnucash crashed with SIGABRT in g_assertion_message())
which seems to have a similar stack top probably the same issue?  It is
causing gnucash to be completely unusable on Wily (for me anyway).

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

Title:
  gedit crashed with SIGABRT in g_assertion_message()

Status in gedit package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in unity-gtk-module package in Ubuntu:
  Triaged

Bug description:
  Gedit crashed just after opening a (small) text file from nautilus
  with "Open with".

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: gedit 3.10.4-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1
  Uname: Linux 4.2.0-11-lowlatency x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Sep 25 16:05:28 2015
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2014-12-13 (285 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: gedit /home/username/Bureau/Export_cabmnt_329340483152739798.csv
  Signal: 6
  SourcePackage: gedit
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   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: gedit crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago)
  UserGroups: adm audio cdrom dialout dip libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult

[Colin Law]

@vedavata I imagine that it is because (according to comment #397 you
are using Xubuntu.  This bug is about Unity, where it has been fixed.
If you have a problem on Xubuntu you should file a bug for that or
extend this bug to Xubuntu.  I don't know what the appropriate package
on Xubuntu would be.

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  
  
  

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of "misses" when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  "invisible" region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System >
  Preferences > Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions

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

[Touch-packages] [Bug 1322864] Re: Sometimes the app search doesn't work in the Dash

[Colin Law]

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

** This bug has been marked a duplicate of bug 1295908
   Sometimes applications stop showing up in the Dash

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

Title:
  Sometimes the app search doesn't work in the Dash

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I open the Dash by using the Super key or by clicking in the Dash 
icon; when I search for an app the Dash just shows files and folders.
  It is really annoying because I need to log out to solve it.

  I'm using the stock Unity Packages in Ubuntu 14.04.

  I don't know how to reproduce it. It happens once in a while but I
  can't seem to find out why.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 24 09:40:50 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3903]
  InstallationDate: Installed on 2014-04-27 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO IdeaPad U310
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=d69245b3-9c0a-42d7-97d2-469d6b3f1c3d ro quiet splash 
intel_pstate=enable vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 65CN89WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194WIN8 STD SGL
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo U310
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr65CN89WW:bd09/04/2012:svnLENOVO:pnIdeaPadU310:pvrLenovoU310:rvnLENOVO:rnLenovo:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoU310:
  dmi.product.name: IdeaPad U310
  dmi.product.version: Lenovo U310
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat May 24 09:04:55 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4140 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 1424744] Re: Dash don't find the applications

[Colin Law]

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

** This bug is no longer a duplicate of bug 1322864
   Sometimes the app search doesn't work in the Dash
** This bug has been marked a duplicate of bug 1295908
   Sometimes applications stop showing up in the Dash

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

Title:
  Dash don't find the applications

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Sometimes, when i use the dash, its only find the files, not the
  application.  To fix it, i need to restart the session.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 23 14:18:18 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:4140]
  InstallationDate: Installed on 2015-02-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: PHILCO 15A
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=ee87b79c-9da0-4561-b371-1f9ffefc1793 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: 15A
  dmi.board.vendor: PHILCO
  dmi.board.version: D02A
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd04/27/2011:svnPHILCO:pn15A:pvrNotApplicable:rvnPHILCO:rn15A:rvrD02A:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 15A
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PHILCO
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 23 11:58:47 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 592 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1318863] Re: unity dash loses ability to search for applications

[Colin Law]

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

** This bug is no longer a duplicate of bug 1322864
   Sometimes the app search doesn't work in the Dash
** This bug has been marked a duplicate of bug 1295908
   Sometimes applications stop showing up in the Dash

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

Title:
  unity dash loses ability to search for applications

Status in Unity:
  New
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Every so often, about once a day (I haven't identified a trigger for this 
behaviour), the unity dash loses the ability to search for applications.  I can 
open the dash and type, say "firefox" and nothing shows up. Rebooting does not 
seem to fix the problem.  However if I type, as recommended here 
 (note this 
is a slightly different bug, I can still search for files and the like):
  rm ~/.local/share/zeitgeist/activity.sqlite
  unity --reset &

  Unity restarts and searches for things normally. Somewhat to my
  annoyance a lot of settings get lost, for instance the custom sizing
  of my launcher icons. Fortunately, I can keep working, but I'd like
  this problem to go away if possible.

  I am running Ubuntu 12.04
  Kernel 3.2.0-58-generic

  I am running the kernel released by siddhu in this bug report
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1093217 because
  it fixes a problem where the computer hangs while booting.

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

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

[Touch-packages] [Bug 1295908] Re: Sometimes applications stop showing up in the Dash

[Colin Law]

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

I don't see how this is a dup of #1229370 as that one refers to a solid
failure of the home scope, whereas I am seeing an intermittent one.  In
fact that one looks like a simple problem to do with whether the scope
is correctly installed.

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

Title:
  Sometimes applications stop showing up in the Dash

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
   1. Open Dash
   2. Type a name of an application installed on your system, like "calculator"
   3. press escape

  What happens: Application scope stops giving results

  What should happen: Application scope should still give results

  How to fix it once it happens:
  A)type something and either hit escape or delete what you have typed.
  B)Check "application" in filters in the Dash (it gets unchecked)

  From the comments, it seems this might have something to do with
  people having online searches disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Mar 21 19:12:19 2014
  InstallationDate: Installed on 2013-10-05 (167 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-12-10 (101 days ago)

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

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

[Touch-packages] [Bug 1295908] Re: Sometimes applications stop showing up in the Dash

[Colin Law]

OK, keep up the good work :)

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

Title:
  Sometimes applications stop showing up in the Dash

Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
   1. Open Dash
   2. Type a name of an application installed on your system, like "calculator"
   3. press escape

  What happens: Application scope stops giving results

  What should happen: Application scope should still give results

  How to fix it once it happens:
  A)type something and either hit escape or delete what you have typed.
  B)Check "application" in filters in the Dash (it gets unchecked)

  From the comments, it seems this might have something to do with
  people having online searches disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Mar 21 19:12:19 2014
  InstallationDate: Installed on 2013-10-05 (167 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-12-10 (101 days ago)

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

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

[Touch-packages] [Bug 1295908] Re: Sometimes applications stop showing up in the Dash

[Colin Law]

I am still seeing it intermittently on 15.10.  See uploaded screenshot

** Attachment added: "Screenshot showing dash with nothing found"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295908/+attachment/4466827/+files/Screenshot%20from%202015-09-17%2013-56-18.png

** Changed in: unity
   Status: Invalid => Confirmed

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

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

Title:
  Sometimes applications stop showing up in the Dash

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
   1. Open Dash
   2. Type a name of an application installed on your system, like "calculator"
   3. press escape

  What happens: Application scope stops giving results

  What should happen: Application scope should still give results

  How to fix it once it happens:
  A)type something and either hit escape or delete what you have typed.
  B)Check "application" in filters in the Dash (it gets unchecked)

  From the comments, it seems this might have something to do with
  people having online searches disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Mar 21 19:12:19 2014
  InstallationDate: Installed on 2013-10-05 (167 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-12-10 (101 days ago)

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

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

[Touch-packages] [Bug 1318863] Re: unity dash loses ability to search for applications

[Colin Law]

Do you have Online Search disabled? (System Settings  Security 
Privacy  Search) If so then this is likely a dup of bug #1320539 (Dash
search of applications is randomly disabled when online searchs have
been turned off).

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

Title:
  unity dash loses ability to search for applications

Status in Unity:
  New
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Every so often, about once a day (I haven't identified a trigger for this 
behaviour), the unity dash loses the ability to search for applications.  I can 
open the dash and type, say firefox and nothing shows up. Rebooting does not 
seem to fix the problem.  However if I type, as recommended here 
http://askubuntu.com/questions/125843/dash-search-gives-no-result (note this 
is a slightly different bug, I can still search for files and the like):
  rm ~/.local/share/zeitgeist/activity.sqlite
  unity --reset 

  Unity restarts and searches for things normally. Somewhat to my
  annoyance a lot of settings get lost, for instance the custom sizing
  of my launcher icons. Fortunately, I can keep working, but I'd like
  this problem to go away if possible.

  I am running Ubuntu 12.04
  Kernel 3.2.0-58-generic

  I am running the kernel released by siddhu in this bug report
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1093217 because
  it fixes a problem where the computer hangs while booting.

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

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

[Touch-packages] [Bug 1072731] Re: Ctrl+Alt+0 does not minimise windows

[Colin Law]

And on 15.04

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

Title:
  Ctrl+Alt+0 does not minimise windows

Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  On an up to date installation of Quantal, System Settings  Keyboard 
  Shortcuts  Windows shows a default shortcut of Ctrl+Alt+0 for
  Minimise Windows.  This does not work however, it seems to have no
  effect.

  If the shortcut is disabled then put back to Ctrl+Alt+0 it then works.

  This may possibly related to bug #1063681 (ctrl+alt+0 does not work on
  Gala Window Manager)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Oct 29 13:44:51 2012
  InstallationDate: Installed on 2012-08-01 (88 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120730.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work

[Colin Law]

@Edward Falk that is nothing to do with this bug, which is about custom
shortcuts added by the user.

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

Title:
  Custom keyboard shortcuts don't work

Status in gnome-control-center:
  New
Status in libxfce4ui:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in libxkbcommon package in Ubuntu:
  Confirmed

Bug description:
  Just noticed that adding custom keyboard shortcuts does not have any
  effect. If, for example, I add a custom keyboard shortcut for Evince
  and set it to Ctrl+Alt+E, pressing this key combination won't launch
  Evince.

  * What happens *
When I add a custom keyboard shortcut (and bind it to some key 
combination), the shortcut does not run the associated command.

  * What I expect *
After adding the custom shortcut, I expect that the shortcut launches the 
associated command.

  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  gnome-control-center:
Installed: 1:3.6.3-0ubuntu36
Candidate: 1:3.6.3-0ubuntu36
Version table:
   *** 1:3.6.3-0ubuntu36 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu36
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic i686
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: i386
  Date: Thu Sep 12 19:21:56 2013
  InstallationDate: Installed on 2013-08-31 (12 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1

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

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

[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult

[Colin Law]

@vedavrata this bug applies to Unity, and is effectively closed.  If you
are seeing a problem on Xubuntu then I suggest you file a new bug.

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  distance name=left_width value=3/
  distance name=right_width value=3/
  distance name=bottom_height value=3/

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of misses when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  invisible region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System 
  Preferences  Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions

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

[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult

[Colin Law]

@Jeremy Huddleston, I see you are right, apologies (except that the fix
appeared only in Unity-3D, it was worse in Unity-2D than it was before
Unity-2D appeared).  Does Xubuntu use Metacity?  If not then my point is
still valid, that it would be best to file a new bug for Xubuntu if the
problem exists there, describing in detail exactly what the problem is.

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  distance name=left_width value=3/
  distance name=right_width value=3/
  distance name=bottom_height value=3/

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of misses when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  invisible region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System 
  Preferences  Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions

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

[Touch-packages] [Bug 1354180] Re: Regression: Ctrl+Alt+T shortcut, volume printScreen keys randomly stop working

[Colin Law]

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

** This bug has been marked a duplicate of bug 1459571
   Keyboard shortcuts stop working

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

Title:
  Regression: Ctrl+Alt+T shortcut, volume  printScreen keys randomly
  stop working

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Not sure Unity is the package.

  Ctrl+Alt+T used to be the keyboard shortcut for opening a new terminal
  window (whether or not one was already open).

  It doesn't work any more.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Aug  7 23:12:06 2014
  InstallationDate: Installed on 2013-10-11 (300 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (75 days ago)

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

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

[Touch-packages] [Bug 1470748] [NEW] Corrupted displays when hot plugging second monitor

[Colin Law]

Public bug reported:

On up to date Wily running on a laptop, when a second monitor is hot
plugged in, the image on the laptop monitor is cropped so only lower two
thirds are visible and the second monitor shows a black screen with
occasional flashes.

If the machine is booted with both monitors connected the displays work
as expected.

Same setup works ok on Vivid.

This report generated with the system in the error condition.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: unity 7.3.2+15.10.20150627.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.3-0ubuntu4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Jul  2 08:34:19 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. Device [10cf:17a9]
InstallationDate: Installed on 2015-07-01 (0 days ago)
InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha i386 (20150609)
MachineType: FUJITSU LIFEBOOK A544
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 
root=UUID=4ab50317-49e7-45c9-b675-d9391fbfd0e3 ro quiet splash
SourcePackage: unity
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.18
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
version.libdrm2: libdrm2 2.4.60-3
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.8-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.8-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Thu Jul  2 08:25:52 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   13890 
 vendor SEC
xserver.version: 2:1.17.1-0ubuntu4

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


** Tags: apport-bug compiz-0.9 i386 ubuntu wily

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

Title:
  Corrupted displays when hot plugging second monitor

Status in unity package in Ubuntu:
  New

Bug description:
  On up to date Wily running on a laptop, when a second monitor is hot
  plugged in, the image on the laptop monitor is cropped so only lower
  two thirds are visible and the second monitor shows a black screen
  with occasional flashes.

  If the machine is booted with both monitors connected the displays
  work as expected.

  Same setup works ok on Vivid.

  This report generated with the system in the error condition.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20150627.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul  2 08:34:19 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2015-07-01 (0 days ago)
  InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha i386 (20150609)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 
root=UUID=4ab50317-49e7-45c9-b675-d9391fbfd0e3 ro quiet 

[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult

[Colin Law]

@Jluc I believe it has been long fixed and is not seen in 15.04 or
later.  As in the first paragraph of the bug description it will not be
fixed in Unity-2D.

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in Decorator for compiz-fusion:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in The Metacity Window Manager:
  In Progress
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 2D:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  distance name=left_width value=3/
  distance name=right_width value=3/
  distance name=bottom_height value=3/

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of misses when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  invisible region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System 
  Preferences  Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions

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

[Touch-packages] [Bug 1414420] Re: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

[Colin Law]

I get the unable to connect message about 10 secs after boot but no
further lightdm messages, and no obvious ill effect, so perhaps it is
unrelated to the PAM messages.  In fact the only lightdm messages I see
are:

$ grep -i lightdm /var/log/syslog
Apr  6 09:57:14 tigger kernel: [   10.835217] audit: type=1400 
audit(1428310634.471:2): apparmor=STATUS operation=profile_load 
profile=unconfined name=/usr/lib/lightdm/lightdm-guest-session pid=512 
comm=apparmor_parser
Apr  6 09:57:21 tigger lightdm[1449]: initctl: Unable to connect to Upstart: 
Failed to connect to socket /com/ubuntu/upstart: Connection refused

syslog contained the complete boot sequence, and more.

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

Title:
  initctl: Unable to connect to Upstart: Failed to connect to socket
  /com/ubuntu/upstart: Connection refused

Status in Light Display Manager:
  Confirmed
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  That vivid system booted with systemd (systemd-sysv installed) have
  logged to journalctl:

  lightdm[1195]: initctl: Unable to connect to Upstart: Failed to connect to 
socket /com/ubuntu/upstart: Connection refused
  lightdm[1220]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  lightdm[1220]: PAM adding faulty module: pam_kwallet.so
  lightdm[1220]: pam_unix(lightdm-greeter:session): session opened for user 
lightdm by (uid=0)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.13.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
  Uname: Linux 3.19.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jan 25 11:35:37 2015
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

Which .desktop file is the one that should be in the launcher?  In 
/usr/share/applications I have three which have Name=Files:
nautilus.desktop
nautilus-folder-handler.desktop
org.gnome.Nautilus.desktop

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

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

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

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

[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown

[Colin Law]

No problem.  Attaching journal

** Attachment added: Journal showing wait on unmount when connected via wifi
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1438612/+attachment/4361872/+files/journal.txt

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

Title:
  remote file systems hang on shutdown

Status in dbus package in Ubuntu:
  Incomplete

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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

[Touch-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

I am still seeing a second nautilus icon opening in the launcher.
$ apt-cache policy unity
unity:
  Installed: 7.3.2+15.04.20150330-0ubuntu1
  Candidate: 7.3.2+15.04.20150330-0ubuntu1
  Version table:
 *** 7.3.2+15.04.20150330-0ubuntu1 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

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

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

[Touch-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

On a vivid which was originally updated from Trusty and is up to date I created 
a new user (via System Settings  User Accts) and logged in as that user.  
Clicking on Files opens a new icon in the launcher.
The desktop file the system has put in the launcher is 
org.gnome.Nautilus.desktop

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

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

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

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

[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early

[Colin Law]

Fixed here too.

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

Title:
  remote file systems hang on shutdown, D-BUS stops too early

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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

[Touch-packages] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

I am pretty sure that a couple of years ago the gnome guys decided that the 
laptop should not suspend if an external monitor is plugged in (which was a 
change to the previous strategy).  I think that by popular request this was 
reverted back to suspend (possibly only in Ubuntu, I don't know).  I am sure 
there was a bug for this but I can't find it.  Now it has apparently changed 
again.
I can see that for some it makes sense to not suspend, but for those who use 
the laptop in a dock with both displays active it is annoying to have to use 
the menus to suspend.  I would have thought it more appropriate to have the 
default stay as it has been for many years.  Ideally there could be an 
additional option in the settings to allow a choice of lid closure actions when 
there are two displays.  Currently the option is to suspend or not.  It does 
not say suspend, but only if there is no external display connected.

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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

[Touch-packages] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

For clarity I am not actually using a dock, I just have the external
monitor plugged in to the laptop, and it does not suspend when I close
the lid.

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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

[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown

[Colin Law]

Yes, I have that version:

$ apt-cache policy wpasupplicant
wpasupplicant:
  Installed: 2.1-0ubuntu7
  Candidate: 2.1-0ubuntu7
  Version table:
 *** 2.1-0ubuntu7 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status

$ systemctl cat wpa_supplicant.service |grep Before
Before=network.target

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

Title:
  remote file systems hang on shutdown

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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

[Touch-packages] [Bug 1431774] Re: network mount hangs on shutdown - NetworkManager needs to stop after network.target

[Colin Law]

I am still seeing the problem when connected via wifi (Ok on wired).

Adding After=dbus.service to
/lib/systemd/system/NetworkManager.service's [Unit] section appears to
fix it.

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

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

Title:
  network mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Confirmed
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa package in Debian:
  New

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 945482] Re: Loud hiss on audio converting mp4 to mpg with avconv or ffmpeg

[Colin Law]

The problem is no longer seen with up to date 14.04 or 15.04

** Changed in: libav (Ubuntu)
   Status: Incomplete = Fix Released

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

Title:
  Loud hiss on audio converting mp4 to mpg with avconv or ffmpeg

Status in the libav multimedia framework:
  New
Status in libav package in Ubuntu:
  Fix Released

Bug description:
  Using avconv on up to date Precise.
  Converting mp4 (downloaded using get-iplayer but I don't know whether this is 
significant) using the command
  avconv -i test.mp4 -target pal-dvd test.mpg
  yields a file with audio that is mostly hiss, with an undercurrent of the 
audio underneath.  The terminal o/p is:

  $ avconv -i test.mp4 -target pal-dvd test.mpg
  avconv version 0.8-4:0.8-1ubuntu2, Copyright (c) 2000-2011 the Libav 
developers
built on Feb  9 2012 08:21:31 with gcc 4.6.2
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x9a54260] multiple edit list entries, a/v desync 
might occur, patch welcome
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'test.mp4':
Metadata:
  major_brand : isom
  minor_version   : 512
  compatible_brands: isomiso2avc1mp41
  encoder : Lavf53.20.0
  media_type  : 10
  copyright   : � 2012 British Broadcasting Corporation, all rights 
reserved
  title   : Rugged Wales
  artist  : BBC One
  album_artist: BBC TV
  album   : Rugged Wales
  composer: BBC iPlayer
  genre   : Factual
  comment : Iolo Williams explores some of the best wild and 
industrial landscapes in Wales.
  date: 2012-03-01T20:00:00Z
  description : Iolo Williams explores some of the best wild and 
industrial landscapes in Wales.
  show: Rugged Wales
  episode_id  : b01cywyz
  network : BBC One
Duration: 00:58:58.16, start: 0.00, bitrate: 1502 kb/s
  Stream #0.0(und): Video: h264 (Main), yuv420p, 832x468 [PAR 117:117 DAR 
16:9], 1401 kb/s, 25 fps, 25 tbr, 25 tbn, 50 tbc
  Stream #0.1(und): Audio: aac, 48000 Hz, stereo, s16, 94 kb/s
  [buffer @ 0x9a59f00] w:832 h:468 pixfmt:yuv420p
  [scale @ 0x9a59d60] w:832 h:468 fmt:yuv420p - w:720 h:576 fmt:yuv420p 
flags:0x4
  Incompatible sample format 's16' for codec 'ac3', auto-selecting format 'flt' 
  - possibly significant  -|
  Output #0, dvd, to 'test.mpg':
Metadata:
  major_brand : isom
  minor_version   : 512
  compatible_brands: isomiso2avc1mp41
  network : BBC One
  media_type  : 10
  copyright   : � 2012 British Broadcasting Corporation, all rights 
reserved
  title   : Rugged Wales
  artist  : BBC One
  album_artist: BBC TV
  album   : Rugged Wales
  composer: BBC iPlayer
  genre   : Factual
  comment : Iolo Williams explores some of the best wild and 
industrial landscapes in Wales.
  date: 2012-03-01T20:00:00Z
  description : Iolo Williams explores some of the best wild and 
industrial landscapes in Wales.
  show: Rugged Wales
  episode_id  : b01cywyz
  encoder : Lavf53.20.0
  Stream #0.0(und): Video: mpeg2video, yuv420p, 720x576 [PAR 64:45 DAR 
16:9], q=2-31, 6000 kb/s, 90k tbn, 25 tbc
  Stream #0.1(und): Audio: ac3, 48000 Hz, stereo, flt, 448 kb/s
  Stream mapping:
Stream #0:0 - #0:0 (h264 - mpeg2video)
Stream #0:1 - #0:1 (aac - ac3)
  Press ctrl-c to stop encoding
  Input stream #0:1 frame changed from rate:48000 fmt:s16 ch:2 to rate:48000 
fmt:flt ch:2
  [mpeg2video @ 0x9a57420] rc buffer underflow
  ^Cframe=  123 fps= 32 q=2.0 Lsize=2360kB time=4.74 bitrate=4082.2kbits/s 
dup=4 drop=0
  video:2042kB audio:259kB global headers:0kB muxing overhead 2.574681%
  Received signal 2: terminating.

  If I add the option -acodec ac3_fixed then the sound is ok, so
  possibly it is a problem with ac3 codec.

  The problem is not seen on an earlier version of ffmpeg.

  I can provide a sample mp4 file showing the problem if necessary.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libav-tools 4:0.8-1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic i686
  ApportVersion: 1.94-0ubuntu1
  Architecture: i386
  Date: Sat Mar  3 09:43:31 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 
(2029.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: libav
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

A workaround for the missing bookmarks is to is to unlock the nautilus shortcut 
from the launcher and instead drag across 
/usr/share/applications/nautilus.desktop and lock that to the launcher (in the 
files view of that folder three items show as Files, it is the one that is 
about 600 bytes long that is wanted).  Then to fix the duplicate icon problem 
add to the end of the [Desktop Entry] section of that file the line
StartupWMClass=nautilus

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

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

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

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

[Touch-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

Unfortunately this fix has resulted in the loss of the right click
bookmarks feature of the nautilus icon in the launcher.  For me at
least.

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

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

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

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

[Touch-packages] [Bug 805087] Re: Dash and launcher appear underneath windows

[Colin Law]

See comment #103

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

Title:
  Dash and launcher appear underneath windows

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Oneiric:
  Fix Released

Bug description:
  main problem:
    unity launcher and dash always hidden (behind displayed application-windows)

  more details and symptoms:
    docky behaves like unity-launcher/dash.
    press super button and type terminal+enter (nothing displayed) ... a 
terminal-window starts/pop-up

  conclusion:
    the input-stack/focus is o.k.
    the windows-display-stack/focus is wrong

  more symptoms:
    After docky-stop and docky-start (restart) the docky-bar shows as 
top-level-window = o.k.
    This is reproducable with firefox windows by moving/maximise/move to 
desktop XY.
    Sometimes other windows (like terminal-window/google-chrome-window) are 
hiding the launcher/dash/docky too.
    This problem is reproducable on a T60p with ATI-FireGL video-card.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.16-0ubuntu1~natty1
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  Date: Sun Jul  3 13:58:33 2011
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroVariant: ubuntu
  DkmsStatus:
   tp-smapi, 0.40, 2.6.38-10-generic, x86_64: installed
   tp-smapi, 0.40, 2.6.38-8-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21d1]
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia_: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia__: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  MachineType: LENOVO 428449G
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic 
root=UUID=be0937c9-8117-4833-a50b-1b5c391c9b69 ro quiet splash 
i915.semaphores=1 vt.handoff=7
  ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  ProcVersionSignature__: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Renderer: Unknown
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 04/19/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8BET42WW (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 428449G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8BET42WW(1.22):bd04/19/2011:svnLENOVO:pn428449G:pvrThinkPadW520:rvnLENOVO:rn428449G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 428449G
  dmi.product.version: ThinkPad W520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2
  version.ia32-libs: ia32-libs 20090808ubuntu13
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

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

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

[Touch-packages] [Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target

[Colin Law]

Having tried with wifi connection (was previously wired) I also still
see the problem if connected via wifi.

** Changed in: network-manager (Ubuntu)
   Status: Fix Released = Confirmed

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

Title:
  cifs mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target

[Colin Law]

Is the fact that WPA Supplicant has been stopped significant?

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

Title:
  cifs mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: Manual cifs mount leads to delay on shutdown

[Colin Law]

Yes, you are right, NetworkManager was stopped earlier, I had missed
that.  Connection is wired, wifi is disabled.  I do use NM.

Wasn't sure whether if I made it private you would be able to see it.
Will send the log by PM.

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

Title:
  Manual cifs mount leads to delay on shutdown

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network{, -online}.target

[Colin Law]

Great, is it as simple as adding
Before=network-online.target network.target
to Unit section of /lib/systemd/system/NetworkManager.service?

Having tried it that does appear to fix the problem (including the
problem with the init script in the duplicate bug, where it was timing
out on a umount command).

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

Title:
  cifs mount hangs on shutdown - NetworkManager needs to stop after
  network{,-online}.target

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: Manual cifs mount leads to delay on shutdown

[Colin Law]

** Attachment added: syslog
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431774/+attachment/4344047/+files/syslog

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

Title:
  Manual cifs mount leads to delay on shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] [NEW] Manual cifs mount leads to delay on shutdown

[Colin Law]

Public bug reported:

To replicate, perform a manual cifs mount, for example:

sudo mount -t cifs -o credentials=,user,rw,uid=1000
//192.168.1.nnn/docs   /media/test_mount

Then shutdown.  When booted with systemd there is a 1 to 2 minute delay
before shutdown.  In syslog the last shutdown (09:47:11 13th March)
showed the effect, though I fear that syslog shuts down too early to see
anything.

If booted with upstart there is no noticeable delay on shutdown.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 13 09:50:08 2015
InstallationDate: Installed on 2014-10-21 (142 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
MachineType: FUJITSU LIFEBOOK A544
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
dmi.bios.date: 12/01/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.18
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU

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


** Tags: amd64 apport-bug vivid

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

Title:
  Manual cifs mount leads to delay on shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: Manual cifs mount leads to delay on shutdown

[Colin Law]

I enabled the debug shell via sudo systemctl start debug-shell and
checked that I could get into it ok.  When I then shutdown it went to
the debug shell by itself but the keyboard was dead so I could not do
anything.  It shutdown after the delay.

Before the shutdown, in the debug shell, I got

#systemctl status media-test_mount.mount
   Loaded: loaded (/proc/self/mountinfo)
   Active: active (mounted) since Fri 2015-03-13 11:44:55 GMT; 1min 15s ago
Where: /media/test_mount
 What: //192.168.1.***/docs

But systemctl cat media-test_mount.mount said
No files found for media-test_mount.mount

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

Title:
  Manual cifs mount leads to delay on shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: Manual cifs mount leads to delay on shutdown

[Colin Law]

** Attachment added: systemctl show media-test_mount.mount (sanitised)
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431774/+attachment/4344325/+files/systemctl-show_sanitised.txt

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

Title:
  Manual cifs mount leads to delay on shutdown

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: Manual cifs mount leads to delay on shutdown

[Colin Law]

I have removed the syslog attachment as I had not sanitised it, let me
know if it is needed.

** Attachment removed: syslog
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431774/+attachment/4344047/+files/syslog

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

Title:
  Manual cifs mount leads to delay on shutdown

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: Manual cifs mount leads to delay on shutdown

[Colin Law]

Martin, yes, have re-attached the systemclt show results.
Have also marked the previous bug which I thought was an error in an init 
script as a dup of this as I believe this is the fundamental problem.

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

Title:
  Manual cifs mount leads to delay on shutdown

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: Manual cifs mount leads to delay on shutdown

[Colin Law]

** Attachment added: systemctl show media-test_mount.mount
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431774/+attachment/4344318/+files/systemctl-show.txt

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

Title:
  Manual cifs mount leads to delay on shutdown

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: Manual cifs mount leads to delay on shutdown

[Colin Law]

** Attachment removed: systemctl show media-test_mount.mount
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431774/+attachment/4344318/+files/systemctl-show.txt

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

Title:
  Manual cifs mount leads to delay on shutdown

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1429143] Re: Slow shutdown after booting with systemd

[Colin Law]

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

** This bug has been marked a duplicate of bug 1431774
   Manual cifs mount leads to delay on shutdown

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

Title:
  Slow shutdown after booting with systemd

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When running vivid booted with systemd kernel, shutdown consistently
  takes around 90 seconds.  With the normal kernel it is about 15
  seconds.

  In the log, shutdown started (from the cog) at 13:50:20, Mar 6th.  The
  purple Ubuntu screen with dots appears after a few seconds and then
  sits there.  It actually powered off at 13:51:55.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1948 F pulseaudio
   /dev/snd/controlC1:  colinl 1948 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar  6 13:54:29 2015
  InstallationDate: Installed on 2014-10-21 (135 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (8 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: Manual cifs mount leads to delay on shutdown

[Colin Law]

I have got the journal but there is a lot of potentially sensitive stuff there. 
 Would it be possible to make the bug private while you review it?
I think it is more subtle than the network going down early.

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

Title:
  Manual cifs mount leads to delay on shutdown

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: Manual cifs mount leads to delay on shutdown

[Colin Law]

Alternatively this may be enough.

Mar 13 16:19:26 tigger systemd[1]: Stopped ACPI event daemon.
Mar 13 16:19:28 tigger mysql[2887]: ...done.
Mar 13 16:19:28 tigger systemd-journal[256]: Forwarding to syslog missed 68 
messages.
Mar 13 16:19:28 tigger systemd[1]: Stopped LSB: Start and stop the mysql 
database server daemon.
Mar 13 16:19:28 tigger systemd[1]: Stopped target System Time Synchronized.
Mar 13 16:19:28 tigger systemd[1]: Stopping System Time Synchronized.
Mar 13 16:19:28 tigger systemd[1]: Stopped target Remote File Systems.
Mar 13 16:19:28 tigger systemd[1]: Stopping Remote File Systems.
Mar 13 16:19:28 tigger systemd[1]: Unmounting /media/test_mount...
Mar 13 16:20:58 tigger systemd[1]: media-test_mount.mount unmounting timed out. 
Stopping.
Mar 13 16:21:14 tigger kernel: CIFS VFS: Server 192.168.1.96 has not responded 
in 120 seconds. Reconnecting...
Mar 13 16:21:34 tigger umount[3012]: umount: /media/test_mount: target is busy
Mar 13 16:21:34 tigger umount[3012]: (In some cases useful info about processes 
that
Mar 13 16:21:34 tigger umount[3012]: use the device is found by lsof(8) or 
fuser(1).)
Mar 13 16:21:34 tigger systemd[1]: media-test_mount.mount mount process exited, 
code=exited status=32
Mar 13 16:21:34 tigger systemd[1]: Failed unmounting /media/test_mount.
Mar 13 16:21:34 tigger systemd[1]: Stopped target Network is Online.
Mar 13 16:21:34 tigger systemd[1]: Stopping Network is Online.
Mar 13 16:21:34 tigger systemd[1]: Stopped Wait for all auto 
/etc/network/interfaces to be up for network-online.target.
Mar 13 16:21:34 tigger systemd[1]: Stopping Wait for all auto 
/etc/network/interfaces to be up for network-online.target...
Mar 13 16:21:34 tigger systemd[1]: Stopped target Basic System.
Mar 13 16:21:34 tigger systemd[1]: Stopping Basic System.
Mar 13 16:21:34 tigger systemd[1]: Stopped target Slices.

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

Title:
  Manual cifs mount leads to delay on shutdown

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1429143] Re: Slow shutdown after booting with systemd

[Colin Law]

Oops, following Martin's helpful pointers I see that it was down to one
my home-brewed services that does not seem to like being run via
systemd.   Likely a problem of my own making.

Thanks for the help and sorry for the noise.

** Changed in: systemd (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  Slow shutdown after booting with systemd

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When running vivid booted with systemd kernel, shutdown consistently
  takes around 90 seconds.  With the normal kernel it is about 15
  seconds.

  In the log, shutdown started (from the cog) at 13:50:20, Mar 6th.  The
  purple Ubuntu screen with dots appears after a few seconds and then
  sits there.  It actually powered off at 13:51:55.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1948 F pulseaudio
   /dev/snd/controlC1:  colinl 1948 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar  6 13:54:29 2015
  InstallationDate: Installed on 2014-10-21 (135 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (8 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1429143] Re: Slow shutdown after booting with systemd

[Colin Law]

Yes, I understand that.  Still analysing, but I think it is probably an
error in my custom init.d script.  Haven't done much with init.d so not
sure what is going on yet.  Will confirm what it was when I find out.

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

Title:
  Slow shutdown after booting with systemd

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When running vivid booted with systemd kernel, shutdown consistently
  takes around 90 seconds.  With the normal kernel it is about 15
  seconds.

  In the log, shutdown started (from the cog) at 13:50:20, Mar 6th.  The
  purple Ubuntu screen with dots appears after a few seconds and then
  sits there.  It actually powered off at 13:51:55.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1948 F pulseaudio
   /dev/snd/controlC1:  colinl 1948 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar  6 13:54:29 2015
  InstallationDate: Installed on 2014-10-21 (135 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (8 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1292560] Re: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()

[Colin Law]

** Tags added: vivid

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

Title:
  unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I booted the system and got this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 14 11:03:04 2014
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   PATH=(custom, user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0b5c9ae583 malloc_consolidate+307:   cmp
0x18(%rax),%rbx
   PC (0x7f0b5c9ae583) ok
   source 0x18(%rax) (0x7f0b5ccee7e80018) not located in a known VMA region 
(needed readable region)!
   destination %rbx ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f0b5ccee760 main_arena) at malloc.c:4157
   _int_malloc (av=av@entry=0x7f0b5ccee760 main_arena, 
bytes=bytes@entry=1056) at malloc.c:3423
   __libc_calloc (n=optimized out, elem_size=optimized out) at malloc.c:3219
   pa_xmalloc0 () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_hashmap_new () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
  Title: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: Upgraded to trusty on 2013-12-06 (97 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1043806] Re: With dual displays unity launcher favours windows on its own display

[Colin Law]

** Tags added: vivid

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

Title:
  With dual displays unity launcher favours windows on its own display

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  On a dual display system (Quantal alpha up to date) if an application
  has multiple windows open on different displays then using the
  launcher icon to return to the app goes to the window on the display
  the launcher is on, even if the focus was previously on the other
  display.

  To reproduce, on a dual display system with the launcher on the right hand 
display open two firefox windows and place one on each display.
  Open a Nautilus window and place it partially over the firefox window in the 
left hand display.
  Click on the Firefox window in the left hand display then on the Nautilus 
window.
  Click on the Firefox launcher.

  What should happen: focus should return to the Firefox window in the left 
hand display
  What happens: focus goes to the Firefox window in the right hand display.

  If the launcher is moved to the left hand display then in the
  equivalent situation focus will return to the firefox window in the
  left hand display.

  The symptom does not appear to be specific to the application,
  reversing the role of nautilus and firefox in the above scenario
  results in focus returning to the wrong nautilus window.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.2.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Thu Aug 30 13:39:35 2012
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120730.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

In terms of the kernel version I don't know exactly as I do not suspend
very often, but I never saw the problem before upgrade from Utopic.  I
have just tried booting into a live Utopic image which was the release
candidate on 17th Oct 14 and uname shows 3.16.0-22 and it suspends ok
there.  Perhaps it is not purely a kernel issue.

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

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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

[Touch-packages] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

In fact I see from my bug #1384454 that Utopic with kernel 3.16.0-23 and
with 3.18.0-031800rc1 both suspended ok with external screen (though
they did suffer from windows moving workspaces as in that bug).

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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

[Touch-packages] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

It is the same situation with v3.16-utopic.  Closing the lid with ext
monitor connected causes windows to move to ext monitor but does not
suspend.

I have discovered another symptom that may possibly be related.  With
any of the kernels and with the external monitor not connected, closing
the lid does nothing during the first four minutes after booting.  After
that time it suspends ok (ext monitor not connected).  If closed during
first four minutes then nothing happens, but if left closed it does
suspend after that time has elapsed.  Since discovering this I have gone
back and checked the other kernels again and waited till it will suspend
with no ext monitor and re-confirmed that it does not suspend with the
ext monitor connected.

As a matter of interest are others seeing suspend ok with external
monitor?

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

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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

[Touch-packages] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

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

Bug still present with BIOS version 1.19

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

** This bug has been marked a duplicate of bug 1426123
   Laptop does not suspend on lid close when external monitor connected

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Running up to date Vivid on laptop with external display, closing the
  lid does not suspend even though suspend is selected in the power
  settings for lid close.  The display flashes and apps move to external
  display.  Syslog shows no attempt to suspend.

  With no external display connected the laptop suspends as expected.

  In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30
  There are messages of the form
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
  in syslog at that time but I suspect they may be a different issue.

  Not sure whether xorg is the correct package for this, hopefully
  someone will redirect if appropriate.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890 
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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

[Touch-packages] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date
..
Version 1.18
12/01/2014


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

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Running up to date Vivid on laptop with external display, closing the
  lid does not suspend even though suspend is selected in the power
  settings for lid close.  The display flashes and apps move to external
  display.  Syslog shows no attempt to suspend.

  With no external display connected the laptop suspends as expected.

  In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30
  There are messages of the form
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
  in syslog at that time but I suspect they may be a different issue.

  Not sure whether xorg is the correct package for this, hopefully
  someone will redirect if appropriate.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890 
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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

[Touch-packages] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

The bug is present with linux-
image-3.17.1-031701-generic_3.17.1-031701.201410150735_amd64.deb

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

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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

[Touch-packages] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

Just in case it is relevant, when I upgraded to BIOS 1.18 I ran into bug
#887793 (Kworker constantly taking about 100% CPU) worked around as in
comment 114 there (echo disable 
/sys/firmware/acpi/interrupts/gpe13).  This suspend bug was still seen
before and after the workaround.  Before disabling gpe13, top showed
kworker hogging one of the cores and there was no sign of Xorg near the
top of the cpu usage list.  After implementing the workaround Xorg re-
appeared as normal with a few % of processor.

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Running up to date Vivid on laptop with external display, closing the
  lid does not suspend even though suspend is selected in the power
  settings for lid close.  The display flashes and apps move to external
  display.  Syslog shows no attempt to suspend.

  With no external display connected the laptop suspends as expected.

  In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30
  There are messages of the form
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
  in syslog at that time but I suspect they may be a different issue.

  Not sure whether xorg is the correct package for this, hopefully
  someone will redirect if appropriate.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890 
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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

[Touch-packages] [Bug 821723] Re: [feature request] add a -u|--update flage

[Colin Law]

I am struggling to think of a situation where it would be harmful or
even undesirable to perform an update after the add.  In which case
possibly the default should be to do the update, with a switch to
prevent it.

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

Title:
  [feature request] add a -u|--update flage

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  It would be *really* useful if apt-add-repository had a -u|--update
  flag, that would immediately trigger an apt-get update on a successful
  repository addition.

  It seems I *always* run:
   $ sudo apt-add-repository ppa:foo/ppa
   $ sudo apt-get update

  Rarely, if ever, are these two decoupled for me.  It would be nice if
  I could just tell apt-add-repository to JFDI ;-)

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

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

[Touch-packages] [Bug 1415958] [NEW] Laptop + external display does not suspend on lid close

[Colin Law]

Public bug reported:

Running up to date Vivid on laptop with external display, closing the
lid does not suspend even though suspend is selected in the power
settings for lid close.  The display flashes and apps move to external
display.  Syslog shows no attempt to suspend.

With no external display connected the laptop suspends as expected.

In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30
There are messages of the form
i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
in syslog at that time but I suspect they may be a different issue.

Not sure whether xorg is the correct package for this, hopefully someone
will redirect if appropriate.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
Uname: Linux 3.18.0-11-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.15.1-0ubuntu4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Jan 29 15:04:52 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. Device [10cf:17a9]
InstallationDate: Installed on 2014-12-27 (33 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
MachineType: FUJITSU LIFEBOOK A544
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.17
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
version.libdrm2: libdrm2 2.4.58-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Thu Jan 29 15:00:08 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   13890 
 vendor SEC
xserver.version: 2:1.16.2.901-1ubuntu3

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


** Tags: apport-bug compiz-0.9 i386 ubuntu vivid

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Running up to date Vivid on laptop with external display, closing the
  lid does not suspend even though suspend is selected in the power
  settings for lid close.  The display flashes and apps move to external
  display.  Syslog shows no attempt to suspend.

  With no external display connected the laptop suspends as expected.

  In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30
  There are messages of the form
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
  in syslog at that time but I suspect they may be a different issue.

  Not sure whether xorg is the correct package for this, hopefully
  someone will redirect if appropriate.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  

[Touch-packages] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

** Attachment added: syslog
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1415958/+attachment/4308022/+files/syslog

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Running up to date Vivid on laptop with external display, closing the
  lid does not suspend even though suspend is selected in the power
  settings for lid close.  The display flashes and apps move to external
  display.  Syslog shows no attempt to suspend.

  With no external display connected the laptop suspends as expected.

  In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30
  There are messages of the form
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
  in syslog at that time but I suspect they may be a different issue.

  Not sure whether xorg is the correct package for this, hopefully
  someone will redirect if appropriate.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890 
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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

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