[Desktop-packages] [Bug 1839247] Re: gvfsd-smb-browse crashed with SIGABRT

[Thomas A. F. Thorne]

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

Apport is once again suggesting this is a duplicate of a private bug.
If I am mean to check whether this is a duplicate or not I cannot do so.

If apport is comfortable to strip this bug of its Private tag, why can
it not do the same for the one being referenced?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1839247

Title:
  gvfsd-smb-browse crashed with SIGABRT

Status in gvfs package in Ubuntu:
  New

Bug description:
  If this was prompted by anything it would have to be either my logging
  in via remote desktop tunnelled over ssh or from the software update
  cycle I can see on the desktop.  As far as I can recall the only smb
  related actions on this machine are a share of a directory in my home
  drive which is not being accessed by anything at the moment as far as
  I am aware.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul 30 10:43:48 2019
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2017-11-16 (628 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.16 
/org/gtk/gvfs/exec_spaw/5
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   _talloc_pooled_object () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   _tevent_req_create () at /usr/lib/x86_64-linux-gnu/libtevent.so.0
   () at /usr/lib/x86_64-linux-gnu/samba/libgse.so.0
   name_query_send () at /usr/lib/x86_64-linux-gnu/samba/libgse.so.0
  Title: gvfsd-smb-browse crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (375 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo 
wireshark

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

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

[Desktop-packages] [Bug 1651130] Re: gvfsd-smb-browse crashed with SIGABRT in talloc_abort()

[Thomas A. F. Thorne]

Marking as non-private as it has been long enough I am comfortable that
anything stored is no longer sensative.  I do not think there is
anything sensitive in there anyway.

I am back here now as I have just raised bug 1839247 however that only
looks related by attributed package and nothing more.  I know I am not
running on the same hardware.

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1651130

Title:
  gvfsd-smb-browse crashed with SIGABRT in talloc_abort()

Status in gvfs package in Ubuntu:
  New

Bug description:
  Had plugged in a Micro SD card.  Closed the two file browser windows
  that automatically opened.  Did an `lsblk` on the command line and
  noticed that no SD card was shown.  A few seconds later an error
  report came up.

  Now the report has complete the sd card is mounted once again.  Things
  managed to recover without any physical intervention on my part.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.2-1ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 19 13:32:28 2016
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2015-03-12 (647 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 
/org/gtk/gvfs/exec_spaw/39
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   talloc_named_const () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libsamba-util.so.0
   smbc_free_context () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
   ?? ()
  Title: gvfsd-smb-browse crashed with SIGABRT in talloc_named_const()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo 
wireshark

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

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

[Desktop-packages] [Bug 1820031] Re: My Ubuntu 18.04 GUI seems frozen

[Thomas A. F. Thorne]

Nothing new comes out in the crash report.

When I visit
https://errors.ubuntu.com/user/1d81a00d35531ca846cc8b470c853c9c4cc299c3a0a42040e68da92210168a3d96818f5de95d8f7d85e66516d77e481a6259123145189d1685f6d22ac584114a
the most recent report is:

https://errors.ubuntu.com/oops/0d2b0694-2b7d-11e9-9d81-fa163e102db1

I shall try to apply the work around from
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/994921 as
suggested in step 3 of the instructions you have linked to.

I do not need to apply it as it is already in place.


So what next... apport-collect perhapse although it seems that enough debug may 
be already posted.  Maybe just a reboot of my system (as I cannot restart a 
service) and move on.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1820031

Title:
  My Ubuntu 18.04 GUI seems frozen

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

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

To manage notifications 

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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 test process 

[Desktop-packages] [Bug 1784358] Re: Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

[Thomas A. F. Thorne]

I have raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=537526 to
cover the installer issue.  There are similar bugs marked as fixed for
the main Eclipse code, but as this is still visible and relates to the
installer, not the main binary, I raised a new bug.

That is probably all from me for now.  I shall await news of an updated
package to test out or some instructions of other things to try.

** Bug watch added: Eclipse bugs #537526
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=537526

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eclipse in Ubuntu.
https://bugs.launchpad.net/bugs/1784358

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

Status in eclipse package in Ubuntu:
  New
Status in eclipse package in Debian:
  New

Bug description:
  I upgraded from 16.04 to 18.04 on Friday.  Following some reboots and
  updates this morning I am now unable to start the Eclipse IDE.  This
  was working before the upgrade.

  I have the C++ developer support added to Eclipse.  To the best of my
  memory (and ability to interrogate apt) it is all installed from the
  Ubuntu repositories.

  When I click the Eclipse launcher pinned to my side bat I get an error 
message from Eclipse that reads:
  An error has occurred.  See the log file
  
/home/thomas/.eclipse/org.eclipse.platform_3.8_155965261/configuration/1532947738216.log

  Viewing the log file I see:
  !SESSION Mon Jul 30 11:48:58 BST 2018 
--
  !ENTRY org.eclipse.equinox.launcher 4 0 2018-07-30 11:48:58.229
  !MESSAGE Exception launching the Eclipse Platform:
  !STACK
  java.lang.ClassNotFoundException: 
org.eclipse.core.runtime.adaptor.EclipseStarter
  at 
java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626)
  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
  at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
  at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

  This is easily repeatable.

  Some internet searching suggests this problem is present upstream as
  there is a Debian bug that looks similar: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=891956

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eclipse 3.8.1-11
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jul 30 11:43:38 2018
  InstallationDate: Installed on 2017-11-16 (255 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: eclipse
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (3 days ago)

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

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

[Desktop-packages] [Bug 1784358] Re: Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

[Thomas A. F. Thorne]

I can confirm that downloading the Eclipse installer from the main
website: http://www.eclipse.org/downloads/ executing it as myself and
then selecting the C/C++ option got me a working copy of Eclipse
installed.  That is a successful work around until the packaged version
is fixed.


When I ran the install I did see some errors that I will bring up with the 
Eclipse team, if I can work out how:

:~/Downloads/eclipse/eclipse-inst-linux64/eclipse-installer$ sudo 
./eclipse-inst 
[sudo] password for thomas: 
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.eclipse.emf.ecore.xmi.impl.XMLHandler 
(file:/home/thomas/Downloads/eclipse/eclipse-inst-linux64/eclipse-installer/plugins/org.eclipse.emf.ecore.xmi_2.13.0.v20170609-0707.jar)
 to method 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser$LocatorProxy.getEncoding()
WARNING: Please consider reporting this to the maintainers of 
org.eclipse.emf.ecore.xmi.impl.XMLHandler
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release

(SWT:17278): IBUS-WARNING **: 14:26:33.796: The owner of
/home/thomas/.config/ibus/bus is not root!

(SWT:17278): GLib-CRITICAL **: 14:26:38.153: Source ID 409 was not found when 
attempting to remove it
:~/Downloads/eclipse/eclipse-inst-linux64/eclipse-installer$ ./eclipse-inst 
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.eclipse.emf.ecore.xmi.impl.XMLHandler 
(file:/home/thomas/Downloads/eclipse/eclipse-inst-linux64/eclipse-installer/plugins/org.eclipse.emf.ecore.xmi_2.13.0.v20170609-0707.jar)
 to method 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser$LocatorProxy.getEncoding()
WARNING: Please consider reporting this to the maintainers of 
org.eclipse.emf.ecore.xmi.impl.XMLHandler
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release

(SWT:17498): GLib-CRITICAL **: 14:27:23.976: Source ID 5293 was not
found when attempting to remove it

(SWT:17498): GLib-CRITICAL **: 14:27:24.432: Source ID 5445 was not
found when attempting to remove it

(SWT:17498): GLib-CRITICAL **: 14:27:25.951: Source ID 5614 was not found when 
attempting to remove it
[Fatal Error] :539:7: XML document structures must start and end within the 
same entity.

However despite the above it did seem to install fine.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eclipse in Ubuntu.
https://bugs.launchpad.net/bugs/1784358

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

Status in eclipse package in Ubuntu:
  New
Status in eclipse package in Debian:
  New

Bug description:
  I upgraded from 16.04 to 18.04 on Friday.  Following some reboots and
  updates this morning I am now unable to start the Eclipse IDE.  This
  was working before the upgrade.

  I have the C++ developer support added to Eclipse.  To the best of my
  memory (and ability to interrogate apt) it is all installed from the
  Ubuntu repositories.

  When I click the Eclipse launcher pinned to my side bat I get an error 
message from Eclipse that reads:
  An error has occurred.  See the log file
  
/home/thomas/.eclipse/org.eclipse.platform_3.8_155965261/configuration/1532947738216.log

  Viewing the log file I see:
  !SESSION Mon Jul 30 11:48:58 BST 2018 
--
  !ENTRY org.eclipse.equinox.launcher 4 0 2018-07-30 11:48:58.229
  !MESSAGE Exception launching the Eclipse Platform:
  !STACK
  java.lang.ClassNotFoundException: 
org.eclipse.core.runtime.adaptor.EclipseStarter
  at 
java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626)
  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
  at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
  at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

  This is easily repeatable.

  Some internet searching suggests this problem is present upstream as
  there is a Debian bug that looks similar: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=891956

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eclipse 3.8.1-11
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jul 30 11:43:38 2018
  InstallationDate: Installed on 2017-11-16 (255 days ago)
  InstallationMedia: Ubuntu 

[Desktop-packages] [Bug 1784358] Re: Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

[Thomas A. F. Thorne]

$ sudo apt-get install --reinstall libequinox-osgi-java

Resulted in no change.  The problem presented as before.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eclipse in Ubuntu.
https://bugs.launchpad.net/bugs/1784358

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

Status in eclipse package in Ubuntu:
  New
Status in eclipse package in Debian:
  New

Bug description:
  I upgraded from 16.04 to 18.04 on Friday.  Following some reboots and
  updates this morning I am now unable to start the Eclipse IDE.  This
  was working before the upgrade.

  I have the C++ developer support added to Eclipse.  To the best of my
  memory (and ability to interrogate apt) it is all installed from the
  Ubuntu repositories.

  When I click the Eclipse launcher pinned to my side bat I get an error 
message from Eclipse that reads:
  An error has occurred.  See the log file
  
/home/thomas/.eclipse/org.eclipse.platform_3.8_155965261/configuration/1532947738216.log

  Viewing the log file I see:
  !SESSION Mon Jul 30 11:48:58 BST 2018 
--
  !ENTRY org.eclipse.equinox.launcher 4 0 2018-07-30 11:48:58.229
  !MESSAGE Exception launching the Eclipse Platform:
  !STACK
  java.lang.ClassNotFoundException: 
org.eclipse.core.runtime.adaptor.EclipseStarter
  at 
java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626)
  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
  at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
  at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

  This is easily repeatable.

  Some internet searching suggests this problem is present upstream as
  there is a Debian bug that looks similar: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=891956

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eclipse 3.8.1-11
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jul 30 11:43:38 2018
  InstallationDate: Installed on 2017-11-16 (255 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: eclipse
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (3 days ago)

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

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

[Desktop-packages] [Bug 1784358] Re: Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

[Thomas A. F. Thorne]

Reinstalling Eclipse and Eclipse C/C++ Development Tooling also did not
change the error.

$ sudo apt-get install --reinstall eclipse eclipse-cdt g++
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 to upgrade, 0 to newly install, 3 reinstalled, 0 to remove and 1 not to 
upgrade.
Need to get 37.5 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 eclipse all 
3.8.1-11 [16.1 kB]
Get:2 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 eclipse-cdt all 
8.6.0-2 [37.5 MB]
Get:3 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 g++ amd64 
4:7.3.0-3ubuntu2 [1,576 B]   
Fetched 37.5 MB in 6s (5,987 kB/s)  
   
(Reading database ... 344165 files and directories currently installed.)
Preparing to unpack .../eclipse_3.8.1-11_all.deb ...
Unpacking eclipse (3.8.1-11) over (3.8.1-11) ...
Preparing to unpack .../eclipse-cdt_8.6.0-2_all.deb ...
Unpacking eclipse-cdt (8.6.0-2) over (8.6.0-2) ...
Preparing to unpack .../g++_4%3a7.3.0-3ubuntu2_amd64.deb ...
Unpacking g++ (4:7.3.0-3ubuntu2) over (4:7.3.0-3ubuntu2) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up g++ (4:7.3.0-3ubuntu2) ...
Setting up eclipse (3.8.1-11) ...
Setting up eclipse-cdt (8.6.0-2) ...

I shall try removing Eclipse using apt and installing from the website
instread.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eclipse in Ubuntu.
https://bugs.launchpad.net/bugs/1784358

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

Status in eclipse package in Ubuntu:
  New
Status in eclipse package in Debian:
  New

Bug description:
  I upgraded from 16.04 to 18.04 on Friday.  Following some reboots and
  updates this morning I am now unable to start the Eclipse IDE.  This
  was working before the upgrade.

  I have the C++ developer support added to Eclipse.  To the best of my
  memory (and ability to interrogate apt) it is all installed from the
  Ubuntu repositories.

  When I click the Eclipse launcher pinned to my side bat I get an error 
message from Eclipse that reads:
  An error has occurred.  See the log file
  
/home/thomas/.eclipse/org.eclipse.platform_3.8_155965261/configuration/1532947738216.log

  Viewing the log file I see:
  !SESSION Mon Jul 30 11:48:58 BST 2018 
--
  !ENTRY org.eclipse.equinox.launcher 4 0 2018-07-30 11:48:58.229
  !MESSAGE Exception launching the Eclipse Platform:
  !STACK
  java.lang.ClassNotFoundException: 
org.eclipse.core.runtime.adaptor.EclipseStarter
  at 
java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626)
  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
  at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
  at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

  This is easily repeatable.

  Some internet searching suggests this problem is present upstream as
  there is a Debian bug that looks similar: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=891956

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eclipse 3.8.1-11
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jul 30 11:43:38 2018
  InstallationDate: Installed on 2017-11-16 (255 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: eclipse
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (3 days ago)

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

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

[Desktop-packages] [Bug 1784358] Re: Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

[Thomas A. F. Thorne]

Reviewing the Debian equivalent people have suggested that:

$ sudo apt-get install --reinstall libequinox-osgi-java

Could resolve the issue.  Although some people note that it does not
help.  Others have recommended completely removing Eclipse as installed
through apt and instead using the version supplied directly on the
Eclipse CDT webpage https://www.eclipse.org/cdt/

I shall try both solutions this afternoon if there are no alternatives
suggested that people would like me to try.

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eclipse in Ubuntu.
https://bugs.launchpad.net/bugs/1784358

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

Status in eclipse package in Ubuntu:
  New
Status in eclipse package in Debian:
  Unknown

Bug description:
  I upgraded from 16.04 to 18.04 on Friday.  Following some reboots and
  updates this morning I am now unable to start the Eclipse IDE.  This
  was working before the upgrade.

  I have the C++ developer support added to Eclipse.  To the best of my
  memory (and ability to interrogate apt) it is all installed from the
  Ubuntu repositories.

  When I click the Eclipse launcher pinned to my side bat I get an error 
message from Eclipse that reads:
  An error has occurred.  See the log file
  
/home/thomas/.eclipse/org.eclipse.platform_3.8_155965261/configuration/1532947738216.log

  Viewing the log file I see:
  !SESSION Mon Jul 30 11:48:58 BST 2018 
--
  !ENTRY org.eclipse.equinox.launcher 4 0 2018-07-30 11:48:58.229
  !MESSAGE Exception launching the Eclipse Platform:
  !STACK
  java.lang.ClassNotFoundException: 
org.eclipse.core.runtime.adaptor.EclipseStarter
  at 
java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626)
  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
  at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
  at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

  This is easily repeatable.

  Some internet searching suggests this problem is present upstream as
  there is a Debian bug that looks similar: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=891956

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eclipse 3.8.1-11
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jul 30 11:43:38 2018
  InstallationDate: Installed on 2017-11-16 (255 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: eclipse
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (3 days ago)

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

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

[Desktop-packages] [Bug 1784358] [NEW] Eclipse not starting with org.eclipse.equinox.launcher.Main.main java.lang.ClassNotFoundException being issued after updgrade to 18.04

[Thomas A. F. Thorne]

Public bug reported:

I upgraded from 16.04 to 18.04 on Friday.  Following some reboots and
updates this morning I am now unable to start the Eclipse IDE.  This was
working before the upgrade.

I have the C++ developer support added to Eclipse.  To the best of my
memory (and ability to interrogate apt) it is all installed from the
Ubuntu repositories.

When I click the Eclipse launcher pinned to my side bat I get an error message 
from Eclipse that reads:
An error has occurred.  See the log file
/home/thomas/.eclipse/org.eclipse.platform_3.8_155965261/configuration/1532947738216.log

Viewing the log file I see:
!SESSION Mon Jul 30 11:48:58 BST 2018 --
!ENTRY org.eclipse.equinox.launcher 4 0 2018-07-30 11:48:58.229
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.ClassNotFoundException: 
org.eclipse.core.runtime.adaptor.EclipseStarter
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

This is easily repeatable.

Some internet searching suggests this problem is present upstream as
there is a Debian bug that looks similar: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=891956

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: eclipse 3.8.1-11
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Mon Jul 30 11:43:38 2018
InstallationDate: Installed on 2017-11-16 (255 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: eclipse
UpgradeStatus: Upgraded to bionic on 2018-07-27 (3 days ago)

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

** Affects: eclipse (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eclipse in Ubuntu.
https://bugs.launchpad.net/bugs/1784358

Title:
  Eclipse not starting with org.eclipse.equinox.launcher.Main.main
  java.lang.ClassNotFoundException being issued after updgrade to 18.04

Status in eclipse package in Ubuntu:
  New
Status in eclipse package in Debian:
  Unknown

Bug description:
  I upgraded from 16.04 to 18.04 on Friday.  Following some reboots and
  updates this morning I am now unable to start the Eclipse IDE.  This
  was working before the upgrade.

  I have the C++ developer support added to Eclipse.  To the best of my
  memory (and ability to interrogate apt) it is all installed from the
  Ubuntu repositories.

  When I click the Eclipse launcher pinned to my side bat I get an error 
message from Eclipse that reads:
  An error has occurred.  See the log file
  
/home/thomas/.eclipse/org.eclipse.platform_3.8_155965261/configuration/1532947738216.log

  Viewing the log file I see:
  !SESSION Mon Jul 30 11:48:58 BST 2018 
--
  !ENTRY org.eclipse.equinox.launcher 4 0 2018-07-30 11:48:58.229
  !MESSAGE Exception launching the Eclipse Platform:
  !STACK
  java.lang.ClassNotFoundException: 
org.eclipse.core.runtime.adaptor.EclipseStarter
  at 
java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626)
  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
  at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
  at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

  This is easily repeatable.

  Some internet searching suggests this problem is present upstream as
  there is a Debian bug that looks similar: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=891956

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eclipse 3.8.1-11
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jul 30 11:43:38 2018
  InstallationDate: Installed on 2017-11-16 (255 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no 

[Desktop-packages] [Bug 1306436] Re: unity-settings-daemon crashed with signal 5 in _XReply()

[Thomas A. F. Thorne]

I am doing OK at being taken to this page every few months.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1306436

Title:
  unity-settings-daemon crashed with signal 5 in _XReply()

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  it crashed itself

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140407-0ubuntu1
  Uname: Linux 3.14.0-031400-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 11 15:58:55 2014
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2014-04-01 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140328)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  Signal: 5
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/unity-settings-daemon-1.0/libclipboard.so
  Title: unity-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1306436/+subscriptions

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

[Desktop-packages] [Bug 1705287] Re: gedit crashed with SIGSEGV in gd_tagged_entry_remove_tag() when closing a file or searching through the text of one

[Thomas A. F. Thorne]

Eyeballed the attachments and cannot see anything sensitive in them.
Making this public instead of private.

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1705287

Title:
  gedit crashed with SIGSEGV in gd_tagged_entry_remove_tag() when
  closing a file or searching through the text of one

Status in gedit package in Ubuntu:
  New

Bug description:
  I had large number of files open (more than a dozen) and was searching
  through each one for test to replace.  I was saving and closing each
  file after I had finished my editing.  Then I would select the next
  file to work on from the top tab bar.

  I had two Gedit windows open.  One of them only a had a single file in
  it.

  Both gedit windows turned grey, eventually close and then the crash
  report was posted.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  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: Wed Jul 19 16:02:04 2017
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2015-03-12 (859 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: gedit
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f6f51107b57 : mov
0x28(%rdi),%rax
   PC (0x7f6f51107b57) ok
   source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gedit
  StacktraceTop:
   gd_tagged_entry_remove_tag () from 
/usr/lib/x86_64-linux-gnu/gedit/libgedit.so
   ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit.so
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gedit crashed with SIGSEGV in gd_tagged_entry_remove_tag()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd mock plugdev sambashare sudo 
wireshark

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

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

[Desktop-packages] [Bug 1245666] Re: Pidgin is creating zombies

[Thomas A. F. Thorne]

Closed down Pidgin.  Waited a few seconds for all the defunct processes
to go away.  Restarted Pidgin.  Probably only a minute later before the
first defunct process has arrived.

I am signed into 4 IRC channels automatically on startup.  I have tried
to send my identify command to the NickServ but other than that I have
not made any chats yet.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1245666

Title:
  Pidgin is creating zombies

Status in Pidgin:
  Unknown
Status in pidgin package in Ubuntu:
  Confirmed
Status in pidgin package in Fedora:
  Unknown

Bug description:
  After upgrading to Kubuntu 13.10 pidgin is constantly creating new
  zombies.

  E.g. after an uptime of roughly 4 hours:
  $ ps aux | grep Z
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  cm2589  0.0  0.0  0 0 ?Z17:46   0:00 [pidgin] 

  cm3045  0.0  0.0  0 0 ?Z17:47   0:00 [pidgin] 

  cm3106  0.0  0.0  0 0 ?Z17:48   0:00 [pidgin] 

  cm3236  0.0  0.0  0 0 ?Z17:50   0:00 [pidgin] 

  cm5760  0.0  0.0  0 0 ?Z17:54   0:00 [pidgin] 

  cm5788  0.0  0.0  0 0 ?Z18:02   0:00 [pidgin] 

  cm6405  0.0  0.0  0 0 ?Z18:12   0:00 [pidgin] 

  cm6501  0.0  0.0  0 0 ?Z18:22   0:00 [pidgin] 

  cm6519  0.0  0.0  0 0 ?Z18:32   0:00 [pidgin] 

  cm6543  0.0  0.0  0 0 ?Z18:42   0:00 [pidgin] 

  cm6580  0.0  0.0  0 0 ?Z18:52   0:00 [pidgin] 

  cm6619  0.0  0.0  0 0 ?Z19:02   0:00 [pidgin] 

  cm6645  0.0  0.0  0 0 ?Z19:12   0:00 [pidgin] 

  cm6672  0.0  0.0  0 0 ?Z19:22   0:00 [pidgin] 

  cm6691  0.0  0.0  0 0 ?Z19:32   0:00 [pidgin] 

  cm6757  0.0  0.0  0 0 ?Z19:42   0:00 [pidgin] 

  cm6846  0.0  0.0  0 0 ?Z19:52   0:00 [pidgin] 

  cm6869  0.0  0.0  0 0 ?Z20:01   0:00 [pidgin] 

  cm6889  0.0  0.0  0 0 ?Z20:11   0:00 [pidgin] 

  cm6914  0.0  0.0  0 0 ?Z20:21   0:00 [pidgin] 

  cm6931  0.0  0.0  0 0 ?Z20:31   0:00 [pidgin] 

  cm6948  0.0  0.0  0 0 ?Z20:41   0:00 [pidgin] 

  cm6972  0.0  0.0  0 0 ?Z20:51   0:00 [pidgin] 

  cm6992  0.0  0.0  0 0 ?Z21:01   0:00 [pidgin] 

  cm7015  0.0  0.0  0 0 ?Z21:11   0:00 [pidgin] 

  cm7036  0.0  0.0  0 0 ?Z21:20   0:00 [pidgin] 

  cm7121  0.0  0.0  0 0 ?Z21:30   0:00 [pidgin] 

  cm7223  0.0  0.0  10984   940 pts/0S+   21:38   0:00 grep 
--color=auto Z

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

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

[Desktop-packages] [Bug 1245666] Re: Pidgin is creating zombies

[Thomas A. F. Thorne]

It has been noted on the developer site for Pidgin that 1 defunct is
normal for DNS lookups.
https://developer.pidgin.im/ticket/15617#comment:11

The rest I have seen might come from failed attempts to connect to chat
services.  https://developer.pidgin.im/ticket/15617#comment:13 mentions
you get one for every connect attempt.  I did have a network issue last
night that would have blocked IPv4 access for several hours.  That might
explain what i have seen.  If I get further defunct processes without
any signs of network disruption I will report back, else assume that it
is provoked by network issues.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1245666

Title:
  Pidgin is creating zombies

Status in Pidgin:
  Unknown
Status in pidgin package in Ubuntu:
  Confirmed
Status in pidgin package in Fedora:
  Unknown

Bug description:
  After upgrading to Kubuntu 13.10 pidgin is constantly creating new
  zombies.

  E.g. after an uptime of roughly 4 hours:
  $ ps aux | grep Z
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  cm2589  0.0  0.0  0 0 ?Z17:46   0:00 [pidgin] 

  cm3045  0.0  0.0  0 0 ?Z17:47   0:00 [pidgin] 

  cm3106  0.0  0.0  0 0 ?Z17:48   0:00 [pidgin] 

  cm3236  0.0  0.0  0 0 ?Z17:50   0:00 [pidgin] 

  cm5760  0.0  0.0  0 0 ?Z17:54   0:00 [pidgin] 

  cm5788  0.0  0.0  0 0 ?Z18:02   0:00 [pidgin] 

  cm6405  0.0  0.0  0 0 ?Z18:12   0:00 [pidgin] 

  cm6501  0.0  0.0  0 0 ?Z18:22   0:00 [pidgin] 

  cm6519  0.0  0.0  0 0 ?Z18:32   0:00 [pidgin] 

  cm6543  0.0  0.0  0 0 ?Z18:42   0:00 [pidgin] 

  cm6580  0.0  0.0  0 0 ?Z18:52   0:00 [pidgin] 

  cm6619  0.0  0.0  0 0 ?Z19:02   0:00 [pidgin] 

  cm6645  0.0  0.0  0 0 ?Z19:12   0:00 [pidgin] 

  cm6672  0.0  0.0  0 0 ?Z19:22   0:00 [pidgin] 

  cm6691  0.0  0.0  0 0 ?Z19:32   0:00 [pidgin] 

  cm6757  0.0  0.0  0 0 ?Z19:42   0:00 [pidgin] 

  cm6846  0.0  0.0  0 0 ?Z19:52   0:00 [pidgin] 

  cm6869  0.0  0.0  0 0 ?Z20:01   0:00 [pidgin] 

  cm6889  0.0  0.0  0 0 ?Z20:11   0:00 [pidgin] 

  cm6914  0.0  0.0  0 0 ?Z20:21   0:00 [pidgin] 

  cm6931  0.0  0.0  0 0 ?Z20:31   0:00 [pidgin] 

  cm6948  0.0  0.0  0 0 ?Z20:41   0:00 [pidgin] 

  cm6972  0.0  0.0  0 0 ?Z20:51   0:00 [pidgin] 

  cm6992  0.0  0.0  0 0 ?Z21:01   0:00 [pidgin] 

  cm7015  0.0  0.0  0 0 ?Z21:11   0:00 [pidgin] 

  cm7036  0.0  0.0  0 0 ?Z21:20   0:00 [pidgin] 

  cm7121  0.0  0.0  0 0 ?Z21:30   0:00 [pidgin] 

  cm7223  0.0  0.0  10984   940 pts/0S+   21:38   0:00 grep 
--color=auto Z

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

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

[Desktop-packages] [Bug 1245666] Re: Pidgin is creating zombies

[Thomas A. F. Thorne]

Well I am seeing something odd in Pidgin.

$ ps -elf | grep defunct | wc -l
121
$ ps -elf | grep defunct | grep pidgin | wc -l
120

(One of the 'defunct' hits is the grep)

$ pidgin --version
Pidgin 2.10.12 (libpurple 2.10.12)

I have IRC, and XMPP to GoogleMail (Hangouts / Talk) configured and
active in Pidgin at the moment.  Someone else mentioned Google Hangouts
and I can easily live without for a few days to see if the problem goes
away.  Account Disabled.

I also have Facebook (XMPP), Skype (D-Bus) and Skype setup with Pidgin
but only the IRC and googlemail chat accounts were enabled when this
error was noticed.  I shall try closing Pidgin to clean up the defuncts.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1245666

Title:
  Pidgin is creating zombies

Status in Pidgin:
  Unknown
Status in pidgin package in Ubuntu:
  Confirmed
Status in pidgin package in Fedora:
  Unknown

Bug description:
  After upgrading to Kubuntu 13.10 pidgin is constantly creating new
  zombies.

  E.g. after an uptime of roughly 4 hours:
  $ ps aux | grep Z
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  cm2589  0.0  0.0  0 0 ?Z17:46   0:00 [pidgin] 

  cm3045  0.0  0.0  0 0 ?Z17:47   0:00 [pidgin] 

  cm3106  0.0  0.0  0 0 ?Z17:48   0:00 [pidgin] 

  cm3236  0.0  0.0  0 0 ?Z17:50   0:00 [pidgin] 

  cm5760  0.0  0.0  0 0 ?Z17:54   0:00 [pidgin] 

  cm5788  0.0  0.0  0 0 ?Z18:02   0:00 [pidgin] 

  cm6405  0.0  0.0  0 0 ?Z18:12   0:00 [pidgin] 

  cm6501  0.0  0.0  0 0 ?Z18:22   0:00 [pidgin] 

  cm6519  0.0  0.0  0 0 ?Z18:32   0:00 [pidgin] 

  cm6543  0.0  0.0  0 0 ?Z18:42   0:00 [pidgin] 

  cm6580  0.0  0.0  0 0 ?Z18:52   0:00 [pidgin] 

  cm6619  0.0  0.0  0 0 ?Z19:02   0:00 [pidgin] 

  cm6645  0.0  0.0  0 0 ?Z19:12   0:00 [pidgin] 

  cm6672  0.0  0.0  0 0 ?Z19:22   0:00 [pidgin] 

  cm6691  0.0  0.0  0 0 ?Z19:32   0:00 [pidgin] 

  cm6757  0.0  0.0  0 0 ?Z19:42   0:00 [pidgin] 

  cm6846  0.0  0.0  0 0 ?Z19:52   0:00 [pidgin] 

  cm6869  0.0  0.0  0 0 ?Z20:01   0:00 [pidgin] 

  cm6889  0.0  0.0  0 0 ?Z20:11   0:00 [pidgin] 

  cm6914  0.0  0.0  0 0 ?Z20:21   0:00 [pidgin] 

  cm6931  0.0  0.0  0 0 ?Z20:31   0:00 [pidgin] 

  cm6948  0.0  0.0  0 0 ?Z20:41   0:00 [pidgin] 

  cm6972  0.0  0.0  0 0 ?Z20:51   0:00 [pidgin] 

  cm6992  0.0  0.0  0 0 ?Z21:01   0:00 [pidgin] 

  cm7015  0.0  0.0  0 0 ?Z21:11   0:00 [pidgin] 

  cm7036  0.0  0.0  0 0 ?Z21:20   0:00 [pidgin] 

  cm7121  0.0  0.0  0 0 ?Z21:30   0:00 [pidgin] 

  cm7223  0.0  0.0  10984   940 pts/0S+   21:38   0:00 grep 
--color=auto Z

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

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

Re: [Desktop-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: 

[Desktop-packages] [Bug 1306436] Re: unity-settings-daemon crashed with signal 5 in _XReply()

[Thomas A. F. Thorne]

Occurred again today.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1306436

Title:
  unity-settings-daemon crashed with signal 5 in _XReply()

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  it crashed itself

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140407-0ubuntu1
  Uname: Linux 3.14.0-031400-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 11 15:58:55 2014
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2014-04-01 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140328)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  Signal: 5
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/unity-settings-daemon-1.0/libclipboard.so
  Title: unity-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1306436/+subscriptions

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

[Desktop-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 Desktop
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: Linux 

[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

[Thomas A. F. Thorne]

Installing the fixed file is not really a work around but the error
piping would work.  I'll live with the noise for now and try to get the
updated package installed once it reaches xenial-backports.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1644498

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

Status in appstream package in Ubuntu:
  In Progress

Bug description:
  Periodically I get emails from a machine with the subject:

  Cron  if [ -x /etc/munin/plugins/apt_all ]; then
  /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
  /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
  >/dev/null; fi

  And a body of:

  AppStream cache update completed, but some metadata was ignored due to
  errors.

  
  I have a machine monitored by Munin.  One of the plugins used on that machine 
is /etc/munin/plugins/apt which periodically counts the number of packets that 
can be upgraded.  This is achieved by a crontab entry installed from the 
package which looks like this:

  #
  # cron-jobs for munin-node
  #

  MAILTO=root

  # If the APT plugin is enabled, update packages databases approx. once
  # an hour (12 invokations an hour, 1 in 12 chance that the update will
  # happen), but ensure that there will never be more than two hour (7200
  # seconds) interval between updates..
  */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 
>/dev/null; fi

  
  For many months everything has been running smoothly.  On the 23rd November 
2016 I started getting the "AppStream cache update completed, but some metadata 
was ignored due to errors." messages at a rate of about ten a day.  

  
  I did a quick Google search which turned up a handful of bugs from earlier 
this year, such as 
  Bug1575248.  That is marked as Fixed Released though, so I am raising this 
new bug.

  If there are any further diagnostic details I can provide, please let
  me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 09:57:18 2016
  InstallationDate: Installed on 2013-05-08 (1295 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
  JournalErrors:
   -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 
GMT. --
   Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
  SourcePackage: appstream
  UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago)

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

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

[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

[Thomas A. F. Thorne]

> I think I found the issue, I'll prepare a patch.

That is great news.  Is there a work around I could try that would
silence the emails for a while?  Let me know if you would like me to try
out the updated binary.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1644498

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

Status in appstream package in Ubuntu:
  In Progress

Bug description:
  Periodically I get emails from a machine with the subject:

  Cron  if [ -x /etc/munin/plugins/apt_all ]; then
  /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
  /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
  >/dev/null; fi

  And a body of:

  AppStream cache update completed, but some metadata was ignored due to
  errors.

  
  I have a machine monitored by Munin.  One of the plugins used on that machine 
is /etc/munin/plugins/apt which periodically counts the number of packets that 
can be upgraded.  This is achieved by a crontab entry installed from the 
package which looks like this:

  #
  # cron-jobs for munin-node
  #

  MAILTO=root

  # If the APT plugin is enabled, update packages databases approx. once
  # an hour (12 invokations an hour, 1 in 12 chance that the update will
  # happen), but ensure that there will never be more than two hour (7200
  # seconds) interval between updates..
  */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 
>/dev/null; fi

  
  For many months everything has been running smoothly.  On the 23rd November 
2016 I started getting the "AppStream cache update completed, but some metadata 
was ignored due to errors." messages at a rate of about ten a day.  

  
  I did a quick Google search which turned up a handful of bugs from earlier 
this year, such as 
  Bug1575248.  That is marked as Fixed Released though, so I am raising this 
new bug.

  If there are any further diagnostic details I can provide, please let
  me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 09:57:18 2016
  InstallationDate: Installed on 2013-05-08 (1295 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
  JournalErrors:
   -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 
GMT. --
   Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
  SourcePackage: appstream
  UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago)

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

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

[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

[Thomas A. F. Thorne]

Thank you.  I could not figure out which combination of commands to send
appsteamcli. I had tried status and validate without success.  Here is
the requested output:

manager@Jenkins:~$ sudo appstreamcli refresh --verbose --force
[sudo] password for manager: 
** (appstreamcli:32754): DEBUG: Refreshing AppStream cache
** (appstreamcli:32754): DEBUG: Reading: 
/usr/share/app-info/xmls/org.freedesktop.fwupd.xml
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial_main_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial_restricted_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial_universe_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/security.ubuntu.com_ubuntu_dists_xenial-security_main_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/security.ubuntu.com_ubuntu_dists_xenial-security_restricted_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/security.ubuntu.com_ubuntu_dists_xenial-security_universe_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/security.ubuntu.com_ubuntu_dists_xenial-security_multiverse_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial_multiverse_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial-updates_main_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial-updates_restricted_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial-updates_universe_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: 
/var/lib/app-info/yaml/gb.archive.ubuntu.com_ubuntu_dists_xenial-updates_multiverse_dep11_Components-amd64.yml.gz
** (appstreamcli:32754): DEBUG: Reading: /var/cache/app-info/xmls/fwupd.xml
** (appstreamcli:32754): DEBUG: Detected colliding ids: plan.desktop was 
already added with the same priority.
** (appstreamcli:32754): DEBUG: Detected colliding ids: flcheckers.desktop was 
already added with the same priority.
** (appstreamcli:32754): DEBUG: Detected colliding ids: flblocks.desktop was 
already added with the same priority.
** (appstreamcli:32754): DEBUG: Detected colliding ids: flsudoku.desktop was 
already added with the same priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-startcenter.desktop' with 
data of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-math.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'eog.desktop' with data of higher 
priority.
** (appstreamcli:32754): DEBUG: Replaced 'display-im6.desktop' with data of 
higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-draw.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-impress.desktop' with 
data of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'display-im6.q16.desktop' with data of 
higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-writer.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'org.gnome.FileRoller.desktop' with 
data of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-base.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'libreoffice-calc.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'gimp.desktop' with data of higher 
priority.
** (appstreamcli:32754): DEBUG: Replaced 'chromium-browser.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'tracker-preferences.desktop' with 
data of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'tracker-needle.desktop' with data of 
higher priority.
** (appstreamcli:32754): DEBUG: Detected colliding ids: eog.desktop was already 
added with a higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'update-manager.desktop' with data of 
higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'gnome-session-properties.desktop' 
with data of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'upstart-monitor.desktop' with data of 
higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'fcitx-configtool.desktop' with data 
of higher priority.
** (appstreamcli:32754): DEBUG: Replaced 'fcitx.desktop' with data of higher 
priority.
** (appstreamcli:32754): DEBUG: Detected colliding ids: 
libreoffice-startcenter.desktop was already added with a higher priority.
** (appstreamcli:32754): DEBUG: 

[Desktop-packages] [Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"

[Thomas A. F. Thorne]

The error message popped out again for me just now.  I still cannot get
it to reproduce reliably but I have raised Bugs1644498 to start
diagnosis.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1575248

Title:
  "AppStream cache update completed, but some metadata was ignored due
  to errors." on "sudo apt-get update"

Status in AppStream:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in appstream package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Checks for apt updates using apt or apt-get also update the
  appstream cache.  Some of the appstream metadata installed locally
  isn't strictly valid as it's missing two fields.

  [Test Case]

   * fwupdmgr refresh
   * apt update
   * check for errors about metadata being ignored

  [Regression Potential]

   * This is just changing the XML metadata locally, I don't see any
  regression potential.

  [Other Info]
   
   * This fix has been applied upstream: 
https://github.com/hughsie/fwupd/commit/f4e0e88f7cba833a4badc1a3d62f1a08dd1bfd96

  [Original report]

  I have found that when there are new packages available which my
  machine doesn't know about yet, if I run "sudo apt-get update" this is
  the output:

  Get:1 http://gb.archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
  Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease [82.2 
kB]
  Get:4 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages [28 B]
  Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease 
[82.2 kB]
  Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted i386 
Packages [28 B]
  Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386 
Packages [28 B]
  Get:8 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 
Packages [28 B]
  Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 
Packages [28 B]
  Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse 
Translation-en [28 B]
  Get:11 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 
[1,201 kB]
  Get:12 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages 
[1,196 kB]
  Get:13 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en_GB 
[426 kB]
  Get:14 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en 
[568 kB]
  Get:15 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 
Metadata [733 kB]
  Get:16 http://gb.archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons 
[409 kB]
  Get:17 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages [8,344 B]
  Get:18 http://gb.archive.ubuntu.com/ubuntu xenial/restricted i386 
Packages [8,684 B]
  Get:19 http://gb.archive.ubuntu.com/ubuntu xenial/restricted 
Translation-en_GB [2,556 B]
  Get:20 http://gb.archive.ubuntu.com/ubuntu xenial/restricted 
Translation-en [2,908 B]
  Get:21 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 DEP-11 
Metadata [186 B]
  Get:22 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 
[7,532 kB]
  Get:23 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 
[7,512 kB]
  Get:24 http://gb.archive.ubuntu.com/ubuntu xenial/universe 
Translation-en_GB [3,040 kB]
  Get:25 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en 
[4,354 kB]
  Get:26 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 DEP-11 
Metadata [3,410 kB]
  Get:27 http://gb.archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64 
Icons [7,448 kB]
  Get:28 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages [144 kB]
  Get:29 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages [140 kB]
  Get:30 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse 
Translation-en_GB [88.1 kB]
  Get:31 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse 
Translation-en [106 kB]
  Get:32 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 DEP-11 
Metadata [63.8 kB]
  Get:33 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse DEP-11 64x64 
Icons [230 kB]
  Get:34 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages [28 B]
  Get:35 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages [28 B]
  Get:36 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main 
Translation-en [28 B]
  Get:37 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages [28 B]
  Get:38 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted i386 
Packages [28 B]
  Get:39 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted 
Translation-en 

[Desktop-packages] [Bug 1644498] [NEW] apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

[Thomas A. F. Thorne]

Public bug reported:

Periodically I get emails from a machine with the subject:

Cron  if [ -x /etc/munin/plugins/apt_all ]; then
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
>/dev/null; fi

And a body of:

AppStream cache update completed, but some metadata was ignored due to
errors.


I have a machine monitored by Munin.  One of the plugins used on that machine 
is /etc/munin/plugins/apt which periodically counts the number of packets that 
can be upgraded.  This is achieved by a crontab entry installed from the 
package which looks like this:

#
# cron-jobs for munin-node
#

MAILTO=root

# If the APT plugin is enabled, update packages databases approx. once
# an hour (12 invokations an hour, 1 in 12 chance that the update will
# happen), but ensure that there will never be more than two hour (7200
# seconds) interval between updates..
*/5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 
>/dev/null; fi


For many months everything has been running smoothly.  On the 23rd November 
2016 I started getting the "AppStream cache update completed, but some metadata 
was ignored due to errors." messages at a rate of about ten a day.  


I did a quick Google search which turned up a handful of bugs from earlier this 
year, such as 
Bug1575248.  That is marked as Fixed Released though, so I am raising this new 
bug.

If there are any further diagnostic details I can provide, please let me
know.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: appstream 0.9.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Nov 24 09:57:18 2016
InstallationDate: Installed on 2013-05-08 (1295 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
JournalErrors:
 -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 
GMT. --
 Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
ProcEnviron:
 TERM=xterm-256color
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
SourcePackage: appstream
UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago)

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


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1644498

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

Status in appstream package in Ubuntu:
  New

Bug description:
  Periodically I get emails from a machine with the subject:

  Cron  if [ -x /etc/munin/plugins/apt_all ]; then
  /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
  /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
  >/dev/null; fi

  And a body of:

  AppStream cache update completed, but some metadata was ignored due to
  errors.

  
  I have a machine monitored by Munin.  One of the plugins used on that machine 
is /etc/munin/plugins/apt which periodically counts the number of packets that 
can be upgraded.  This is achieved by a crontab entry installed from the 
package which looks like this:

  #
  # cron-jobs for munin-node
  #

  MAILTO=root

  # If the APT plugin is enabled, update packages databases approx. once
  # an hour (12 invokations an hour, 1 in 12 chance that the update will
  # happen), but ensure that there will never be more than two hour (7200
  # seconds) interval between updates..
  */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 
>/dev/null; fi

  
  For many months everything has been running smoothly.  On the 23rd November 
2016 I started getting the "AppStream cache update completed, but some metadata 
was ignored due to errors." messages at a rate of about ten a day.  

  
  I did a quick Google search which turned up a handful of bugs from earlier 
this year, such as 
  Bug1575248.  That is marked as Fixed Released though, so I am raising this 
new bug.

  If there are any further diagnostic details I can provide, please let
  me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 09:57:18 2016
  InstallationDate: Installed on 2013-05-08 (1295 days ago)
  

[Desktop-packages] [Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"

[Thomas A. F. Thorne]

I started seeing this message: 
 AppStream cache update completed, but some metadata was ignored due to errors.
on one machine on the 23rd November 2016.  I would expect this to be a seperate 
issue.   I cannot reproduce it right now, if I am able to do so later I will 
try and raise a new bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1575248

Title:
  "AppStream cache update completed, but some metadata was ignored due
  to errors." on "sudo apt-get update"

Status in AppStream:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in appstream package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Checks for apt updates using apt or apt-get also update the
  appstream cache.  Some of the appstream metadata installed locally
  isn't strictly valid as it's missing two fields.

  [Test Case]

   * fwupdmgr refresh
   * apt update
   * check for errors about metadata being ignored

  [Regression Potential]

   * This is just changing the XML metadata locally, I don't see any
  regression potential.

  [Other Info]
   
   * This fix has been applied upstream: 
https://github.com/hughsie/fwupd/commit/f4e0e88f7cba833a4badc1a3d62f1a08dd1bfd96

  [Original report]

  I have found that when there are new packages available which my
  machine doesn't know about yet, if I run "sudo apt-get update" this is
  the output:

  Get:1 http://gb.archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
  Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease [82.2 
kB]
  Get:4 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages [28 B]
  Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease 
[82.2 kB]
  Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted i386 
Packages [28 B]
  Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386 
Packages [28 B]
  Get:8 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 
Packages [28 B]
  Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 
Packages [28 B]
  Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse 
Translation-en [28 B]
  Get:11 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 
[1,201 kB]
  Get:12 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages 
[1,196 kB]
  Get:13 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en_GB 
[426 kB]
  Get:14 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en 
[568 kB]
  Get:15 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 
Metadata [733 kB]
  Get:16 http://gb.archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons 
[409 kB]
  Get:17 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages [8,344 B]
  Get:18 http://gb.archive.ubuntu.com/ubuntu xenial/restricted i386 
Packages [8,684 B]
  Get:19 http://gb.archive.ubuntu.com/ubuntu xenial/restricted 
Translation-en_GB [2,556 B]
  Get:20 http://gb.archive.ubuntu.com/ubuntu xenial/restricted 
Translation-en [2,908 B]
  Get:21 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 DEP-11 
Metadata [186 B]
  Get:22 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 
[7,532 kB]
  Get:23 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 
[7,512 kB]
  Get:24 http://gb.archive.ubuntu.com/ubuntu xenial/universe 
Translation-en_GB [3,040 kB]
  Get:25 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en 
[4,354 kB]
  Get:26 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 DEP-11 
Metadata [3,410 kB]
  Get:27 http://gb.archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64 
Icons [7,448 kB]
  Get:28 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages [144 kB]
  Get:29 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages [140 kB]
  Get:30 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse 
Translation-en_GB [88.1 kB]
  Get:31 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse 
Translation-en [106 kB]
  Get:32 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 DEP-11 
Metadata [63.8 kB]
  Get:33 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse DEP-11 64x64 
Icons [230 kB]
  Get:34 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages [28 B]
  Get:35 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages [28 B]
  Get:36 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main 
Translation-en [28 B]
  Get:37 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages [28 B]
  Get:38 

[Desktop-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 Desktop
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 to xenial 

[Desktop-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: 

[Desktop-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 Desktop
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 in.  Shortly 

[Desktop-packages] [Bug 1462327] Re: Apport retracing service says my packages are out of date but shows very similar version numbers

[Thomas A. F. Thorne]

So you are saying that the debug packages were probably unavailable and
that caused the error.  The confusing part was that the error message
said "Please upgrade your system to the latest package versions." when
what it needed to say was something like "Please try generating this
report later once the debug symbol packages are available."

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1462327

Title:
  Apport retracing service says my packages are out of date but shows
  very similar version numbers

Status in xorg-server-lts-utopic package in Ubuntu:
  Invalid

Bug description:
  Over in : https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-
  utopic/+bug/1462308 I got a message starting:

  Thank you for your report!

  However, processing it in order to get sufficient information for the
  developers failed (it does not generate a useful symbolic stack trace). This
  might be caused by some outdated packages which were installed on your system
  at the time of the report:

  outdated debug symbol package for libudev1: package version 204-5ubuntu20.12 
dbgsym version 204-5ubuntu20
  outdated debug symbol package for libfreetype6: package version 
2.5.2-1ubuntu2.4 dbgsym version 2.5.2-1ubuntu2
  no debug symbol package found for libbz2-1.0
  outdated debug symbol package for libcgmanager0: package version 
0.24-0ubuntu7.3 dbgsym version 0.24-0ubuntu5

  Please upgrade your system to the latest package versions. If you still
  encounter the crash, please file a new report.

  Thank you for your understanding, and sorry for the inconvenience!

  -

  Which seemed fair enough to me until I took a closer look at the
  packages.  I noticed that I had not packages to update:

  I have just done an update and then
  $ sudo apt-get upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

  That I had not updated any of the listed packages recently (based on
  /var/log/apt/histroy) and that I had rebooted at 14:00 the previous
  day which was long after the last time I was asked to reboot following
  and update.

  
  Looking at those numbers it seems that the dbgsm system has dropped the 
lesser digits and then said I was out of date? 
  I think there is possibly a bug with that.   I am raising this ticket to 
check if those numbers are equivalent and the apport system is dropping the 
last digits off the version number and getting confused.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-utopic/+bug/1462327/+subscriptions

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

[Desktop-packages] [Bug 1547340] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

[Thomas A. F. Thorne]

Actually, having looked at the SD card again it seems that the old
partitions were removed but the new partition was not added.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1547340

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  crashed when making a usb fat32 and did not finish making a fat32 file
  system.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: hostname 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 01:10:08 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-02-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160217)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa8b4a38b6f :   
mov(%rbx),%rdi
   PC (0x7fa8b4a38b6f) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  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/ubuntu/+source/gnome-disk-utility/+bug/1547340/+subscriptions

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

[Desktop-packages] [Bug 1547340] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

[Thomas A. F. Thorne]

Making a second attempt after reopening the Disks application seemed to
work.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1547340

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  crashed when making a usb fat32 and did not finish making a fat32 file
  system.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: hostname 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 01:10:08 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-02-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160217)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa8b4a38b6f :   
mov(%rbx),%rdi
   PC (0x7fa8b4a38b6f) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  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/ubuntu/+source/gnome-disk-utility/+bug/1547340/+subscriptions

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

[Desktop-packages] [Bug 1547340] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

[Thomas A. F. Thorne]

I was creating a Ext4 filesystem on an SD card.  AS far as I could tell
the process had completed several seconds before the crash report came
up.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1547340

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  crashed when making a usb fat32 and did not finish making a fat32 file
  system.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: hostname 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 01:10:08 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-02-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160217)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa8b4a38b6f :   
mov(%rbx),%rdi
   PC (0x7fa8b4a38b6f) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_window_select_object ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  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/ubuntu/+source/gnome-disk-utility/+bug/1547340/+subscriptions

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

[Desktop-packages] [Bug 1527817] Re: unhelpful error message "Parsing filters is unsupported."

[Thomas A. F. Thorne]

The Archive Manager GUI does not seem to handle some files that it
possibly should.  It seems that for some files it is necessary to
instead install unrar and then uncompress these files from the command
line with `uunrar x `

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1527817

Title:
  unhelpful error message "Parsing filters is unsupported."

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

1. download 
http://www.speedlink.com/support/bin/sl-8861-b-cd-content-02-26-10.zip
2. try to extract the `.iso` file into `/tmp/`

  The error message `Parsing filters is unsupported.` doesn't provide
  any information and doesn't explain if something and what is wrong and
  thus needs to be replaced by  a message which does that.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: file-roller 3.16.4-1ubuntu3
  Uname: Linux 4.3.0-040300-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 19 02:11:40 2015
  InstallationDate: Installed on 2015-12-12 (6 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: file-roller
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1527817/+subscriptions

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

[Desktop-packages] [Bug 1364285] Re: nautilus does not start

[Thomas A. F. Thorne]

I have apparently seen this error on:
$ uname -a
Linux thorne-ul-dt 3.16.0-71-generic #91~14.04.1-Ubuntu SMP Mon Apr 18 19:43:36 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
I do not know how I caused it to happen though.  The automatic error reporting 
brought me here.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1364285

Title:
  nautilus does not start

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  After clicking the nautilus could not be launched for many clicks

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic i686
  NonfreeKernelModules: wl
  ActionNames:
   
  ActionPaths: 
/org/gnome/Nautilus;/com/canonical/unity/gtk/window/29;/org/gnome/Nautilus/window/15;
  Added: 1
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: i386
  BusName: :1.74
  CurrentDesktop: Unity
  Date: Tue Sep  2 11:30:30 2014
  DuplicateSignature: GMenuModelItemsChangedInvalidIndex
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'type', 'date_modified', 'where']"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'group', 'where', 'mime_type', 'owner', 'permissions']"
  InstallationDate: Installed on 2012-03-24 (891 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324)
  ItemCount: 1
  LinkType: sub menu
  MenuLabel:
   
  MenuName:
   
  MenuPath: /com/canonical/unity/gtk/window/29
  ParentActionNames: 
unity.File;unity.Edit;unity.View;unity.Go;unity.Bookmarks;unity.Help;
  ParentLinkType: section
  ParentMenuLabel:
   
  ParentMenuName:
   
  Position: 6
  ProcCmdline: nautilus -n
  Removed: 0
  SourcePackage: nautilus
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-08-24 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1557370] Re: evolution-alarm-notify crashed with signal 5 in g_object_new_valist()

[Thomas A. F. Thorne]

I could not see anything sensitive in the logs so I have opened up this
bug to being public.

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1557370

Title:
  evolution-alarm-notify crashed with signal 5 in g_object_new_valist()

Status in evolution package in Ubuntu:
  New

Bug description:
  After rebooting my PC I was presented with an error report dialogue
  which lead me to filing this report.  I do not know at what point the
  error was originally generated.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libevolution 3.10.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-67.87~14.04.1-generic 3.16.7-ckt24
  Uname: Linux 3.16.0-67-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Mar 15 08:31:41 2016
  ExecutablePath: /usr/lib/evolution/3.10/evolution-alarm-notify
  InstallationDate: Installed on 2015-03-12 (368 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/evolution/3.10/evolution-alarm-notify
  Signal: 5
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: evolution-alarm-notify crashed with signal 5 in g_object_new_valist()
  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/+bug/1557370/+subscriptions

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

[Desktop-packages] [Bug 1506430] Re: /usr/lib/evolution/evolution-alarm-notify:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new

[Thomas A. F. Thorne]

Bug #1548226 has been marked as a duplicate of this bug.  I cannot
access the extra details contained at
https://errors.ubuntu.com/problem/6278aa0a9d4c4b72421d1b1f986661f47e7357c5
so I cannot confirm if this is a duplicate or not.

Please could a public facing summary of the hidden details be provided
here for users who do not have access to the error reports.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1506430

Title:
  /usr/lib/evolution/evolution-alarm-
  
notify:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new

Status in evolution package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding evolution.  This problem was most recently seen with version
  3.16.5-1ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6278aa0a9d4c4b72421d1b1f986661f47e7357c5
  contains more details.

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

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

[Desktop-packages] [Bug 1548226] Re: evolution-alarm-notify crashed with signal 5 in g_object_new_valist() on Login

[Thomas A. F. Thorne]

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

Bug #1506430 contains very little information, so it is hard to say if
this is a duplicate of that bug or not.  It looks as if things should be
fixed in 3.16.5-1ubuntu2; so if anyone has that package (or a later one)
installed and sees this issue repeat they should either reopen Bug
#1506430 or mark this bug as not being a duplicate of it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1548226

Title:
  evolution-alarm-notify crashed with signal 5 in g_object_new_valist()
  on Login

Status in evolution package in Ubuntu:
  New

Bug description:
  Login to Ubuntu and you are presented with this problem.  In my case
  this seems to have come about after removing the evolution mail
  client.

  Suggested duplicates were: 
  Bug #1386599 
  Bug #1264075 
  Bug #1259943
  Bug #273951 
  Bug #1386599

  All of those do look similar to me.  However I am raising a new ticket
  as some of them have no traces and some of them have traces that the
  retracer failed to deal with.

  I do not think the traces matter, I think the problem is that you cannot 
easily and cleanly uninstall evolution after having used it for a while.  All I 
have installed is the evolution-data-server package.  
  $ sudo aptitude search evolution | grep "i "
  i A evolution-data-server   - evolution database backend server   
  
  i A evolution-data-server-common- architecture independent files for 
Evoluti
  i A evolution-data-server-online-ac - evolution data server integration with 
Ubu
  p   evolution-mapi  - Exchange support for the Evolution 
groupwa

  If I attempt to remove that, it want to take some other things with it:
  thomasthorne@thorne-ul-dt:~$ sudo aptitude remove evolution-data-server
  The following packages will be REMOVED:  
evolution-data-server 
  0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  Need to get 0 B of archives. After unpacking 1,452 kB will be freed.
  The following packages have unmet dependencies:
   libfolks-eds25 : Depends: evolution-data-server (>= 3.2.0) but it is not 
going to be installed.
  The following actions will resolve these dependencies:

   Remove the following packages:   
  1) gnome-contacts 
  2) libfolks-eds25 

   Leave the following dependencies unresolved: 
  3) indicator-datetime recommends evolution-data-server
  4) libfolks25 recommends libfolks-eds25   
  5) empathy recommends gnome-contacts  

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

   Keep the following packages at their current version:
  1) evolution-data-server [3.10.4-0ubuntu1.5 (now, trusty-updates)]


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

   Downgrade the following packages:
  
  1) evolution-data-server [3.10.4-0ubuntu1.5 (now, trusty-updates) -> 
3.10.4-0ubuntu1
  2) evolution-data-server-common [3.10.4-0ubuntu1.5 (now, trusty-updates) 
-> 3.10.4-0
  3) evolution-data-server-online-accounts [3.10.4-0ubuntu1.5 (now, 
trusty-updates) ->
  4) libcamel-1.2-45 [3.10.4-0ubuntu1.5 (now, trusty-updates) -> 
3.10.4-0ubuntu1 (trus


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


  I guess that the 5 other bugs raised for this since 2008 might also
  have been from people that removed evolution.  There was also a Gnome
  bug marked as related
  https://bugzilla.gnome.org/show_bug.cgi?id=553631 but it was for a
  version that was too old to be looked into.  If raising this ticket
  gets some helpful traces generated, perhapse that bug could be updated
  to show them too.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libevolution 3.10.4-0ubuntu2
  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: Mon Feb 22 07:32:30 2016
  ExecutablePath: /usr/lib/evolution/3.10/evolution-alarm-notify
  InstallationDate: Installed on 2015-03-12 (346 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/evolution/3.10/evolution-alarm-notify
  Signal: 5
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: evolution-alarm-notify 

[Desktop-packages] [Bug 1259943] Re: evolution-alarm-notify crashed with signal 5 in g_settings_set_property()

[Thomas A. F. Thorne]

I think I have seen something quite similar to this bug.  I made a fresh
report as Bug #1548226 which includes some valid symbolic stack traces.
Hopefully the developers will be able to use them to work on the issue.

Should this bug ticket be marked as a duplicate of Bug #1548226 as the
circumstances in which it happens are very similar?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1259943

Title:
  evolution-alarm-notify crashed with signal 5 in
  g_settings_set_property()

Status in evolution package in Ubuntu:
  Invalid

Bug description:
  Appeared after login to freshly booted Ubuntu 13.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: libevolution 3.8.4-0ubuntu1
  Uname: Linux 3.11.0-031100rc7-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Dec 11 14:47:32 2013
  ExecutablePath: /usr/lib/evolution/3.8/evolution-alarm-notify
  InstallationDate: Installed on 2013-02-26 (288 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/3.8/evolution-alarm-notify
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  Signal: 5
  SourcePackage: evolution
  StacktraceTop:
   g_settings_set_property (object=0x7fa7d5942ab0, prop_id=, 
value=, pspec=) at 
/build/buildd/glib2.0-2.38.1/./gio/gsettings.c:492
   object_set_property (nqueue=0x7fa7d589e200, value=, 
pspec=0x7fa7d57da740, object=0x7fa7d5942ab0) at 
/build/buildd/glib2.0-2.38.1/./gobject/gobject.c:1366
   g_object_new_internal (class=class@entry=0x7fa7d57cf2a0, 
params=params@entry=0x7fffa8d762a0, n_params=1) at 
/build/buildd/glib2.0-2.38.1/./gobject/gobject.c:1779
   g_object_new_valist (object_type=object_type@entry=140358818165504, 
first_property_name=first_property_name@entry=0x7fa7d204702f "schema-id", 
var_args=var_args@entry=0x7fffa8d763f8) at 
/build/buildd/glib2.0-2.38.1/./gobject/gobject.c:2002
   g_object_new (object_type=140358818165504, 
first_property_name=0x7fa7d204702f "schema-id") at 
/build/buildd/glib2.0-2.38.1/./gobject/gobject.c:1559
  Title: evolution-alarm-notify crashed with signal 5 in 
g_settings_set_property()
  UpgradeStatus: Upgraded to saucy on 2013-11-05 (36 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo vboxusers

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

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

[Desktop-packages] [Bug 273951] Re: evolution-alarm-notify crashed with SIGSEGV in g_object_newv()

[Thomas A. F. Thorne]

I think I have seen something quite similar to this bug.  I made a fresh
report as Bug #1548226 which includes some valid symbolic stack traces.
Hopefully the developers will be able to use them to work on the issue.

Should this bug ticket be marked as a duplicate of Bug #1548226 as the
circumstances in which it happens are very similar?

If this is thought to be the same bug then perhaps the upstream records
should also be amended as I must be using a more recent version of
evolution.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/273951

Title:
  evolution-alarm-notify crashed with SIGSEGV in g_object_newv()

Status in Evolution:
  Expired
Status in evolution package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: evolution

  Description:Ubuntu intrepid (development branch)
  Release:8.10

  evolution:
Installed: 2.24.0-0ubuntu1
Candidate: 2.24.0-0ubuntu1
Version table:
   *** 2.24.0-0ubuntu1 0
  500 http://ubuntu.intergenia.de intrepid/main Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/lib/evolution/2.24/evolution-alarm-notify
  Package: evolution 2.24.0-0ubuntu1
  ProcAttrCurrent: unconfined
  ProcCmdline: /usr/lib/evolution/2.24/evolution-alarm-notify 
--oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_AlarmNotify_Factory:2.24 
--oaf-ior-fd=20
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   g_object_newv () from /usr/lib/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
   g_object_new () from /usr/lib/libgobject-2.0.so.0
   gtk_window_group_new () from /usr/lib/libgtk-x11-2.0.so.0
   gtk_window_get_group () from /usr/lib/libgtk-x11-2.0.so.0
  Title: evolution-alarm-notify crashed with SIGSEGV in g_object_newv()
  Uname: Linux 2.6.27-4-generic i686
  UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1264075] Re: evolution-alarm-notify crashed with signal 5 in g_settings_set_property()

[Thomas A. F. Thorne]

I think I have seen something quite similar to this bug.  I made a fresh
report as Bug #1548226 which includes some valid symbolic stack traces.
Hopefully the developers will be able to use them to work on the issue.

Should this bug ticket be marked as a duplicate of Bug #1548226 as the
circumstances in which it happens are very similar?

Matthias; are you able to confirm if the Evolution email package was
removed before this problem stated to occur?  I realise it was quite a
while ago that you made the report.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1264075

Title:
  evolution-alarm-notify crashed with signal 5 in
  g_settings_set_property()

Status in evolution package in Ubuntu:
  Invalid

Bug description:
  Appeared after login to freshly booted Ubuntu 13.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: libevolution 3.8.4-0ubuntu1
  Uname: Linux 3.11.0-031100rc7-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Dec 25 11:25:22 2013
  ExecutablePath: /usr/lib/evolution/3.8/evolution-alarm-notify
  InstallationDate: Installed on 2013-02-26 (302 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/3.8/evolution-alarm-notify
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  Signal: 5
  SourcePackage: evolution
  StacktraceTop:
   g_settings_set_property (object=0x7faeba046ab0, prop_id=, 
value=, pspec=) at 
/build/buildd/glib2.0-2.38.1/./gio/gsettings.c:492
   object_set_property (nqueue=0x7faeb9fc1a00, value=, 
pspec=0x7faeb9f24740, object=0x7faeba046ab0) at 
/build/buildd/glib2.0-2.38.1/./gobject/gobject.c:1366
   g_object_new_internal (class=class@entry=0x7faeb9f5d670, 
params=params@entry=0x7fffdb6dfc20, n_params=1) at 
/build/buildd/glib2.0-2.38.1/./gobject/gobject.c:1779
   g_object_new_valist (object_type=object_type@entry=140388420817664, 
first_property_name=first_property_name@entry=0x7faeb636002f "schema-id", 
var_args=var_args@entry=0x7fffdb6dfd78) at 
/build/buildd/glib2.0-2.38.1/./gobject/gobject.c:2002
   g_object_new (object_type=140388420817664, 
first_property_name=0x7faeb636002f "schema-id") at 
/build/buildd/glib2.0-2.38.1/./gobject/gobject.c:1559
  Title: evolution-alarm-notify crashed with signal 5 in 
g_settings_set_property()
  UpgradeStatus: Upgraded to saucy on 2013-11-05 (49 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo vboxusers

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

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

[Desktop-packages] [Bug 1386599] Re: evolution-alarm-notify crashed with signal 5 in g_object_new_valist()

[Thomas A. F. Thorne]

I think I have seen something quite similar to this bug.  I made a fresh
report as Bug #1548226 which includes some valid symbolic stack traces.
Hopefully the developers will be able to use them to work on the issue.

Should this bug ticket be marked as a duplicate of Bug #1548226 as the
circumstances in which it happens are very similar?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1386599

Title:
  evolution-alarm-notify crashed with signal 5 in g_object_new_valist()

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  I've seen this problem's  been around since former Ubuntu versions,
  i'm using 14.04 trusty  disto and the problem continues to happen,
  every time i just restart or switch on the computer after an off
  period i get this message and it's very annoying. Any further
  information about it would be appreciated.

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

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

[Desktop-packages] [Bug 1548226] Re: evolution-alarm-notify crashed with signal 5 in g_object_new_valist() on Login

[Thomas A. F. Thorne]

I have looked through the traces and other logs files supplied, nothing
looks sensitive to me.  Setting to public as I cannot see a reason to
keep this bug marked as private.

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1548226

Title:
  evolution-alarm-notify crashed with signal 5 in g_object_new_valist()
  on Login

Status in evolution package in Ubuntu:
  New

Bug description:
  Login to Ubuntu and you are presented with this problem.  In my case
  this seems to have come about after removing the evolution mail
  client.

  Suggested duplicates were: 
  Bug #1386599 
  Bug #1264075 
  Bug #1259943
  Bug #273951 
  Bug #1386599

  All of those do look similar to me.  However I am raising a new ticket
  as some of them have no traces and some of them have traces that the
  retracer failed to deal with.

  I do not think the traces matter, I think the problem is that you cannot 
easily and cleanly uninstall evolution after having used it for a while.  All I 
have installed is the evolution-data-server package.  
  $ sudo aptitude search evolution | grep "i "
  i A evolution-data-server   - evolution database backend server   
  
  i A evolution-data-server-common- architecture independent files for 
Evoluti
  i A evolution-data-server-online-ac - evolution data server integration with 
Ubu
  p   evolution-mapi  - Exchange support for the Evolution 
groupwa

  If I attempt to remove that, it want to take some other things with it:
  thomasthorne@thorne-ul-dt:~$ sudo aptitude remove evolution-data-server
  The following packages will be REMOVED:  
evolution-data-server 
  0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  Need to get 0 B of archives. After unpacking 1,452 kB will be freed.
  The following packages have unmet dependencies:
   libfolks-eds25 : Depends: evolution-data-server (>= 3.2.0) but it is not 
going to be installed.
  The following actions will resolve these dependencies:

   Remove the following packages:   
  1) gnome-contacts 
  2) libfolks-eds25 

   Leave the following dependencies unresolved: 
  3) indicator-datetime recommends evolution-data-server
  4) libfolks25 recommends libfolks-eds25   
  5) empathy recommends gnome-contacts  

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

   Keep the following packages at their current version:
  1) evolution-data-server [3.10.4-0ubuntu1.5 (now, trusty-updates)]


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

   Downgrade the following packages:
  
  1) evolution-data-server [3.10.4-0ubuntu1.5 (now, trusty-updates) -> 
3.10.4-0ubuntu1
  2) evolution-data-server-common [3.10.4-0ubuntu1.5 (now, trusty-updates) 
-> 3.10.4-0
  3) evolution-data-server-online-accounts [3.10.4-0ubuntu1.5 (now, 
trusty-updates) ->
  4) libcamel-1.2-45 [3.10.4-0ubuntu1.5 (now, trusty-updates) -> 
3.10.4-0ubuntu1 (trus


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


  I guess that the 5 other bugs raised for this since 2008 might also
  have been from people that removed evolution.  There was also a Gnome
  bug marked as related
  https://bugzilla.gnome.org/show_bug.cgi?id=553631 but it was for a
  version that was too old to be looked into.  If raising this ticket
  gets some helpful traces generated, perhapse that bug could be updated
  to show them too.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libevolution 3.10.4-0ubuntu2
  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: Mon Feb 22 07:32:30 2016
  ExecutablePath: /usr/lib/evolution/3.10/evolution-alarm-notify
  InstallationDate: Installed on 2015-03-12 (346 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/evolution/3.10/evolution-alarm-notify
  Signal: 5
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: evolution-alarm-notify crashed with signal 5 in g_object_new_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

To manage notifications 

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1147600] Re: pidgin crashed with SIGABRT in __libc_message()

[Thomas A. F. Thorne]

D-Bus has one problem and if I switch back I just see this one instead.
I guess I will have to drop Skype support from Pidgin on my system as it
seems to have too many problems.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1147600

Title:
  pidgin crashed with SIGABRT in __libc_message()

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Pidgin starts normally, then crashes after a few minutes.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: pidgin 1:2.10.7-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2
  Uname: Linux 3.8.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  5 14:43:58 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pidgin
  MarkForUpload: True
  ProcCmdline: pidgin --session 2b1b064a5-7292-486d-918b-5d0c90deaa46 --display 
:0.0
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pidgin
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   _IceFreeConnection () from /usr/lib/x86_64-linux-gnu/libICE.so.6
  Title: pidgin crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to raring on 2013-02-16 (17 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1306436] Re: unity-settings-daemon crashed with signal 5 in _XReply()

[Thomas A. F. Thorne]

Seen again today it seems.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1306436

Title:
  unity-settings-daemon crashed with signal 5 in _XReply()

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  it crashed itself

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140407-0ubuntu1
  Uname: Linux 3.14.0-031400-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 11 15:58:55 2014
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2014-04-01 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140328)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  Signal: 5
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/unity-settings-daemon-1.0/libclipboard.so
  Title: unity-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1306436/+subscriptions

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

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1194465] Re: scope-runner-dbus.py crashed with SIGSEGV in auth_session_remote_object_destroyed_cb()

[Thomas A. F. Thorne]

My Ubuntu 14.04 LTS 64-bit system had just rebooted after installing
some software updates.  As it happens my DHCP server was offline when I
rebooted so I ended up with no IP networking for 1/2 hour.  While I was
instigating what was wrong with my PC (not yet knowing that the DHCP
server was offline) I had an error report pop up.  Once the Internet
connection was restored I reported the error.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-scope-gdrive in Ubuntu.
https://bugs.launchpad.net/bugs/1194465

Title:
  scope-runner-dbus.py crashed with SIGSEGV in
  auth_session_remote_object_destroyed_cb()

Status in Google Documents Lens:
  New
Status in unity-scope-gdrive package in Ubuntu:
  Triaged

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity-scopes-runner 7.0.4daily13.06.24-0ubuntu1
  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
  CheckboxSubmission: 2f383a1679e8525d7196eb2518a1921f
  CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
  CrashCounter: 1
  Date: Tue Jun 25 14:03:13 2013
  Dependencies:
   
  ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
  InstallationDate: Installed on 2011-08-19 (676 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110817)
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py 
/usr/share/unity-scopes/gdrive/unity_gdrive_daemon.py
  SegvAnalysis:
   Segfault happened at: 0x7f5d8db9a91e:cmp%rbp,(%rax)
   PC (0x7f5d8db9a91e) ok
   source "%rbp" ok
   destination "(%rax)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: libunity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: Upgraded to saucy on 2013-06-07 (17 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare utah

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scope-gdrive/+bug/1194465/+subscriptions

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

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 

[Desktop-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 Desktop
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 O.E.M.
  

[Desktop-packages] [Bug 1147600] Re: pidgin crashed with SIGABRT in __libc_message()

[Thomas A. F. Thorne]

This seems to happen quite repeatedly.  I'll try switching from the
Skype to Skype (D-Bus) within Pidgin to see if that changes things much.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1147600

Title:
  pidgin crashed with SIGABRT in __libc_message()

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Pidgin starts normally, then crashes after a few minutes.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: pidgin 1:2.10.7-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2
  Uname: Linux 3.8.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  5 14:43:58 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pidgin
  MarkForUpload: True
  ProcCmdline: pidgin --session 2b1b064a5-7292-486d-918b-5d0c90deaa46 --display 
:0.0
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pidgin
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   _IceFreeConnection () from /usr/lib/x86_64-linux-gnu/libICE.so.6
  Title: pidgin crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to raring on 2013-02-16 (17 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1306436] Re: unity-settings-daemon crashed with signal 5 in _XReply()

[Thomas A. F. Thorne]

It seems that I hit this again today while also seeing Bug #1493103, Bug
#1493852 and Bug #1022993.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1306436

Title:
  unity-settings-daemon crashed with signal 5 in _XReply()

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  it crashed itself

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140407-0ubuntu1
  Uname: Linux 3.14.0-031400-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 11 15:58:55 2014
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2014-04-01 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140328)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  Signal: 5
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/unity-settings-daemon-1.0/libclipboard.so
  Title: unity-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1306436/+subscriptions

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

[Desktop-packages] [Bug 1306436] Re: unity-settings-daemon crashed with signal 5 in _XReply()

[Thomas A. F. Thorne]

I have been direct here after Bug #1493107 was marked of a duplicate of
this one.  I can see the stacktrace bits do look similar in places.
Something about the clipboard being present in both.  I do not think I
had just performed a copy or paste when I hit this issue but it would be
very likely that I had something in a buffer.

Are there any steps I should take to aid diagnostics, should this bug
reproduce on my system?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1306436

Title:
  unity-settings-daemon crashed with signal 5 in _XReply()

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  it crashed itself

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140407-0ubuntu1
  Uname: Linux 3.14.0-031400-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 11 15:58:55 2014
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2014-04-01 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140328)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  Signal: 5
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/unity-settings-daemon-1.0/libclipboard.so
  Title: unity-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1306436/+subscriptions

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

[Desktop-packages] [Bug 1147600] Re: pidgin crashed with SIGABRT in __libc_message()

[Thomas A. F. Thorne]

No Skype crash today just a Pidgin one.  Other suggested bugs were Bugs
#159488, #249096 and #556430.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1147600

Title:
  pidgin crashed with SIGABRT in __libc_message()

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Pidgin starts normally, then crashes after a few minutes.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: pidgin 1:2.10.7-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2
  Uname: Linux 3.8.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  5 14:43:58 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pidgin
  MarkForUpload: True
  ProcCmdline: pidgin --session 2b1b064a5-7292-486d-918b-5d0c90deaa46 --display 
:0.0
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pidgin
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   _IceFreeConnection () from /usr/lib/x86_64-linux-gnu/libICE.so.6
  Title: pidgin crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to raring on 2013-02-16 (17 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1147600] Re: pidgin crashed with SIGABRT in __libc_message()

[Thomas A. F. Thorne]

I had skype crash much earlier on in the day but it seemed to have
recovered.  I am using both Skype and Google Hangouts on a different
machine with the same accounts linked into Pidgin.  Let me know if there
is any other data I can provide that might be useful.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1147600

Title:
  pidgin crashed with SIGABRT in __libc_message()

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Pidgin starts normally, then crashes after a few minutes.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: pidgin 1:2.10.7-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2
  Uname: Linux 3.8.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  5 14:43:58 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pidgin
  MarkForUpload: True
  ProcCmdline: pidgin --session 2b1b064a5-7292-486d-918b-5d0c90deaa46 --display 
:0.0
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pidgin
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   _IceFreeConnection () from /usr/lib/x86_64-linux-gnu/libICE.so.6
  Title: pidgin crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to raring on 2013-02-16 (17 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1483643] Re: evolution hangs (grey window) while previewing an email

[Thomas A. F. Thorne]

strace-6288-evolution-calendar-factory.txt showing strace output of
evolution-calendar-factory taken over a few minutes.

** Attachment added: strace-6288-evolution-calendar-factory.txt
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442846/+files/strace-6288-evolution-calendar-factory.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1483643

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  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/1483643/+subscriptions

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

[Desktop-packages] [Bug 1483643] Re: evolution hangs (grey window) while previewing an email

[Thomas A. F. Thorne]

strace-7088-evolution-alarm-notify.txt showing strace for evolution-
alarm-notify taken over the same few minutes.

** Attachment added: strace-7088-evolution-alarm-notify.txt
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442848/+files/strace-7088-evolution-alarm-notify.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1483643

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  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/1483643/+subscriptions

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

[Desktop-packages] [Bug 1483643] Re: evolution hangs (grey window) while previewing an email

[Thomas A. F. Thorne]

strace-6165-evolution-source-registry.txt strace volution-source-
registry of taken over the same few minutes.

** Attachment added: strace-6165-evolution-source-registry.txt
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442849/+files/strace-6165-evolution-source-registry.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1483643

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  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/1483643/+subscriptions

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

[Desktop-packages] [Bug 1483643] Re: evolution hangs (grey window) while previewing an email

[Thomas A. F. Thorne]

strace-25363-evolution-addressbook-factory strace of evolution-
addressbook-factory taken over the same few minutes.

** Attachment added: strace-25363-evolution-addressbook-factory
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442850/+files/strace-25363-evolution-addressbook-factory

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1483643

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  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/1483643/+subscriptions

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

[Desktop-packages] [Bug 1483643] [NEW] evolution hangs (grey window) while previewing an email

[Thomas A. F. Thorne]

Public bug reported:

I had left evolution running overnight.  It seems to develop issues
after being left to run for a while on my current system.

This morning I returned focus to the evolution window and tried to view
the latest email from my Exchange account in the preview window.
retrieving message 'AQMk...' is displayed in the preview area and
after a short while the application turns gray, suggesting that the
process has hung.  It has been that way for about an hour, so I started
trying to collect some diagnostic info.

$ ps -elf | grep evolution
0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

$ sudo strace -p 7492
Process 7492 attached
futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

I'll attach the other data as .txt files in a bit.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: evolution 3.10.4-0ubuntu2
Uname: Linux 4.1.0-040100rc8-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug 11 11:36:36 2015
InstallationDate: Installed on 2015-03-12 (151 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1483643

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  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/1483643/+subscriptions

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

[Desktop-packages] [Bug 1483643] Re: evolution hangs (grey window) while previewing an email

[Thomas A. F. Thorne]

I did  
  $ sudo gdb --batch --ex t a a bt -pid=`pidof evolution` bt.txt
the resulting file is attached.  I had a quick look through it and could not 
see any sensitive data in there.  


** Attachment added: $ sudo gdb --batch --ex t a a bt -pid=`pidof evolution` 
bt.txt
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442844/+files/bt.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1483643

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  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/1483643/+subscriptions

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

[Desktop-packages] [Bug 1482529] Re: pidgin crashed with SIGSEGV in start_thread() on login to Ubuntu

[Thomas A. F. Thorne]

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

If I manually type the URL for 1208209 into my browser I get a page that
suggests it might exist and be private.  So there is a good chance this
is another case of bug #764414 causing confusion.  I don't know why the
system does not make 1 private bug and mark everything ever raised as a
duplicate of that.  The experience for users would not change and
developers might see a bit less bug noise, which seems to be the main
concern in most of the 764414 family of woes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1482529

Title:
  pidgin crashed with SIGSEGV in start_thread() on login to Ubuntu

Status in pidgin package in Ubuntu:
  New

Bug description:
  I logged into Ubuntu desktop this morning after shutting down the
  machine overnight.  When it had logged in a message about Pidgin
  having experienced a problem was on the screen.  The timestamp on
  /var/crash/_usr_bin_pidgin.1000.crash suggests this did happen while
  logging into the Unity desktop this morning.

  Recent changes including switch to the Skype plugin (instead of the
  Skype (D-Bus) one) and setting Skype as a startup application inside
  the Startup Applications application.  Skype started but did not login
  as I had not saved my password into it.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pidgin 1:2.10.9-0ubuntu3.2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  7 08:05:56 2015
  ExecutablePath: /usr/bin/pidgin
  InstallationDate: Installed on 2015-03-12 (147 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  ProcCmdline: pidgin
  SegvAnalysis:
   Segfault happened at: 0x7f76eef728a9:cmpb   $0x0,(%rdi)
   PC (0x7f76eef728a9) ok
   source $0x0 ok
   destination (%rdi) (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: pidgin
  StacktraceTop:
   ?? () from /usr/lib/purple-2/libskype.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   start_thread (arg=0x7f76d0b42700) at pthread_create.c:312
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
  Title: pidgin crashed with SIGSEGV in start_thread()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin mock plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1482529] Re: pidgin crashed with SIGSEGV in start_thread() on login to Ubuntu

[Thomas A. F. Thorne]

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

This is a new high in my experience of Apport.  Instead of doing it's
usual trick of marking something a duplicate of a private bug, it has
just marked this one as a duplicate of bug #1208209 which Cannot be
found according to the pop up window.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1482529

Title:
  pidgin crashed with SIGSEGV in start_thread() on login to Ubuntu

Status in pidgin package in Ubuntu:
  New

Bug description:
  I logged into Ubuntu desktop this morning after shutting down the
  machine overnight.  When it had logged in a message about Pidgin
  having experienced a problem was on the screen.  The timestamp on
  /var/crash/_usr_bin_pidgin.1000.crash suggests this did happen while
  logging into the Unity desktop this morning.

  Recent changes including switch to the Skype plugin (instead of the
  Skype (D-Bus) one) and setting Skype as a startup application inside
  the Startup Applications application.  Skype started but did not login
  as I had not saved my password into it.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pidgin 1:2.10.9-0ubuntu3.2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  7 08:05:56 2015
  ExecutablePath: /usr/bin/pidgin
  InstallationDate: Installed on 2015-03-12 (147 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  ProcCmdline: pidgin
  SegvAnalysis:
   Segfault happened at: 0x7f76eef728a9:cmpb   $0x0,(%rdi)
   PC (0x7f76eef728a9) ok
   source $0x0 ok
   destination (%rdi) (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: pidgin
  StacktraceTop:
   ?? () from /usr/lib/purple-2/libskype.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   start_thread (arg=0x7f76d0b42700) at pthread_create.c:312
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
  Title: pidgin crashed with SIGSEGV in start_thread()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin mock plugdev sambashare sudo

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

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

[Desktop-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 Desktop
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 fine.  It 

[Desktop-packages] [Bug 1477574] [NEW] unity-settings-daemon crashed while I was using Synergy on another screen

[Thomas A. F. Thorne]

Public bug reported:

I have a laptop and keyboard plugged into my Ubuntu desktop PC.  I have
Synergy installed on this PC and a laptop so that I can use the same
keyboard an mouse on both.  While I was working on my laptop I heard the
HDD of the PC grind up then saw the Ubuntu machine drop out to the login
screen.

== ApportVersion =
2.14.1-0ubuntu3.11

== Architecture =
amd64

== CoreDump =
(58638336 bytes)

== CurrentDesktop =
Unity

== Date =
Thu Jul 23 13:41:30 2015

== Disassembly =
= 0x7f7173c7fc13 g_logv+739: lea0x2b7606(%rip),%rdi# 
0x7f7173f37220
   0x7f7173c7fc1a g_logv+746: mov%ebp,%esi
   0x7f7173c7fc1c g_logv+748: callq  0x7f7173cbad40 g_private_set
   0x7f7173c7fc21 g_logv+753: jmpq   0x7f7173c7fb0e g_logv+478
   0x7f7173c7fc26 g_logv+758: mov$0x5,%ecx
   0x7f7173c7fc2b g_logv+763: jmpq   0x7f7173c7fa74 g_logv+324
   0x7f7173c7fc30 g_logv+768: mov0x8(%r14),%esi
   0x7f7173c7fc34 g_logv+772: lea0x30(%rsp),%r15
   0x7f7173c7fc39 g_logv+777: mov%r15,%rdi
   0x7f7173c7fc3c g_logv+780: callq  0x7f7173c7ee70
   0x7f7173c7fc41 g_logv+785: mov0x10(%r14),%rdx
   0x7f7173c7fc45 g_logv+789: lea0x47bbc(%rip),%rdi# 
0x7f7173cc7808
   0x7f7173c7fc4c g_logv+796: mov%r15,%rsi
   0x7f7173c7fc4f g_logv+799: xor%eax,%eax
   0x7f7173c7fc51 g_logv+801: callq  0x7f7173c95c90 g_strdup_printf
   0x7f7173c7fc56 g_logv+806: mov%r12d,%esi

== DistroRelease =
Ubuntu 14.04

== ExecutablePath =
/usr/lib/unity-settings-daemon/unity-settings-daemon

== ExecutableTimestamp =
1426788581

== InstallationDate =
Installed on 2015-03-12 (132 days ago)

== InstallationMedia =
Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)

== Package =
unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu2

== PackageArchitecture =
amd64

== ProblemType =
Crash

== ProcCmdline =
/usr/lib/unity-settings-daemon/unity-settings-daemon

== ProcEnviron =
PATH=(custom, user)
SHELL=/bin/bash
LD_LIBRARY_PATH=set
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
XDG_RUNTIME_DIR=set

== ProcStatus =
Name:   unity-settings-
State:  D (disk sleep)
Tgid:   3292
Ngid:   0
Pid:3292
PPid:   3098
TracerPid:  0
Uid:1000100010001000
Gid:1000100010001000
FDSize: 64
Groups: 4 24 27 30 46 108 124 999 1000 1001 
NStgid: 3292
NSpid:  3292
NSpgid: 3292
NSsid:  3292
VmPeak:   874120 kB
VmSize:   812324 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM: 27472 kB
VmRSS: 23692 kB
VmData:   447220 kB
VmStk:   136 kB
VmExe:32 kB
VmLib: 31688 kB
VmPTE:   644 kB
VmPMD:12 kB
VmSwap:  752 kB
Threads:4
SigQ:   0/45781
SigPnd: 
ShdPnd: 
SigBlk: 
SigIgn: 1000
SigCgt: 000180004000
CapInh: 
CapPrm: 
CapEff: 
CapBnd: 003f
Seccomp:0
Cpus_allowed:   ff
Cpus_allowed_list:  0-7
Mems_allowed:   ,0001
Mems_allowed_list:  0
voluntary_ctxt_switches:9627
nonvoluntary_ctxt_switches: 125

== Stacktrace =
#0  0x7f7173c7fc13 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#1  0x7f7173c7fd72 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7f717298d351 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
No symbol table info available.
#3  0x7f7172995ab1 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
No symbol table info available.
#4  0x7f7172f3154b in _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
No symbol table info available.
#5  0x7f7172f2e5e7 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
No symbol table info available.
#6  0x7f7172f2e695 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
No symbol table info available.
#7  0x7f7172f2f578 in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
No symbol table info available.
#8  0x7f7172f2b0cd in XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
No symbol table info available.
#9  0x7f7150cf0718 in ?? () from 
/usr/lib/unity-settings-daemon-1.0/libclipboard.so
No symbol table info available.
#10 0x7f7150cf0e66 in ?? () from 
/usr/lib/unity-settings-daemon-1.0/libclipboard.so
No symbol table info available.
#11 0x7f7172992b91 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
No symbol table info available.
#12 

[Desktop-packages] [Bug 1477566] Re: compiz crashed with SIGSEGV in g_closure_invoke() seemingly without user interaction

[Thomas A. F. Thorne]

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

Apport has said that this is a duplicate of bug #1438210 but as I cannot
view that bug I cannot comment on whether it is correct or not.  Why is
that one a private bug but this one a public one?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1477566

Title:
  compiz crashed with SIGSEGV in g_closure_invoke() seemingly without
  user interaction

Status in compiz package in Ubuntu:
  New

Bug description:
  The error reported in the bug report does resemble that of 
  ​Bug #727041 unity-window-decorator crashed with SIGSEGV in g_closure_invoke()
  Fix Released (34 comments) last updated 2014-10-11 view this bug
  Bug  #724874 unity-window-decorator crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECT()
  Fix Released (41 comments) last updated 2012-02-16 view this bug
  Bug #726432 compiz crashed with SIGSEGV in g_type_check_instance_cast()
  Confirmed (10 comments) last updated 2012-07-15 view this bug
  Bug  #726897 unity-window-decorator crashed with SIGSEGV in g_closure_invoke()
  Invalid (6 comments) last updated 2011-04-10 view this bug

  However all of those seem to state they needed some user interaction.
  I was using my keyboard and mouse through Synergy to control a laptop.
  I should not have been exorcising any of the onbox GUI when this crash
  seemed to occur.  I have a second crash report listed under /var/crash
  /_usr_lib_unity-settings-daemon_unity-settings-daemon.1000.crash but
  when I tried to report it I was instructed to update nautilus-data and
  see if it still occurs.  This confused me as the Software Updater did
  not list this as needing an update but when I do `apt-get upgrade -s`
  I can see that it is listed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11.3+14.04.20150313-0ubuntu1
  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 13:41:33 2015
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  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
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin mock plugdev sambashare sudo
  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
  

[Desktop-packages] [Bug 1477566] Re: compiz crashed with SIGSEGV in g_closure_invoke() seemingly without user interaction

[Thomas A. F. Thorne]

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

I manually created Bug #1477574 from the /var/crash/_usr_lib_unity-
settings-daemon_unity-settings-daemon.1000.crash reported above in case
the data in it is helpful in the diagnosis of this bug, or vis versa.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1477566

Title:
  compiz crashed with SIGSEGV in g_closure_invoke() seemingly without
  user interaction

Status in compiz package in Ubuntu:
  New

Bug description:
  The error reported in the bug report does resemble that of 
  ​Bug #727041 unity-window-decorator crashed with SIGSEGV in g_closure_invoke()
  Fix Released (34 comments) last updated 2014-10-11 view this bug
  Bug  #724874 unity-window-decorator crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECT()
  Fix Released (41 comments) last updated 2012-02-16 view this bug
  Bug #726432 compiz crashed with SIGSEGV in g_type_check_instance_cast()
  Confirmed (10 comments) last updated 2012-07-15 view this bug
  Bug  #726897 unity-window-decorator crashed with SIGSEGV in g_closure_invoke()
  Invalid (6 comments) last updated 2011-04-10 view this bug

  However all of those seem to state they needed some user interaction.
  I was using my keyboard and mouse through Synergy to control a laptop.
  I should not have been exorcising any of the onbox GUI when this crash
  seemed to occur.  I have a second crash report listed under /var/crash
  /_usr_lib_unity-settings-daemon_unity-settings-daemon.1000.crash but
  when I tried to report it I was instructed to update nautilus-data and
  see if it still occurs.  This confused me as the Software Updater did
  not list this as needing an update but when I do `apt-get upgrade -s`
  I can see that it is listed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11.3+14.04.20150313-0ubuntu1
  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 13:41:33 2015
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  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
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin mock plugdev sambashare sudo
  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: 

[Desktop-packages] [Bug 1477574] Re: unity-settings-daemon crashed while I was using Synergy on another screen

[Thomas A. F. Thorne]

I have just mentioned this bug in Bug #1477631, which manifested itself
in a similar way a couple of hours after I saw and reported this bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1477574

Title:
  unity-settings-daemon crashed while I was using Synergy on another
  screen

Status in compiz package in Ubuntu:
  New

Bug description:
  I have a laptop and keyboard plugged into my Ubuntu desktop PC.  I
  have Synergy installed on this PC and a laptop so that I can use the
  same keyboard an mouse on both.  While I was working on my laptop I
  heard the HDD of the PC grind up then saw the Ubuntu machine drop out
  to the login screen.

  == ApportVersion =
  2.14.1-0ubuntu3.11

  == Architecture =
  amd64

  == CoreDump =
  (58638336 bytes)

  == CurrentDesktop =
  Unity

  == Date =
  Thu Jul 23 13:41:30 2015

  == Disassembly =
  = 0x7f7173c7fc13 g_logv+739: lea0x2b7606(%rip),%rdi# 
0x7f7173f37220
 0x7f7173c7fc1a g_logv+746: mov%ebp,%esi
 0x7f7173c7fc1c g_logv+748: callq  0x7f7173cbad40 g_private_set
 0x7f7173c7fc21 g_logv+753: jmpq   0x7f7173c7fb0e g_logv+478
 0x7f7173c7fc26 g_logv+758: mov$0x5,%ecx
 0x7f7173c7fc2b g_logv+763: jmpq   0x7f7173c7fa74 g_logv+324
 0x7f7173c7fc30 g_logv+768: mov0x8(%r14),%esi
 0x7f7173c7fc34 g_logv+772: lea0x30(%rsp),%r15
 0x7f7173c7fc39 g_logv+777: mov%r15,%rdi
 0x7f7173c7fc3c g_logv+780: callq  0x7f7173c7ee70
 0x7f7173c7fc41 g_logv+785: mov0x10(%r14),%rdx
 0x7f7173c7fc45 g_logv+789: lea0x47bbc(%rip),%rdi# 
0x7f7173cc7808
 0x7f7173c7fc4c g_logv+796: mov%r15,%rsi
 0x7f7173c7fc4f g_logv+799: xor%eax,%eax
 0x7f7173c7fc51 g_logv+801: callq  0x7f7173c95c90 g_strdup_printf
 0x7f7173c7fc56 g_logv+806: mov%r12d,%esi

  == DistroRelease =
  Ubuntu 14.04

  == ExecutablePath =
  /usr/lib/unity-settings-daemon/unity-settings-daemon

  == ExecutableTimestamp =
  1426788581

  == InstallationDate =
  Installed on 2015-03-12 (132 days ago)

  == InstallationMedia =
  Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)

  == Package =
  unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu2

  == PackageArchitecture =
  amd64

  == ProblemType =
  Crash

  == ProcCmdline =
  /usr/lib/unity-settings-daemon/unity-settings-daemon

  == ProcEnviron =
  PATH=(custom, user)
  SHELL=/bin/bash
  LD_LIBRARY_PATH=set
  LANG=en_GB.UTF-8
  LANGUAGE=en_GB:en
  XDG_RUNTIME_DIR=set

  == ProcStatus =
  Name:   unity-settings-
  State:  D (disk sleep)
  Tgid:   3292
  Ngid:   0
  Pid:3292
  PPid:   3098
  TracerPid:  0
  Uid:1000100010001000
  Gid:1000100010001000
  FDSize: 64
  Groups: 4 24 27 30 46 108 124 999 1000 1001 
  NStgid: 3292
  NSpid:  3292
  NSpgid: 3292
  NSsid:  3292
  VmPeak:   874120 kB
  VmSize:   812324 kB
  VmLck: 0 kB
  VmPin: 0 kB
  VmHWM: 27472 kB
  VmRSS: 23692 kB
  VmData:   447220 kB
  VmStk:   136 kB
  VmExe:32 kB
  VmLib: 31688 kB
  VmPTE:   644 kB
  VmPMD:12 kB
  VmSwap:  752 kB
  Threads:4
  SigQ:   0/45781
  SigPnd: 
  ShdPnd: 
  SigBlk: 
  SigIgn: 1000
  SigCgt: 000180004000
  CapInh: 
  CapPrm: 
  CapEff: 
  CapBnd: 003f
  Seccomp:0
  Cpus_allowed:   ff
  Cpus_allowed_list:  0-7
  Mems_allowed:   ,0001
  Mems_allowed_list:  0
  voluntary_ctxt_switches:9627
  nonvoluntary_ctxt_switches: 125

  == Stacktrace =
  #0  0x7f7173c7fc13 in g_logv () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #1  0x7f7173c7fd72 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f717298d351 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  No symbol table info available.
  #3  0x7f7172995ab1 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  No symbol table info available.
  #4  0x7f7172f3154b in _XError () from 
/usr/lib/x86_64-linux-gnu/libX11.so.6
  No symbol table info available.
  #5  0x7f7172f2e5e7 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
  No symbol table info available.
  #6  

[Desktop-packages] [Bug 1477566] Re: compiz crashed with SIGSEGV in g_closure_invoke() seemingly without user interaction

[Thomas A. F. Thorne]

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

I have just mentioned this bug in Bug #1477631, which manifested itself
in a similar way a couple of hours after I saw and reported this bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1477566

Title:
  compiz crashed with SIGSEGV in g_closure_invoke() seemingly without
  user interaction

Status in compiz package in Ubuntu:
  New

Bug description:
  The error reported in the bug report does resemble that of 
  ​Bug #727041 unity-window-decorator crashed with SIGSEGV in g_closure_invoke()
  Fix Released (34 comments) last updated 2014-10-11 view this bug
  Bug  #724874 unity-window-decorator crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECT()
  Fix Released (41 comments) last updated 2012-02-16 view this bug
  Bug #726432 compiz crashed with SIGSEGV in g_type_check_instance_cast()
  Confirmed (10 comments) last updated 2012-07-15 view this bug
  Bug  #726897 unity-window-decorator crashed with SIGSEGV in g_closure_invoke()
  Invalid (6 comments) last updated 2011-04-10 view this bug

  However all of those seem to state they needed some user interaction.
  I was using my keyboard and mouse through Synergy to control a laptop.
  I should not have been exorcising any of the onbox GUI when this crash
  seemed to occur.  I have a second crash report listed under /var/crash
  /_usr_lib_unity-settings-daemon_unity-settings-daemon.1000.crash but
  when I tried to report it I was instructed to update nautilus-data and
  see if it still occurs.  This confused me as the Software Updater did
  not list this as needing an update but when I do `apt-get upgrade -s`
  I can see that it is listed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11.3+14.04.20150313-0ubuntu1
  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 13:41:33 2015
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  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
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin mock plugdev sambashare sudo
  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
  

[Desktop-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

[Desktop-packages] [Bug 713551] Re: Xorg freeze; system locks and accepts no input, keyboard lights go out when key is touched

[Thomas A. F. Thorne]

** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
https://bugs.launchpad.net/bugs/713551

Title:
  Xorg freeze; system locks and accepts no input, keyboard lights go out
  when key is touched

Status in MythTV:
  New
Status in nvidia-graphics-drivers-173 package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: xorg

  I have a rather old machine running a MythTV backend using a WinTV
  NOVA T USB2 (93000 Rev B8A2) and it seems that randomly the system
  will lock up completely.  I have done my best to work out if the
  freeze occurs when recording or performing some function of the
  mythtv-backend but based on the logs it seems that it can occur during
  a recording, during a database update or when there is no activity at
  all.

  I do have BOINC installed and running but disabling that so it does
  not run at startup didn't seem to stop the problem; as the freeze
  occurs randomly every few days I had to wait about a week but the
  system did lock up without BOINC running at all.  My next fiddle was
  to change the priority of the mythtvbackend process to be -3; this
  seemed to reduce the frequency of the freeze occurring but it may have
  been psychological as the occurance rate is so drawn out anyway.

  One thing which triggered a freeze was using the ubuntu-bug program,
  before the report that I am using to make this bug entry the system
  froze while ubuntu-bug was off collecting information about the
  problem.  Again the mythtvbackend was running so I cannot discount
  this just being coincidence.

  Another symptom, which may just be how the thing works, is that the
  NOVA T USB2 strays in warm mode during the crash and if I use the
  PC's reset button to restart the system.  When the system comes up
  like this the NOVA T is unresponsive and the red light on the from of
  it remains lit.  If I power down the machine or pull the USB cord out
  from the NOVA T then plug it back in after several seconds while the
  bios boot splash screen is going then the red LED extinguishes and the
  device works fine once Ubuntu has booted.

  This is all a little scattered and probably unhelpful but I have tried
  to hunt down answers to this problem myself and have run out of ideas
  what to do next.  Please do let me know if there are any further
  diagnostics that may be helpful.

  lsb_release -rd
  Description:  Ubuntu 10.04.1 LTS
  Release:  10.04

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xorg 1:7.5+5ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
  Uname: Linux 2.6.32-28-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  CheckboxSubmission: 5d0602330b5d44cd5ded7b4846756bb0
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  Date: Sat Feb  5 08:45:59 2011
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-28-generic 
root=UUID=f8cbb2f7-5b7c-46db-94bc-1802d312a175 ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  dmi.bios.date: 08/16/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-6570E
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/16/2004:svn:pn:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6570E:rvr:cvn:ct3:cvr:
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-28-generic
  --- 
  Architecture: i386
  CheckboxSubmission: 5d0602330b5d44cd5ded7b4846756bb0
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  CurrentDmesg:
   [   26.607216] agpgart-nvidia :00:00.0: AGP 3.0 bridge
   [   26.607241] agpgart-nvidia :00:00.0: putting AGP V3 device into 8x 
mode
   [   26.607326] nvidia :01:00.0: putting AGP V3 device into 8x mode
   [   29.232041] eth0: no IPv6 routers present
   [  104.758599] ondemand governor failed, too long transition latency of HW, 
fallback to performance governor
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
  NonfreeKernelModules: nvidia
  Package: nvidia-graphics-drivers-173 (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-28-generic 
root=UUID=f8cbb2f7-5b7c-46db-94bc-1802d312a175 ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
  Tags: lucid lucid
  Uname: Linux 2.6.32-28-generic i686
  UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare
  dmi.bios.date: 08/16/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-6570E
  

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 720295] Re: system-config-printer.py crashed with AttributeError in nextNPTab(): Device instance has no attribute 'hp_scannable'

[Thomas A. F. Thorne]

Thank you Chris.  I suppose it is more a question for Robert Roth as he
seems to have marked this bug as Fix Released but apport seems to think
I hit it yesterday morning.

On my second attempt to add the printer things worked.  This is not
blocking me but it feels wrong to leave infrequent crashes marked as
fixed when they are not.  Perhaps apport was mistaken when it attributed
things to this bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/720295

Title:
  system-config-printer.py crashed with AttributeError in nextNPTab():
  Device instance has no attribute 'hp_scannable'

Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: system-config-printer

  Attempted to add printer. Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: system-config-printer-gnome 1.2.7+20110216-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
  Uname: Linux 2.6.38-1-generic i686
  Architecture: i386
  CupsErrorLog:
   
  Date: Wed Feb 16 14:07:51 2011
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 Karmic Koala - Release i386 
(20091028.4)
  InterpreterPath: /usr/bin/python2.7
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK Computer INC. 1005HA
  PackageArchitecture: all
  Papersize: letter
  ProcCmdline: /usr/bin/python 
/usr/share/system-config-printer/system-config-printer.py
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic 
root=UUID=cf74d3f3-d8d8-4c5c-b59d-b6be12838571 ro 
crashkernel=384M-2G:64M,2G-:128M
  PythonArgs: ['/usr/share/system-config-printer/system-config-printer.py']
  SourcePackage: system-config-printer
  Title: system-config-printer.py crashed with AttributeError in nextNPTab(): 
Device instance has no attribute 'hp_scannable'
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev 
sambashare tape video
  dmi.bios.date: 02/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1005HA
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd02/26/2010:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1005HA
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/720295/+subscriptions

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

[Desktop-packages] [Bug 720295] Re: system-config-printer.py crashed with AttributeError in nextNPTab(): Device instance has no attribute 'hp_scannable'

[Thomas A. F. Thorne]

If this was fixed in Natty, how have I just been told that I have hit it
in  Ubuntu 14.04.2 LTS by apport?  That suggests it was not fixed or a
regression has occurred.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/720295

Title:
  system-config-printer.py crashed with AttributeError in nextNPTab():
  Device instance has no attribute 'hp_scannable'

Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: system-config-printer

  Attempted to add printer. Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: system-config-printer-gnome 1.2.7+20110216-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
  Uname: Linux 2.6.38-1-generic i686
  Architecture: i386
  CupsErrorLog:
   
  Date: Wed Feb 16 14:07:51 2011
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 Karmic Koala - Release i386 
(20091028.4)
  InterpreterPath: /usr/bin/python2.7
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK Computer INC. 1005HA
  PackageArchitecture: all
  Papersize: letter
  ProcCmdline: /usr/bin/python 
/usr/share/system-config-printer/system-config-printer.py
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic 
root=UUID=cf74d3f3-d8d8-4c5c-b59d-b6be12838571 ro 
crashkernel=384M-2G:64M,2G-:128M
  PythonArgs: ['/usr/share/system-config-printer/system-config-printer.py']
  SourcePackage: system-config-printer
  Title: system-config-printer.py crashed with AttributeError in nextNPTab(): 
Device instance has no attribute 'hp_scannable'
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev 
sambashare tape video
  dmi.bios.date: 02/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1005HA
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd02/26/2010:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1005HA
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/720295/+subscriptions

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

[Desktop-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 Desktop
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]: [pulseaudio] pid.c: 

[Desktop-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: 

[Desktop-packages] [Bug 1299747] Re: Cannot create PGP key in Ubuntu 14.04

[Thomas A. F. Thorne]

I select 'add a new key or item'  PGP Key and I am presented with a
dialogue box requesting my Full Name and E-mail address.  The first 3
attempts that I made failed but the final attempt seemed to succeed.
For the last attempt I avoided expanding the 'Advanced key options'
area.  I thought that perhaps setting an Expiry Date or Comment was
causing an issue.

I can see now that I have a second key added.  As mentioned above it
seems that the real problem is that it takes a very long time to finish
the key generation process, over 18 minutes so far on some of the keys.
I agree with TORNADO that the interface should give some hint that it is
working still rather than silently failing.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/1299747

Title:
  Cannot create PGP key in Ubuntu 14.04

Status in seahorse package in Ubuntu:
  Confirmed

Bug description:
  When I try to create a PGP key, enter my informations, passphrase and
  click ok, nothing happens. I am using Ubuntu 14.04 beta.

  I don't know if this is related to security.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: seahorse 3.10.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Mar 30 17:49:49 2014
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2014-03-20 (10 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: seahorse
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 713551] Re: Xorg freeze; system locks and accepts no input, keyboard lights go out when key is touched

[Thomas A. F. Thorne]

I switched to a new machine.  Ran a similar set of code and everything
was OK.  I was using the same USB TV Recorder and the same version of
MythBuntu.  My apologies for not replying to this thread earlier.

I beleiver this can be rejected on the basis that it was a hardware
fault with my system.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
https://bugs.launchpad.net/bugs/713551

Title:
  Xorg freeze; system locks and accepts no input, keyboard lights go out
  when key is touched

Status in MythTV:
  New
Status in nvidia-graphics-drivers-173 package in Ubuntu:
  New

Bug description:
  Binary package hint: xorg

  I have a rather old machine running a MythTV backend using a WinTV
  NOVA T USB2 (93000 Rev B8A2) and it seems that randomly the system
  will lock up completely.  I have done my best to work out if the
  freeze occurs when recording or performing some function of the
  mythtv-backend but based on the logs it seems that it can occur during
  a recording, during a database update or when there is no activity at
  all.

  I do have BOINC installed and running but disabling that so it does
  not run at startup didn't seem to stop the problem; as the freeze
  occurs randomly every few days I had to wait about a week but the
  system did lock up without BOINC running at all.  My next fiddle was
  to change the priority of the mythtvbackend process to be -3; this
  seemed to reduce the frequency of the freeze occurring but it may have
  been psychological as the occurance rate is so drawn out anyway.

  One thing which triggered a freeze was using the ubuntu-bug program,
  before the report that I am using to make this bug entry the system
  froze while ubuntu-bug was off collecting information about the
  problem.  Again the mythtvbackend was running so I cannot discount
  this just being coincidence.

  Another symptom, which may just be how the thing works, is that the
  NOVA T USB2 strays in warm mode during the crash and if I use the
  PC's reset button to restart the system.  When the system comes up
  like this the NOVA T is unresponsive and the red light on the from of
  it remains lit.  If I power down the machine or pull the USB cord out
  from the NOVA T then plug it back in after several seconds while the
  bios boot splash screen is going then the red LED extinguishes and the
  device works fine once Ubuntu has booted.

  This is all a little scattered and probably unhelpful but I have tried
  to hunt down answers to this problem myself and have run out of ideas
  what to do next.  Please do let me know if there are any further
  diagnostics that may be helpful.

  lsb_release -rd
  Description:  Ubuntu 10.04.1 LTS
  Release:  10.04

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xorg 1:7.5+5ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
  Uname: Linux 2.6.32-28-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  CheckboxSubmission: 5d0602330b5d44cd5ded7b4846756bb0
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  Date: Sat Feb  5 08:45:59 2011
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-28-generic 
root=UUID=f8cbb2f7-5b7c-46db-94bc-1802d312a175 ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  dmi.bios.date: 08/16/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-6570E
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/16/2004:svn:pn:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6570E:rvr:cvn:ct3:cvr:
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-28-generic
  --- 
  Architecture: i386
  CheckboxSubmission: 5d0602330b5d44cd5ded7b4846756bb0
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  CurrentDmesg:
   [   26.607216] agpgart-nvidia :00:00.0: AGP 3.0 bridge
   [   26.607241] agpgart-nvidia :00:00.0: putting AGP V3 device into 8x 
mode
   [   26.607326] nvidia :01:00.0: putting AGP V3 device into 8x mode
   [   29.232041] eth0: no IPv6 routers present
   [  104.758599] ondemand governor failed, too long transition latency of HW, 
fallback to performance governor
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
  NonfreeKernelModules: nvidia
  Package: nvidia-graphics-drivers-173 (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-28-generic 
root=UUID=f8cbb2f7-5b7c-46db-94bc-1802d312a175 ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
  Tags: lucid lucid
  Uname: Linux