nautilus crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
up to date quantal 120922
problem didn't happen before.
perhaps related, if i leave my pc for 10 min the screen goes black, which is normal but i can't get it back.
alt+f1 doesn't work to switch. I need to do REISUB to reboot. In the above discribed state it won't suspend either.
Pc isn't locked up because i can still mute the sound or deactivate wifi.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.
ProcVersionSign
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 22 13:13:46 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120713.1)
ProcCmdline: nautilus -n
ProcEnviron:
LANGUAGE=nl_BE:nl
PATH=(custom, no user)
LANG=nl_BE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f0fba970e8c <g_type_
PC (0x7f0fba970e8c) ok
source "(%rax)" (0x700000008) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_type_
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: nautilus crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
(nautilus:1700): GLib-GObject-
(nautilus:1700): GLib-GObject-
(nautilus:1700): GLib-GObject-
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 #1053670, 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.