[Bug 796465] Re: gnome-settings-daemon crashed with SIGSEGV

2011-06-21 Thread Eliah Kagan
*** This bug is a duplicate of bug 800065 ***
https://bugs.launchpad.net/bugs/800065

** This bug is no longer a duplicate of bug 798722
   gnome-settings-daemon crashed with SIGSEGV
** This bug has been marked a duplicate of bug 800065
   gnome-settings-daemon crashed with SIGSEGV

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796465

Title:
  gnome-settings-daemon crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 796465] Re: gnome-settings-daemon crashed with SIGSEGV

2011-06-17 Thread Eliah Kagan
*** This bug is a duplicate of bug 798722 ***
https://bugs.launchpad.net/bugs/798722

** This bug has been marked a duplicate of bug 798722
   gnome-settings-daemon crashed with SIGSEGV

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796465

Title:
  gnome-settings-daemon crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 796465]

2011-06-16 Thread Apport retracing service
Stacktrace:
 #0  0x04bfda70 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfdade4c
StacktraceTop: ?? ()

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796465

Title:
  gnome-settings-daemon crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 796465] ThreadStacktrace.txt

2011-06-16 Thread Apport retracing service
** Attachment added: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/796465/+attachment/2171239/+files/ThreadStacktrace.txt

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796465

Title:
  gnome-settings-daemon crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 796465] Crash report cannot be processed

2011-06-16 Thread Apport retracing service
Thank you for your report!

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

libgcc1: installed version 1:4.6.0-11ubuntu2, latest version: 1:4.6.0-13ubuntu1
libgcc1-dbg: installed version 1:4.6.0-11ubuntu2, latest version: 
1:4.6.0-13ubuntu1
libxxf86vm1-dbg: installed version 1:1.1.1-1ubuntu1, latest version: 1:1.1.1-2
libcups2: installed version 1.4.6-8, latest version: 1.4.6-9
gcc-4.6-base: installed version 4.6.0-11ubuntu2, latest version: 4.6.0-13ubuntu1
libxft2-dbg: installed version 2.2.0-2ubuntu2, latest version: 2.2.0-3ubuntu1
libgtk-3-0: installed version 3.0.11-0ubuntu1, latest version: 3.1.6-0ubuntu2
libxt6-dbg: installed version 1:1.1.1-1ubuntu1, latest version: 1:1.1.1-2
libxft2: installed version 2.2.0-2ubuntu2, latest version: 2.2.0-3ubuntu1
libpango1.0-0: installed version 1.28.4-0ubuntu1, latest version: 
1.28.4-0ubuntu2
libxfixes3: installed version 1:5.0-2ubuntu1, latest version: 1:5.0-4
libgtk-3-common: installed version 3.0.11-0ubuntu1, latest version: 
3.1.6-0ubuntu2
libglib2.0-0: installed version 2.29.6-0ubuntu3, latest version: 2.29.8-0ubuntu1
cpp-4.6: installed version 4.6.0-11ubuntu2, latest version: 4.6.0-13ubuntu1
libgdk-pixbuf2.0-0: installed version 2.23.3-0ubuntu3, latest version: 
2.23.4-0ubuntu1
libxfixes3-dbg: installed version 1:5.0-2ubuntu1, latest version: 1:5.0-4
libatk1.0-data: installed version 2.0.0-1ubuntu1, latest version: 2.0.1-0ubuntu1
libxxf86vm1: installed version 1:1.1.1-1ubuntu1, latest version: 1:1.1.1-2
libegl1-mesa-dbg: installed version 7.10.2-0ubuntu2, latest version: 
7.10.3-0ubuntu1
libgl1-mesa-glx-dbg: installed version 7.10.2-0ubuntu2, latest version: 
7.10.3-0ubuntu1
libstdc++6: installed version 4.6.0-11ubuntu2, latest version: 4.6.0-13ubuntu1
libxi6-dbg: installed version 2:1.4.1-1ubuntu3, latest version: 2:1.4.3-3ubuntu1
libxt6: installed version 1:1.1.1-1ubuntu1, latest version: 1:1.1.1-2
libpango1.0-0-dbg: installed version 1.28.4-0ubuntu1, latest version: 
1.28.4-0ubuntu2
libgtk-3-0-dbg: installed version 3.0.11-0ubuntu1, latest version: 
3.1.6-0ubuntu2
libxi6: installed version 2:1.4.1-1ubuntu3, latest version: 2:1.4.3-3ubuntu1
x11-common: installed version 1:7.6+4ubuntu3, latest version: 1:7.6+7ubuntu1
libatk1.0-0: installed version 2.0.0-1ubuntu1, latest version: 2.0.1-0ubuntu1
libglib2.0-0-dbg: installed version 2.29.6-0ubuntu3, latest version: 
2.29.8-0ubuntu1


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!


** Attachment removed: CoreDump.gz
   https://bugs.launchpad.net/bugs/796465/+attachment/2167080/+files/CoreDump.gz

** Tags removed: need-i386-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796465

Title:
  gnome-settings-daemon crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 796465] Re: gnome-settings-daemon crashed with SIGSEGV

2011-06-15 Thread Eliah Kagan
** Description changed:

  Binary package hint: gnome-settings-daemon
  
  This crash in gnome-settings-daemon 3.0.2-1ubuntu3 occurred twice
  (nearly identical, not very informative stack traces) in succession
  after logging in to a unity-2d session on a recently updated Oneiric
- i386 system. I think this crash may have occurred before the updates (if
- so, I don't think I reported it then). My other Oneiric i386 system,
- installed on identical (virtual) hardware and also fully updated, does
- not appear to be affected by this bug.
+ i386 system. I think this crash may have occurred before the updates as
+ well (if so, I don't think I reported it then). My other Oneiric i386
+ system, installed on identical (virtual) hardware and also fully
+ updated, does not appear to be affected by this bug.
  
  This might be bug 788710. I was able to produce that bug on this same
  system, by running gnome-settings-daemon in a Terminal after the two
  instances of this crash. But I suspect they are not really the same bug,
  because they both occurred in the same session without any package
  management operations performed in between them, yet the stack trace in
  this bug is much worse. Furthermore, right now it looks like the crash
  in bug 788710 occurs whenever a second concurrent instance of gnome-
  settings-daemon is launched (see
  https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
  daemon/+bug/788710/comments/15, and also bug 796497, which is a
  duplicate of bug 788710).
  
  This bug looks cursorily similar to bug 779878, since they are both
  SIGSEGV crashes in gnome-settings-daemon with no function name (and thus
  have the same apport-generated title). Since bug 779878's stack trace
  has no symbol names or addresses and this stack trace has only the
  address where the segfault occurred and no other information, they
  cannot really be compared. Since there are no positive similarities
  besides occurring spontaneously (other than that, all the similarities
  between the two bugs are in the information that is *not* available
  about them), and bug 779878 occurred in Maverick while this bug occurred
  in Oneiric, I doubt they are the same bug.
  
  Due to stack corruption, the stack trace here is very bad--hopefully
  Apport retracing service will be able to process it and the core dump,
  and yield better information.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-settings-daemon 3.0.2-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
  Uname: Linux 2.6.39-3-generic i686
  Architecture: i386
  Date: Mon Jun 13 02:00:54 2011
  Disassembly: = 0x4bfda70:Cannot access memory at address 0x4bfda70
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110610)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4bfda70: Cannot access memory at address 
0x4bfda70
   PC (0x04bfda70) not located in a known VMA region (needed executable region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  Stacktrace:
   #0  0x04bfda70 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0xbfdade4c
  StacktraceTop: ?? ()
  Title: gnome-settings-daemon crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796465

Title:
  gnome-settings-daemon crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 796465] Re: gnome-settings-daemon crashed with SIGSEGV

2011-06-13 Thread Eliah Kagan
** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796465

Title:
  gnome-settings-daemon crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 796465] Re: gnome-settings-daemon crashed with SIGSEGV

2011-06-13 Thread Eliah Kagan
** Description changed:

  Binary package hint: gnome-settings-daemon
  
  This crash in gnome-settings-daemon 3.0.2-1ubuntu3 occurred twice
  (nearly identical, not very informative stack traces) in succession
  after logging in to a recently updated unity-2d session on an Oneiric
  i386 system. I think this crash may have occurred before the updates (if
  so, I don't think I reported it then). My other Oneiric i386 system,
  installed on identical (virtual) hardware and also fully updated, does
  not appear to be affected by this bug.
  
  This might be bug 788710. I was able to produce that bug on this same
  system, by running gnome-settings-daemon in a Terminal after the two
  instances of this crash. (I'll post in that bug with more details about
  the possible connection.) But I suspect they are not really the same
  bug, because they both occurred in the same session without any package
  management operations performed in between them, yet the stack trace in
  this bug is much worse.
  
- This also looks a bit like bug 779878. I haven't yet compared the stack
- traces.
+ This bug looks cursorily similar to bug 779878, since they are both
+ SIGSEGV crashes in gnome-settings-daemon with no function name (and thus
+ have the same apport-generated title). Since bug 779878's stack trace
+ has no symbol names or addresses and this stack trace has only the
+ address where the segfault occurred and no other information, they
+ cannot really be compared. Since there are no positive similarities
+ besides occurring spontaneously (other than that, all the similarities
+ between the two bugs are in the information that is *not* available
+ about them), and bug 779878 occurred in Maverick while this bug occurred
+ in Oneiric, I doubt they are the same bug.
+ 
+ Due to stack corruption, the stack trace here is very bad--hopefully
+ Apport retracing service will be able to process it and the core dump,
+ and yield better information.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-settings-daemon 3.0.2-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
  Uname: Linux 2.6.39-3-generic i686
  Architecture: i386
  Date: Mon Jun 13 02:00:54 2011
  Disassembly: = 0x4bfda70:Cannot access memory at address 0x4bfda70
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110610)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcEnviron:
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x4bfda70: Cannot access memory at address 
0x4bfda70
-  PC (0x04bfda70) not located in a known VMA region (needed executable region)!
+  Segfault happened at: 0x4bfda70: Cannot access memory at address 
0x4bfda70
+  PC (0x04bfda70) not located in a known VMA region (needed executable region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  Stacktrace:
-  #0  0x04bfda70 in ?? ()
-  No symbol table info available.
-  Cannot access memory at address 0xbfdade4c
+  #0  0x04bfda70 in ?? ()
+  No symbol table info available.
+  Cannot access memory at address 0xbfdade4c
  StacktraceTop: ?? ()
  Title: gnome-settings-daemon crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796465

Title:
  gnome-settings-daemon crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 796465] Re: gnome-settings-daemon crashed with SIGSEGV

2011-06-13 Thread Eliah Kagan
** Description changed:

  Binary package hint: gnome-settings-daemon
  
  This crash in gnome-settings-daemon 3.0.2-1ubuntu3 occurred twice
  (nearly identical, not very informative stack traces) in succession
  after logging in to a recently updated unity-2d session on an Oneiric
  i386 system. I think this crash may have occurred before the updates (if
  so, I don't think I reported it then). My other Oneiric i386 system,
  installed on identical (virtual) hardware and also fully updated, does
  not appear to be affected by this bug.
  
  This might be bug 788710. I was able to produce that bug on this same
  system, by running gnome-settings-daemon in a Terminal after the two
- instances of this crash. (I'll post in that bug with more details about
- the possible connection.) But I suspect they are not really the same
- bug, because they both occurred in the same session without any package
+ instances of this crash. But I suspect they are not really the same bug,
+ because they both occurred in the same session without any package
  management operations performed in between them, yet the stack trace in
- this bug is much worse.
+ this bug is much worse. Furthermore, right now it looks like the crash
+ in bug 788710 occurs whenever a second concurrent instance of gnome-
+ settings-daemon is launched (see
+ https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
+ daemon/+bug/788710/comments/15, and also bug 796497, which is a
+ duplicate of bug 788710).
  
  This bug looks cursorily similar to bug 779878, since they are both
  SIGSEGV crashes in gnome-settings-daemon with no function name (and thus
  have the same apport-generated title). Since bug 779878's stack trace
  has no symbol names or addresses and this stack trace has only the
  address where the segfault occurred and no other information, they
  cannot really be compared. Since there are no positive similarities
  besides occurring spontaneously (other than that, all the similarities
  between the two bugs are in the information that is *not* available
  about them), and bug 779878 occurred in Maverick while this bug occurred
  in Oneiric, I doubt they are the same bug.
  
  Due to stack corruption, the stack trace here is very bad--hopefully
  Apport retracing service will be able to process it and the core dump,
  and yield better information.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-settings-daemon 3.0.2-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
  Uname: Linux 2.6.39-3-generic i686
  Architecture: i386
  Date: Mon Jun 13 02:00:54 2011
  Disassembly: = 0x4bfda70:Cannot access memory at address 0x4bfda70
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110610)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4bfda70: Cannot access memory at address 
0x4bfda70
   PC (0x04bfda70) not located in a known VMA region (needed executable region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  Stacktrace:
   #0  0x04bfda70 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0xbfdade4c
  StacktraceTop: ?? ()
  Title: gnome-settings-daemon crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796465

Title:
  gnome-settings-daemon crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 796465] Re: gnome-settings-daemon crashed with SIGSEGV

2011-06-13 Thread Eliah Kagan
** Description changed:

  Binary package hint: gnome-settings-daemon
  
  This crash in gnome-settings-daemon 3.0.2-1ubuntu3 occurred twice
  (nearly identical, not very informative stack traces) in succession
- after logging in to a recently updated unity-2d session on an Oneiric
+ after logging in to a unity-2d session on a recently updated Oneiric
  i386 system. I think this crash may have occurred before the updates (if
  so, I don't think I reported it then). My other Oneiric i386 system,
  installed on identical (virtual) hardware and also fully updated, does
  not appear to be affected by this bug.
  
  This might be bug 788710. I was able to produce that bug on this same
  system, by running gnome-settings-daemon in a Terminal after the two
  instances of this crash. But I suspect they are not really the same bug,
  because they both occurred in the same session without any package
  management operations performed in between them, yet the stack trace in
  this bug is much worse. Furthermore, right now it looks like the crash
  in bug 788710 occurs whenever a second concurrent instance of gnome-
  settings-daemon is launched (see
  https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
  daemon/+bug/788710/comments/15, and also bug 796497, which is a
  duplicate of bug 788710).
  
  This bug looks cursorily similar to bug 779878, since they are both
  SIGSEGV crashes in gnome-settings-daemon with no function name (and thus
  have the same apport-generated title). Since bug 779878's stack trace
  has no symbol names or addresses and this stack trace has only the
  address where the segfault occurred and no other information, they
  cannot really be compared. Since there are no positive similarities
  besides occurring spontaneously (other than that, all the similarities
  between the two bugs are in the information that is *not* available
  about them), and bug 779878 occurred in Maverick while this bug occurred
  in Oneiric, I doubt they are the same bug.
  
  Due to stack corruption, the stack trace here is very bad--hopefully
  Apport retracing service will be able to process it and the core dump,
  and yield better information.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-settings-daemon 3.0.2-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
  Uname: Linux 2.6.39-3-generic i686
  Architecture: i386
  Date: Mon Jun 13 02:00:54 2011
  Disassembly: = 0x4bfda70:Cannot access memory at address 0x4bfda70
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110610)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4bfda70: Cannot access memory at address 
0x4bfda70
   PC (0x04bfda70) not located in a known VMA region (needed executable region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  Stacktrace:
   #0  0x04bfda70 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0xbfdade4c
  StacktraceTop: ?? ()
  Title: gnome-settings-daemon crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796465

Title:
  gnome-settings-daemon crashed with SIGSEGV

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs