The bug didn't get activity/new duplicates for some years and the
nautilus code saw quite some changes since which probably deprecated the
issue so closing it. If it's still a problem in recent Ubuntu/nautilus
version please submit a new report

** Changed in: nautilus (Ubuntu)
       Status: Confirmed => Invalid

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.

  nautilus crashed with SIGSEGV in gdk_x11_window_set_user_time()

Status in nautilus package in Ubuntu:

Bug description:
  Tried to open nautilus and got this exception.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu11
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: amd64
  Date: Thu Mar 21 21:44:45 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
  InstallationDate: Installed on 2012-10-19 (153 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: nautilus -n
   Segfault happened at: 0x7fd5cf15f46f <gdk_x11_window_set_user_time+31>:      
testb  $0x60,0x7c(%rdi)
   PC (0x7fd5cf15f46f) ok
   source "$0x60" ok
   destination "0x7c(%rdi)" (0x0000007c) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: nautilus
   gdk_x11_window_set_user_time () from /usr/lib/x86_64-linux-gnu/
   ?? ()
   g_cclosure_marshal_VOID(unsigned int0_t, void) () from 
   ?? () from /usr/lib/x86_64-linux-gnu/
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/
  Title: nautilus crashed with SIGSEGV in gdk_x11_window_set_user_time()
  UpgradeStatus: Upgraded to raring on 2013-03-07 (14 days ago)
  UserGroups: adm lpadmin sambashare sudo

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to