[Bug 475314] Re: devkit-disks-daemon crashed with SIGSEGV in memalign()

2010-03-01 Thread motomast3r
** Changed in: devicekit-disks (Ubuntu) Status: Invalid = New -- devkit-disks-daemon crashed with SIGSEGV in memalign() https://bugs.launchpad.net/bugs/475314 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 475314] Re: devkit-disks-daemon crashed with SIGSEGV in memalign()

2010-03-01 Thread Chris Coulson
Please don't reopen it unless you can provide the requested information ** Changed in: devicekit-disks (Ubuntu) Status: New = Invalid -- devkit-disks-daemon crashed with SIGSEGV in memalign() https://bugs.launchpad.net/bugs/475314 You received this bug notification because you are a

[Bug 475314] Re: devkit-disks-daemon crashed with SIGSEGV in memalign()

2010-02-15 Thread Martin Pitt
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on

[Bug 475314] Re: devkit-disks-daemon crashed with SIGSEGV in memalign()

2009-12-23 Thread Martin Pitt
Anyone with a recipe how to reproduce this? -- devkit-disks-daemon crashed with SIGSEGV in memalign() https://bugs.launchpad.net/bugs/475314 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 475314] Re: devkit-disks-daemon crashed with SIGSEGV in memalign()

2009-12-23 Thread ealthuis
Unfrortunately I am not able to provide detailed info, but this is what happened: I started simple backup config, a Backup properties screen displayed, Under General the Manual Backups only radio button was on Entered Backup Now! Result: A backup run is initiated in the background. The

[Bug 475314] Re: devkit-disks-daemon crashed with SIGSEGV in memalign()

2009-11-10 Thread Martin Pitt
I'm afraid I can't make any sense of the stack trace. Can you reproduce this crash? What are the steps to do this? (Please note that the crash reporter is disabled now in the final Ubuntu 9.10 release; you can explicitly enable it again in /etc/default/apport). ** Changed in: devicekit-disks