[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

2017-03-22 Thread Bryce Nesbitt
Bug #1624644 is a very old one, marked as fixed, with considerable
discussion and confusion.

This bug is a clear indication that as of 16.04LTS, a bug exists with
/boot filling up.  Maybe it's the same cause, maybe it's different
cause.   This bug is trivial to reproduce: it happens on freshly
installed stock no-changes versions of 16.04 if LVM is chosen, and the
machine is left idle for 3 or more update cycles.

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

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


[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2017-03-22 Thread Bryce Nesbitt
Not fixed
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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


[Touch-packages] [Bug 1675079] [NEW] 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

2017-03-22 Thread Bryce Nesbitt
Public bug reported:

On a 16.04LTS system, the /boot partition will eventually fill with
Kernel images, until the point where "apt-get autoremove" can't
complete.

This issue has previously been reported as fixed, but it is not fixed:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

Generally what I see is the final kernel image that fills the drive is
incompletely installed (the header package does not make it).  "apt-get
autoremove" tries to work, but fails.  I must manually remove kernel
images to free enough space.

I see this on a machine used by my elderly parents, where 'Download and
install updates automatically' is set.  And on my home machines, where
the setting is elsewhere.

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

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

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


[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2017-03-22 Thread Bryce Nesbitt
My elderly parents are on Ubuntu 16.04, with updates set to 'Download and 
install automatically'.
I must manually prune the Kernel images every so often, or the system's 
underwear gets all in a twist, and "apt-get autoremove' won't even work.

Let's be clear: THIS IS NOT FIXED as of 16.04 LTS.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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


[Touch-packages] [Bug 1284164] Re: ~/.cache/upstart grows enormous

2017-03-22 Thread Bryce Nesbitt
-rw-r- 1 bnesbitt bnesbitt6747 Mar 22 08:42 dbus.log
-rw-r- 1 bnesbitt bnesbitt   20295 Mar 21 07:40 
gnome-session-Unity.log.1.gz
-rw-r- 1 bnesbitt bnesbitt  138016 Mar 20 09:03 
gnome-session-Unity.log.3.gz
-rw-r- 1 bnesbitt bnesbitt  141565 Mar 15 10:43 
gnome-session-Unity.log.7.gz
-rw-r- 1 bnesbitt bnesbitt  173361 Mar 20 22:02 
gnome-session-Unity.log.2.gz
-rw-r- 1 bnesbitt bnesbitt  346368 Mar 19 08:59 
gnome-session-Unity.log.4.gz
-rw-r- 1 bnesbitt bnesbitt  469737 Mar 18 09:36 
gnome-session-Unity.log.5.gz
-rw-r- 1 bnesbitt bnesbitt  529850 Mar 17 10:38 
gnome-session-Unity.log.6.gz
-rw-r- 1 bnesbitt bnesbitt 10686756450 Mar 22 08:44 gnome-session-Unity.log


The gnome log is filled with completely non-actionable log messages for anyone 
other than the developer of the given app:

(firefox:5419): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'object->ref_count > 0' failed
(putty:17960): GLib-CRITICAL **: Source ID 95654 was not found when attempting 
to remove it

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

Title:
  ~/.cache/upstart grows enormous

Status in dbus package in Ubuntu:
  Confirmed
Status in logrotate package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  
  $ du -hs ~/.cache/upstart/
  454M  /home/smoser/.cache/upstart/

  $ ls -altr ~/.cache/upstart/ | egrep "[0-9]{6,} "
  -rw-r-  1 smoser smoser  14105029 Feb 10 08:53 gnome-session.log
  -rw-r-  1 smoser smoser   3112634 Feb 23 23:09 gnome-settings-daemon.log
  -rw-r-  1 smoser smoser   1179973 Feb 24 08:29 indicator-application.log
  -rw-r-  1 smoser smoser   4129955 Feb 24 09:31 hud.log
  -rw-r-  1 smoser smoser  18668572 Feb 24 10:13 unity-panel-service.log
  -rw-r-  1 smoser smoser 429582393 Feb 24 10:13 dbus.log
  -rw-r-  1 smoser smoser   3708061 Feb 24 10:13 gnome-session-ubuntu.log

  $ uptime
   10:15:17 up 14 days,  1:20, 24 users,  load average: 1.09, 0.95, 1.33

  I suspect my desktop has been logged in and being used for about 14
  days, but clearly not longer.  Also, it has gone through 'apt-get
  dist-upgrade' in that time (those are possible excuses for the above).

  However, I have 450M of data in a ~/.cache/upstart and 430M in a
  single file.

  I'll attach the log shortly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.11-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Mon Feb 24 10:11:04 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-19 (859 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2013-05-20 (280 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.11)
  UpstartRunningSystemVersion: init (upstart 1.11)

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

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


[Touch-packages] [Bug 1284164] Re: ~/.cache/upstart grows enormous

2017-03-22 Thread Bryce Nesbitt
This is also an issue for SSD owners, as it results in significant write
churn on the drive, for no benefit to the owner of the computer.

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

Title:
  ~/.cache/upstart grows enormous

Status in dbus package in Ubuntu:
  Confirmed
Status in logrotate package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  
  $ du -hs ~/.cache/upstart/
  454M  /home/smoser/.cache/upstart/

  $ ls -altr ~/.cache/upstart/ | egrep "[0-9]{6,} "
  -rw-r-  1 smoser smoser  14105029 Feb 10 08:53 gnome-session.log
  -rw-r-  1 smoser smoser   3112634 Feb 23 23:09 gnome-settings-daemon.log
  -rw-r-  1 smoser smoser   1179973 Feb 24 08:29 indicator-application.log
  -rw-r-  1 smoser smoser   4129955 Feb 24 09:31 hud.log
  -rw-r-  1 smoser smoser  18668572 Feb 24 10:13 unity-panel-service.log
  -rw-r-  1 smoser smoser 429582393 Feb 24 10:13 dbus.log
  -rw-r-  1 smoser smoser   3708061 Feb 24 10:13 gnome-session-ubuntu.log

  $ uptime
   10:15:17 up 14 days,  1:20, 24 users,  load average: 1.09, 0.95, 1.33

  I suspect my desktop has been logged in and being used for about 14
  days, but clearly not longer.  Also, it has gone through 'apt-get
  dist-upgrade' in that time (those are possible excuses for the above).

  However, I have 450M of data in a ~/.cache/upstart and 430M in a
  single file.

  I'll attach the log shortly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.11-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Mon Feb 24 10:11:04 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-19 (859 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2013-05-20 (280 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.11)
  UpstartRunningSystemVersion: init (upstart 1.11)

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

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


[Touch-packages] [Bug 1640924] [NEW] MFC8600 Brother Prints OK first PDF job, second job prints garbage

2016-11-10 Thread Bryce Nesbitt
Public bug reported:

It's been like this for years. Some initialization problem between
driver and printer.

If I print certain types of documents the printer is fine.
If I print a pdf, it's fine.
If I print a second pdf, reams of paper spit out of the machine each with a few 
random characters on them.

Resetting CUPS or power cycling the printer fixes the issue for one printout.
Resetting CPUS ("sudo /etc/init.d/cups restart") fixes the issue for one 
printout.

I use the "Brother MFC-8600 Foomatic/hl7x0 (recommended)" driver.  Changing 
driver
does not... at least not for sure... fix the problem.

--

Or maybe it is an end job problem, as the printer often reports a state of
"Idle - Sending data to printer."
Hours after the last printout.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.7
ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
Uname: Linux 3.13.0-100-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CupsErrorLog:
 E [09/Nov/2016:09:07:28 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
 E [10/Nov/2016:09:18:42 -0800] [Job 2767] Unable to send data to printer.
 E [10/Nov/2016:09:23:43 -0800] [Job 2767] Stopping unresponsive job.
 E [10/Nov/2016:09:26:06 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
CurrentDesktop: Unity
Date: Thu Nov 10 11:37:50 2016
Lpstat:
 device for Brother-MFC-8600: 
ipps://Bryces-Mac-mini.local:631/printers/Brother_MFC_8600
 device for MFC-8600: usb://Brother/MFC-8600
 device for MFCJ985DW: dnssd://Brother%20MFC-J985DW._ipp._tcp.local/
MachineType: Supermicro X8SAX
Papersize: letter
PpdFiles:
 MFCJ985DW: Brother MFC-J985DW CUPS
 MFC-8600: Brother MFC-8600 Foomatic/hl7x0 (recommended)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic 
root=UUID=8a67d411-9750-46e4-8a53-b2059e5a4eeb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/17/10
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: X8SAX
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd09/17/10:svnSupermicro:pnX8SAX:pvr1234567890:rvnSupermicro:rnX8SAX:rvr2.0:cvnSupermicro:ct3:cvr1234567890:
dmi.product.name: X8SAX
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
mtime.conffile..etc.cups.cupsd.conf: 2015-01-21T15:19:58.577664

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


** Tags: amd64 apport-bug trusty

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

Title:
  MFC8600 Brother Prints OK first PDF job, second job prints garbage

Status in cups package in Ubuntu:
  New

Bug description:
  It's been like this for years. Some initialization problem between
  driver and printer.

  If I print certain types of documents the printer is fine.
  If I print a pdf, it's fine.
  If I print a second pdf, reams of paper spit out of the machine each with a 
few random characters on them.

  Resetting CUPS or power cycling the printer fixes the issue for one printout.
  Resetting CPUS ("sudo /etc/init.d/cups restart") fixes the issue for one 
printout.

  I use the "Brother MFC-8600 Foomatic/hl7x0 (recommended)" driver.  Changing 
driver
  does not... at least not for sure... fix the problem.

  --

  Or maybe it is an end job problem, as the printer often reports a state of
  "Idle - Sending data to printer."
  Hours after the last printout.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-100-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CupsErrorLog:
   E [09/Nov/2016:09:07:28 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
   E [10/Nov/2016:09:18:42 -0800] [Job 2767] Unable to send data to printer.
   E [10/Nov/2016:09:23:43 -0800] [Job 2767] Stopping unresponsive job.
   E [10/Nov/2016:09:26:06 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
  CurrentDesktop: Unity
  Date: Thu Nov 10 11:37:50 2016
  Lpstat:
   device for Brother-MFC-8600: 
ipps://Bryces-Mac-mini.local:631/printers/Brother_MFC_8600
   device for MFC-8600: usb://Brother/MFC-8600
   device for MFCJ985DW: dnssd://Brother%20MFC-J985DW._ipp._tcp.local/
  MachineType: Supermicro X8SAX
  Papersize: letter
  PpdFiles:
   MFCJ985DW: Brother MFC-J985DW CUPS
   MFC-8

[Touch-packages] [Bug 1158432] Re: On graphical login, Network Manager window gets in the way

2016-07-14 Thread Bryce Nesbitt
Still relevant in 16.04 LTS.

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

Title:
  On graphical login, Network Manager window gets in the way

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  New in 13.04, on a laptop with wifi (in addition to being wired), when
  the login gui comes up on boot-up, I can no longer simply type in my
  password to log in.

  This is because a wifi authentication window pops up, asking for a
  password for my wifi connection.  Worse, it does not let me get the
  focus back to the log in screen or anywhere else: I have to explicitly
  click "cancel ".

  After I log in, the wifi password is not needed, since the Manager has
  stored it and connects automatically, using its stored password.

  It may be nice to be able to access the network before logging in, but
  that option should not interrupt my log-in process, and certainly not
  block it!

  Moreover, given that my machine is also connected to wired ethernet
  (by DHCP, no password), it is hardly a high priority to get wifi
  going.

  This problem exists on both of my laptops (very different hardware).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  ApportVersion: 2.9.2-0ubuntu1
  Architecture: amd64
  Date: Thu Mar 21 13:47:50 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-03-18 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
  IpRoute:
   default via 132.206.112.1 dev eth0  proto static 
   132.206.112.0/26 dev eth0  proto kernel  scope link  src 132.206.112.10  
metric 1 
   142.157.168.0/23 dev wlan0  proto kernel  scope link  src 142.157.168.8  
metric 9 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-03-19T18:52:07.457464
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   IHSP  3985ff88-5770-4938-8133-23b8ded92641   
802-3-ethernet1363888105   Thu 21 Mar 2013 01:48:25 PM EDTyes   
no /org/freedesktop/NetworkManager/Settings/2
   DHCP  aec2f3e7-cdaa-46ff-b51d-401084613817   
802-3-ethernet0never  no
no /org/freedesktop/NetworkManager/Settings/1
   wpa.mcgill.ca 4ce783b2-6946-417e-ac7c-eb6984d01f15   
802-11-wireless   1363888105   Thu 21 Mar 2013 01:48:25 PM EDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

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

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


[Touch-packages] [Bug 1503930] Re: zeitgeist-datahub "Freezing of tasks failed after 20.005 seconds"

2015-12-24 Thread Bryce Nesbitt
See also https://bugs.launchpad.net/ubuntu/+source/zeitgeist-
datahub/+bug/792229

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

Title:
  zeitgeist-datahub "Freezing of tasks failed after 20.005 seconds"

Status in zeitgeist package in Ubuntu:
  New

Bug description:
  My system no longer properly goes to sleep.  The logs are filled with
  variants of:

  [114631.282599] PM: Syncing filesystems ... done.
  [114631.328752] PM: Preparing system for mem sleep
  [114631.896631] Freezing user space processes ... 
  [114651.913199] Freezing of tasks failed after 20.005 seconds (1 tasks 
refusing to freeze, wq_busy=0):
  [114651.913321] zeitgeist-datah D 88033fc33180 0  4659   4142 
0x0004
  [114651.913325]  8802d6a05aa8 0086 8802f3c4c800 
8802d6a05fd8
  [114651.913328]  00013180 00013180 8802f3c4c800 
88032a3bbe28
  [114651.913330]  8800b0366000 8802d6a05ad0 88032a3bbf08 
88032a3bbe28
  [114651.91] Call Trace:
  [114651.913340]  [] schedule+0x29/0x70
  [114651.913345]  [] __fuse_request_send+0x115/0x280
  [114651.913350]  [] ? prepare_to_wait_event+0x100/0x100
  [114651.913352]  [] fuse_request_send+0x12/0x20
  [114651.913355]  [] fuse_dentry_revalidate+0x194/0x350
  [114651.913360]  [] lookup_fast+0x26d/0x2c0
  [114651.913363]  [] link_path_walk+0x1a3/0x880
  [114651.913365]  [] ? enqueue_entity+0x2ad/0xbb0
  [114651.913368]  [] path_lookupat+0x5b/0x790
  [114651.913372]  [] ? ttwu_do_wakeup+0x19/0xc0
  [114651.913376]  [] ? kmem_cache_alloc+0x35/0x1e0
  [114651.913378]  [] ? getname_flags+0x4f/0x190
  [114651.913381]  [] filename_lookup+0x2b/0xc0
  [114651.913384]  [] user_path_at_empty+0x54/0x90
  [114651.913388]  [] ? from_kgid_munged+0x12/0x20
  [114651.913390]  [] ? cp_new_stat+0x13d/0x160
  [114651.913393]  [] user_path_at+0x11/0x20
  [114651.913395]  [] vfs_fstatat+0x50/0xa0
  [114651.913397]  [] SYSC_newstat+0x1f/0x40
  [114651.913400]  [] SyS_newstat+0xe/0x10
  [114651.913403]  [] system_call_fastpath+0x1a/0x1f
  [114651.913432] 
  [114651.913433] Restarting tasks ... done.

  and the occasional

  [46466.515860] INFO: task zeitgeist-datah:4659 blocked for more than 120 
seconds.
  [46466.515868]   Tainted: P   OX 3.13.0-63-generic #103-Ubuntu
  [46466.515870] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [46466.515873] zeitgeist-datah D 88033fc33180 0  4659   4142 
0x0004
  [46466.515880]  8802d6a05aa8 0086 8802f3c4c800 
8802d6a05fd8
  [46466.515886]  00013180 00013180 8802f3c4c800 
88032a3bbe28
  [46466.515890]  8800b0366000 8802d6a05ad0 88032a3bbf08 
88032a3bbe28
  [46466.515895] Call Trace:
  [46466.515906]  [] schedule+0x29/0x70
  [46466.515913]  [] __fuse_request_send+0x115/0x280
  [46466.515922]  [] ? prepare_to_wait_event+0x100/0x100
  [46466.515926]  [] fuse_request_send+0x12/0x20
  [46466.515932]  [] fuse_dentry_revalidate+0x194/0x350
  [46466.515939]  [] lookup_fast+0x26d/0x2c0
  [46466.515944]  [] link_path_walk+0x1a3/0x880
  [46466.515949]  [] ? enqueue_entity+0x2ad/0xbb0
  [46466.515954]  [] path_lookupat+0x5b/0x790
  [46466.515960]  [] ? ttwu_do_wakeup+0x19/0xc0
  [46466.515966]  [] ? kmem_cache_alloc+0x35/0x1e0
  [46466.515971]  [] ? getname_flags+0x4f/0x190
  [46466.515976]  [] filename_lookup+0x2b/0xc0
  [46466.515981]  [] user_path_at_empty+0x54/0x90
  [46466.515988]  [] ? from_kgid_munged+0x12/0x20
  [46466.515992]  [] ? cp_new_stat+0x13d/0x160
  [46466.515997]  [] user_path_at+0x11/0x20
  [46466.516001]  [] vfs_fstatat+0x50/0xa0
  [46466.516005]  [] SYSC_newstat+0x1f/0x40
  [46466.516010]  [] SyS_newstat+0xe/0x10
  [46466.516015]  [] system_call_fastpath+0x1a/0x1f

  6831104 Oct  6 16:57 activity.sqlite
  3271680 Sep 17  2014 activity.sqlite.bck
  163840 Oct  7 17:15 activity.sqlite-shm
  288943064 Oct  7 17:15 activity.sqlite-wal
  322 Nov 10  2013 datasources.pickle
  4096 Oct  7 14:03 fts.index

  Going to settings and selecting "Clear usage data" and "All time" resulted in 
no change of file sizes
  and no improvement to suspend.  Turning "record file and usage" to "off" left 
the zeitgeist-datahub running.

  A "kill -9" of the datahub process results in no change (the task does
  not die)

  # ps -F 4659
  UIDPID  PPID  CSZ   RSS PSR STIME TTY  STAT   TIME CMD
  xx  4659  4142  0 105023 11872  1 Oct06 ?D  0:33 
zeitgeist-datahub


  See also
  http://linuxaria.com/howto/how-to-remove-zeitgeist-in-ubuntu-and-why

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

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

[Touch-packages] [Bug 1503930] [NEW] zeitgeist-datahub "Freezing of tasks failed after 20.005 seconds"

2015-10-07 Thread Bryce Nesbitt
Public bug reported:

My system no longer properly goes to sleep.  The logs are filled with
variants of:

[114631.282599] PM: Syncing filesystems ... done.
[114631.328752] PM: Preparing system for mem sleep
[114631.896631] Freezing user space processes ... 
[114651.913199] Freezing of tasks failed after 20.005 seconds (1 tasks refusing 
to freeze, wq_busy=0):
[114651.913321] zeitgeist-datah D 88033fc33180 0  4659   4142 0x0004
[114651.913325]  8802d6a05aa8 0086 8802f3c4c800 
8802d6a05fd8
[114651.913328]  00013180 00013180 8802f3c4c800 
88032a3bbe28
[114651.913330]  8800b0366000 8802d6a05ad0 88032a3bbf08 
88032a3bbe28
[114651.91] Call Trace:
[114651.913340]  [] schedule+0x29/0x70
[114651.913345]  [] __fuse_request_send+0x115/0x280
[114651.913350]  [] ? prepare_to_wait_event+0x100/0x100
[114651.913352]  [] fuse_request_send+0x12/0x20
[114651.913355]  [] fuse_dentry_revalidate+0x194/0x350
[114651.913360]  [] lookup_fast+0x26d/0x2c0
[114651.913363]  [] link_path_walk+0x1a3/0x880
[114651.913365]  [] ? enqueue_entity+0x2ad/0xbb0
[114651.913368]  [] path_lookupat+0x5b/0x790
[114651.913372]  [] ? ttwu_do_wakeup+0x19/0xc0
[114651.913376]  [] ? kmem_cache_alloc+0x35/0x1e0
[114651.913378]  [] ? getname_flags+0x4f/0x190
[114651.913381]  [] filename_lookup+0x2b/0xc0
[114651.913384]  [] user_path_at_empty+0x54/0x90
[114651.913388]  [] ? from_kgid_munged+0x12/0x20
[114651.913390]  [] ? cp_new_stat+0x13d/0x160
[114651.913393]  [] user_path_at+0x11/0x20
[114651.913395]  [] vfs_fstatat+0x50/0xa0
[114651.913397]  [] SYSC_newstat+0x1f/0x40
[114651.913400]  [] SyS_newstat+0xe/0x10
[114651.913403]  [] system_call_fastpath+0x1a/0x1f
[114651.913432] 
[114651.913433] Restarting tasks ... done.

and the occasional

[46466.515860] INFO: task zeitgeist-datah:4659 blocked for more than 120 
seconds.
[46466.515868]   Tainted: P   OX 3.13.0-63-generic #103-Ubuntu
[46466.515870] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[46466.515873] zeitgeist-datah D 88033fc33180 0  4659   4142 0x0004
[46466.515880]  8802d6a05aa8 0086 8802f3c4c800 
8802d6a05fd8
[46466.515886]  00013180 00013180 8802f3c4c800 
88032a3bbe28
[46466.515890]  8800b0366000 8802d6a05ad0 88032a3bbf08 
88032a3bbe28
[46466.515895] Call Trace:
[46466.515906]  [] schedule+0x29/0x70
[46466.515913]  [] __fuse_request_send+0x115/0x280
[46466.515922]  [] ? prepare_to_wait_event+0x100/0x100
[46466.515926]  [] fuse_request_send+0x12/0x20
[46466.515932]  [] fuse_dentry_revalidate+0x194/0x350
[46466.515939]  [] lookup_fast+0x26d/0x2c0
[46466.515944]  [] link_path_walk+0x1a3/0x880
[46466.515949]  [] ? enqueue_entity+0x2ad/0xbb0
[46466.515954]  [] path_lookupat+0x5b/0x790
[46466.515960]  [] ? ttwu_do_wakeup+0x19/0xc0
[46466.515966]  [] ? kmem_cache_alloc+0x35/0x1e0
[46466.515971]  [] ? getname_flags+0x4f/0x190
[46466.515976]  [] filename_lookup+0x2b/0xc0
[46466.515981]  [] user_path_at_empty+0x54/0x90
[46466.515988]  [] ? from_kgid_munged+0x12/0x20
[46466.515992]  [] ? cp_new_stat+0x13d/0x160
[46466.515997]  [] user_path_at+0x11/0x20
[46466.516001]  [] vfs_fstatat+0x50/0xa0
[46466.516005]  [] SYSC_newstat+0x1f/0x40
[46466.516010]  [] SyS_newstat+0xe/0x10
[46466.516015]  [] system_call_fastpath+0x1a/0x1f

6831104 Oct  6 16:57 activity.sqlite
3271680 Sep 17  2014 activity.sqlite.bck
163840 Oct  7 17:15 activity.sqlite-shm
288943064 Oct  7 17:15 activity.sqlite-wal
322 Nov 10  2013 datasources.pickle
4096 Oct  7 14:03 fts.index

Going to settings and selecting "Clear usage data" and "All time" resulted in 
no change of file sizes
and no improvement to suspend.  Turning "record file and usage" to "off" left 
the zeitgeist-datahub running.

A "kill -9" of the datahub process results in no change (the task does
not die)

# ps -F 4659
UIDPID  PPID  CSZ   RSS PSR STIME TTY  STAT   TIME CMD
xx  4659  4142  0 105023 11872  1 Oct06 ?D  0:33 
zeitgeist-datahub


See also
http://linuxaria.com/howto/how-to-remove-zeitgeist-in-ubuntu-and-why

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

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

Title:
  zeitgeist-datahub "Freezing of tasks failed after 20.005 seconds"

Status in zeitgeist package in Ubuntu:
  New

Bug description:
  My system no longer properly goes to sleep.  The logs are filled with
  variants of:

  [114631.282599] PM: Syncing filesystems ... done.
  [114631.328752] PM: Preparing system for mem sleep
  [114631.896631] Freezing user space processes ... 
  [114651.913199] Freezing of tasks failed after 20.005 seconds (1 tasks 
refusing to freeze, wq_busy=0):
  [114651.913321] zeitgeist-datah D 88033fc33180 0  4659   4142 
0x0004
  [114651.9133

[Touch-packages] [Bug 1123347] Re: Zeitgeist using too much RAM memory

2015-10-07 Thread Bryce Nesbitt
Confirmed: 1GB of memory.  An easy way to disable zeitgeist would be
nice.

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

Title:
  Zeitgeist using too much RAM memory

Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  zeitgeist is using 30% of 8GB of RAM. Seems like way too much.

PID TTY  STAT   TIME  MAJFL   TRS   DRS   RSS %MEM COMMAND
   2245 ?Sl 0:21  2   312 2719715 2485852 30.5 
/usr/lib/zeitgeist/zeitgeist-fts

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: zeitgeist-core 0.9.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
  Uname: Linux 3.8.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 12 12:49:49 2013
  ExecutablePath: /usr/lib/zeitgeist/zeitgeist-fts
  InstallationDate: Installed on 2012-04-07 (311 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: zeitgeist
  UpgradeStatus: Upgraded to raring on 2013-02-11 (1 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-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 (Ubuntu 13.10, 14.04)

2014-09-24 Thread Bryce Nesbitt
'killall unity-panel-service' brings it back temporarily, on Ubuntu
14.04LTS

-- 
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
  (Ubuntu 13.10, 14.04)

Status in One Hundred Papercuts:
  Triaged
Status in The Date and Time Indicator:
  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 1115466] Re: _sysconfigdata_nd.py missing in /usr/lib/python2.7/

2014-09-24 Thread Bryce Nesbitt
See also the pip issues, which I found to be at the
heart of virtualenv issues 
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1373254

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

Title:
  _sysconfigdata_nd.py missing in /usr/lib/python2.7/

Status in “python2.7” package in Ubuntu:
  Invalid
Status in “virtualenv” package in Ubuntu:
  Invalid

Bug description:
  The file is present on Debian.
  This is causing virtualenv to fail, and probably other modules too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1115466/+subscriptions

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