This is/was part of another bug that I was having regarding the same
problem. Problem is that gphoto/gvfs shouldn't be grabbing hold of the
Zen players.
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 Z
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.
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 ch
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 'do
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 much
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 dev
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 mou
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 w
This particular problem seems to be gone since the last update. Have not been
able to replicate it the last two days.
Gnomad works like it should, mostly - plug in the player, open gnomad,
it mounts and lets me add tracks, etc... However, if I try to edit a
track, it completely locks the progra
So, came home and got all set up. Plugged in the Zen, and (of course), worked
as always and as expected, did not auto mount and cause the crash... So, at
this time I suppose the gvfsd-gphoto2 crash problem is solved... However, the
system isn't quite right concerning the Zen. It works with Gnom
if you could dumb down your explanation a bit more what do i need
to enter into the fields to enable valgrind. I
know what mv does, i've heard of wrappers, etc - but couldn't make one
at this point. I have some good Linux experience, but am in no way
fluent quite yet.
S*
> Date: Thu, 2
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 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 time. Again,
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 subscribed
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 in
** 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
** Attachm
Public bug reported:
Binary package hint: gnome-panel
Sometimes at log-in, other times just by closing a program, etc - The
gnome panel freezes up and is unavailable (does not work,
unresponsive...) It is bad enough that I created a shortcut on my
desktop that executes killall gnome-panel, which
Tried to install icon set on Jaunty Alpha 6 through appearance manager - got
this error.
S*
--
gnome-appearance-properties crashed with SIGSEGV in
g_cclosure_marshal_VOID__BOXED()
https://bugs.launchpad.net/bugs/337421
You received this bug notification because you are a member of Ubuntu
Deskto
** Visibility changed to: Public
--
gnome-appearance-properties crashed with SIGSEGV in
pango_layout_iter_get_line_readonly()
https://bugs.launchpad.net/bugs/340823
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
I just got Alpha 5 running and had this error happen twice when attempting to
install an icon set. Appearance preferences is frozen, with tab on lower panel
that does nothing. Menus are unresponsive. If I log out and kill the appearance
settings, I can log back in and things seem ok...
S*
--
g
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/23449342/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/23449343/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/23449344/ProcMaps.txt
** Attachment ad
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/7148121/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/7148122/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/7148123/Disassembly.txt
** Attachm
Public bug reported:
Binary package hint: gnome-media
accidentally had two recordings going at the same time. Stopped the
first recording with the stop button and it closed both windows and sort
of crashed out. Not a big deal and probably my fault. Otherwise
seemed like the program was runnin
22 matches
Mail list logo
