[Bug 210882] Re: sshfs crashed with SIGSEGV in g_slice_alloc()

2010-07-21 Thread Charlie Kravetz
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to New. Thanks again!

** Changed in: sshfs-fuse (Ubuntu)
   Status: Incomplete = Invalid

-- 
sshfs crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/210882
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 210882] Re: sshfs crashed with SIGSEGV in g_slice_alloc()

2010-05-08 Thread Charlie Kravetz
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!

-- 
sshfs crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/210882
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 210882] Re: sshfs crashed with SIGSEGV in g_slice_alloc()

2010-03-16 Thread Charlie Kravetz
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. Could test the current
Ubuntu development version? It would help us greatly if you could test
with it so we can work on getting it fixed in the next release of
Ubuntu. You can find out more about the development release at
http://www.ubuntu.com/testing/ .

Is this reproducable now? Even Ubuntu 8.04 has an upgraded sshfs
package, now at version 1.9-1. Lucid now has 2.2-1.

** Changed in: sshfs-fuse (Ubuntu)
   Status: New = Incomplete

-- 
sshfs crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/210882
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 210882] Re: sshfs crashed with SIGSEGV in g_slice_alloc()

2009-09-16 Thread Kees Cook
** Description changed:

  I looked at other crash reports where it was seems to be similar. I can
  reproduce the error and this is not the same as it was described in
  other similar/related bugs.
  
  Today I tried a Xinerama using a notebook (Intel 945GM) as main monitor
  and a LCD as left-on monitor.  I'm using the (old) i810 driver, because
  it works.  Two separated screens (#0 and #1).
  
  1.  In the second monitor I ran (LCD/VGA):
   $ sshfs cronos: ssh/cronos
  
   That is, mount my home at cronos into the directory ssh/cronos.
  
   In my main monitor (notebook/LVDS) a new Nautilus window was opened, 
   located at ssh/cronos.
  
  2. In the second monitor, same terminal I ran:
  $ cd ssh/cronos
  
  And then it crashs, showing a report window in the main screen.
  I'm confident when I try to access to the 'remote' directory it crashs. 
Because I tried several times.  I even used Nautilus to browse the 'remote' 
directory.  I wait for a while, etc.  But, I try to access from the second 
monitor, it crashed.
  
  It seems it is not possible to work with two monitors, if the sshfs was
  ran from the second one.
  
  
  If I run all the same commands only in the main window, it works fine. I 
mean, If apply the following procedure, it works:
  1.  In the main window:
   $ sshfs cronos: ssh/cronos
  
  In the same main window a new Nautilus window is opened (located at
  ssh/cronos).
  
  2. In the main monitor:
  $ cd ssh/cronos
  $ ls -las
  
  Everything runs smoothly.
  
  3. In the second monitor I ran:
  $ cd ssh/cronos
  $ ls -als
  ...
  
  And everything works fine also.
  
  
  As additional notes:
  - I'm using Hardy and it is up to date.
  
  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  Date: Wed Apr  2 11:49:56 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/sshfs
  Package: sshfs 1.7-2.1
  PackageArchitecture: i386
  ProcCmdline: sshfs cronos: ssh/cronos
  ProcEnviron:
   SHELL=/bin/bash
   
PATH=/home/username/bin:/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/username/code/bzr/postr.dev:/home/username/code/pgsql/settings/bin
   LC_COLLATE=C
   LANG=en_US.UTF-8
  Signal: 11
  SourcePackage: sshfs-fuse
  StacktraceTop:
   g_slice_alloc () from /usr/lib/libglib-2.0.so.0
   ?? () from /usr/lib/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: sshfs crashed with SIGSEGV in g_slice_alloc()
  Uname: Linux 2.6.24-12-generic i686
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev 
video
+ SegvAnalysis:
+  Segfault happened at: 0xb7eb5de0 g_slice_alloc+624:mov
(%ecx),%eax
+  PC (0xb7eb5de0) ok
+  source (%ecx) (0x5f63696c) not located in a known VMA region (needed 
readable region)!
+  destination %eax ok
+ SegvReason: reading unknown VMA

-- 
sshfs crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/210882
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 210882] Re: sshfs crashed with SIGSEGV in g_slice_alloc()

2009-05-04 Thread Andreas Olsson
** Visibility changed to: Public

-- 
sshfs crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/210882
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs