so far no longer a issue

-- 
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/947269

Title:
  nautilus crashed with SIGSEGV in g_file_has_prefix()

Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  while copying files from a external luks hd to internal, unencrypted
  hd via nautilus

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.3.90-0ubuntu6
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
  Uname: Linux 3.2.0-18-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94-0ubuntu1
  Architecture: i386
  Date: Mon Mar  5 17:40:01 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+1118+24'
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  ProcCmdline: nautilus -n
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb6bc05e2 <g_file_has_prefix+146>:    mov    
(%edx),%ecx
   PC (0xb6bc05e2) ok
   source "(%edx)" (0x00474747) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_file_has_prefix () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? ()
   g_hash_table_foreach () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in g_file_has_prefix()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/947269/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to