[Bug 413660] [NEW] nautilus crashed with SIGSEGV in strcmp()

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Binary package hint: nautilus

Nautilus crashes immediately at start-up (using auto-login) and starts many new nautilus instances.
Stacktrace looks different then bug 403549.
This started after today's updates. Until today I have not seen this crash.

$ apt-cache policy nautilus
nautilus:
  Installed: 1:2.27.4-0ubuntu6
  Candidate: 1:2.27.4-0ubuntu6
  Version table:
 *** 1:2.27.4-0ubuntu6 0
        500 http://192.168.1.100 karmic/main Packages
        100 /var/lib/dpkg/status
$ apt-cache policy libbrasero-media0
libbrasero-media0:
  Installed: 2.27.90-0ubuntu1
  Candidate: 2.27.90-0ubuntu1
  Version table:
 *** 2.27.90-0ubuntu1 0
        500 http://192.168.1.100 karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
Date: Fri Aug 14 17:30:23 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.4-0ubuntu6
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x7f94d6cacd42 <strcmp+2>:	cmp    (%rsi),%al
 PC (0x7f94d6cacd42) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 strcmp () from /lib/libc.so.6
 brasero_medium_monitor_get_drive (
 brasero_medium_monitor_init (object=0x2267c00)
 IA__g_type_create_instance (
 g_object_constructor (type=34214272,
Title: nautilus crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.31-5-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sbuild

** Affects: brasero (Ubuntu)
     Importance: Medium
     Assignee: Ubuntu Desktop Bugs (desktop-bugs)
         Status: Confirmed


** Tags: amd64 apport-crash
-- 
nautilus crashed with SIGSEGV in strcmp()
https://bugs.edge.launchpad.net/bugs/413660
You received this bug notification because you are a member of Ubuntu Burning Team, which is subscribed to brasero in ubuntu.