** Changed in: gvfs
Status: Invalid = Expired
** Changed in: gvfs
Importance: Unknown = Critical
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
closing the bug since the crash doesn't happen now, there is an another
bug about mtp device being locked by gvfs see bug #348287
** Changed in: gvfs (Ubuntu)
Status: Triaged = Invalid
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received
So - as of 4-13 updates, the problem seems to have gone away. I could
not get the gvfs error to come up again.
I completely reinstalled the system with the release candidate, then got
all updates and gnomad. Tried it again and still no error as far as gvfs
is concerned.
However, the system was
Looking at the 'mounted' Zen. It shows it's properties as a gphoto2
filesystem. Once again, the issue seems to be that gphoto2 is mounting
the Zen, which it should not be doing. It's not a camera or camera
device. It can handle pictures, but only for viewing, and is easily
loaded through Gnomad2.
I tried about a week ago same setup, on Debian 5.0. Everything worked
as normal. Hardy worked just fine. I currently compiled latest libmtp,
gnomad2 and Jaunty still mounts/docks incorrectly.
AT this point I feel that it has alot more to do with how it is being
handled by the USBbus, not so
how did you get the log? could you install the debug packages for gtk
glib gvfs?
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
how did you get the log? could you install the debug packages for gtk
glib gvfs? you might want to rename gvfsd-gphoto2 to gvfsd-
gphoto2.binary and have a gvfsd-gphoto2 wrapper calling the binary
under valgrind
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
I already explained the valgrind trick before, you might want to make
sure that there is no running backend or that you don't restart one
which would overwrite the log then or add some logic to name logs
differently
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
I'm not sure what it is , but seems like when whenever you ask for more
logging, etc the problem has vanished.
Got home tonite and got all set up, plugged in and (of course), everything is
as it's been in previous releases for the most part. No error came up _BUT -
more importantly- the
Here is valgrind log. This is happens when Zen is plugged in for the
first time. If I leave machine running it doesn't seem to happen until
next startup. However, the issue with the Zen 'double mounting' happens
all the time. Something is definitely not right in how the system is
identifying or
there is no error in this log
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Regardless, the error listed in the beginning comes up without fail.
I've heard complaints of this maybe being a problem with a missing udev
rule, or possibly a binary package. I am willing to try to help track it
another way. My question is maybe why is gphoto trying to run if it's
not a photo
reopening the bug, new bug is bug 357954
** Changed in: gvfs (Ubuntu)
Status: Invalid = Triaged
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
On latest comment from the upstream developer it says that this maybe is
a memory corruption, may you please try to obtain a valgrind log
following the instructions at https://wiki.ubuntu.com/Valgrind and
attach the file to the bug report. This will greatly help us in tracking
down your problem.
Back again - happened today the same thing. When Zen is attached it 'mounts'
for a second or two to id, then should not stay mounted. It does release, but
then immediately mounts a second time and causes the error. At that point I
have to go into 'Places', etc and unmount from the side of the
** Changed in: gvfs
Status: New = Invalid
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
closing the gvfs bug since the crash seems fixed now
** Changed in: gvfs (Ubuntu)
Status: Triaged = Invalid
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
does it work correctly now?
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
*
Date: Fri, 3 Apr 2009 10:55:10 +
From: seb...@ubuntu.com
To: granny6...@hotmail.com
Subject: [Bug 349555] Re: gvfsd-gphoto2 crashed with SIGSEGV in strlen()
does it work correctly now?
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You
the correct binary name is /usr/lib/gvfs/gvfsd-photo2, an another way is
to mv the binary and have a wrapper using the normal name copy valgrind
binarycopy
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received this bug notification because you are
*
Date: Thu, 2 Apr 2009 07:39:34 +
From: seb...@ubuntu.com
To: granny6...@hotmail.com
Subject: [Bug 349555] Re: gvfsd-gphoto2 crashed with SIGSEGV in strlen()
the correct binary name is /usr/lib/gvfs/gvfsd-photo2, an another way is
to mv the binary and have a wrapper using the normal
cd /usr/lib/gvfs
sudo mv gvfsd-photo2 gvfsd-photo2.binary
sudo gedit gvfsd-photo2
write
#!/bin/sh
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind
--log-file=/tmp/valgrind.log gvfsd-photo2.binary $@
sudo chmod 775 gvfsd-photo2
restart your session
get the crash
add /tmp/valgrind.log there
] Re: gvfsd-gphoto2 crashed with SIGSEGV in strlen()
cd /usr/lib/gvfs
sudo mv gvfsd-photo2 gvfsd-photo2.binary
sudo gedit gvfsd-photo2
write
#!/bin/sh
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind
--log-file=/tmp/valgrind.log gvfsd-photo2.binary $@
sudo chmod 775 gvfsd-photo2
Sebastian - got valgrind installed, but couldn't figure out how to
attach it to whichever program to make it log... The wiki page is pretty
vague. I replaced program with gvfsd-ghoto2 and it says 'command not
found'. Not sure what I need to do here to fire up valgrind.
This does happen every
StacktraceTop:strlen () at ../sysdeps/i386/i486/strlen.S:69
split_filename_with_ignore_prefix (
do_enumerate (backend=0x8ab6800, job=0x8b45330,
run (job=0x8b45330) at gvfsjobenumerate.c:260
g_vfs_job_run (job=0x8b45330) at gvfsjob.c:198
** Attachment removed: CoreDump.gz
Thanks for your bug report. This bug has been reported to the developers
of the software. You can track it and make comments here:
http://bugzilla.gnome.org/show_bug.cgi?id=577417
** Changed in: gvfs (Ubuntu)
Importance: Undecided = Low
** Changed in: gvfs (Ubuntu)
Status: New =
Do you get the issue every time? Do you think you could try to obtain a
valgrind log following the instructions at
https://wiki.ubuntu.com/Valgrind and attach the file to the bug report
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received this
** Changed in: gvfs
Status: Unknown = New
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Same error today, now on Ubuntu Studio Beta. Same action, plugged in a Zen
Vision and the system mounted it as if a camera. This blocks out the
functionality of Rhythmbox, Gnomad, etc, until I tell it to eject, at which
point the crash popped up. After telling it to eject, but leaving plugged
Again tonite, same error doing the same thing. - Seems the Zen is interpreted
as a camera somehow...
S*
--
gvfsd-gphoto2 crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/349555
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/24403816/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24403817/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/24403818/Disassembly.txt
** Attachment
31 matches
Mail list logo
