desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #09552
[Bug 840210] Re: nautilus crashed with SIGSEGV after trying to close it
** Description changed:
- This crash is happening repeatedly,and I can think about how to reproduce it,but the last time it happened I was copying some files from my Ext. HDD to my home folder and some of them to their appropriate places(Downloads,Videos,Music)
+ This crash is happening repeatedly,and I can't think about how to reproduce it,but the last time it happened I was copying some files from my Ext. HDD to my home folder and some of them to their appropriate places(Downloads,Videos,Music)
I also did safely remove the Ext. HDD before closing nautilus
I had 2 nautilus window,closed one,no crash,closed second,and it told me that its not working correctly and I should force close it...
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Sat Sep 3 14:04:18 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: nautilus -n
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: 0x810f1cd: mov 0x308(%eax),%eax
- PC (0x0810f1cd) ok
- source "0x308(%eax)" (0xaaaaadb2) not located in a known VMA region (needed readable region)!
- destination "%eax" ok
+ Segfault happened at: 0x810f1cd: mov 0x308(%eax),%eax
+ PC (0x0810f1cd) ok
+ source "0x308(%eax)" (0xaaaaadb2) not located in a known VMA region (needed readable region)!
+ destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
- #0 0x0810f1cd in ?? ()
- No symbol table info available.
- Cannot access memory at address 0xbfac9e9c
+ #0 0x0810f1cd in ?? ()
+ No symbol table info available.
+ Cannot access memory at address 0xbfac9e9c
StacktraceTop: ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
** Visibility changed to: Public
--
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/840210
Title:
nautilus crashed with SIGSEGV after trying to close it
Status in “nautilus” package in Ubuntu:
New
Bug description:
This crash is happening repeatedly,and I can't think about how to reproduce it,but the last time it happened I was copying some files from my Ext. HDD to my home folder and some of them to their appropriate places(Downloads,Videos,Music)
I also did safely remove the Ext. HDD before closing nautilus
I had 2 nautilus window,closed one,no crash,closed second,and it told me that its not working correctly and I should force close it...
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Sat Sep 3 14:04:18 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: nautilus -n
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x810f1cd: mov 0x308(%eax),%eax
PC (0x0810f1cd) ok
source "0x308(%eax)" (0xaaaaadb2) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
#0 0x0810f1cd in ?? ()
No symbol table info available.
Cannot access memory at address 0xbfac9e9c
StacktraceTop: ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/840210/+subscriptions