[Touch-packages] [Bug 1820030] [NEW] My Ubuntu 18.04 GUI seems frozen

[Thomas A. F. Thorne]

Public bug reported:

This will possibly be a duplicate of Bug #1820028 or Bug #1820028

I was trying to report a frozen GUI over SSH. This is the second report
that apport-cli generated when I ran it with lightdm as the target
package.

The symptoms I see are that I started running a go test last night and
my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless
mouse or keyboard to move anything on the display and the time shown on
the clock matches when things froze last night.

Before I made the report I looked for any process using high amounts of
CUP with top and htop but spotted none. I tried to local a SIGTERM the
go test process but that made no difference.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Mar 14 09:09:36 2019
InstallationDate: Installed on 2017-11-16 (482 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 LANG=en_GB.UTF-8
 TERM=xterm
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to bionic on 2018-07-27 (229 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  My Ubuntu 18.04 GUI seems frozen

Status in lightdm package in Ubuntu:
  New

Bug description:
  This will possibly be a duplicate of Bug #1820028 or Bug #1820028

  I was trying to report a frozen GUI over SSH. This is the second
  report that apport-cli generated when I ran it with lightdm as the
  target package.

  The symptoms I see are that I started running a go test last night and
  my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless
  mouse or keyboard to move anything on the display and the time shown
  on the clock matches when things froze last night.

  Before I made the report I looked for any process using high amounts
  of CUP with top and htop but spotted none. I tried to local a SIGTERM
  the go test process but that made no difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Mar 14 09:09:36 2019
  InstallationDate: Installed on 2017-11-16 (482 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANG=en_GB.UTF-8
   TERM=xterm
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (229 days ago)

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

-- 
Mailing list: https://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 1820031] [NEW] My Ubuntu 18.04 GUI seems frozen

[Thomas A. F. Thorne]

Public bug reported:

This will possibly be a duplicate of Bug #1820028 or Bug #1820029 or Bug
#1820030

I was trying to report a frozen GUI over SSH. This is the second report
that apport-cli generated when I ran it with xorg as the target package.
I made three four reports to see if different diagnostics were
geneereated as Ihave no way of knowing what is causing the lock up at
present.

The symptoms I see are that I started running a go test last night and
my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless
mouse or keyboard to move anything on the display and the time shown on
the clock matches when things froze last night.

Before I made the report I looked for any process using high amounts of
CUP with top and htop but spotted none. I tried to local a SIGTERM the
go test process but that made no difference.



I shall attempt to restart my desktop service

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Mar 14 09:12:51 2019
DistUpgraded: 2018-07-27 11:19:59,510 DEBUG failed to SystemUnLock() (E:Not 
locked)
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694]
InstallationDate: Installed on 2017-11-16 (482 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=473dc1b9-3a5c-4f95-8cc0-e3b0f628ca41 ro quiet splash vt.handoff=1
SourcePackage: xorg
UnitySupportTest:
 Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with 
exit code 5: PuTTY X11 proxy: unable to connect to forwarded X server: Network 
error: Connection refused
 Error: unable to open display
UpgradeStatus: Upgraded to bionic on 2018-07-27 (229 days ago)
dmi.bios.date: 09/27/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0811
dmi.board.asset.tag: Default string
dmi.board.name: STRIX H270F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0811:bd09/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Mar 12 13:46:44 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  My Ubuntu 18.04 GUI seems frozen

Status in xorg package in Ubuntu:
  New

Bug description:
  This will possibly be a duplicate of Bug #1820028 or Bug #1820029 or
  Bug #1820030

  I was trying to report a frozen GUI over SSH. This is the second
  report that apport-cli generated when I ran it with xorg as the target
  package.  I made three four reports to see if different diagnostics
  were geneereated as Ihave no way of knowing what is causing the lock
  up at present.

  The symptoms I see are that I started running a go test last night and
  my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless
  mouse or keyboard to move anything on the display and the time shown
  on the clock matches when things froze last night.

  Before I made the report I looked for any process using high amounts
  of CUP with top and htop but spotted none. I tried to local a SIGTERM
  the go 

[Touch-packages] [Bug 1748844] Re: hud-service crash with qmessageLogger::fatal() reported at login

[Thomas A. F. Thorne]

Happened again today.  Raised #1760792 this morning to see if the trace
will work.  If it does not I shall try adding more -dev packages to see
if the backtrace can be brought about.

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

Status in hud package in Ubuntu:
  New

Bug description:
  I start up my Ubuntu 16.04 machine and immediately after loginning in
  to the GUI I get a crash report about the hub-service.  Often this is
  followed by one or two other reports but not today.

  Today I followed the instructions on: 
https://help.ubuntu.com/community/ReportingBugs 
  `enabled=1` was already set in /etc/default/apport but I had not set `# 
'problem_types': ['Bug', 'Package'],` in /etc/apport/crashdb.conf until this 
morning.  This had the effect of a bug report appearing to be sent in the 
background but no launchpad page opening.  After setting both of the above I 
did `ubuntu-bug hud` on the command line to generate this report.  

  This PC was a fresh install a few months ago.  As far as I can recall
  it has been generating the crash report message for most of that time.

  It would be nice if I could at least silence the error.  Ideally I
  would like to fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 12 09:11:35 2018
  InstallationDate: Installed on 2017-11-16 (87 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

-- 
Mailing list: https://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 1748844] Re: hud-service crash with qmessageLogger::fatal() reported at login

[Thomas A. F. Thorne]

Occurred again today.  New report raised at +bug1756839

I raised a new report as this bug seems to happen as a pair with another
bug.  The original pair that went with this bug (+bug1753393) asked me
to raise a new bug to see if better diagnostics were included.  I have
done so and created +bug1756835.  +bug1756839 is the new copy of this
bug, created from the same login as +bug1756835

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

Status in hud package in Ubuntu:
  New

Bug description:
  I start up my Ubuntu 16.04 machine and immediately after loginning in
  to the GUI I get a crash report about the hub-service.  Often this is
  followed by one or two other reports but not today.

  Today I followed the instructions on: 
https://help.ubuntu.com/community/ReportingBugs 
  `enabled=1` was already set in /etc/default/apport but I had not set `# 
'problem_types': ['Bug', 'Package'],` in /etc/apport/crashdb.conf until this 
morning.  This had the effect of a bug report appearing to be sent in the 
background but no launchpad page opening.  After setting both of the above I 
did `ubuntu-bug hud` on the command line to generate this report.  

  This PC was a fresh install a few months ago.  As far as I can recall
  it has been generating the crash report message for most of that time.

  It would be nice if I could at least silence the error.  Ideally I
  would like to fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 12 09:11:35 2018
  InstallationDate: Installed on 2017-11-16 (87 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

-- 
Mailing list: https://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 1753393] Re: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

[Thomas A. F. Thorne]

Changing report to Public so that others can see it.

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

Title:
  window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

Status in hud package in Ubuntu:
  Invalid

Bug description:
  After powering on my PC and logging in I was presented with two
  automated error reporting windows.  The first led me to +bug1748844
  the second prompted me to create a new error reporting message.  By
  the time this second report happened I had Google Chrome and Synergy
  running.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar  5 08:20:42 2018
  ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  InstallationDate: Installed on 2017-11-16 (108 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: hud
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   QObjectPrivate::QObjectPrivate(int) () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusAbstractInterface::QDBusAbstractInterface(QString const&, QString 
const&, char const*, QDBusConnection const&, QObject*) () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusConnectionInterface::QDBusConnectionInterface(QDBusConnection const&, 
QObject*) () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  Title: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

-- 
Mailing list: https://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 1753393] Re: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

[Thomas A. F. Thorne]

Would +bug1756835 work better as a link?

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

Title:
  window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

Status in hud package in Ubuntu:
  Invalid

Bug description:
  After powering on my PC and logging in I was presented with two
  automated error reporting windows.  The first led me to +bug1748844
  the second prompted me to create a new error reporting message.  By
  the time this second report happened I had Google Chrome and Synergy
  running.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar  5 08:20:42 2018
  ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  InstallationDate: Installed on 2017-11-16 (108 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: hud
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   QObjectPrivate::QObjectPrivate(int) () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusAbstractInterface::QDBusAbstractInterface(QString const&, QString 
const&, char const*, QDBusConnection const&, QObject*) () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusConnectionInterface::QDBusConnectionInterface(QDBusConnection const&, 
QObject*) () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  Title: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

-- 
Mailing list: https://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 1753393] Re: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

[Thomas A. F. Thorne]

The problem happened again this morning.

As requested above I have filed a new report at #1756835.  Hopefully
this will include more useful diagnostic information.

** Information type changed from Private to Public

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

Title:
  window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()

Status in hud package in Ubuntu:
  Invalid

Bug description:
  After powering on my PC and logging in I was presented with two
  automated error reporting windows.  The first led me to +bug1748844
  the second prompted me to create a new error reporting message.  By
  the time this second report happened I had Google Chrome and Synergy
  running.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar  5 08:20:42 2018
  ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  InstallationDate: Installed on 2017-11-16 (108 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: hud
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   QObjectPrivate::QObjectPrivate(int) () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusAbstractInterface::QDBusAbstractInterface(QString const&, QString 
const&, char const*, QDBusConnection const&, QObject*) () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusConnectionInterface::QDBusConnectionInterface(QDBusConnection const&, 
QObject*) () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  Title: window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

-- 
Mailing list: https://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 1748844] Re: hud-service crash with qmessageLogger::fatal() reported at login

[Thomas A. F. Thorne]

Seems simple enough to recreate this each time I restart the machine.

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

Status in hud package in Ubuntu:
  New

Bug description:
  I start up my Ubuntu 16.04 machine and immediately after loginning in
  to the GUI I get a crash report about the hub-service.  Often this is
  followed by one or two other reports but not today.

  Today I followed the instructions on: 
https://help.ubuntu.com/community/ReportingBugs 
  `enabled=1` was already set in /etc/default/apport but I had not set `# 
'problem_types': ['Bug', 'Package'],` in /etc/apport/crashdb.conf until this 
morning.  This had the effect of a bug report appearing to be sent in the 
background but no launchpad page opening.  After setting both of the above I 
did `ubuntu-bug hud` on the command line to generate this report.  

  This PC was a fresh install a few months ago.  As far as I can recall
  it has been generating the crash report message for most of that time.

  It would be nice if I could at least silence the error.  Ideally I
  would like to fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 12 09:11:35 2018
  InstallationDate: Installed on 2017-11-16 (87 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

-- 
Mailing list: https://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 1748844] Re: hud-service crash with qmessageLogger::fatal() reported at login

[Thomas A. F. Thorne]

This morning the second automated bug report prompted me to create
+bug1753393

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

Status in hud package in Ubuntu:
  New

Bug description:
  I start up my Ubuntu 16.04 machine and immediately after loginning in
  to the GUI I get a crash report about the hub-service.  Often this is
  followed by one or two other reports but not today.

  Today I followed the instructions on: 
https://help.ubuntu.com/community/ReportingBugs 
  `enabled=1` was already set in /etc/default/apport but I had not set `# 
'problem_types': ['Bug', 'Package'],` in /etc/apport/crashdb.conf until this 
morning.  This had the effect of a bug report appearing to be sent in the 
background but no launchpad page opening.  After setting both of the above I 
did `ubuntu-bug hud` on the command line to generate this report.  

  This PC was a fresh install a few months ago.  As far as I can recall
  it has been generating the crash report message for most of that time.

  It would be nice if I could at least silence the error.  Ideally I
  would like to fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 12 09:11:35 2018
  InstallationDate: Installed on 2017-11-16 (87 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

-- 
Mailing list: https://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 1748844] Re: hud-service crash with qmessageLogger::fatal() reported at login

[Thomas A. F. Thorne]

Occurred again this morning and an automated bug report brought me back
here.

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

Status in hud package in Ubuntu:
  New

Bug description:
  I start up my Ubuntu 16.04 machine and immediately after loginning in
  to the GUI I get a crash report about the hub-service.  Often this is
  followed by one or two other reports but not today.

  Today I followed the instructions on: 
https://help.ubuntu.com/community/ReportingBugs 
  `enabled=1` was already set in /etc/default/apport but I had not set `# 
'problem_types': ['Bug', 'Package'],` in /etc/apport/crashdb.conf until this 
morning.  This had the effect of a bug report appearing to be sent in the 
background but no launchpad page opening.  After setting both of the above I 
did `ubuntu-bug hud` on the command line to generate this report.  

  This PC was a fresh install a few months ago.  As far as I can recall
  it has been generating the crash report message for most of that time.

  It would be nice if I could at least silence the error.  Ideally I
  would like to fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 12 09:11:35 2018
  InstallationDate: Installed on 2017-11-16 (87 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

-- 
Mailing list: https://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 1748844] [NEW] hud-service crash with qmessageLogger::fatal() reported at login

[Thomas A. F. Thorne]

Public bug reported:

I start up my Ubuntu 16.04 machine and immediately after loginning in to
the GUI I get a crash report about the hub-service.  Often this is
followed by one or two other reports but not today.

Today I followed the instructions on: 
https://help.ubuntu.com/community/ReportingBugs 
`enabled=1` was already set in /etc/default/apport but I had not set `# 
'problem_types': ['Bug', 'Package'],` in /etc/apport/crashdb.conf until this 
morning.  This had the effect of a bug report appearing to be sent in the 
background but no launchpad page opening.  After setting both of the above I 
did `ubuntu-bug hud` on the command line to generate this report.  

This PC was a fresh install a few months ago.  As far as I can recall it
has been generating the crash report message for most of that time.

It would be nice if I could at least silence the error.  Ideally I would
like to fix the issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: hud 14.10+16.04.20160415-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb 12 09:11:35 2018
InstallationDate: Installed on 2017-11-16 (87 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: hud
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.hud.log:
 This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
 in "".
 
 Reinstalling the application may fix this problem.

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

Status in hud package in Ubuntu:
  New

Bug description:
  I start up my Ubuntu 16.04 machine and immediately after loginning in
  to the GUI I get a crash report about the hub-service.  Often this is
  followed by one or two other reports but not today.

  Today I followed the instructions on: 
https://help.ubuntu.com/community/ReportingBugs 
  `enabled=1` was already set in /etc/default/apport but I had not set `# 
'problem_types': ['Bug', 'Package'],` in /etc/apport/crashdb.conf until this 
morning.  This had the effect of a bug report appearing to be sent in the 
background but no launchpad page opening.  After setting both of the above I 
did `ubuntu-bug hud` on the command line to generate this report.  

  This PC was a fresh install a few months ago.  As far as I can recall
  it has been generating the crash report message for most of that time.

  It would be nice if I could at least silence the error.  Ideally I
  would like to fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 12 09:11:35 2018
  InstallationDate: Installed on 2017-11-16 (87 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

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

-- 
Mailing list: https://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 1713004] Re: Temporary files left under /var/tmp by mkinitramfs

[Thomas A. F. Thorne]

Looks like this bug is related to bug #1597661 and bug #1515513 although
both of those point the upgrade process being the prompt for a failing
run of the initramfs-tools.

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

Title:
  Temporary files left under /var/tmp by mkinitramfs

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  I recently ran out of disk space on my / mount.  While looking for
  what consumed the disk I noticed a large number (130) of directories
  with names / paths beginning /var/tmp/mkinitramfs.  These directories
  seem to be either ~103 MB or ~927 MB in size.  Many of these files are
  months old, some are almost a year.

  Having had a quick look about for an explanation as to why these files
  are here and found Debian Bug #814345.  That explains that temporary
  files are left behind by the initramfs-tools if something fails in the
  process.  If this is the cause of my files then updating the Ubuntu
  package to version 0.123 should resolve this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 25 09:40:41 2017
  InstallationDate: Installed on 2015-03-12 (896 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1713004] [NEW] Temporary files left under /var/tmp by mkinitramfs

[Thomas A. F. Thorne]

Public bug reported:

I recently ran out of disk space on my / mount.  While looking for what
consumed the disk I noticed a large number (130) of directories with
names / paths beginning /var/tmp/mkinitramfs.  These directories seem to
be either ~103 MB or ~927 MB in size.  Many of these files are months
old, some are almost a year.

Having had a quick look about for an explanation as to why these files
are here and found Debian Bug #814345.  That explains that temporary
files are left behind by the initramfs-tools if something fails in the
process.  If this is the cause of my files then updating the Ubuntu
package to version 0.123 should resolve this issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.8
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Aug 25 09:40:41 2017
InstallationDate: Installed on 2015-03-12 (896 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: initramfs-tools (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug xenial

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

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

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

Title:
  Temporary files left under /var/tmp by mkinitramfs

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  I recently ran out of disk space on my / mount.  While looking for
  what consumed the disk I noticed a large number (130) of directories
  with names / paths beginning /var/tmp/mkinitramfs.  These directories
  seem to be either ~103 MB or ~927 MB in size.  Many of these files are
  months old, some are almost a year.

  Having had a quick look about for an explanation as to why these files
  are here and found Debian Bug #814345.  That explains that temporary
  files are left behind by the initramfs-tools if something fails in the
  process.  If this is the cause of my files then updating the Ubuntu
  package to version 0.123 should resolve this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 25 09:40:41 2017
  InstallationDate: Installed on 2015-03-12 (896 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk

[Thomas A. F. Thorne]

Hi Christian, 
A more careful read through of the instructions you link to and I have spotted 
the required tag.  Now added that as requested.  I'll try to get the other two 
tested using lsc tomorrow.  
Tag now added.  

** Tags added: verification-done-xenial

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

Status in One Hundred Papercuts:
  Triaged
Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Trusty:
  Fix Committed
Status in logrotate source package in Xenial:
  Fix Committed
Status in logrotate source package in Yakkety:
  Fix Committed
Status in logrotate source package in Zesty:
  Fix Released
Status in logrotate package in Debian:
  Fix Released

Bug description:
  [Impact]

  Logrotate fails to rotate a log and then will continue to fail to
  rotate it until manual intervention takes place. If messaging has not
  been configured on the system there will be no warning issued to the
  user. The log will grow day by day until a user intervenes or the
  drive that the log is stored on is full.

  Very large log files can make it more difficult to find useful data.
  Full drives make the rest of the system fail to operate. Backporting a
  fix would prevent drives filling up on stable releases.

  [Test Case]

  Go to your logs area (/var/logs) and create a file with a name ending
  .2, as would be created part way through the logrotate process. So if
  you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz,
  /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your
  subsequent log rotate runs will fail.

  [Regression Potential]

  - I'd hope the potential is low as it only triggers under certain conditions 
that are special (target filename in the way).
  - So far in those conditions it failed to rotate
  - Yet If despite my hope there still manifests an issue I'd expect it could 
be renaming files it should not, so people would end up "missing" their logs - 
the good thing is that this is a rename, so they should find it at different 
names.
  - Another thing I consider possible is that some unexpected conditions cause 
e.g. a crash in the changed code, in that case the logs are not rotated, but 
since there is no unlink the logs will still exist.
  - Therefore I consider the Potential low enough to consider the fix.

  [Other Info]
  n/a

  ---

  Good afternoon.
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/syslog.1.gz: File exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  Different file, different machine but a very similar error message.

  Checking on the syslog file I can see that it better fits with other reports 
on this bug as my duplicated .1 files has a corresponding .1.gz file.
  manager@trac:/var/log$ ll syslog*
  -rw-r- 1 syslog adm 918492 Oct  5 10:30 syslog
  -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
  -rw-r- 1 syslog adm  20638 Oct  2 02:01 syslog.1.gz
  -rw-r- 1 syslog adm  41989 Sep 30 02:00 syslog.2.gz
  -rw-r- 1 syslog adm  18654 Sep 28 02:01 syslog.3.gz
  

[Touch-packages] [Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk

[Thomas A. F. Thorne]

Looks to me like everything worked fine overnight.
$ ls -l /var/log/syslog*
-rw-r- 1 syslog adm   587351 Apr 26 12:10 /var/log/syslog
-rw-r- 1 syslog adm  1824727 Apr 26 07:38 /var/log/syslog.1
-rw-r--r-- 1 root   root   0 Apr 25 15:48 /var/log/syslog.2
-rw-r- 1 syslog adm37783 Apr 25 07:35 /var/log/syslog.2.gz
-rw-r- 1 syslog adm26955 Apr 24 07:35 /var/log/syslog.3.gz
-rw-r- 1 syslog adm26695 Apr 23 07:35 /var/log/syslog.4.gz
-rw-r- 1 syslog adm31307 Apr 22 07:35 /var/log/syslog.5.gz
-rw-r- 1 syslog adm32909 Apr 21 07:35 /var/log/syslog.6.gz
-rw-r- 1 syslog adm39182 Apr 20 07:35 /var/log/syslog.7.gz

The presence of the inconveniently named file looks to have been ignored
and the log rotations continued unabated.

> change the tag from verification-needed to verification-done

I have only verified this on Xenia so far.  I think that means I leave
the tags alone for now right?

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

Status in One Hundred Papercuts:
  Triaged
Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Trusty:
  Fix Committed
Status in logrotate source package in Xenial:
  Fix Committed
Status in logrotate source package in Yakkety:
  Fix Committed
Status in logrotate source package in Zesty:
  Fix Released
Status in logrotate package in Debian:
  Fix Released

Bug description:
  [Impact]

  Logrotate fails to rotate a log and then will continue to fail to
  rotate it until manual intervention takes place. If messaging has not
  been configured on the system there will be no warning issued to the
  user. The log will grow day by day until a user intervenes or the
  drive that the log is stored on is full.

  Very large log files can make it more difficult to find useful data.
  Full drives make the rest of the system fail to operate. Backporting a
  fix would prevent drives filling up on stable releases.

  [Test Case]

  Go to your logs area (/var/logs) and create a file with a name ending
  .2, as would be created part way through the logrotate process. So if
  you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz,
  /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your
  subsequent log rotate runs will fail.

  [Regression Potential]

  - I'd hope the potential is low as it only triggers under certain conditions 
that are special (target filename in the way).
  - So far in those conditions it failed to rotate
  - Yet If despite my hope there still manifests an issue I'd expect it could 
be renaming files it should not, so people would end up "missing" their logs - 
the good thing is that this is a rename, so they should find it at different 
names.
  - Another thing I consider possible is that some unexpected conditions cause 
e.g. a crash in the changed code, in that case the logs are not rotated, but 
since there is no unlink the logs will still exist.
  - Therefore I consider the Potential low enough to consider the fix.

  [Other Info]
  n/a

  ---

  Good afternoon.
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  >
  > 

[Touch-packages] [Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk

[Thomas A. F. Thorne]

Running through on Xenial.

$ sudo apt-get install logrotate/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '3.8.7-2ubuntu2.16.04.1' (Ubuntu:16.04/xenial-proposed 
[amd64]) for 'logrotate'
The following packages will be upgraded:
  logrotate
1 to upgrade, 0 to newly install, 0 to remove and 22 not to upgrade.
Need to get 37.8 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 logrotate 
amd64 3.8.7-2ubuntu2.16.04.1 [37.8 kB]
Fetched 37.8 kB in 0s (639 kB/s) 
(Reading database ... 889765 files and directories currently installed.)
Preparing to unpack .../logrotate_3.8.7-2ubuntu2.16.04.1_amd64.deb ...
Unpacking logrotate (3.8.7-2ubuntu2.16.04.1) over (3.8.7-2ubuntu2) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up logrotate (3.8.7-2ubuntu2.16.04.1) ...
$ cd /var/log/
$ sudo touch syslog.2
$ ls -l syslog*
-rw-r- 1 syslog adm  193861 Apr 25 15:48 syslog
-rw-r- 1 syslog adm  586698 Apr 25 07:35 syslog.1
-rw-r--r-- 1 root   root  0 Apr 25 15:48 syslog.2
-rw-r- 1 syslog adm   26955 Apr 24 07:35 syslog.2.gz
-rw-r- 1 syslog adm   26695 Apr 23 07:35 syslog.3.gz
-rw-r- 1 syslog adm   31307 Apr 22 07:35 syslog.4.gz
-rw-r- 1 syslog adm   32909 Apr 21 07:35 syslog.5.gz
-rw-r- 1 syslog adm   39182 Apr 20 07:35 syslog.6.gz
-rw-r- 1 syslog adm   27036 Apr 19 07:35 syslog.7.gz
Either things will fail overnight (well first thing tomorrow morning or all 
will be well.  I shall get back in touch soon.

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

Status in One Hundred Papercuts:
  Triaged
Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Trusty:
  Fix Committed
Status in logrotate source package in Xenial:
  Fix Committed
Status in logrotate source package in Yakkety:
  Fix Committed
Status in logrotate source package in Zesty:
  Fix Released
Status in logrotate package in Debian:
  Fix Released

Bug description:
  [Impact]

  Logrotate fails to rotate a log and then will continue to fail to
  rotate it until manual intervention takes place. If messaging has not
  been configured on the system there will be no warning issued to the
  user. The log will grow day by day until a user intervenes or the
  drive that the log is stored on is full.

  Very large log files can make it more difficult to find useful data.
  Full drives make the rest of the system fail to operate. Backporting a
  fix would prevent drives filling up on stable releases.

  [Test Case]

  Go to your logs area (/var/logs) and create a file with a name ending
  .2, as would be created part way through the logrotate process. So if
  you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz,
  /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your
  subsequent log rotate runs will fail.

  [Regression Potential]

  - I'd hope the potential is low as it only triggers under certain conditions 
that are special (target filename in the way).
  - So far in those conditions it failed to rotate
  - Yet If despite my hope there still manifests an issue I'd expect it could 
be renaming files it should not, so people would end up "missing" their logs - 
the good thing is that this is a rename, so they should find it at different 
names.
  - Another thing I consider possible is that some unexpected conditions cause 
e.g. a crash in the changed code, in that case the logs are not rotated, but 
since there is no unlink the logs will still exist.
  - Therefore I consider the Potential low enough to consider the fix.

  [Other Info]
  n/a

  ---

  Good afternoon.
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  

[Touch-packages] [Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk

[Thomas A. F. Thorne]

To finish off my confirmation of the fix, I did not see any email
notifications overnight.  When I look at the relevant log files I can
see the rotation is progressing:

$ ls -l /var/log/apt-cacher-ng/apt-cacher.err*
-rw-r--r-- 1 apt-cacher-ng apt-cacher-ng   0 Apr  5 06:28 
/var/log/apt-cacher-ng/apt-cacher.err
-rw-r--r-- 1 apt-cacher-ng apt-cacher-ng   0 Apr  4 06:26 
/var/log/apt-cacher-ng/apt-cacher.err.1
-rw-r--r-- 1 apt-cacher-ng apt-cacher-ng   0 Mar 31 06:26 
/var/log/apt-cacher-ng/apt-cacher.err.1.gz-2017040406.backup
-rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 180 Mar 31 13:40 
/var/log/apt-cacher-ng/apt-cacher.err.2.gz
-rw-r--r-- 1 apt-cacher-ng apt-cacher-ng  20 Mar 29 06:25 
/var/log/apt-cacher-ng/apt-cacher.err.3.gz
-rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 190 Mar 29 01:53 
/var/log/apt-cacher-ng/apt-cacher.err.4.gz
-rw-r--r-- 1 apt-cacher-ng apt-cacher-ng  20 Mar 27 06:25 
/var/log/apt-cacher-ng/apt-cacher.err.5.gz
-rw-r--r-- 1 apt-cacher-ng apt-cacher-ng  20 Mar 26 06:25 
/var/log/apt-cacher-ng/apt-cacher.err.6.gz
-rw-r--r-- 1 apt-cacher-ng apt-cacher-ng  20 Mar 25 06:25 
/var/log/apt-cacher-ng/apt-cacher.err.7.gz


> Thank you Thomas

You are welcome.  Thank you for fixing the bug (or porting the fix into
Ubuntu).

> I hope that does not appear like a burden, the purpose of this process
is to mimimize the risk to unintentionally regress users.

That is fine.  I work in software development so I know the benefits of
thorough QA.

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

Status in One Hundred Papercuts:
  Triaged
Status in logrotate package in Ubuntu:
  Triaged
Status in logrotate source package in Zesty:
  Triaged
Status in logrotate package in Debian:
  Fix Released

Bug description:
  [Impact]

  Logrotate fails to rotate a log and then will continue to fail to
  rotate it until manual intervention takes place. If messaging has not
  been configured on the system there will be no warning issued to the
  user. The log will grow day by day until a user intervenes or the
  drive that the log is stored on is full.

  Very large log files can make it more difficult to find useful data.
  Full drives make the rest of the system fail to operate. Backporting a
  fix would prevent drives filling up on stable releases.

  [Test Case]

  Go to your logs area (/var/logs) and create a file with a name ending
  .2, as would be created part way through the logrotate process. So if
  you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz,
  /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your
  subsequent log rotate runs will fail.

  [Regression Potential]

  - I'd hope the potential is low as it only triggers under certain conditions 
that are special (target filename in the way).
  - So far in those conditions it failed to rotate
  - Yet If despite my hope there still manifests an issue I'd expect it could 
be renaming files it should not, so people would end up "missing" their logs - 
the good thing is that this is a rename, so they should find it at different 
names.
  - Another thing I consider possible is that some unexpected conditions cause 
e.g. a crash in the changed code, in that case the logs are not rotated, but 
since there is no unlink the logs will still exist.
  - Therefore I consider the Potential low enough to consider the fix.

  [Other Info]
  n/a

  ---

  Good afternoon.
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.

  I deleted all but the munin-node.log file to 

[Touch-packages] [Bug 1679233] Re: sudo crashed with SIGABRT in kill()

[Thomas A. F. Thorne]

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

Interesting.  I expected this bug to be a duplicate of bug #1678877 that
I reported earlier in the day but it did not get identified as a
duplicate of bug #1663453 so it must be a different one.

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

Title:
  sudo crashed with SIGABRT in kill()

Status in sudo package in Ubuntu:
  New

Bug description:
  Message arrived after login after a reboot.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Apr  3 15:15:50 2017
  ExecutablePath: /usr/bin/sudo
  InstallationDate: Installed on 2015-03-12 (752 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: sudo ./test Base32
  Signal: 6
  SourcePackage: sudo
  StacktraceTop:
   kill () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   __libc_start_main (main=0x55b4a05efa20, argc=3, argv=0x7ffcfb79ac68, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcfb79ac58) at ../csu/libc-start.c:291
   ?? ()
  Title: sudo crashed with SIGABRT in kill()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK
  modified.conffile..etc.sudoers: [modified]
  mtime.conffile..etc.sudoers: 2016-07-11T15:06:58.741085

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

-- 
Mailing list: https://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 1565332] Re: sudo crashed with SIGABRT in kill()

[Thomas A. F. Thorne]

Is bug #1663453 also a duplicate of this bug?  I raised two bugs
yesterday that I thought were probably the same but one got marked as a
duplicate of this bug and the other was marked as a duplicate of bug
#1663453.  My two bugs were bug #1678877 and bug #1679233.

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

Title:
  sudo crashed with SIGABRT in kill()

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  crash appeared in less than a second after boot-up

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Fri Apr  1 15:23:06 2016
  ExecutablePath: /usr/bin/sudo
  InstallationDate: Installed on 2016-03-28 (4 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  ProcCmdline: /usr/bin/sudo -H -S -p GNOME_SUDO_PASS -u root -- caja
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: sudo
  StacktraceTop:
   kill () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: sudo crashed with SIGABRT in kill()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

-- 
Mailing list: https://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 1678877] Re: sudo crashed with SIGSEGV in kill()

[Thomas A. F. Thorne]

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

Oh good.  Another bug that has been marked as a duplicate of a private
bug so I cannot tell if it should or should not be a duplicate of it.

This bug is not marked as private any more.  Please can someone with
access to #1663453 check if it should or should not be still marked as
private.

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

Title:
  sudo crashed with SIGSEGV in kill()

Status in sudo package in Ubuntu:
  New

Bug description:
  Logged into a machine and I was informed of an error.  There is not
  much way for me to say what triggered it until the diags are
  presented.  If the suggested bugs of #1565332, #1618602, #312835 and
  #1659846 are anything to go by the diagnostics are not going to reveal
  anything either.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 27 12:19:57 2017
  ExecutablePath: /usr/bin/sudo
  InstallationDate: Installed on 2015-03-12 (752 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: sudo ./test -t Timer
  Signal: 11
  SourcePackage: sudo
  StacktraceTop:
   kill () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   __libc_start_main (main=0x55e026690a20, argc=4, argv=0x7ecec8c8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ecec8b8) at ../csu/libc-start.c:291
   ?? ()
  Title: sudo crashed with SIGSEGV in kill()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK
  mtime.conffile..etc.sudoers: 2016-07-11T15:06:58.741085

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

-- 
Mailing list: https://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 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk

[Thomas A. F. Thorne]

Installing for 16.04 xenial on a machine that has just reproduced the
issue on its own.  If I do not see the error message emailed out to me
tonight then it is likely that the fix has succeeded.  I shall try to
post an update promptly, sorry for the delay.

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

Status in One Hundred Papercuts:
  Triaged
Status in logrotate package in Ubuntu:
  Triaged
Status in logrotate source package in Zesty:
  Triaged
Status in logrotate package in Debian:
  Fix Released

Bug description:
  [Impact]

  Logrotate fails to rotate a log and then will continue to fail to
  rotate it until manual intervention takes place. If messaging has not
  been configured on the system there will be no warning issued to the
  user. The log will grow day by day until a user intervenes or the
  drive that the log is stored on is full.

  Very large log files can make it more difficult to find useful data.
  Full drives make the rest of the system fail to operate. Backporting a
  fix would prevent drives filling up on stable releases.

  [Test Case]

  Go to your logs area (/var/logs) and create a file with a name ending
  .2, as would be created part way through the logrotate process. So if
  you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz,
  /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your
  subsequent log rotate runs will fail.

  [Regression Potential]

  - I'd hope the potential is low as it only triggers under certain conditions 
that are special (target filename in the way).
  - So far in those conditions it failed to rotate
  - Yet If despite my hope there still manifests an issue I'd expect it could 
be renaming files it should not, so people would end up "missing" their logs - 
the good thing is that this is a rename, so they should find it at different 
names.
  - Another thing I consider possible is that some unexpected conditions cause 
e.g. a crash in the changed code, in that case the logs are not rotated, but 
since there is no unlink the logs will still exist.
  - Therefore I consider the Potential low enough to consider the fix.

  [Other Info]
  n/a

  ---

  Good afternoon.
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/syslog.1.gz: File exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  Different file, different machine but a very similar error message.

  Checking on the syslog file I can see that it better fits with other reports 
on this bug as my duplicated .1 files has a corresponding .1.gz file.
  manager@trac:/var/log$ ll syslog*
  -rw-r- 1 syslog adm 918492 Oct  5 10:30 syslog
  -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
  -rw-r- 1 syslog adm  20638 Oct  2 02:01 syslog.1.gz
  -rw-r- 1 syslog adm  41989 Sep 30 02:00 syslog.2.gz
  -rw-r- 1 syslog adm  18654 Sep 28 02:01 syslog.3.gz
  -rw-r- 1 syslog adm  31720 Sep 26 06:40 syslog.4.gz
  -rw-r- 1 syslog adm  33151 Sep 25 02:01 syslog.5.gz
  -rw-r- 1 syslog adm  17290 Sep 23 02:01 syslog.6.gz
  -rw-r- 1 syslog adm  

[Touch-packages] [Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk

[Thomas A. F. Thorne]

SRU Bug Template


[Impact] 

Logrotate fails to rotate a log and then will continue to fail to rotate
it until manual intervention takes place.  If messaging has not been
configured on the system there will be no warning issued to the user.
The log will grow day by day until a user intervenes or the drive that
the log is stored on is full.

Very large log files can make it more difficult to find useful data.
Full drives make the rest of the system fail to operate.  Backporting a
fix would prevent drives filling up on stable releases.

[Test Case]

Go to your logs area (/var/logs) and create a file with a name ending
.2, as would be created part way through the logrotate process.  So if
you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz,
/var/log/syslog.3.gz; create a new file named /var/log/syslog.2.  Your
subsequent log rotate runs will fail.

[Regression Potential]



[Other Info]

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

Title:
  Logrotate doesn't clean old system logs, allowing them to fill the
  disk

Status in One Hundred Papercuts:
  Triaged
Status in logrotate package in Ubuntu:
  Triaged
Status in logrotate source package in Zesty:
  Triaged
Status in logrotate package in Debian:
  Fix Released

Bug description:
  Good afternoon.  
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have 
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.  
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.  

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/syslog.1.gz: File exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  Different file, different machine but a very similar error message.  

  Checking on the syslog file I can see that it better fits with other reports 
on this bug as my duplicated .1 files has a corresponding .1.gz file.  
  manager@trac:/var/log$ ll syslog*
  -rw-r- 1 syslog adm 918492 Oct  5 10:30 syslog
  -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
  -rw-r- 1 syslog adm  20638 Oct  2 02:01 syslog.1.gz
  -rw-r- 1 syslog adm  41989 Sep 30 02:00 syslog.2.gz
  -rw-r- 1 syslog adm  18654 Sep 28 02:01 syslog.3.gz
  -rw-r- 1 syslog adm  31720 Sep 26 06:40 syslog.4.gz
  -rw-r- 1 syslog adm  33151 Sep 25 02:01 syslog.5.gz
  -rw-r- 1 syslog adm  17290 Sep 23 02:01 syslog.6.gz
  -rw-r- 1 syslog adm  39275 Sep 21 06:35 syslog.7.gz

  There has been some speculation that a full or nearly full /var
  partition would cause this issue.  I can confirm that /var is part of
  / on my systems and that presently both of them have several gigabytes
  of space.  I run Munin an Icinga to monitor system state.  Neither of
  these show / being completely full in the past month.  They have both
  had /boot fill significantly.  Trac had a highest use value of / being
  99.28% full in the past year  but warden has only had a peak of 33% in
  the past year.

  A quick search of the internet suggests a couple of other people reporting 
similar issues: 
  https://github.com/gitlabhq/gitlabhq/issues/6894
  
http://raspberrypi.stackexchange.com/questions/22545/why-are-system-logs-not-rotating
 

  I do not believe that I have altered by logrotate configuration files but 
here is a copy of the ones I know about:
  $ cat /etc/logrotate.conf 
  # see "man logrotate" for details
  # 

Re: [Touch-packages] [Bug 1636564] Re: Segfault from libX11.so.6.3.0

[Thomas A. F. Thorne]

I don't think I'm using the Nvidia drivers on the machine I reported this
from. That would mean they could not be the route cause.

On Mon, 20 Mar 2017, 17:51 Jan Lachnitt, <1636...@bugs.launchpad.net>
wrote:

> Another report and some thoughts below
>
> HW: Asus Vivobook (touchscreen, Intel graphics), external monitor attached.
> OS: Linux Mint 18 Cinnamon x64.
> State before crash: Running X session using both displays ("big desktop"),
> several applications, Vivaldi browser active.
> My aim: Lock the computer.
> Course of action, the USUAL part: Pressed Ctrl+Alt+L, not locked - Vivaldi
> displayed its menu (to be displayed upon pressing Alt), tapped the
> touchscreen to get rid of the menu and thus actually lock the computer.
> Course of action, the UNUSUAL part: Black screen for a few seconds, then
> login screen, old X session gone.
>
> syslog:
> Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]: XIO:  fatal IO
> error 11 (Resource temporarily unavailable) on X server ":0"
> Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]:   after 2925
> requests (2925 known processed) with 0 events remaining.
> Mar 20 14:43:20 VivoBook cinnamon-session[1640]: Gdk-WARNING:
> t+4492,79569s: cinnamon-session: Fatal IO error 11 (Prostředek je dočasně
> nepřístupný) on X server :0.
> Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus
> can't be made
> Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus
> can't be made
> Mar 20 14:43:20 VivoBook mdm[1212]: WARNING: mdm_slave_xioerror_handler:
> Kritická chyba X - Restartování :0
> Mar 20 14:43:20 VivoBook kernel: [ 4538.677519] vivaldi-bin[4100]:
> segfault at 968 ip 7f61ac384643 sp 7ffc09f25b50 error 4 in
> libX11.so.6.3.0[7f61ac35c000+135000]
> Mar 20 14:43:20 VivoBook ag[4118]: mdm-superpost Starting...
> Mar 20 14:43:20 VivoBook ag[4122]: mdm-superpost Finished
> Mar 20 14:43:20 VivoBook console-kit-daemon[1566]: (process:4128):
> GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
> Mar 20 14:43:21 VivoBook acpid: client 1219[0:0] has disconnected
> Mar 20 14:43:21 VivoBook acpid: client connected from 4131[0:0]
> Mar 20 14:43:21 VivoBook acpid: 1 client rule loaded
> Mar 20 14:43:22 VivoBook ag[4139]: mdm-superinit Starting...
> Mar 20 14:43:22 VivoBook ag[4140]: mdm-superinit Finished
>
> Xorg.0.log covers the new session, Xorg.0.log.old has no record of the
> event.
>
> The segfault really seems to affect multiple users, especially with
> Chromium-based browsers, e.g.:
> https://bbs.archlinux.org/viewtopic.php?id=131328 - from 2011 already
> https://bbs.archlinux.org/viewtopic.php?id=221888 - solution?
>
> I don't know if syslog preserves the order of events (within a second),
> but if yes, then the segfault is just a consequence of another problem,
> e.g.:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/999191
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1636564
>
> Title:
>   Segfault from libX11.so.6.3.0
>
> Status in libx11 package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Something went wrong with my Ubuntu 16.04 LTS desktop today.  When I
>   got back to the system Mattermost and a Chrome were indicating that
>   the network was not working.  I started to look about and it seemed
>   that my main ethernet network connection had lost its IPv4 address
>   somehow.  ifconfig and the GUI network manager confirmed this.
>
>   To try and resolve this I physically removed the connector and the
>   plugged it back in.  Shortly after I did this my GUI seemed to die out
>   and I ended up back at the login screen.
>
>   Once everything had calmed down I logged back in.  After some digging
>   about in the logs I noticed the following in /var/log/kern.log
>
>   Oct 25 13:01:09 thorne-ul-dt kernel: [694321.877561] Mattermost[744]:
> segfault at 968 ip 7f8a9e257643 sp 7ffe72a3b510 error 4 in
> libX11.so.6.3.0[7f8a9e22f000+135000]
>   Oct 25 13:01:09 thorne-ul-dt kernel: [694322.029362] chrome[745]:
> segfault at 968 ip 7fd4b5c73643 sp 7fff94f78d90 error 4 in
> libX11.so.6.3.0[7fd4b5c4b000+135000]
>
>   That seemed to be the correct time for the problem I noticed.   What
>   exactly caused it I am not sure.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: libx11-6 2:1.6.3-1ubuntu2
>   ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
>   Uname: Linux 4.4.0-42-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.1
>   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: Tue Oct 25 17:07:28 2016
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: 

[Touch-packages] [Bug 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited wit

[Thomas A. F. Thorne]

The stock not security reply can be found at
https://wiki.ubuntu.com/SecurityTeam/BugTriage#Not_Security which says
"unmarked it as a security issue since this bug does not show evidence
of allowing attackers to cross privilege boundaries nor directly cause
loss of data/privacy."

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

Title:
  Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
  error creating output file /var/log/... File exists run-parts:
  /etc/cron.daily/logrotate exited with return code 1

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

Bug description:
  Good afternoon.  
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have 
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.  
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.  

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/syslog.1.gz: File exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  Different file, different machine but a very similar error message.  

  Checking on the syslog file I can see that it better fits with other reports 
on this bug as my duplicated .1 files has a corresponding .1.gz file.  
  manager@trac:/var/log$ ll syslog*
  -rw-r- 1 syslog adm 918492 Oct  5 10:30 syslog
  -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
  -rw-r- 1 syslog adm  20638 Oct  2 02:01 syslog.1.gz
  -rw-r- 1 syslog adm  41989 Sep 30 02:00 syslog.2.gz
  -rw-r- 1 syslog adm  18654 Sep 28 02:01 syslog.3.gz
  -rw-r- 1 syslog adm  31720 Sep 26 06:40 syslog.4.gz
  -rw-r- 1 syslog adm  33151 Sep 25 02:01 syslog.5.gz
  -rw-r- 1 syslog adm  17290 Sep 23 02:01 syslog.6.gz
  -rw-r- 1 syslog adm  39275 Sep 21 06:35 syslog.7.gz

  There has been some speculation that a full or nearly full /var
  partition would cause this issue.  I can confirm that /var is part of
  / on my systems and that presently both of them have several gigabytes
  of space.  I run Munin an Icinga to monitor system state.  Neither of
  these show / being completely full in the past month.  They have both
  had /boot fill significantly.  Trac had a highest use value of / being
  99.28% full in the past year  but warden has only had a peak of 33% in
  the past year.

  A quick search of the internet suggests a couple of other people reporting 
similar issues: 
  https://github.com/gitlabhq/gitlabhq/issues/6894
  
http://raspberrypi.stackexchange.com/questions/22545/why-are-system-logs-not-rotating
 

  I do not believe that I have altered by logrotate configuration files but 
here is a copy of the ones I know about:
  $ cat /etc/logrotate.conf 
  # see "man logrotate" for details
  # rotate log files weekly
  weekly

  # use the syslog group by default, since this is the owning group
  # of /var/log/syslog.
  su root syslog

  # keep 4 weeks worth of backlogs
  rotate 4

  # create new (empty) log files after rotating old ones
  create

  # uncomment this if you want your log files compressed
  #compress

  # packages drop log rotation information into this directory
  include /etc/logrotate.d

  # no packages own wtmp, or btmp -- we'll rotate them here
  /var/log/wtmp {
  missingok
  monthly
  create 0664 root utmp
  rotate 1
  }

  /var/log/btmp {
  missingok
  

[Touch-packages] [Bug 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited wit

[Thomas A. F. Thorne]

I checked on IRC #ubuntu-hardened (the actual name for the #ubuntu-
security channel) and was told that "we typically only consider bugs to
have a security impact if there's an attacker to the story".  The reason
for that is "else, almost every bug has an indirect security impact"
which I can see the logic to.

So that means this is not a security bug, just a bug.

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

Title:
  Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
  error creating output file /var/log/... File exists run-parts:
  /etc/cron.daily/logrotate exited with return code 1

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

Bug description:
  Good afternoon.  
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have 
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.  
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.  

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/syslog.1.gz: File exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  Different file, different machine but a very similar error message.  

  Checking on the syslog file I can see that it better fits with other reports 
on this bug as my duplicated .1 files has a corresponding .1.gz file.  
  manager@trac:/var/log$ ll syslog*
  -rw-r- 1 syslog adm 918492 Oct  5 10:30 syslog
  -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
  -rw-r- 1 syslog adm  20638 Oct  2 02:01 syslog.1.gz
  -rw-r- 1 syslog adm  41989 Sep 30 02:00 syslog.2.gz
  -rw-r- 1 syslog adm  18654 Sep 28 02:01 syslog.3.gz
  -rw-r- 1 syslog adm  31720 Sep 26 06:40 syslog.4.gz
  -rw-r- 1 syslog adm  33151 Sep 25 02:01 syslog.5.gz
  -rw-r- 1 syslog adm  17290 Sep 23 02:01 syslog.6.gz
  -rw-r- 1 syslog adm  39275 Sep 21 06:35 syslog.7.gz

  There has been some speculation that a full or nearly full /var
  partition would cause this issue.  I can confirm that /var is part of
  / on my systems and that presently both of them have several gigabytes
  of space.  I run Munin an Icinga to monitor system state.  Neither of
  these show / being completely full in the past month.  They have both
  had /boot fill significantly.  Trac had a highest use value of / being
  99.28% full in the past year  but warden has only had a peak of 33% in
  the past year.

  A quick search of the internet suggests a couple of other people reporting 
similar issues: 
  https://github.com/gitlabhq/gitlabhq/issues/6894
  
http://raspberrypi.stackexchange.com/questions/22545/why-are-system-logs-not-rotating
 

  I do not believe that I have altered by logrotate configuration files but 
here is a copy of the ones I know about:
  $ cat /etc/logrotate.conf 
  # see "man logrotate" for details
  # rotate log files weekly
  weekly

  # use the syslog group by default, since this is the owning group
  # of /var/log/syslog.
  su root syslog

  # keep 4 weeks worth of backlogs
  rotate 4

  # create new (empty) log files after rotating old ones
  create

  # uncomment this if you want your log files compressed
  #compress

  # packages drop log rotation information into this directory
  include /etc/logrotate.d

  # no packages own wtmp, or btmp -- we'll rotate them here
  /var/log/wtmp {
  missingok
  monthly
   

[Touch-packages] [Bug 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited wit

[Thomas A. F. Thorne]

That does sound a bit tenuous but could be easily settled by a policy decision 
on whether: 
 i) Bugs that directly block the installation of security patches are security 
bugs.  
 ii) Bugs that cause disk space to fill which in turn block security patch 
install are security bugs.  

I would have said that i sounds like a possible valid case but ii is
getting a bit drawn out.  Still I expect the situation and suggestion
will have popped up before somewhere.  Looking at
https://wiki.ubuntu.com/DebuggingSecurity#How%20to%20File it does not
mention blocking security patches as a criteria which would thrown the
whole idea of it being a security bug out.

If in doubt ask.  I shall try heading over to IRC and seeing if someone
can answer the question.

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

Title:
  Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
  error creating output file /var/log/... File exists run-parts:
  /etc/cron.daily/logrotate exited with return code 1

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

Bug description:
  Good afternoon.  
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have 
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.  
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.  

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/syslog.1.gz: File exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  Different file, different machine but a very similar error message.  

  Checking on the syslog file I can see that it better fits with other reports 
on this bug as my duplicated .1 files has a corresponding .1.gz file.  
  manager@trac:/var/log$ ll syslog*
  -rw-r- 1 syslog adm 918492 Oct  5 10:30 syslog
  -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
  -rw-r- 1 syslog adm  20638 Oct  2 02:01 syslog.1.gz
  -rw-r- 1 syslog adm  41989 Sep 30 02:00 syslog.2.gz
  -rw-r- 1 syslog adm  18654 Sep 28 02:01 syslog.3.gz
  -rw-r- 1 syslog adm  31720 Sep 26 06:40 syslog.4.gz
  -rw-r- 1 syslog adm  33151 Sep 25 02:01 syslog.5.gz
  -rw-r- 1 syslog adm  17290 Sep 23 02:01 syslog.6.gz
  -rw-r- 1 syslog adm  39275 Sep 21 06:35 syslog.7.gz

  There has been some speculation that a full or nearly full /var
  partition would cause this issue.  I can confirm that /var is part of
  / on my systems and that presently both of them have several gigabytes
  of space.  I run Munin an Icinga to monitor system state.  Neither of
  these show / being completely full in the past month.  They have both
  had /boot fill significantly.  Trac had a highest use value of / being
  99.28% full in the past year  but warden has only had a peak of 33% in
  the past year.

  A quick search of the internet suggests a couple of other people reporting 
similar issues: 
  https://github.com/gitlabhq/gitlabhq/issues/6894
  
http://raspberrypi.stackexchange.com/questions/22545/why-are-system-logs-not-rotating
 

  I do not believe that I have altered by logrotate configuration files but 
here is a copy of the ones I know about:
  $ cat /etc/logrotate.conf 
  # see "man logrotate" for details
  # rotate log files weekly
  weekly

  # use the syslog group by default, since this is the owning group
  # of /var/log/syslog.
  su root 

[Touch-packages] [Bug 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited wit

[Thomas A. F. Thorne]

Still present on 14.04.1.  I am seeing this again today.

I wonder if this would count as a papercut?  I am not really sure as
https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Mission says "Have the
impression the desktop is rock solid." and this is a log rotation system
that only moans if root mail is setup. On the other hand
https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Triage/Classify%20as%20a%20papercut?highlight=%28CategoryPapercuts%29
says "If a bug is trivial to fix, you shall classify it as a papercut by
marking it as affecting the "hundredpapercuts" project." and this bug
just needs the upstream bug brought in.  It would make at least 6 of us
feel like someone is caring too.

Front page of the One Hundred Papercuts says "If any doubt, you can ask
any time." so I shall add papercuts-ninja list to the subscription.
This is a very low traffic bug so someone can unsubscribe them before
this thread generates more than a couple of posts.

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

Title:
  Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
  error creating output file /var/log/... File exists run-parts:
  /etc/cron.daily/logrotate exited with return code 1

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

Bug description:
  Good afternoon.  
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have 
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.  
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.  

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/syslog.1.gz: File exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  Different file, different machine but a very similar error message.  

  Checking on the syslog file I can see that it better fits with other reports 
on this bug as my duplicated .1 files has a corresponding .1.gz file.  
  manager@trac:/var/log$ ll syslog*
  -rw-r- 1 syslog adm 918492 Oct  5 10:30 syslog
  -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
  -rw-r- 1 syslog adm  20638 Oct  2 02:01 syslog.1.gz
  -rw-r- 1 syslog adm  41989 Sep 30 02:00 syslog.2.gz
  -rw-r- 1 syslog adm  18654 Sep 28 02:01 syslog.3.gz
  -rw-r- 1 syslog adm  31720 Sep 26 06:40 syslog.4.gz
  -rw-r- 1 syslog adm  33151 Sep 25 02:01 syslog.5.gz
  -rw-r- 1 syslog adm  17290 Sep 23 02:01 syslog.6.gz
  -rw-r- 1 syslog adm  39275 Sep 21 06:35 syslog.7.gz

  There has been some speculation that a full or nearly full /var
  partition would cause this issue.  I can confirm that /var is part of
  / on my systems and that presently both of them have several gigabytes
  of space.  I run Munin an Icinga to monitor system state.  Neither of
  these show / being completely full in the past month.  They have both
  had /boot fill significantly.  Trac had a highest use value of / being
  99.28% full in the past year  but warden has only had a peak of 33% in
  the past year.

  A quick search of the internet suggests a couple of other people reporting 
similar issues: 
  https://github.com/gitlabhq/gitlabhq/issues/6894
  
http://raspberrypi.stackexchange.com/questions/22545/why-are-system-logs-not-rotating
 

  I do not believe that I have altered by logrotate configuration files but 
here is a copy of the ones I know about:
  $ 

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Thomas A. F. Thorne]

@jarnos mentions having generated a script to remove extra kernels.
There is already a purge-old-kernels command line tool lingering in the
bikeshed package.

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

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

-- 
Mailing list: https://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 1660574] [NEW] IPv4 Address Lost 8 Days After Previous DHCP Allocation

[Thomas A. F. Thorne]

Public bug reported:

My Ubuntu 16.04 desktop frequently loses the IPv4 address on its wired
ethernet connection to my office's network.  This happened this morning
and previously happened 8 days ago.

The network uses a Windows Small Business Server as its main Active
Domain Domain Controller which includes a DHCP service.  There are
several other Ubuntu 16.04 machines on the network that do not seem to
experience this issue.  This is an IPv4 only network, no IPv6 services
are configures and IPv6 is disabled on most machines.

My PC has two wired network ports.  One connects to the office network
and uses DHCP to get an IPv4 address.  The other connects to a switch on
my desk that has test equipment connected to it and uses a static IPv4
address.

I have the output from: 
 ll /var/lib/NetworkManager
 nmcli -p c
 nmcli -p c show TN\ Wired
Taken; after the renewal of the address eight days ago, this morning before I 
"Disconnect"ed the connection from the drop down menu and after I reconnected 
and an IPv4 address was re-acquired.  If any of this would be helpful, please 
let me know and I shall post it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 31 09:55:10 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-03-12 (690 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
IpRoute:
 default via 172.16.20.21 dev eth0  proto static  metric 100 
 169.254.0.0/16 dev eth1  scope link  metric 1000 
 172.16.20.0/24 dev eth0  proto kernel  scope link  src 172.16.20.67  metric 
100 
 192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.10  metric 100
IwConfig:
 lono wireless extensions.
 
 eth1  no wireless extensions.
 
 eth0  no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-11T09:44:29.848008
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
 eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  TN 
Wired  decbd8d4-b045-4214-88c3-904bcabaa386  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 eth1ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  Test 
Network  c2e4c3e8-027e-4201-8486-824d32ee164f  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  -- 
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  IPv4 Address Lost 8 Days After Previous DHCP Allocation

Status in network-manager package in Ubuntu:
  New

Bug description:
  My Ubuntu 16.04 desktop frequently loses the IPv4 address on its wired
  ethernet connection to my office's network.  This happened this
  morning and previously happened 8 days ago.

  The network uses a Windows Small Business Server as its main Active
  Domain Domain Controller which includes a DHCP service.  There are
  several other Ubuntu 16.04 machines on the network that do not seem to
  experience this issue.  This is an IPv4 only network, no IPv6 services
  are configures and IPv6 is disabled on most machines.

  My PC has two wired network ports.  One connects to the office network
  and uses DHCP to get an IPv4 address.  The other connects to a switch
  on my desk that has test equipment connected to it and uses a static
  IPv4 address.

  I have the output from: 
   ll /var/lib/NetworkManager
   nmcli -p c
   nmcli -p c show TN\ Wired
  Taken; after the renewal of the address eight days ago, this morning before I 
"Disconnect"ed the connection from the drop down menu and after I reconnected 
and an IPv4 address was re-acquired.  If any of this would be helpful, please 
let me know and I shall post it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: 

[Touch-packages] [Bug 1527166] Re: cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg: 'linux-headers..."

[Thomas A. F. Thorne]

Seen in an email this morning from a 16.04 system:
/etc/cron.daily/apt:
MarkUpgrade() called on a non-upgrable pkg: 'linux-image-4.4.0-59-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-tools-3.13.0-107-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-tools-3.13.0-107'
MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-4.4.0-59-generic'
MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-4.4.0-59'
MarkUpgrade() called on a non-upgrable pkg: 'linux-cloud-tools-3.13.0-107'
MarkUpgrade() called on a non-upgrable pkg: 
'linux-cloud-tools-3.13.0-107-generic'

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

Title:
  cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg:
  'linux-headers..."

Status in python-apt package in Ubuntu:
  Triaged
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  Today I received the following messages from /etc/cron.daily/apt on my
  14.04 LTS server

  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73'
  MarkUpgrade() called on a non-upgrable pkg: 
'linux-image-extra-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-image-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73-generic'

  
  First of all I suppose  the message should read  non-upgradable
  non-upgrable is possibly incorrect and should be corrected.

  Secondly I have no clue, what this message means so the error message
  should be revised to give more details.

  I think this as a minor bug but messages should always be correct,
  precise and possibly helpful.

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

-- 
Mailing list: https://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 1642600] [NEW] PC freeze when turning off screen

[Thomas A. F. Thorne]

Public bug reported:

I have an ubuntu 16.04 PC which was recently upgraded from 10.something
to 12.04 and then to 16.04 (I think that is how it went, it was a two
day thing with me checking on it now and again to say yes.  Now that it
is running on 16.04 I have noticed that when I left the PC for a while
it locked up.  The display was off, the power light on the tower solidly
on and the keyboard unresponsive.  The Num Lock light was lit but would
not respond to key presses, nor would the Caps Lock or Scroll Lock
lights.  No key presses or short press of a power light would change the
system state.  The only thing I could do while sat at the PC was hold
the power button in to force a power off.

When the PC was powered back on everything seemed to be OK.

I thought it might be a problem with suspending the PC.  I was able to
do that manually though.  The display went off, the tower fans went
quiet and the power light started to blink.  Pressing keyboard keys did
nothing but a short press of the power button brought the system back
online.  The only problem being that the Wi-Fi was lost until I
restarted the system, not ideal but better than frozen.

I attempted to disable the automatic suspend option from the Settings
menu but the system still ended up in the frozen state.  Next to
completely disable suspend by creating a
/etc/polkit-1/localauthority/50-local.d/com.ubuntu.disable-suspend.pkla
file as suggested at http://askubuntu.com/questions/452908/how-to-
disable-suspend-in-14-04 but the system still ended up frozen.

That leaves me to think it was the act of going into the Monitor
Disabled state which caused the issue.  So I started to report an
ubuntu-bug and here I am typing out this description of what I remember
doing.

$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

Memory 2.0 GiB
Processor Intel Core 2 Duo CPU E4400 @ 2.00 GHz x 2
Graphics Gallium 0.4 on ATI RV515
OS type 64-bit
Disk 96.6 GB

If there are any further diagnostic steps I can take please let me know.
This is a personal machine so I can do most things to it.  I am a c/c++
software engineer by trade so although I am not great with the GNU
Debugger I can do most things with a bit of instruction.  I do not do
much Ubuntu or Kernel work so links to getting started guides for how to
do anything more specific that git clone or make would be appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Thu Nov 17 13:29:59 2016
DistUpgraded: 2016-11-16 07:49:36,758 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
   Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0d02]
   Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0d03]
InstallationDate: Installed on 2014-02-03 (1017 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
LightdmGreeterLogOld:
 (lightdm-gtk-greeter:1176): GLib-CRITICAL **: g_shell_parse_argv: assertion 
'command_line != NULL' failed
 
 ** (lightdm-gtk-greeter:1176): WARNING **: Failed to open sessions directory: 
Error opening directory '/usr/share/lightdm/sessions': No such file or directory
 
 ** (lightdm-gtk-greeter:1176): WARNING **: Failed to load user image: Failed 
to open file '/home/thomas/.face': No such file or directory
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=ce39165f-49f5-4875-a74e-2be810fd63c9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to xenial on 2016-11-16 (1 days ago)
dmi.bios.date: 06/23/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.15
dmi.board.name: 0CU409
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: OEM
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.15:bd06/23/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM:
dmi.product.name: Vostro 200
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: 

[Touch-packages] [Bug 1642600] Re: PC freeze when turning off screen

[Thomas A. F. Thorne]

I probably should have put that I have not seen the issue since setting
the turn off screen option to never.  It has only been a couple of hours
since I did that but it is better than before when it would fail within
the ~30 minutes that setting was at before.

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

Title:
  PC freeze when turning off screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I have an ubuntu 16.04 PC which was recently upgraded from
  10.something to 12.04 and then to 16.04 (I think that is how it went,
  it was a two day thing with me checking on it now and again to say
  yes.  Now that it is running on 16.04 I have noticed that when I left
  the PC for a while it locked up.  The display was off, the power light
  on the tower solidly on and the keyboard unresponsive.  The Num Lock
  light was lit but would not respond to key presses, nor would the Caps
  Lock or Scroll Lock lights.  No key presses or short press of a power
  light would change the system state.  The only thing I could do while
  sat at the PC was hold the power button in to force a power off.

  When the PC was powered back on everything seemed to be OK.

  I thought it might be a problem with suspending the PC.  I was able to
  do that manually though.  The display went off, the tower fans went
  quiet and the power light started to blink.  Pressing keyboard keys
  did nothing but a short press of the power button brought the system
  back online.  The only problem being that the Wi-Fi was lost until I
  restarted the system, not ideal but better than frozen.

  I attempted to disable the automatic suspend option from the Settings
  menu but the system still ended up in the frozen state.  Next to
  completely disable suspend by creating a
  /etc/polkit-1/localauthority/50-local.d/com.ubuntu.disable-
  suspend.pkla file as suggested at
  http://askubuntu.com/questions/452908/how-to-disable-suspend-in-14-04
  but the system still ended up frozen.

  That leaves me to think it was the act of going into the Monitor
  Disabled state which caused the issue.  So I started to report an
  ubuntu-bug and here I am typing out this description of what I
  remember doing.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Memory 2.0 GiB
  Processor Intel Core 2 Duo CPU E4400 @ 2.00 GHz x 2
  Graphics Gallium 0.4 on ATI RV515
  OS type 64-bit
  Disk 96.6 GB

  If there are any further diagnostic steps I can take please let me
  know.  This is a personal machine so I can do most things to it.  I am
  a c/c++ software engineer by trade so although I am not great with the
  GNU Debugger I can do most things with a bit of instruction.  I do not
  do much Ubuntu or Kernel work so links to getting started guides for
  how to do anything more specific that git clone or make would be
  appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Thu Nov 17 13:29:59 2016
  DistUpgraded: 2016-11-16 07:49:36,758 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7183] (prog-if 00 [VGA controller])
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] [1028:0d02]
 Subsystem: Dell RV516 [Radeon X1300/X1550 Series] (Secondary) [1028:0d03]
  InstallationDate: Installed on 2014-02-03 (1017 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  LightdmGreeterLogOld:
   (lightdm-gtk-greeter:1176): GLib-CRITICAL **: g_shell_parse_argv: assertion 
'command_line != NULL' failed
   
   ** (lightdm-gtk-greeter:1176): WARNING **: Failed to open sessions 
directory: Error opening directory '/usr/share/lightdm/sessions': No such file 
or directory
   
   ** (lightdm-gtk-greeter:1176): WARNING **: Failed to load user image: Failed 
to open file '/home/thomas/.face': No such file or directory
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=ce39165f-49f5-4875-a74e-2be810fd63c9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded 

[Touch-packages] [Bug 1636564] [NEW] Segfault from libX11.so.6.3.0

[Thomas A. F. Thorne]

Public bug reported:

Something went wrong with my Ubuntu 16.04 LTS desktop today.  When I got
back to the system Mattermost and a Chrome were indicating that the
network was not working.  I started to look about and it seemed that my
main ethernet network connection had lost its IPv4 address somehow.
ifconfig and the GUI network manager confirmed this.

To try and resolve this I physically removed the connector and the
plugged it back in.  Shortly after I did this my GUI seemed to die out
and I ended up back at the login screen.

Once everything had calmed down I logged back in.  After some digging
about in the logs I noticed the following in /var/log/kern.log

Oct 25 13:01:09 thorne-ul-dt kernel: [694321.877561] Mattermost[744]: segfault 
at 968 ip 7f8a9e257643 sp 7ffe72a3b510 error 4 in 
libX11.so.6.3.0[7f8a9e22f000+135000]
Oct 25 13:01:09 thorne-ul-dt kernel: [694322.029362] chrome[745]: segfault at 
968 ip 7fd4b5c73643 sp 7fff94f78d90 error 4 in 
libX11.so.6.3.0[7fd4b5c4b000+135000]

That seemed to be the correct time for the problem I noticed.   What
exactly caused it I am not sure.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libx11-6 2:1.6.3-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
Uname: Linux 4.4.0-42-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Tue Oct 25 17:07:28 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
InstallationDate: Installed on 2015-03-12 (592 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
vt.handoff=7
SourcePackage: libx11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-DS2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: H81M-DS2V
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Oct 25 13:01:04 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   30926 
 vendor BNQ
xserver.version: 2:1.18.4-0ubuntu0.1

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


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

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

Title:
  Segfault from libX11.so.6.3.0

Status in libx11 package in Ubuntu:
  New

Bug description:
  Something went wrong with my Ubuntu 16.04 LTS desktop today.  When I
  got back to the system Mattermost and a Chrome were indicating that
  the network was not working.  I started to look about and it seemed
  that my main ethernet network connection had lost its IPv4 address
  somehow.  ifconfig and the GUI network manager confirmed this.

  To try and resolve this I physically removed the connector and the
  plugged it back 

[Touch-packages] [Bug 1630516] [NEW] Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited w

[Thomas A. F. Thorne]

Public bug reported:

Good afternoon.  
I have started seeing something very similar to Debian Dug 734688 "Logs are not 
rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have 
$ logrotate --version
logrotate 3.8.7
bundled in it.  A few weeks ago I started getting root emails such as this:
> Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
> --report /etc/cron.daily )
>
> /etc/cron.daily/logrotate:
> error: error creating output file /var/log/munin/munin-node.log.1: File exists
> run-parts: /etc/cron.daily/logrotate exited with return code 1
When I inspected the area of concern I was able to see that there was an 
existing .1 file.  
manager@warden:/var/log/munin$ ll
total 580
drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
-rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
-rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
-rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
-rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
-rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.  

I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
> Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
> --report /etc/cron.daily )
>
> /etc/cron.daily/logrotate:
> error: error creating output file /var/log/syslog.1.gz: File exists
> run-parts: /etc/cron.daily/logrotate exited with return code 1
Different file, different machine but a very similar error message.  

Checking on the syslog file I can see that it better fits with other reports on 
this bug as my duplicated .1 files has a corresponding .1.gz file.  
manager@trac:/var/log$ ll syslog*
-rw-r- 1 syslog adm 918492 Oct  5 10:30 syslog
-rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
-rw-r- 1 syslog adm  20638 Oct  2 02:01 syslog.1.gz
-rw-r- 1 syslog adm  41989 Sep 30 02:00 syslog.2.gz
-rw-r- 1 syslog adm  18654 Sep 28 02:01 syslog.3.gz
-rw-r- 1 syslog adm  31720 Sep 26 06:40 syslog.4.gz
-rw-r- 1 syslog adm  33151 Sep 25 02:01 syslog.5.gz
-rw-r- 1 syslog adm  17290 Sep 23 02:01 syslog.6.gz
-rw-r- 1 syslog adm  39275 Sep 21 06:35 syslog.7.gz

There has been some speculation that a full or nearly full /var
partition would cause this issue.  I can confirm that /var is part of /
on my systems and that presently both of them have several gigabytes of
space.  I run Munin an Icinga to monitor system state.  Neither of these
show / being completely full in the past month.  They have both had
/boot fill significantly.  Trac had a highest use value of / being
99.28% full in the past year  but warden has only had a peak of 33% in
the past year.

A quick search of the internet suggests a couple of other people reporting 
similar issues: 
https://github.com/gitlabhq/gitlabhq/issues/6894
http://raspberrypi.stackexchange.com/questions/22545/why-are-system-logs-not-rotating
 

I do not believe that I have altered by logrotate configuration files but here 
is a copy of the ones I know about:
$ cat /etc/logrotate.conf 
# see "man logrotate" for details
# rotate log files weekly
weekly

# use the syslog group by default, since this is the owning group
# of /var/log/syslog.
su root syslog

# keep 4 weeks worth of backlogs
rotate 4

# create new (empty) log files after rotating old ones
create

# uncomment this if you want your log files compressed
#compress

# packages drop log rotation information into this directory
include /etc/logrotate.d

# no packages own wtmp, or btmp -- we'll rotate them here
/var/log/wtmp {
missingok
monthly
create 0664 root utmp
rotate 1
}

/var/log/btmp {
missingok
monthly
create 0660 root utmp
rotate 1
}

# system-specific logs may be configured here

$ cat /etc/logrotate.d/rsyslog 
/var/log/syslog
{
rotate 7
daily
missingok
notifempty
delaycompress
compress
postrotate
reload rsyslog >/dev/null 2>&1 || true
endscript
}

/var/log/mail.info
/var/log/mail.warn
/var/log/mail.err
/var/log/mail.log
/var/log/daemon.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/lpr.log
/var/log/cron.log
/var/log/debug
/var/log/messages
{
rotate 4
weekly
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
reload rsyslog >/dev/null 2>&1 || true
endscript
}

manager@trac:/var/log$ cat 

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Thomas A. F. Thorne]

I hit this today.  `df -h` confirmed my /boot was quite full (15MB
left).  Running `sudo purge-old-kernels` (from the bikeshed package)
cleared out some things and brought the free space on /boot up to 93MB.

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

-- 
Mailing list: https://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 1060081] Re: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte

[Thomas A. F. Thorne]

Tripped over this again today.

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

Title:
  aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8'
  codec can't decode byte 0x93 in position 1: invalid start byte

Status in apt package in Ubuntu:
  Triaged
Status in aptdaemon package in Ubuntu:
  Triaged
Status in apt package in Debian:
  Fix Released

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: aptdaemon 0.45+bzr861-0ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  2 06:17:45 2012
  ExecutablePath: /usr/sbin/aptd
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.2 /usr/sbin/aptd
  ProcEnviron:
   
  PythonArgs: ['/usr/sbin/aptd']
  SourcePackage: aptdaemon
  Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' 
codec can't decode byte 0x93 in position 1: invalid start byte
  UpgradeStatus: Upgraded to quantal on 2012-09-22 (9 days ago)
  UserGroups:

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

-- 
Mailing list: https://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 1235177] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

[Thomas A. F. Thorne]

Seen again today and I like Michael suspect this might be a duplicate of
bug #1195662.  That would add another 6 duplicates to the other bug and
up its heat by 36  and give it 11 more affected people which is another
44.  That would give a total heat of 156+36+44=236.  That would even be
enough to get it near the heady heights of a privately marked bug.

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

Title:
  evolution-source-registry crashed with SIGSEGV in
  magazine_chain_pop_head()

Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Crashed after me ignoring authentication error from online accounts
  where 13.10 Beta keeps losing auth. because of 2-factor

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: evolution-data-server 3.8.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  4 12:16:16 2013
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2011-06-19 (838 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  SegvAnalysis:
   Segfault happened at: 0x7f3065c7e9ba :mov
0x8(%rdx),%rbx
   PC (0x7f3065c7e9ba) ok
   source "0x8(%rdx)" (0x7f30696d10a0e8) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_from_bytes () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: Upgraded to saucy on 2013-09-26 (7 days ago)
  UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare scanner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1235177/+subscriptions

-- 
Mailing list: https://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 1543591] Re: python2.7 crashed with SIGSEGV in gdk_pixbuf_get_from_drawable() possibly after starting WftO from Steam

[Thomas A. F. Thorne]

I have looked through the logs and traces and cannot see anything
sensitive in them.  Setting this to public as I cannot see a reason to
keep it private.

** Information type changed from Private to Public

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

Title:
  python2.7 crashed with SIGSEGV in gdk_pixbuf_get_from_drawable()
  possibly after starting WftO from Steam

Status in python2.7 package in Ubuntu:
  Incomplete

Bug description:
  I had finished reporting bug #1543585 so I restarted Steam and
  attempted to restart WftO.  This time the game loaded without an issue
  and I was able to play it.  Nothing seemed wrong with the Steam
  interface either.  This seemed someone different to before so I chose
  to open a new bug and see what the traces say.

  About Steam shows
  Build: Feb 4 2016, at 12:25:24
  Steam API: v017
  Steam package versions: 1454620878

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: python2.7-minimal 2.7.6-8ubuntu0.2
  ProcVersionSignature: Ubuntu 3.16.0-60.80~14.04.1-generic 3.16.7-ckt22
  Uname: Linux 3.16.0-60-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Feb  9 13:48:31 2016
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2015-03-12 (333 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: python indicator-applet-skype.py
  SegvAnalysis:
   Segfault happened at: 0x5b763d:  mov0x10(%rax),%rdi
   PC (0x005b763d) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: python2.7
  StacktraceTop:
   gdk_pixbuf_get_from_drawable () from 
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
   ?? () from /usr/lib/libwnck-1.so.22
   ?? () from /usr/lib/libwnck-1.so.22
   ?? () from /usr/lib/libwnck-1.so.22
   ?? () from /usr/lib/libwnck-1.so.22
  Title: python2.7 crashed with SIGSEGV in gdk_pixbuf_get_from_drawable()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

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

-- 
Mailing list: https://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 1543585] Re: python2.7 crashed with SIGSEGV in gdk_pixbuf_get_from_drawable() possibly while starting WftO from Steam

[Thomas A. F. Thorne]

I have had a look through the logs and re-traced items.  Nothing looks
that sensitive so I am setting this to public on the belief that there
is no need for it to remain private.

** Information type changed from Private to Public

** Changed in: python2.7 (Ubuntu)
   Status: Invalid => New

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

Title:
  python2.7 crashed with SIGSEGV in gdk_pixbuf_get_from_drawable()
  possibly while starting WftO from Steam

Status in python2.7 package in Ubuntu:
  New

Bug description:
  I was starting up War For The Overworld from the Steam application.
  The game said that Steam had had some sort of error and the game could
  not continue to load.  The game then sat there, seemingly frozen.
  After a short while I exited it and found a report about a Python 2.7
  error waiting to be reported.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: python2.7-minimal 2.7.6-8ubuntu0.2
  ProcVersionSignature: Ubuntu 3.16.0-60.80~14.04.1-generic 3.16.7-ckt22
  Uname: Linux 3.16.0-60-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb  9 13:43:49 2016
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2015-03-12 (333 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: python indicator-applet-skype.py
  SegvAnalysis:
   Segfault happened at: 0x5b763d:  mov0x10(%rax),%rdi
   PC (0x005b763d) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: python2.7
  StacktraceTop:
   gdk_pixbuf_get_from_drawable () from 
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
   ?? () from /usr/lib/libwnck-1.so.22
   ?? () from /usr/lib/libwnck-1.so.22
   ?? () from /usr/lib/libwnck-1.so.22
   ?? () from /usr/lib/libwnck-1.so.22
  Title: python2.7 crashed with SIGSEGV in gdk_pixbuf_get_from_drawable()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

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

-- 
Mailing list: https://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 1543585] Re: python2.7 crashed with SIGSEGV in gdk_pixbuf_get_from_drawable() possibly while starting WftO from Steam

[Thomas A. F. Thorne]

I am confident that I had up to date packages when this bug report was 
generated.  Tracing took almost two weeks, which seems a rather long time to 
me.  Is the tracing service OK?  
In any case this bug is not invalid as it is not spam.  It might be hard to 
investigate but that does not devalue its status.  Setting to New for now.  I 
might be able to reproduce this again in the next few days with the latest 
packages installed.  If I cannot then it may be safe to assume this has been 
resolved.

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

Title:
  python2.7 crashed with SIGSEGV in gdk_pixbuf_get_from_drawable()
  possibly while starting WftO from Steam

Status in python2.7 package in Ubuntu:
  New

Bug description:
  I was starting up War For The Overworld from the Steam application.
  The game said that Steam had had some sort of error and the game could
  not continue to load.  The game then sat there, seemingly frozen.
  After a short while I exited it and found a report about a Python 2.7
  error waiting to be reported.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: python2.7-minimal 2.7.6-8ubuntu0.2
  ProcVersionSignature: Ubuntu 3.16.0-60.80~14.04.1-generic 3.16.7-ckt22
  Uname: Linux 3.16.0-60-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb  9 13:43:49 2016
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2015-03-12 (333 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: python indicator-applet-skype.py
  SegvAnalysis:
   Segfault happened at: 0x5b763d:  mov0x10(%rax),%rdi
   PC (0x005b763d) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: python2.7
  StacktraceTop:
   gdk_pixbuf_get_from_drawable () from 
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
   ?? () from /usr/lib/libwnck-1.so.22
   ?? () from /usr/lib/libwnck-1.so.22
   ?? () from /usr/lib/libwnck-1.so.22
   ?? () from /usr/lib/libwnck-1.so.22
  Title: python2.7 crashed with SIGSEGV in gdk_pixbuf_get_from_drawable()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

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

-- 
Mailing list: https://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 1195662] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

[Thomas A. F. Thorne]

Seen again today.

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

Title:
  evolution-source-registry crashed with SIGSEGV in
  magazine_chain_pop_head()

Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Crashed at login

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: evolution-data-server 3.8.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic x86_64
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: amd64
  Date: Fri Jun 28 19:52:38 2013
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2013-06-22 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   LANG=en_AU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f6da1c4375a :mov
0x8(%rdx),%rbx
   PC (0x7f6da1c4375a) ok
   source "0x8(%rdx)" (0x15c11207f) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_bytes_new_with_free_func () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_byte () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1195662/+subscriptions

-- 
Mailing list: https://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 1527495] Re: evolution-source-registry crashed with SIGSEGV in g_slice_alloc() after closing evolution

[Thomas A. F. Thorne]

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

Seen again today.  As before #1195662 and Bug #1235177 were offered as
suggestions but bug #1279108 was not.  Can anyone that is able to view
all four of these bugs make a judgement on whether the first two are in
fact a duplicate of the latter as this one is?

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

Title:
  evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  after closing evolution

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Yesterday I closed Evolution down.  This morning when I got back into
  the office and login to my Ubuntu machine (after leaving it locked
  overnight) I get a report about a problem.  I was prompted about bug
  #1195662 and bug #1235177 being similar, however neither of those seem
  to have had any activity in a year.  Also this has now occurred on a
  more recent version of Ubuntu so I felt fresh diagnostic files may be
  helpful.  Please make this bug a duplicate of something if it looks to
  be one.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution-data-server 3.10.4-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.16.0-56.75~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-56-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec 18 04:21:15 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-03-12 (280 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  SegvAnalysis:
   Segfault happened at: 0x7fb9d8a1628a :mov
0x8(%rdx),%rbx
   PC (0x7fb9d8a1628a) ok
   source "0x8(%rdx)" (0x7fb9b802159008) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_dict_entry () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1527495/+subscriptions

-- 
Mailing list: https://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 1235177] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

[Thomas A. F. Thorne]

Seen again today.

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

Title:
  evolution-source-registry crashed with SIGSEGV in
  magazine_chain_pop_head()

Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Crashed after me ignoring authentication error from online accounts
  where 13.10 Beta keeps losing auth. because of 2-factor

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: evolution-data-server 3.8.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  4 12:16:16 2013
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2011-06-19 (838 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  SegvAnalysis:
   Segfault happened at: 0x7f3065c7e9ba :mov
0x8(%rdx),%rbx
   PC (0x7f3065c7e9ba) ok
   source "0x8(%rdx)" (0x7f30696d10a0e8) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_from_bytes () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: Upgraded to saucy on 2013-09-26 (7 days ago)
  UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare scanner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1235177/+subscriptions

-- 
Mailing list: https://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 1527495] Re: evolution-source-registry crashed with SIGSEGV in g_slice_alloc() after closing evolution

[Thomas A. F. Thorne]

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

So I have tripped over the same problem again, but this time only Bug
#1195662  and Bug #1235177 were offered as suggestions.  Bug #1527495
that I raised a while ago was not seen as a likely similarity.

It seems that I am able to periodically reproduce a problem, whether it
is one of the three bugs listed above or the possibly mythical bug
#1279108 I cannot say.  However if there are any investigative steps I
can take or work arounds to try please do get in touch.

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

Title:
  evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  after closing evolution

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Yesterday I closed Evolution down.  This morning when I got back into
  the office and login to my Ubuntu machine (after leaving it locked
  overnight) I get a report about a problem.  I was prompted about bug
  #1195662 and bug #1235177 being similar, however neither of those seem
  to have had any activity in a year.  Also this has now occurred on a
  more recent version of Ubuntu so I felt fresh diagnostic files may be
  helpful.  Please make this bug a duplicate of something if it looks to
  be one.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution-data-server 3.10.4-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.16.0-56.75~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-56-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec 18 04:21:15 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-03-12 (280 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  SegvAnalysis:
   Segfault happened at: 0x7fb9d8a1628a :mov
0x8(%rdx),%rbx
   PC (0x7fb9d8a1628a) ok
   source "0x8(%rdx)" (0x7fb9b802159008) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_dict_entry () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1527495/+subscriptions

-- 
Mailing list: https://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 1235177] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

[Thomas A. F. Thorne]

So I have tripped over the same problem again, but this time only Bug
#1195662  and Bug #1235177 were offered as suggestions.  Bug #1527495
that I raised a while ago was not seen as a likely similarity.

It seems that I am able to periodically reproduce a problem, whether it
is one of the three bugs listed above or the possibly mythical bug
#1279108 I cannot say.  However if there are any investigative steps I
can take or work arounds to try please do get in touch.

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

Title:
  evolution-source-registry crashed with SIGSEGV in
  magazine_chain_pop_head()

Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Crashed after me ignoring authentication error from online accounts
  where 13.10 Beta keeps losing auth. because of 2-factor

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: evolution-data-server 3.8.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  4 12:16:16 2013
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2011-06-19 (838 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  SegvAnalysis:
   Segfault happened at: 0x7f3065c7e9ba :mov
0x8(%rdx),%rbx
   PC (0x7f3065c7e9ba) ok
   source "0x8(%rdx)" (0x7f30696d10a0e8) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_from_bytes () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: Upgraded to saucy on 2013-09-26 (7 days ago)
  UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare scanner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1235177/+subscriptions

-- 
Mailing list: https://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 1195662] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

[Thomas A. F. Thorne]

So I have tripped over the same problem again, but this time only Bug
#1195662  and Bug #1235177 were offered as suggestions.  Bug #1527495
that I raised a while ago was not seen as a likely similarity.

It seems that I am able to periodically reproduce a problem, whether it
is one of the three bugs listed above or the possibly mythical bug
#1279108 I cannot say.  However if there are any investigative steps I
can take or work arounds to try please do get in touch.

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

Title:
  evolution-source-registry crashed with SIGSEGV in
  magazine_chain_pop_head()

Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Crashed at login

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: evolution-data-server 3.8.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic x86_64
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: amd64
  Date: Fri Jun 28 19:52:38 2013
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2013-06-22 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   LANG=en_AU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f6da1c4375a :mov
0x8(%rdx),%rbx
   PC (0x7f6da1c4375a) ok
   source "0x8(%rdx)" (0x15c11207f) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_bytes_new_with_free_func () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_byte () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1195662/+subscriptions

-- 
Mailing list: https://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 1195662] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

[Thomas A. F. Thorne]

I have just raised Bug #1527495 which was initially suggested as a
possible duplicate of this bug and Bug #1235177.  Now that apport has
done its thing my new bug has been marked as a duplicate of bug #1279108
which could suggest that this bug is also a duplicate of that one.

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

Title:
  evolution-source-registry crashed with SIGSEGV in
  magazine_chain_pop_head()

Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Crashed at login

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: evolution-data-server 3.8.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic x86_64
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: amd64
  Date: Fri Jun 28 19:52:38 2013
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2013-06-22 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   LANG=en_AU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f6da1c4375a :mov
0x8(%rdx),%rbx
   PC (0x7f6da1c4375a) ok
   source "0x8(%rdx)" (0x15c11207f) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_bytes_new_with_free_func () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_byte () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1195662/+subscriptions

-- 
Mailing list: https://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 1235177] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

[Thomas A. F. Thorne]

I have just raised Bug #1527495 which was initially suggested as a
possible duplicate of this bug and Bug #1195662.  Now that apport has
done its thing my new bug has been marked as a duplicate of bug #1279108
which could suggest that this bug is also a duplicate of that one.

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

Title:
  evolution-source-registry crashed with SIGSEGV in
  magazine_chain_pop_head()

Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Crashed after me ignoring authentication error from online accounts
  where 13.10 Beta keeps losing auth. because of 2-factor

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: evolution-data-server 3.8.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  4 12:16:16 2013
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2011-06-19 (838 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  SegvAnalysis:
   Segfault happened at: 0x7f3065c7e9ba :mov
0x8(%rdx),%rbx
   PC (0x7f3065c7e9ba) ok
   source "0x8(%rdx)" (0x7f30696d10a0e8) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_from_bytes () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: Upgraded to saucy on 2013-09-26 (7 days ago)
  UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare scanner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1235177/+subscriptions

-- 
Mailing list: https://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 1527495] Re: evolution-source-registry crashed with SIGSEGV in g_slice_alloc() after closing evolution

[Thomas A. F. Thorne]

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

I have added a comment to each of the similar bugs (bug #1195662 and bug
#1235177) mentioning that they may also be a bug of bug #1279108.  Sadly
bug #1279108 "Cannot be found" by me, which is usually a sign that it
has been left marked as Private.  There ends my possible involvement in
the diagnosis unless someone reading this can evaluate bug #1279108 and
either state that this bug is not a duplicate of it or remove the
Private stamp from bug #1279108.

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

Title:
  evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  after closing evolution

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Yesterday I closed Evolution down.  This morning when I got back into
  the office and login to my Ubuntu machine (after leaving it locked
  overnight) I get a report about a problem.  I was prompted about bug
  #1195662 and bug #1235177 being similar, however neither of those seem
  to have had any activity in a year.  Also this has now occurred on a
  more recent version of Ubuntu so I felt fresh diagnostic files may be
  helpful.  Please make this bug a duplicate of something if it looks to
  be one.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution-data-server 3.10.4-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.16.0-56.75~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-56-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec 18 04:21:15 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-03-12 (280 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  SegvAnalysis:
   Segfault happened at: 0x7fb9d8a1628a :mov
0x8(%rdx),%rbx
   PC (0x7fb9d8a1628a) ok
   source "0x8(%rdx)" (0x7fb9b802159008) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_dict_entry () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1527495/+subscriptions

-- 
Mailing list: https://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 1527495] Re: evolution-source-registry crashed with SIGSEGV in g_slice_alloc() after closing evolution

[Thomas A. F. Thorne]

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

Weirdly the top of this bug report currently states it is a duplicate of
nothing.  I take it that is a launchpad but, as other bits of launchpad
manage to state it is a duplicate of bug #1279108 (which I don't seem to
have permissions to view).  I will search for or raise a launchpad bug
about this.

** Attachment added: "Duplicate of: "
   
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1527495/+attachment/4536649/+files/DuplicateOfNothing

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

Title:
  evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  after closing evolution

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Yesterday I closed Evolution down.  This morning when I got back into
  the office and login to my Ubuntu machine (after leaving it locked
  overnight) I get a report about a problem.  I was prompted about bug
  #1195662 and bug #1235177 being similar, however neither of those seem
  to have had any activity in a year.  Also this has now occurred on a
  more recent version of Ubuntu so I felt fresh diagnostic files may be
  helpful.  Please make this bug a duplicate of something if it looks to
  be one.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution-data-server 3.10.4-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.16.0-56.75~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-56-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec 18 04:21:15 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-03-12 (280 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  SegvAnalysis:
   Segfault happened at: 0x7fb9d8a1628a :mov
0x8(%rdx),%rbx
   PC (0x7fb9d8a1628a) ok
   source "0x8(%rdx)" (0x7fb9b802159008) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_dict_entry () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1527495/+subscriptions

-- 
Mailing list: https://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 1527495] Re: evolution-source-registry crashed with SIGSEGV in g_slice_alloc() after closing evolution

[Thomas A. F. Thorne]

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

I could not find an open bug for launchpad that seemed to describe the
problem with the blank after the This bug report is a duplicate of:
message so I have raised
https://bugs.launchpad.net/launchpad/+bug/1527529 (which I guess might
be bug #1527529 if bug numbers are universal between projects and
packages.

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

Title:
  evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  after closing evolution

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Yesterday I closed Evolution down.  This morning when I got back into
  the office and login to my Ubuntu machine (after leaving it locked
  overnight) I get a report about a problem.  I was prompted about bug
  #1195662 and bug #1235177 being similar, however neither of those seem
  to have had any activity in a year.  Also this has now occurred on a
  more recent version of Ubuntu so I felt fresh diagnostic files may be
  helpful.  Please make this bug a duplicate of something if it looks to
  be one.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution-data-server 3.10.4-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.16.0-56.75~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-56-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec 18 04:21:15 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-03-12 (280 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  SegvAnalysis:
   Segfault happened at: 0x7fb9d8a1628a :mov
0x8(%rdx),%rbx
   PC (0x7fb9d8a1628a) ok
   source "0x8(%rdx)" (0x7fb9b802159008) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_dict_entry () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1527495/+subscriptions

-- 
Mailing list: https://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 1060081] Re: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte

[Thomas A. F. Thorne]

I hit this today while using apt 1.0.1ubuntu2 for amd64 compiled on Aug  1 2015 
19:20:48.  The Debian bug says that this has been fixed in apt/1.1~exp4 and 
apt/1.0.9.8.  Any chance of these getting pulled into Ubuntu LTS to avoid this 
ongoing crash?  
Is there anything I could try and do on my system to avoid hitting this?

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

Title:
  aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8'
  codec can't decode byte 0x93 in position 1: invalid start byte

Status in apt package in Ubuntu:
  Triaged
Status in aptdaemon package in Ubuntu:
  Triaged
Status in apt package in Debian:
  Fix Released

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: aptdaemon 0.45+bzr861-0ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  2 06:17:45 2012
  ExecutablePath: /usr/sbin/aptd
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.2 /usr/sbin/aptd
  ProcEnviron:
   
  PythonArgs: ['/usr/sbin/aptd']
  SourcePackage: aptdaemon
  Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' 
codec can't decode byte 0x93 in position 1: invalid start byte
  UpgradeStatus: Upgraded to quantal on 2012-09-22 (9 days ago)
  UserGroups:

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

-- 
Mailing list: https://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 1200819] Re: evolution-source-registry crashed with SIGSEGV in g_hash_table_lookup_node()

[Thomas A. F. Thorne]

I raised bug #1509269 and apport has marked it as a duplicate of this one.  Are 
there any steps I should take to help with diagnosis?  
Originally I was commenting on bug #1494804 but it was suggested that what I 
was seeing was not the same bug.  I ran the application under valgrind, with 
the results posted to bug #1494804 earlier in the week.

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

Title:
  evolution-source-registry crashed with SIGSEGV in
  g_hash_table_lookup_node()

Status in libaccounts-glib package in Ubuntu:
  Confirmed

Bug description:
  Maybe crashed at login trying to connect to calendar for the
  indicator-datetime

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: evolution-data-server 3.8.3-0ubuntu5
  ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Jul 13 10:26:04 2013
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2013-06-22 (20 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   LANG=en_AU.UTF-8
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ag_auth_data_get_login_parameters () from 
/usr/lib/x86_64-linux-gnu/libaccounts-glib.so.0
   ?? () from 
/usr/lib/evolution-data-server/registry-modules/module-ubuntu-online-accounts.so
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_hash_table_lookup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libaccounts-glib/+bug/1200819/+subscriptions

-- 
Mailing list: https://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 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

[Thomas A. F. Thorne]

I raised Bug #1509269 which apport marked as a duplicate of Bug
#1200819.

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

Title:
  evolution-source-registry crashed with SIGABRT in
  g_assertion_message()

Status in evolution-data-server:
  Incomplete
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Random crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: evolution-data-server 3.16.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 11 16:29:44 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150911)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  Signal: 6
  SourcePackage: evolution-data-server
  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
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   e_source_get_extension () from /usr/lib/libedataserver-1.2.so.20
   ?? () from /usr/lib/libebackend-1.2.so.10
  Title: evolution-source-registry crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1494804/+subscriptions

-- 
Mailing list: https://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 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

[Thomas A. F. Thorne]

I don't quite understand that part about "seems like you didn't active
ddeb for trusty-updates".  Do you mean that there are some steps I need
to take to enable the installation of debug symbols for packages that
come from trusty-updates?

If it is likely that this is a different issue, I can raise a new bug
report.  I seem to still have the /var/crash
/_usr_lib_evolution_evolution-source-registry.1000.crash file from the
19th so I will try and file a report from that.

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

Title:
  evolution-source-registry crashed with SIGABRT in
  g_assertion_message()

Status in evolution-data-server:
  Incomplete
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Random crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: evolution-data-server 3.16.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 11 16:29:44 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150911)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  Signal: 6
  SourcePackage: evolution-data-server
  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
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   e_source_get_extension () from /usr/lib/libedataserver-1.2.so.20
   ?? () from /usr/lib/libebackend-1.2.so.10
  Title: evolution-source-registry crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1494804/+subscriptions

-- 
Mailing list: https://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 1509269] [NEW] evolution-source-registry crashed with SIGSEGV in g_hash_table_lookup()

[Thomas A. F. Thorne]

Public bug reported:

Raising a new bug after discussions on Bug #1494804 suggested that this
was a different issue as the one documented under #1494804 originated in
15.10.

I don't know what I did to stimulate the problem.  An error report
prompt appeared one day.


I'll answer the same questions from Bug #1494804 here in case they are 
relevant.  

> what accounts he/she has configured, whether any are from Ubuntu
Online Accounts or GNOME Online Accounts?

I have a personal GoogleMail imapx account created though the Online
Accounts Service and an ews OWA account linked to my work exchange
server.

> whether it crashes also when he/she runs the evolution-source-registry
from a terminal manually?

It seems to have worked OK when I ran 
/usr/lib/evolution/evolution-source-registry. The output I can see is as follow 
(with my addresses changed manually to t...@work-domain.com & 
t...@googlemail.com):
$ /usr/lib/evolution/evolution-source-registry
Migrating mail accounts from GConf...
Migrating addressbook sources from GConf...
Migrating calendar sources from GConf...
Migrating task list sources from GConf...
Migrating memo list sources from GConf...
Registering EGoogleBackendFactory ('google')
Registering EOutlookBackendFactory ('outlook')
Registering EYahooBackendFactory ('yahoo')
Registering EOwncloudBackendFactory ('owncloud')
Registering EEwsBackendFactory ('ews')
Registering EMapiBackendFactory ('mapi')
Registering ECollectionBackendFactory ('none')
Adding 1433155791.2289.1@thorne-ul-dt ('Source')
Adding vfolder ('Source_1')
Adding 1433325395.16396.0@thorne-ul-dt ('Source_2')
OWA t...@work-domain.com: Pairing 1434544712.3155.0@thorne-ul-dt with resource 
e82c1433-e2e3-4cbf-a933-0f1e68930f98:Global Address List
Adding 1434544712.3155.0@thorne-ul-dt ('Source_3')
Adding 1434381690.5760.2@thorne-ul-dt ('Source_4')
Adding 1434381690.5760.17@thorne-ul-dt ('Source_5')
Adding 1437989181.5803.1@thorne-ul-dt ('Source_6')
Adding 1434381690.5760.0@thorne-ul-dt ('Source_7')
Adding 1432804779.11643.0@thorne-ul-dt ('Source_8')
Adding 1434381690.5760.5@thorne-ul-dt ('Source_9')
Adding 1432718461.14988.73@thorne-ul-dt ('Source_10')
Adding 1432718462.14988.82@thorne-ul-dt ('Source_11')
Adding 1432718461.14988.68@thorne-ul-dt ('Source_12')
Adding 1432889488.2725.0@thorne-ul-dt ('Source_13')
Adding 1432889488.2725.2@thorne-ul-dt ('Source_14')
Adding 1432889488.2725.3@thorne-ul-dt ('Source_15')
Adding 1432640797.18834.16@thorne-ul-dt ('Source_16')
Adding 1432640797.18834.14@thorne-ul-dt ('Source_17')
Adding 1432640791.18834.0@thorne-ul-dt ('Source_18')
Adding local ('Source_19')
Adding 1432889488.2725.1@thorne-ul-dt ('Source_20')
Adding 1432640791.18834.4@thorne-ul-dt ('Source_21')
Adding 1433155649.2289.0@thorne-ul-dt ('Source_22')
Adding caldav-stub ('Source_23')
Adding contacts-stub ('Source_24')
Adding birthdays ('Source_25')
Adding google-stub ('Source_26')
Adding ldap-stub ('Source_27')
Adding local-stub ('Source_28')
Adding system-calendar ('Source_29')
Adding system-address-book ('Source_30')
Adding weather-stub ('Source_31')
Adding webcal-stub ('Source_32')
Adding webdav-stub ('Source_33')
Adding sendmail ('Source_34')
Adding system-memo-list ('Source_35')
Adding system-task-list ('Source_36')
module-cache-reaper-Message: Scanning data directories
module-cache-reaper-Message: Scanning cache directories
Server is up and running...
AUTH (1434381690.5760.2@thorne-ul-dt): Initiated
Bus name 'org.gnome.evolution.dataserver.Sources2' acquired.
t...@googlemail.com: Pairing 1432889488.2725.4@thorne-ul-dt with resource 
Calendar
Adding 1432889488.2725.4@thorne-ul-dt ('Source_37')
t...@googlemail.com: Pairing 1432889488.2725.5@thorne-ul-dt with resource 
Contacts
Adding 1432889488.2725.5@thorne-ul-dt ('Source_38')
t...@googlemail.com: Pairing 1432640844.2689.0@thorne-ul-dt with resource 
Calendar
Adding 1432640844.2689.0@thorne-ul-dt ('Source_39')
t...@googlemail.com: Pairing 1432640844.2689.1@thorne-ul-dt with resource 
Contacts
Adding 1432640844.2689.1@thorne-ul-dt ('Source_40')
AUTH (1432640797.18834.16@thorne-ul-dt): Initiated
AUTH (1434381690.5760.2@thorne-ul-dt): Complete (SUCCESS)
AUTH (1434381690.5760.2@thorne-ul-dt): Initiated
AUTH (1432640797.18834.16@thorne-ul-dt): Complete (SUCCESS)
OWA t...@work-domain.com: Pairing 1434382914.8424.11@thorne-ul-dt with resource 
AQMkAGIyMTMwOGY0LTI2MzItNDU5My05Y2I4LWVhNjNhYjg1YmYwMAAALgAAA+FP9N9wssFJj6t++ut4zlABABYLVCVV+HBMs/5Q8mHfMpkAAAMs
Adding 1434382914.8424.11@thorne-ul-dt ('Source_41')
OWA t...@work-domain.com: Pairing 1434382914.8424.12@thorne-ul-dt with resource 
AQMkAGIyMTMwOGY0LTI2MzItNDU5My05Y2I4LWVhNjNhYjg1YmYwMAAALgAAA+FP9N9wssFJj6t++ut4zlABABYLVCVV+HBMs/5Q8mHfMpkAAAMt
Adding 1434382914.8424.12@thorne-ul-dt ('Source_42')
OWA t...@work-domain.com: Pairing 1434382914.8424.13@thorne-ul-dt with resource 
AAMkAGIyMTMwOGY0LTI2MzItNDU5My05Y2I4LWVhNjNhYjg1YmYwMAAuAADhT/TfcLLBSY+rfvrreM5QAQAGKp/LPBeQR4xLDDWtTzVlFwAgAAA=
Adding 

[Touch-packages] [Bug 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

[Thomas A. F. Thorne]

Not so easily it seems.

$ sudo aptitude install libaccounts-glib0-dbgsym 
evolution-data-server-online-accounts-dbgsym libglib2.0-0-dbgsym
The following NEW packages will be installed:
  evolution-data-server-online-accounts-dbgsym{b} libaccounts-glib0-dbgsym 
libglib2.0-0-dbgsym{b} 
0 packages upgraded, 3 newly installed, 0 to remove and 8 not upgraded.
Need to get 96.7 kB of archives. After unpacking 414 kB will be used.
The following packages have unmet dependencies:
 evolution-data-server-online-accounts-dbgsym : Depends: 
evolution-data-server-dbg (= 3.10.4-0ubuntu1) but it is not going to be 
installed.
 libglib2.0-0-dbgsym : Depends: libglib2.0-0-dbg (= 2.40.0-2) but it is not 
going to be installed.
The following actions will resolve these dependencies:

 Keep the following packages at their current version: 
1) evolution-data-server-online-accounts-dbgsym [Not Installed]
2) libglib2.0-0-dbgsym [Not Installed] 


Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

  Remove the following packages:
  
1)  libelfg0
  
2)  libglib2.0-bin  
  

  Install the following packages:   
  
3)  evolution-data-server-dbg [3.10.4-0ubuntu1 (trusty)]
  
4)  libelfg0:i386 [0.8.13-4~1 (raring)] 
  
5)  libglib2.0-0-dbg [2.40.0-2 (trusty)]
  
6)  libglib2.0-bin:i386 [2.40.0-2 (trusty)] 
  

  Downgrade the following packages: 
  
7)  evolution-data-server [3.10.4-0ubuntu1.5 (now, trusty-updates) -> 
3.10.4-0ubuntu1 (trusty)]   
8)  evolution-data-server-common [3.10.4-0ubuntu1.5 (now, trusty-updates) 
-> 3.10.4-0ubuntu1 (trus
9)  evolution-data-server-online-accounts [3.10.4-0ubuntu1.5 (now, 
trusty-updates) -> 3.10.4-0ubun
10) libcamel-1.2-45 [3.10.4-0ubuntu1.5 (now, trusty-updates) -> 
3.10.4-0ubuntu1 (trusty)] 
11) libglib2.0-0 [2.40.2-0ubuntu1 (now, trusty-updates) -> 2.40.0-2 
(trusty)] 
12) libglib2.0-0:i386 [2.40.2-0ubuntu1 (now, trusty-updates) -> 2.40.0-2 
(trusty)]


Accept this solution? [Y/n/q/?]


Would something like the suggested set of downgrades be acceptable or would it 
change too much that possibly relates to the issue.

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

Title:
  evolution-source-registry crashed with SIGABRT in
  g_assertion_message()

Status in evolution-data-server:
  Incomplete
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Random crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: evolution-data-server 3.16.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 11 16:29:44 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150911)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  Signal: 6
  SourcePackage: evolution-data-server
  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
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   e_source_get_extension () from /usr/lib/libedataserver-1.2.so.20
   ?? () from /usr/lib/libebackend-1.2.so.10
  Title: evolution-source-registry crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1494804/+subscriptions

-- 
Mailing list: https://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 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

[Thomas A. F. Thorne]

I had evolution-source-registry running for a while without noticing the
error reproducing itself.

The only output that looks suspect is: 
Adding system-memo-list ('Source_35')
Adding system-task-list ('Source_36')
module-cache-reaper-Message: Scanning data directories
module-cache-reaper-Message: Scanning cache directories
Server is up and running...
AUTH (1434381690.5760.2@thorne-ul-dt): Initiated
==11889== Conditional jump or move depends on uninitialised value(s)
==11889==at 0xC7FF0DD: ag_auth_data_unref (in 
/usr/lib/x86_64-linux-gnu/libaccounts-glib.so.0.1.3)
==11889==by 0xC5EC83E: ??? (in 
/usr/lib/evolution-data-server/registry-modules/module-ubuntu-online-accounts.so)
==11889==by 0xC5ECB72: ??? (in 
/usr/lib/evolution-data-server/registry-modules/module-ubuntu-online-accounts.so)
==11889==by 0xC5ED31C: ??? (in 
/usr/lib/evolution-data-server/registry-modules/module-ubuntu-online-accounts.so)
==11889==by 0x5F403B7: g_closure_invoke (in 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4002.0)
==11889==by 0x5F51FD0: ??? (in 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4002.0)
==11889==by 0x5F59A28: g_signal_emit_valist (in 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4002.0)
==11889==by 0x5F59CE1: g_signal_emit (in 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4002.0)
==11889==by 0x5C8EA63: ??? (in 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4002.0)
==11889==by 0x5C2E3B6: g_simple_async_result_complete (in 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4002.0)
==11889==by 0x5C2E418: ??? (in 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4002.0)
==11889==by 0x61C9CE4: g_main_context_dispatch (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4002.0)
==11889== 
==11889== Conditional jump or move depends on uninitialised value(s)

As I know jumping to memory based on what could be uninitialised
variables is a bad thing.  It seems possible that the tool is mistaken
about the initialisation though.

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

Title:
  evolution-source-registry crashed with SIGABRT in
  g_assertion_message()

Status in evolution-data-server:
  Incomplete
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Random crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: evolution-data-server 3.16.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 11 16:29:44 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150911)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  Signal: 6
  SourcePackage: evolution-data-server
  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
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   e_source_get_extension () from /usr/lib/libedataserver-1.2.so.20
   ?? () from /usr/lib/libebackend-1.2.so.10
  Title: evolution-source-registry crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1494804/+subscriptions

-- 
Mailing list: https://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 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

[Thomas A. F. Thorne]

I seem to be seeing this now.  The other suggested possibilities when
reporting were bugz #1200934, #1200819 & #1383852.  I can see on this
bug that some questions were posed.

> what accounts he/she has configured, whether any are from Ubuntu Online 
> Accounts or GNOME Online Accounts?
I have a personal GoogleMail imapx account created though the Online Accounts 
Service and an ews OWA account linked to my work exchange server.  

> whether it crashes also when he/she runs the evolution-source-registry  from 
> a terminal manually?
It seems to have worked OK when I ran 
/usr/lib/evolution/evolution-source-registry.  The output I can see is as 
follow (with my addresses changed manually to t...@work-domain.com & 
t...@googlemail.com): 
$ /usr/lib/evolution/evolution-source-registry
Migrating mail accounts from GConf...
Migrating addressbook sources from GConf...
Migrating calendar sources from GConf...
Migrating task list sources from GConf...
Migrating memo list sources from GConf...
Registering EGoogleBackendFactory ('google')
Registering EOutlookBackendFactory ('outlook')
Registering EYahooBackendFactory ('yahoo')
Registering EOwncloudBackendFactory ('owncloud')
Registering EEwsBackendFactory ('ews')
Registering EMapiBackendFactory ('mapi')
Registering ECollectionBackendFactory ('none')
Adding 1433155791.2289.1@thorne-ul-dt ('Source')
Adding vfolder ('Source_1')
Adding 1433325395.16396.0@thorne-ul-dt ('Source_2')
OWA t...@work-domain.com: Pairing 1434544712.3155.0@thorne-ul-dt with resource 
e82c1433-e2e3-4cbf-a933-0f1e68930f98:Global Address List
Adding 1434544712.3155.0@thorne-ul-dt ('Source_3')
Adding 1434381690.5760.2@thorne-ul-dt ('Source_4')
Adding 1434381690.5760.17@thorne-ul-dt ('Source_5')
Adding 1437989181.5803.1@thorne-ul-dt ('Source_6')
Adding 1434381690.5760.0@thorne-ul-dt ('Source_7')
Adding 1432804779.11643.0@thorne-ul-dt ('Source_8')
Adding 1434381690.5760.5@thorne-ul-dt ('Source_9')
Adding 1432718461.14988.73@thorne-ul-dt ('Source_10')
Adding 1432718462.14988.82@thorne-ul-dt ('Source_11')
Adding 1432718461.14988.68@thorne-ul-dt ('Source_12')
Adding 1432889488.2725.0@thorne-ul-dt ('Source_13')
Adding 1432889488.2725.2@thorne-ul-dt ('Source_14')
Adding 1432889488.2725.3@thorne-ul-dt ('Source_15')
Adding 1432640797.18834.16@thorne-ul-dt ('Source_16')
Adding 1432640797.18834.14@thorne-ul-dt ('Source_17')
Adding 1432640791.18834.0@thorne-ul-dt ('Source_18')
Adding local ('Source_19')
Adding 1432889488.2725.1@thorne-ul-dt ('Source_20')
Adding 1432640791.18834.4@thorne-ul-dt ('Source_21')
Adding 1433155649.2289.0@thorne-ul-dt ('Source_22')
Adding caldav-stub ('Source_23')
Adding contacts-stub ('Source_24')
Adding birthdays ('Source_25')
Adding google-stub ('Source_26')
Adding ldap-stub ('Source_27')
Adding local-stub ('Source_28')
Adding system-calendar ('Source_29')
Adding system-address-book ('Source_30')
Adding weather-stub ('Source_31')
Adding webcal-stub ('Source_32')
Adding webdav-stub ('Source_33')
Adding sendmail ('Source_34')
Adding system-memo-list ('Source_35')
Adding system-task-list ('Source_36')
module-cache-reaper-Message: Scanning data directories
module-cache-reaper-Message: Scanning cache directories
Server is up and running...
AUTH (1434381690.5760.2@thorne-ul-dt): Initiated
Bus name 'org.gnome.evolution.dataserver.Sources2' acquired.
t...@googlemail.com: Pairing 1432889488.2725.4@thorne-ul-dt with resource 
Calendar
Adding 1432889488.2725.4@thorne-ul-dt ('Source_37')
t...@googlemail.com: Pairing 1432889488.2725.5@thorne-ul-dt with resource 
Contacts
Adding 1432889488.2725.5@thorne-ul-dt ('Source_38')
t...@googlemail.com: Pairing 1432640844.2689.0@thorne-ul-dt with resource 
Calendar
Adding 1432640844.2689.0@thorne-ul-dt ('Source_39')
t...@googlemail.com: Pairing 1432640844.2689.1@thorne-ul-dt with resource 
Contacts
Adding 1432640844.2689.1@thorne-ul-dt ('Source_40')
AUTH (1432640797.18834.16@thorne-ul-dt): Initiated
AUTH (1434381690.5760.2@thorne-ul-dt): Complete (SUCCESS)
AUTH (1434381690.5760.2@thorne-ul-dt): Initiated
AUTH (1432640797.18834.16@thorne-ul-dt): Complete (SUCCESS)
OWA t...@work-domain.com: Pairing 1434382914.8424.11@thorne-ul-dt with resource 
AQMkAGIyMTMwOGY0LTI2MzItNDU5My05Y2I4LWVhNjNhYjg1YmYwMAAALgAAA+FP9N9wssFJj6t++ut4zlABABYLVCVV+HBMs/5Q8mHfMpkAAAMs
Adding 1434382914.8424.11@thorne-ul-dt ('Source_41')
OWA t...@work-domain.com: Pairing 1434382914.8424.12@thorne-ul-dt with resource 
AQMkAGIyMTMwOGY0LTI2MzItNDU5My05Y2I4LWVhNjNhYjg1YmYwMAAALgAAA+FP9N9wssFJj6t++ut4zlABABYLVCVV+HBMs/5Q8mHfMpkAAAMt
Adding 1434382914.8424.12@thorne-ul-dt ('Source_42')
OWA t...@work-domain.com: Pairing 1434382914.8424.13@thorne-ul-dt with resource 
AAMkAGIyMTMwOGY0LTI2MzItNDU5My05Y2I4LWVhNjNhYjg1YmYwMAAuAADhT/TfcLLBSY+rfvrreM5QAQAGKp/LPBeQR4xLDDWtTzVlFwAgAAA=
Adding 1434382914.8424.13@thorne-ul-dt ('Source_43')
OWA t...@work-domain.com: Pairing 1434382914.8424.14@thorne-ul-dt with resource 

[Touch-packages] [Bug 1477631] Re: Xorg crash which returned me to my login screen

[Thomas A. F. Thorne]

I have now performed the BIOS update  by following the links provided and the 
rufus program described at 
http://ubuntuforums.org/showthread.php?t=2266278=13233591#post13233591 
For my Gigabyte H81M-DS2V motherboard you press F12 key during the initial 
power on stages to be given a boot menu.  From that menu it should be possible 
to select a bootable USB device that is connect to the system.  

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
Now produces "/dev/mem: No such file or directory".  Before it showed the old 
release details.  I entered the BIOS menu and confirmed that the BIOS date is 
now August 2015.  

Marking status back to New as requested.  I will post an update if I see
the problem reproduce.


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

Title:
  Xorg crash which returned me to my login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  This looked like the same thing as when Bug #1477574 and Bug #1477566
  happened just now.  I had Chrome, Terminal & Eclipse open on my Ubuntu
  PC and was focused on using my laptop via Synergy.  In my Synergy
  setup the Ubuntu PC is the server and the laptop is the client.

  As in the two bugs I mentioned, the Ubuntu machine seemed to reset
  back to the login screen.  Unlike the last time nothing complained
  about out of date packages this time.  I had not run the upgrade when
  this bug happened.  I have now updated however.

  Yesterday there was a power cut to this building.  I am starting to worry 
about my hardware integrity.  The previous software update I did was at 
2015-07-22  08:15:01, some 29 hours before the first time I saw an issue and 
now I have hit the login screen twice in about 2 hours.  
  Start-Date: 2015-07-22  08:13:51
  Commandline: aptdaemon role='role-commit-packages' sender=':1.712'
  Upgrade: mysql-server-core-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 
5.5.44-0ubuntu0.14.04.1), mysql-server-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 
5.5.44-0ubuntu0.14.04.1), mysql-client-core-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 
5.5.44-0ubuntu0.14.04.1), mysql-client:amd64 (5.5.43-0ubuntu0.14.04.1, 
5.5.44-0ubuntu0.14.04.1), google-chrome-stable:amd64 (43.0.2357.134-1, 
44.0.2403.89-1), thunderbird-locale-en-us:amd64 
(31.7.0+build1-0ubuntu0.14.04.1, 31.8.0+build1-0ubuntu0.14.04.1), 
thunderbird:amd64 (31.7.0+build1-0ubuntu0.14.04.1, 
31.8.0+build1-0ubuntu0.14.04.1), thunderbird-locale-en:amd64 
(31.7.0+build1-0ubuntu0.14.04.1, 31.8.0+build1-0ubuntu0.14.04.1), 
mysql-client-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), 
mysql-common:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), 
thunderbird-gnome-support:amd64 (31.7.0+build1-0ubuntu0.14.04.1, 
31.8.0+build1-0ubuntu0.14.04.1), libmysqlclient18:amd64 
(5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), libmysqlclient18:i386 (5.
 5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), mysql-server:amd64 
(5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1)
  End-Date: 2015-07-22  08:15:01
  Having said that the power-cut was bout 24 hours before the problem was first 
seen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  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: Thu Jul 23 15:30:26 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2015-03-12 (132 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By 

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Thomas A. F. Thorne]

I am not sure when this problem occurred but reading over it it sounds
like it pertains to a lack of space.  I know that my /boot partition has
run out of space several times recently.  I do not know why, as I
thought left the partitioning plan up to Ubuntu when I installed.

I have found that the 
purge-old-kernels
script is very helpful in getting me down to just the kernel images that I am 
using.  It might be worth performing that action too if you are low on space.  
I think the script will come from the main repos, so if you do not have it I 
expect an appropriate 'apg-get install 'prompt will be provided.

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor or manually free space on
  your partition containing the /boot file system.

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

-- 
Mailing list: https://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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Thomas A. F. Thorne]

According to 
https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels the 
purge-old-kernels is part of the bikeshed package.  To install it you will need 
to do:
  sudo apt-get install bikeshed 
To run it you will need to do
  sudo purge-old-kernels
You can confirm if it (and any other tidying up actions) have helped by 
comparing the output of 
  df -h
before and after you run the command.  I usually see my /boot Mounted on point 
go from ~100% Use to ~50% Use.  If you have prombles with disk space on other 
file-systems then 
  sudo apt-get autoremove 
may help you.  After that I would recommend that you try running the Disk Usage 
Analyser program.  It provides a relatively intuitive GUI that helps locate 
where most of your disk space is being used.  It will then be up to the 
operator to work out what files can and cannot be removed in an attempt to free 
space.  I would advise that you do not remove anything you do not know the 
source or use of.  Hopefully some searching can aid in identifying where most 
files come from though.

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor or manually free space on
  your partition containing the /boot file system.

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

-- 
Mailing list: https://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 1482553] [NEW] LaunchPad asks users to evaluate of a bug is a duplicate of another bug they can see no details of

[Thomas A. F. Thorne]

Public bug reported:

Frequently apport will mark a bug that I have raised as a duplicate of a
bug I cannot access (see bug #764414 et. al. for issues that raises).
Whether or not that should happen, it does happen frequently and
Launchpad's behaviour is odd when it does happen.

Based on Bug #1482529 which I raised today, I noticed the following odd
things are disabled.

 1)  Top of the page states This bug report is a duplicate of:  and that is 
all.  The bug number is not even displayed.  Further down in the comment that 
apport made it says: 
Thank you for taking the time to report this crash and helping to make this 
software better. This particular crash has already been reported and is a 
duplicate of bug #1208209, so is being marked as such. Please look at the other 
bug report to see if there is any missing information that you can provide, or 
to see if there is a workaround for the bug. Additionally, any further 
discussion regarding the bug should occur in the other report. Please continue 
to report any other bugs you may find.

information type:   Private → Public
tags:   removed: need-amd64-retrace

As the alleged duplicate is clearly known, why is it not displayed under
the title in the This bug report is a duplicate of: bug #1208209?

 2)  Launchpad now seems to block the bug #1208209 for me and greys it
out.  That is fine.  It provides a pop-up box stating The page at
https://bugs.launchpad.net/ says: Bug 1208209 cannot be found.  If this
box is provided because the bug does not exist, there is a bug with
apport.  If this message is being shown because I do not have permission
to read 1208209 then it should state that.  Right now it is suggesting
to the user that apport has picked invalid data as the duplicate.

 3) At the end of the launchpad page is a warning stating Remember, this bug 
report is a duplicate of a private bug.
Comment here only if you think the duplicate status is wrong. but there is no 
way I can provide a valid comment on whether the status is wrong.  Launchpad 
knows that I cannot access bug #1208209 so it should be able to infer that I 
cannot confirm or deny that it is the correct duplicate or not.  I think that 
the Comment here only if you think the duplicate status is wrong. part of the 
message should be reconsidered.  

 4)  (possibly apport related and not launchpad) The comment included when this 
bug was marked as a duplicate of a non-existent or private bug (I have no way 
to say which at present) states: 
Please look at the other bug report to see if there is any missing information 
that you can provide, or to see if there is a workaround for the bug. 
Additionally, any further discussion regarding the bug should occur in the 
other report.   
I cannot loot at the other bug report.  
I cannot see if there is a work around.  
I cannot add any information to the other report.  
Launchpad knows that I cannot do these things, even if apport cannot.  
Launchpad should either remove these messages for me or add something to 
confirm it is impossible to follow the requests.  Right now it is asking users 
to do the impossible.

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

** Changed in: apport (Ubuntu)
   Status: New = Opinion

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

Title:
  LaunchPad asks users to evaluate of a bug is a duplicate of another
  bug they can see no details of

Status in apport package in Ubuntu:
  Opinion

Bug description:
  Frequently apport will mark a bug that I have raised as a duplicate of
  a bug I cannot access (see bug #764414 et. al. for issues that
  raises).  Whether or not that should happen, it does happen frequently
  and Launchpad's behaviour is odd when it does happen.

  Based on Bug #1482529 which I raised today, I noticed the following
  odd things are disabled.

   1)  Top of the page states This bug report is a duplicate of:  and that is 
all.  The bug number is not even displayed.  Further down in the comment that 
apport made it says: 
  Thank you for taking the time to report this crash and helping to make this 
software better. This particular crash has already been reported and is a 
duplicate of bug #1208209, so is being marked as such. Please look at the other 
bug report to see if there is any missing information that you can provide, or 
to see if there is a workaround for the bug. Additionally, any further 
discussion regarding the bug should occur in the other report. Please continue 
to report any other bugs you may find.

  information type: Private → Public
  tags: removed: need-amd64-retrace

  As the alleged duplicate is clearly known, why is it not displayed
  under the title in the This bug report is a duplicate of: bug
  #1208209?

   2)  Launchpad now seems to block the bug #1208209 for me and greys it
  out.  That is 

[Touch-packages] [Bug 764414] Re: private master bugs are confusing and lead to more duplicate filings

[Thomas A. F. Thorne]

I would like to +1 the idea of a 
   A.  Public master bug 
However I do not think is a job that apport could be expected to do safely.  It 
cannot interpret what data is safe to make public, what summary would be 
helpful to future reports trying to determine duplicates or what should go in 
the description (besides some attribution to the private bug that was (or is) 
the head bug still.  
 Trade-off is all crash bugs  appear to be filed by apport.
Not if a human has to create it as I suggest.  
 Further, both alternatives have the additional trade-off that there are two 
 bug reports filed for each crash bug.
We are already talking about duplicates, so there are probably multiple bugs 
reported anyway.  Most or all of them get marked as duplicates by machines.  
What users are asking for is some public data to be made visible.  A new top 
level public bug that other bugs (private or otherwise) can be made duplicates 
of is one bug being raised by one person once.  That is a small increase in 
workload for what I think could lead to a big improvement in user experience 
and possibly less future work for the maintainer.  

Having one public bug at the top of all the duplicates will allow
maintainers to publicly ask for any other diagnostics they might find
helpful from users.  Currently people reporting duplicates hit a dead
end where they can be of no use.  There is no way for a maintainer to
ask them all to do something helpful ( though I expect maintainers with
special permissions could go to every duplicate bug and post a message
to each one in turn, which sound like a lot of work).  Maintainers could
also publicly provide a work around, an explanation of the problem, a
fixed-in status, a first know affected version and a lot of other data
that people cannot currently see.

The benefit for users is that instead of seeing Not Permitted they can
get some useful data.  They could see if the bug their is allegedly a
duplicate of is fixed.  They might be able to confirm that it does seem
like a duplicate (do maintainers have to do this at present?  They are
the only ones who might have permission to).  They can ask questions,
possibly view other duplicates of the same bug (which might be public)
and could have helpful details in.

It would double the quantity of bug reports they need to manage, and either 
obscure the reporter's name or obscure the attachments.
I suggest not moving the attachments.  Give maintainers a Make Public Head 
Bug button of some kind that does some of the heavy lifting (e.g. moves 
duplicates to the new bug, adds link to old private head bug, adds a list of 
know duplciates?).  They have to press one button, make one title and one 
public summary and that is all.  For that they possibly get better data from 
their users.  

 After filing, apport sometimes marks bugs as dupes of a master  private bug, 
 which the dupee can't view.
 This does sound like an annoying problem.  In practice I've not seen this 
 happen that much.
It is a very annoying problem and at present it feels like it happens to me a 
lot.  That might be because I am using the LTS release with bug reporting 
enabled, which is not the norm.  


I hope that some of my comments spark some helpful thought in the head of 
someone that can help improve the current situation.  I don't know how many 
users are put off by seeing the permission denied page but it is probably quite 
a few.  These are people who might not both using apport or reporting a bug 
again.  They are the same people who might have gone to help maintain a package 
in some way but were put off by their early experience being a closed system 
without a dialogue run only by a machine.

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

Title:
  private master bugs are confusing and lead to more duplicate filings

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apport

  Apport currently tracks the master bug as a private bug visible only
  to Ubuntu developers (bugcontrol) and makes duplicate bugs public
  after stripping their data.

  This works well but has some downsides:
   - Launchpad cannot show the master bug to folk reporting bugs via apport (so 
they file new bugs always)
   - After users file a new bug apport detects its a duplicate and then they 
cannot see the master bug and get frustrated.

  It would be nice to have:
   - the master bug be public so that reporters of dups can see it in the dupe 
finder and can see if a dupe is detected post-filing.
   - Developers still have easy access to the raw crash data.
    - One way to do that that does not need much development would be to have a 
private bug exist, linked from the master bug (e.g. with a comment or in the 
description; something like 'Confidential crashdump for this bug is attached to 
bug 12345 - only visible to 

[Touch-packages] [Bug 1477558] [NEW] aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode bytes in position 0-1: invalid continuation byte while trying to report a

[Thomas A. F. Thorne]

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

Public bug reported:

I was trying to report a problem that caused my unity session to restart.  When 
I tried to submit the report a new error occured and I was taken to Bug 
#1022993 where I posted: 
--
I did not have to do an upgrade and reboot to hit this. It seems that my unity 
session crashed out and took me back the login prompt (so almost a restart). 
After that I did a ls -l on /var/crash to see if there was a new report. There 
was so I went to the launcher things and searched for 'up' which gave me a link 
to Software Updater, as I wanted. I started the updater so that it would see 
the crash report and start the bug report filing. It spotted the changes, 
opened a second window from which I could report the bug. I left that window 
alone while I waited for the main Software Updater window to finish checking 
for updates. While that was going I opened Chrome and let it restore its 
session so that I would be ready when a bug window opened. Once Chrome was 
sorted and all the updates were found I clicked send bug report, which then 
seemed to fail and then took me to this bug.
--

As the first bug happened about 3 years ago I wanted to submit updated
apport-collect style details to it.  When I tried to do that it said
that I could not do so as I did not own the bug and should make a new
one.  So here is the new one that I will mark as a duplicate of Bug
#1022993 in a bit.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.8
Uname: Linux 4.1.0-040100rc8-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul 23 14:00:47 2015
InstallationDate: Installed on 2015-03-12 (132 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** This bug has been marked a duplicate of bug 1022993
   aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec 
can't decode bytes in position 0-1: invalid continuation byte

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

Title:
  aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8'
  codec can't decode bytes in position 0-1: invalid continuation byte
  while trying to report a bug

Status in apt package in Ubuntu:
  New

Bug description:
  I was trying to report a problem that caused my unity session to restart.  
When I tried to submit the report a new error occured and I was taken to Bug 
#1022993 where I posted: 
  --
  I did not have to do an upgrade and reboot to hit this. It seems that my 
unity session crashed out and took me back the login prompt (so almost a 
restart). After that I did a ls -l on /var/crash to see if there was a new 
report. There was so I went to the launcher things and searched for 'up' which 
gave me a link to Software Updater, as I wanted. I started the updater so that 
it would see the crash report and start the bug report filing. It spotted the 
changes, opened a second window from which I could report the bug. I left that 
window alone while I waited for the main Software Updater window to finish 
checking for updates. While that was going I opened Chrome and let it restore 
its session so that I would be ready when a bug window opened. Once Chrome was 
sorted and all the updates were found I clicked send bug report, which then 
seemed to fail and then took me to this bug.
  --

  As the first bug happened about 3 years ago I wanted to submit updated
  apport-collect style details to it.  When I tried to do that it said
  that I could not do so as I did not own the bug and should make a new
  one.  So here is the new one that I will mark as a duplicate of Bug
  #1022993 in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.8
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 23 14:00:47 2015
  InstallationDate: Installed on 2015-03-12 (132 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1477631] [NEW] Xorg crash which returned me to my login screen

[Thomas A. F. Thorne]

Public bug reported:

This looked like the same thing as when Bug #1477574 and Bug #1477566
happened just now.  I had Chrome, Terminal  Eclipse open on my Ubuntu
PC and was focused on using my laptop via Synergy.  In my Synergy setup
the Ubuntu PC is the server and the laptop is the client.

As in the two bugs I mentioned, the Ubuntu machine seemed to reset back
to the login screen.  Unlike the last time nothing complained about out
of date packages this time.  I had not run the upgrade when this bug
happened.  I have now updated however.

Yesterday there was a power cut to this building.  I am starting to worry about 
my hardware integrity.  The previous software update I did was at 2015-07-22  
08:15:01, some 29 hours before the first time I saw an issue and now I have hit 
the login screen twice in about 2 hours.  
Start-Date: 2015-07-22  08:13:51
Commandline: aptdaemon role='role-commit-packages' sender=':1.712'
Upgrade: mysql-server-core-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 
5.5.44-0ubuntu0.14.04.1), mysql-server-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 
5.5.44-0ubuntu0.14.04.1), mysql-client-core-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 
5.5.44-0ubuntu0.14.04.1), mysql-client:amd64 (5.5.43-0ubuntu0.14.04.1, 
5.5.44-0ubuntu0.14.04.1), google-chrome-stable:amd64 (43.0.2357.134-1, 
44.0.2403.89-1), thunderbird-locale-en-us:amd64 
(31.7.0+build1-0ubuntu0.14.04.1, 31.8.0+build1-0ubuntu0.14.04.1), 
thunderbird:amd64 (31.7.0+build1-0ubuntu0.14.04.1, 
31.8.0+build1-0ubuntu0.14.04.1), thunderbird-locale-en:amd64 
(31.7.0+build1-0ubuntu0.14.04.1, 31.8.0+build1-0ubuntu0.14.04.1), 
mysql-client-5.5:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), 
mysql-common:amd64 (5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), 
thunderbird-gnome-support:amd64 (31.7.0+build1-0ubuntu0.14.04.1, 
31.8.0+build1-0ubuntu0.14.04.1), libmysqlclient18:amd64 
(5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), libmysqlclient18:i386 (5.5.
 43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1), mysql-server:amd64 
(5.5.43-0ubuntu0.14.04.1, 5.5.44-0ubuntu0.14.04.1)
End-Date: 2015-07-22  08:15:01
Having said that the power-cut was bout 24 hours before the problem was first 
seen.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
Uname: Linux 4.1.0-040100rc8-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.11
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: Thu Jul 23 15:30:26 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
InstallationDate: Installed on 2015-03-12 (132 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-DS2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: H81M-DS2V
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Jul 23 15:27:58 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   26053 
 vendor

[Touch-packages] [Bug 1060081] Re: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte

[Thomas A. F. Thorne]

Somewhere during, before or after my current xorg or unity problems I am
hitting this bug too according to apport.

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

Title:
  aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8'
  codec can't decode byte 0x93 in position 1: invalid start byte

Status in apt package in Ubuntu:
  Triaged
Status in aptdaemon package in Ubuntu:
  Triaged
Status in apt package in Debian:
  Fix Released

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: aptdaemon 0.45+bzr861-0ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  2 06:17:45 2012
  ExecutablePath: /usr/sbin/aptd
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.2 /usr/sbin/aptd
  ProcEnviron:
   
  PythonArgs: ['/usr/sbin/aptd']
  SourcePackage: aptdaemon
  Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' 
codec can't decode byte 0x93 in position 1: invalid start byte
  UpgradeStatus: Upgraded to quantal on 2012-09-22 (9 days ago)
  UserGroups:

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

-- 
Mailing list: https://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 1060081] Re: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte

[Thomas A. F. Thorne]

Having read the background post from ~chris-bainbridge I can see that
this will be a random crash.  Unless there is any further information I
can supply that will be of help, I will not add further comments or bugs
in relation to this item.

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

Title:
  aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8'
  codec can't decode byte 0x93 in position 1: invalid start byte

Status in apt package in Ubuntu:
  Triaged
Status in aptdaemon package in Ubuntu:
  Triaged
Status in apt package in Debian:
  Fix Released

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: aptdaemon 0.45+bzr861-0ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  2 06:17:45 2012
  ExecutablePath: /usr/sbin/aptd
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.2 /usr/sbin/aptd
  ProcEnviron:
   
  PythonArgs: ['/usr/sbin/aptd']
  SourcePackage: aptdaemon
  Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' 
codec can't decode byte 0x93 in position 1: invalid start byte
  UpgradeStatus: Upgraded to quantal on 2012-09-22 (9 days ago)
  UserGroups:

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

-- 
Mailing list: https://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 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account

[Thomas A. F. Thorne]

** Summary changed:

- Can't create EWS or MAPI account
+ Evolution appears unable to create EWS or Exchange MAPI account

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

Title:
  Evolution appears unable to create EWS or Exchange MAPI account

Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Evolution appears unable to create an EW or MAPI account. All the
  steps proceed normally, including fetching the URL (for EWS) or
  authenticating (for MAPI). However, at the conclusion of account
  creation process, no actual account appears in the list.

  I've tried starting Evolution from the command line using various
  DEBUG_ variables and there are no EWS- or MAPI-specific errors. So I'm
  not exactly sure what to do next.

  I am fairly certain the problem doesn't lie with my corporate Exchange
  server, as web mail works fine and any other EWS-capable client (like
  the mail app in Android).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evolution 3.6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 12:40:28 2012
  InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Beta amd64 
(20120925)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1061195/+subscriptions

-- 
Mailing list: https://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 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account

[Thomas A. F. Thorne]

I can confirm that I hit this bug while running 3.10.4 installed from the 
Ubuntu Software Center for the current LTS version of Ubuntu 
$ lsb_release -rc
Release:14.04
Codename:   trusty

I had previous setup Gmail (googlemail) and a pop account in Evolution.
Some recent changes to my work's exchange setup meant that pop was no
longer a connection option.  I disabled the pop account.   Installed
evolution-ews from the Software Centre and tried to add my Exchange
account.  Everything worked very well until I clicked the final button,
which caused the window to close and seemingly no new email account to
be added.  This looks very much like a silent failure.

Closing Evolution and reopening it using the File  Quite or  red X did
not seem to change the state of things.  After finding this bug via an
Internet search I tried the work around of logging out from my current
GUI session and logging back in.  When I opened Evolution two new
Exchange MAPI accounts were shown.  Both seemed to work.

If people have tried to setup Exchange with Microsoft Exchange instead
of using Outlook on Windows and seen this they may think it has silently
failed.  They may be wholly unaware that there is in fact a working mail
account if they were to open Evolution agian, but why would they try
when they have seen it fail?

** Also affects: evolution-ews (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: evolution-mapi (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Evolution appears unable to create EWS or Exchange MAPI account

Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  Confirmed
Status in evolution-ews package in Ubuntu:
  New
Status in evolution-mapi package in Ubuntu:
  New

Bug description:
  Evolution appears unable to create an EW or MAPI account. All the
  steps proceed normally, including fetching the URL (for EWS) or
  authenticating (for MAPI). However, at the conclusion of account
  creation process, no actual account appears in the list.

  I've tried starting Evolution from the command line using various
  DEBUG_ variables and there are no EWS- or MAPI-specific errors. So I'm
  not exactly sure what to do next.

  I am fairly certain the problem doesn't lie with my corporate Exchange
  server, as web mail works fine and any other EWS-capable client (like
  the mail app in Android).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evolution 3.6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 12:40:28 2012
  InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Beta amd64 
(20120925)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1458818] Re: Xorg crash while starting Eclipse

[Thomas A. F. Thorne]

I have not reproduced this issue yet.  If I can find a way to reproduce
the issue I will gladly try it out on the latest sat of code.

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

Title:
  Xorg crash while starting Eclipse

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I had a few terminals and Chrome running.  Started Eclipse from the
  GUI search, it started too load, the screen flicked to black for a
  moment then came back but was frozen.  I have system monitor graphs
  going on the task bar and these were not updating.  I could still move
  the mouse within the display it was in at the time of the crash but
  not on to the second display or over to my Windows box via Synergy.

  After 30s or so the screen flicked to black and back again.  Then I
  was  returned to the login prompt.  Once  I logged back in the
  applications I had had open were closed.

  Inspected some logs to see what would come up.

  In kern.log I spotted:
  May 26 10:26:44 thorne-ul-dt kernel: [436212.122636] traps: 
unity-settings-[2567] trap int3 ip:7f84149d1c13 sp:7ffc1b310e70 error:0
  May 26 10:26:50 thorne-ul-dt kernel: [436218.561645] compiz[2712]: segfault 
at 0 ip   (null) sp 7fff04c25ed8 error 14 in compiz[40+3000]
  May 26 10:28:06 thorne-ul-dt kernel: [436294.229229] Qt bearer threa[10079]: 
segfault at 7fe2bc26ba50 ip 7fe2eb821b84 sp 7fe2715aa520 error 4 in 
libQt5Network.so.5.2.1[7fe2eb78d000+13c000]
  So to me this looks like a unity utility, compiz or a bit of Qt might have 
gone wonky.  Is Eclipse written in Qt?  I could imagine that being the case and 
that being a possible explanation for it being mentioned here.  

  In syslog I spotted:
  May 26 10:26:31 thorne-ul-dt signond[1600]: 
../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure 
storage will not be available. 
  May 26 10:26:44 thorne-ul-dt kernel: [436212.122636] traps: 
unity-settings-[2567] trap int3 ip:7f84149d1c13 sp:7ffc1b310e70 error:0
  May 26 10:26:47 thorne-ul-dt colord: device removed: xrandr-NEC 
Corporation-NEC LS15-2103104IE
  May 26 10:26:47 thorne-ul-dt colord: device removed: xrandr-BenQ-BenQ 
GL2460-N9E03540SL0
  May 26 10:26:47 thorne-ul-dt colord: Profile removed: 
icc-2ffb9a562d1ec077158027d9057422e8
  May 26 10:26:47 thorne-ul-dt colord: Profile removed: 
icc-85cdf70ddeb10c2e9c44d2e50148165c
  May 26 10:26:50 thorne-ul-dt dbus[782]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  May 26 10:26:50 thorne-ul-dt kernel: [436218.561645] compiz[2712]: segfault 
at 0 ip   (null) sp 7fff04c25ed8 error 14 in compiz[40+3000]
  May 26 10:26:51 thorne-ul-dt dbus[782]: [system] Successfully activated 
service 'org.freedesktop.systemd1'
  ...
  May 26 10:28:05 thorne-ul-dt gnome-session[2596]: WARNING: Application 
'compiz.desktop' killed by signal 11
  May 26 10:28:05 thorne-ul-dt gnome-session[2596]: WARNING: App 
'compiz.desktop' respawning too quickly
  May 26 10:28:05 thorne-ul-dt gnome-session[2596]: CRITICAL: We failed, but 
the fail whale is dead. Sorry
  May 26 10:28:06 thorne-ul-dt kernel: [436294.229229] Qt bearer threa[10079]: 
segfault at 7fe2bc26ba50 ip 7fe2eb821b84 sp 7fe2715aa520 error 4 in 
libQt5Network.so.5.2.1[7fe2eb78d000+13c000]
  May 26 10:28:08 thorne-ul-dt colord: device removed: xrandr-NEC 
Corporation-NEC LS15-2103104IE
  May 26 10:28:08 thorne-ul-dt colord: device removed: xrandr-BenQ-BenQ 
GL2460-N9E03540SL0
  May 26 10:28:08 thorne-ul-dt colord: Profile removed: 
icc-2ffb9a562d1ec077158027d9057422e8
  May 26 10:28:08 thorne-ul-dt colord: Profile removed: 
icc-85cdf70ddeb10c2e9c44d2e50148165c
  May 26 10:28:09 thorne-ul-dt pulseaudio[1770]: [pulseaudio] main.c: 
User-configured server at 
{2cc0dcd84f1d9f789af8f02555029f0b}unix:/run/user/1000/pulse/native, which 
appears to be local. Probing deeper.
  ...
  May 26 10:28:13 thorne-ul-dt rtkit-daemon[1768]: Successfully made thread 
1801 of process 1787 (n/a) owned by '1000' RT at priority 5.
  May 26 10:28:13 thorne-ul-dt rtkit-daemon[1768]: Supervising 8 threads of 2 
processes of 2 users.
  May 26 10:28:13 thorne-ul-dt pulseaudio[1787]: [pulseaudio] server-lookup.c: 
Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect 
to socket /tmp/dbus-APSNbDfhBj: Connection refused
  May 26 10:28:13 thorne-ul-dt pulseaudio[1787]: [pulseaudio] main.c: Unable to 
contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket 
/tmp/dbus-APSNbDfhBj: Connection refused
  May 26 10:28:13 thorne-ul-dt rtkit-daemon[1768]: Successfully made thread 
1803 of process 1803 (n/a) owned by '1000' high priority at nice level -11.
  May 26 10:28:13 thorne-ul-dt rtkit-daemon[1768]: Supervising 9 threads of 3 
processes of 2 users.
  May 26 10:28:13 thorne-ul-dt pulseaudio[1803]: 

[Touch-packages] [Bug 1458818] [NEW] Xorg crash while starting Eclipse

[Thomas A. F. Thorne]

Public bug reported:

I had a few terminals and Chrome running.  Started Eclipse from the GUI
search, it started too load, the screen flicked to black for a moment
then came back but was frozen.  I have system monitor graphs going on
the task bar and these were not updating.  I could still move the mouse
within the display it was in at the time of the crash but not on to the
second display or over to my Windows box via Synergy.

After 30s or so the screen flicked to black and back again.  Then I was
returned to the login prompt.  Once  I logged back in the applications I
had had open were closed.

Inspected some logs to see what would come up.

In kern.log I spotted:
May 26 10:26:44 thorne-ul-dt kernel: [436212.122636] traps: 
unity-settings-[2567] trap int3 ip:7f84149d1c13 sp:7ffc1b310e70 error:0
May 26 10:26:50 thorne-ul-dt kernel: [436218.561645] compiz[2712]: segfault at 
0 ip   (null) sp 7fff04c25ed8 error 14 in compiz[40+3000]
May 26 10:28:06 thorne-ul-dt kernel: [436294.229229] Qt bearer threa[10079]: 
segfault at 7fe2bc26ba50 ip 7fe2eb821b84 sp 7fe2715aa520 error 4 in 
libQt5Network.so.5.2.1[7fe2eb78d000+13c000]
So to me this looks like a unity utility, compiz or a bit of Qt might have gone 
wonky.  Is Eclipse written in Qt?  I could imagine that being the case and that 
being a possible explanation for it being mentioned here.  

In syslog I spotted:
May 26 10:26:31 thorne-ul-dt signond[1600]: 
../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure 
storage will not be available. 
May 26 10:26:44 thorne-ul-dt kernel: [436212.122636] traps: 
unity-settings-[2567] trap int3 ip:7f84149d1c13 sp:7ffc1b310e70 error:0
May 26 10:26:47 thorne-ul-dt colord: device removed: xrandr-NEC Corporation-NEC 
LS15-2103104IE
May 26 10:26:47 thorne-ul-dt colord: device removed: xrandr-BenQ-BenQ 
GL2460-N9E03540SL0
May 26 10:26:47 thorne-ul-dt colord: Profile removed: 
icc-2ffb9a562d1ec077158027d9057422e8
May 26 10:26:47 thorne-ul-dt colord: Profile removed: 
icc-85cdf70ddeb10c2e9c44d2e50148165c
May 26 10:26:50 thorne-ul-dt dbus[782]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
May 26 10:26:50 thorne-ul-dt kernel: [436218.561645] compiz[2712]: segfault at 
0 ip   (null) sp 7fff04c25ed8 error 14 in compiz[40+3000]
May 26 10:26:51 thorne-ul-dt dbus[782]: [system] Successfully activated service 
'org.freedesktop.systemd1'
...
May 26 10:28:05 thorne-ul-dt gnome-session[2596]: WARNING: Application 
'compiz.desktop' killed by signal 11
May 26 10:28:05 thorne-ul-dt gnome-session[2596]: WARNING: App 'compiz.desktop' 
respawning too quickly
May 26 10:28:05 thorne-ul-dt gnome-session[2596]: CRITICAL: We failed, but the 
fail whale is dead. Sorry
May 26 10:28:06 thorne-ul-dt kernel: [436294.229229] Qt bearer threa[10079]: 
segfault at 7fe2bc26ba50 ip 7fe2eb821b84 sp 7fe2715aa520 error 4 in 
libQt5Network.so.5.2.1[7fe2eb78d000+13c000]
May 26 10:28:08 thorne-ul-dt colord: device removed: xrandr-NEC Corporation-NEC 
LS15-2103104IE
May 26 10:28:08 thorne-ul-dt colord: device removed: xrandr-BenQ-BenQ 
GL2460-N9E03540SL0
May 26 10:28:08 thorne-ul-dt colord: Profile removed: 
icc-2ffb9a562d1ec077158027d9057422e8
May 26 10:28:08 thorne-ul-dt colord: Profile removed: 
icc-85cdf70ddeb10c2e9c44d2e50148165c
May 26 10:28:09 thorne-ul-dt pulseaudio[1770]: [pulseaudio] main.c: 
User-configured server at 
{2cc0dcd84f1d9f789af8f02555029f0b}unix:/run/user/1000/pulse/native, which 
appears to be local. Probing deeper.
...
May 26 10:28:13 thorne-ul-dt rtkit-daemon[1768]: Successfully made thread 1801 
of process 1787 (n/a) owned by '1000' RT at priority 5.
May 26 10:28:13 thorne-ul-dt rtkit-daemon[1768]: Supervising 8 threads of 2 
processes of 2 users.
May 26 10:28:13 thorne-ul-dt pulseaudio[1787]: [pulseaudio] server-lookup.c: 
Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect 
to socket /tmp/dbus-APSNbDfhBj: Connection refused
May 26 10:28:13 thorne-ul-dt pulseaudio[1787]: [pulseaudio] main.c: Unable to 
contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket 
/tmp/dbus-APSNbDfhBj: Connection refused
May 26 10:28:13 thorne-ul-dt rtkit-daemon[1768]: Successfully made thread 1803 
of process 1803 (n/a) owned by '1000' high priority at nice level -11.
May 26 10:28:13 thorne-ul-dt rtkit-daemon[1768]: Supervising 9 threads of 3 
processes of 2 users.
May 26 10:28:13 thorne-ul-dt pulseaudio[1803]: [pulseaudio] pid.c: Daemon 
already running.
May 26 10:28:13 thorne-ul-dt Synergy 1.7.1: FATAL: X display has unexpectedly 
disconnected
May 26 10:28:14 thorne-ul-dt acpid: client 1454[0:0] has disconnected
May 26 10:28:14 thorne-ul-dt acpid: client connected from 1804[0:0]
May 26 10:28:14 thorne-ul-dt acpid: 1 client rule loaded
May 26 10:28:16 thorne-ul-dt dbus[782]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper
...
May 26 10:28:32 thorne-ul-dt colord: