Fix is out in upstream version 12.6.4
--
VMWare fusion host + vmmouse driver generates drag events on any click
https://bugs.launchpad.net/bugs/366521
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
Public bug reported:
The vmmouse driver currently included in Intrepid is broken when used in
conjunction with Server 1.5. This has been noted in bug 248521.
I have made an upstream update release of the driver that fixes this
problem:
http://xorg.freedesktop.org/releases/individual/driver/xf86-
** Attachment added: "fdi descriptor for vmmouse"
http://launchpadlibrarian.net/18655083/11-x11-vmmouse.fdi
--
vmmouse doesn't work with input hotplug
https://bugs.launchpad.net/bugs/285305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Attachment added: "Callout script to invoke vmmouse-detect"
http://launchpadlibrarian.net/18655088/hal-probe-vmmouse
--
vmmouse doesn't work with input hotplug
https://bugs.launchpad.net/bugs/285305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I'd like to nominate adding input hotplug support as an SRU. Intrepid
isn't officially out yet, but it will be before any update can take
place. If we agree that the broken driver should be fixed, the driver
will still be very difficult to actually use in the absence of fixing
this bug. Users would
I have pushed a new upstream release that fixes the broken mouseclicks:
http://xorg.freedesktop.org/releases/individual/driver/xf86-input-
vmmouse-12.5.2.tar.bz2
and I have filed bug 285305 to track adding proper input hotplug
detection.
--
vmmouse seems to register incorrect x,y values for mou
I'd like to nominate updating the driver as an SRU. Intrepid isn't
officially out yet, but it will be before any update can take place. As
the current driver is completely broken and unusable, there is no way to
regress the situation and having a broken driver sitting around is
highly undesirable.
Package from -proposed works correctly in a VMware VM.
--
vmmouse doesn't work with input hotplug
https://bugs.launchpad.net/bugs/285305
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.ubunt
That other build is incorrect in the way it attempts to address the
problem.
What is your output of 'xinput list' with the original and new 12.5.1?
--
vmmouse seems to register incorrect x,y values for mouseclick
https://bugs.launchpad.net/bugs/248521
You received this bug notification because y
Bryce. Your patch unfortunately left out the configure.ac change.
Without it, it won't set the #ifdef correctly. So, the net result is
that nothing has changed. That's why Christopher didn't observe any
change.
Christopher - if you build 12.5.2 from source, it should work.
--
vmmouse seems to re
Diff attached.
** Attachment added: "configure.ac diff"
http://launchpadlibrarian.net/18753759/configure.diff
--
vmmouse seems to register incorrect x,y values for mouseclick
https://bugs.launchpad.net/bugs/248521
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Those of you with problems with the new (working) driver should remove
all input device references from xorg.conf. vmmouse now works with input
hotplug.
--
vmmouse seems to register incorrect x,y values for mouseclick
https://bugs.launchpad.net/bugs/248521
You received this bug notification becau
Bryce, diff looks good to me.
I'm attaching an improved version of the fdi file - it tries to detect
the VMware virtual machine so the probe binary isn't actually called on
real hardware. The probe is still required because a VM could have the
mouse device disabled.
This is just an optimization -
Martin,
Good point. As I said, I have no problems shipping the original fdi file
- it will work just fine.
--
vmmouse doesn't work with input hotplug
https://bugs.launchpad.net/bugs/285305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bryce has incorporated a more robust fix for 248521 into his diff for
this bug.
--
vmmouse doesn't work with input hotplug
https://bugs.launchpad.net/bugs/285305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Change looks fine and Martin's file locations are the the ones to use.
As Martin says, we'd better make sure the updated vmmouse binary works
correctly or the hotplug support will actually make things worse
(throwing a completely broken driver at the user instead of a sub-
optimal but basically fu
If that doesn't work, nothing will :-)
--
vmmouse doesn't work with input hotplug
https://bugs.launchpad.net/bugs/285305
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://li
Public bug reported:
Binary package hint: xorg
The vmmouse driver is now available in Xorg 7.1 and should, at the very
least, be available as an Ubuntu package.
Ideally, the installer would detect the hardware and use the driver when
installing in a VM, just as it already does for the video driv
Gary has identified the fundamental cause. If libdbus-1-2 is removed,
things will mostly work (the player will not use HAL for device
enumeration, but it won't crash either). By the time Edgy is finished,
libdbus-1-2 will be gone (right now it's just there for openoffice which
apparently hasn't bee
It's the default location to look for VMs. It's behaviour that's
inherited from Workstation - it admittedly makes less sense here because
the player can't create VMs.
--
VMware Player creates empty ~/vmware directory
https://launchpad.net/bugs/63785
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
Public bug reported:
First, see bug 69780 about making sure the vmmouse driver is in main (or
it won't be available to use at install time).
To provide the best user experience for someone installing Ubuntu into a
VM, the vmware mouse driver should be autoselected just as the video
driver is. Now
Public bug reported:
Libview is an open-source set of widgets produced by VMware and used by
VMware products. To successfully produce a VMware workstation or player
deb with the correct dependencies, all dependencies must be available,
and as there is no libview package, that's not going to work o
This was already fixed in feisty.
** Changed in: usplash (Ubuntu)
Status: New => Fix Released
--
Usplash in edgy doesn't play well with vmware
https://bugs.launchpad.net/bugs/72772
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
I have put together a simple program that will test for the presence of
the vmmouse device and return 0 if it is present or 1 otherwise.
http://intr.overt.org/misc/vmmouse-detect-1.0.0.tar.bz2
I don't know what the best way to integrate this into the installer and
live-cd startup flows is. It mig
Public bug reported:
Binary package hint: xserver-xorg-input-vmmouse
If the vmware video driver is worthy of being in main (and I totally
agree it is), then the mouse driver should be too. Both are essential
for a smooth user experience.
** Affects: xserver-xorg-input-vmmouse (Ubuntu)
Impor
Edgy has a bug where the locales that are installed are not accessible
to 32bit applications (like vmplayer in this case).
You might be able to work around it by symlinking /usr/lib64/locale to
/usr/lib32/locale
--
fonts in vmplayer are not readable under amd64
https://launchpad.net/bugs/93858
Public bug reported:
In Edgy, locale files generated by locale-gen go into /usr/lib/locale.
Without these files, an application cannot use any locales. 32bit
applications look in /usr/lib32/locale for locale files and consequently
can never find any and always fallback to the built in C locale.
S
You must mount /proc/bus/usb which is no longer done by default in Edgy
- the player uses it for usb device detection and enumeration.
--
[edgy] vmware-player cannot see usb devices
https://launchpad.net/bugs/62707
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
Not for me to say. The situation of /proc/bus/usb vs (/dev/usb/usb +
sysfs + hal) is unclear - the last word from the kernel driver
maintainer was that /proc/bus/usb was not deprecated but everyone else
seems to think it is. Go figure.
--
[edgy] vmware-player cannot see usb devices
https://launch
It's likely but he doesn't say if he used a separate build output
directory or not.
--
DKMS cannot build nvidia-graphics-drivers against a custom kernel using a
separate build ouput directory
https://bugs.launchpad.net/bugs/570323
You received this bug notification because you are a member of Ub
Public bug reported:
When building against a custom kernel using a separate build output
directory, the source directory (/lib/modules//source) should
be passed to the nvidia makefile as SYSSRC and the build output
directory (/lib/modules//build) as SYSOUT.
Currently dkms passes the build output
Changing the make invocation in dkms.conf to:
"make module KERNDIR=/lib/modules/$kernelver IGNORE_XEN_PRESENCE=1
IGNORE_CC_MISMATCH=1 SYSSRC="/lib/modules/$kernelver/source"
SYSOUT=$kernel_source_dir"
fixes the problem.
DKMS sets $kernel_source_dir to the build dir and has no specific
variable f
I can't test the latest packages fully because I'm running eoan but I
did install the packages from focal and it didn't work, while I'm home-
built binaries from mid october do work, so maybe some regressed? The
usbmuxd upgrade is fine, but libimobiledevice/libusbmuxd is what breaks
it. I can't dis
I'll try out the focal builds when I get a chance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854403
Title:
Need updated libimobiledevice and dependencies to access iOS 13
devices
To manage n
At the time I filed the bug, I did not notice an updated build in focal
- it was still the same one as in eoan, but perhaps I was just not
paying enough attention. I will try it out. That version is likely to be
new enough to work, although I know there was an update to libusbmuxd
with a version an
It already uses gtk3. It builds in this complicated way where it can use
either gtk3 or gtk2 at runtime, but presumably you can just stop
building the gtk2 support in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
This has been fixed and released upstream (1.32.2, 1.34.2.1, 1.36.0)
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=787992
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This was actually a gvfs issue, and it was fixed many years ago. The
root of the device is now correctly marked as read-only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368868
Title:
libmtp erro
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
** This bug is no longer a duplicate of bug 1693390
gvfsd-mtp crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
--
You received this bug notif
Public bug reported:
iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd
to work correctly. Without the updates, the device appears to be
accessible but it's impossible to copy files to the devices.
** Affects: libimobiledevice (Ubuntu)
Importance: Undecided
Stat
Upstream fix for the openssl issue is in: f56a65f in libimobiledevice.
Taking advantage of that requires switching the ubuntu build from using
gnutls to openssl.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
So, the new builds are new enough versions but libimobiledevice is still
built against gnutls and so file transfers don't work. If I build my own
library at the 1.3.0 version against openssl and drop it in, then it all
works fine.
The new builds of libplist and libusbmuxd are very helpful as they
Ah, sorry. Yes, if you rebuild the focal package with f56a65f and use
openssl, then connectivity and file transfers work correctly. There does
not appear to be any other changes required. I can't vouch for all the
functionality, of course. The device backup functionality seems popular,
but I don't
Ok, so this is progress. Building against gnutls fixes the trust
pairing, but breaks file transfers. I rebuild the same source with
openssl vs gnutls and that's exactly what I see. With openssl I have to
re-pair every time I plug in but with gnutls, the file transfers don't
work.
The official ubun
I've upgraded to 20.04 and have checked out the installed versions. For
now, I was able to get it working "just" by upgrading libimobiledevice
to the latest git and building against gnutls (using openssl resulted in
it needing to re-trust every time I plug in because the TLS information
it is savin
https://github.com/libimobiledevice/libimobiledevice/issues/941
** Bug watch added: github.com/libimobiledevice/libimobiledevice/issues #941
https://github.com/libimobiledevice/libimobiledevice/issues/941
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
The following bug was reported and fixed in cups 2.2.11.
https://github.com/apple/cups/issues/5484
Without the fix, it is not possible to add or use a number of Canon
printers.
Currently, 19.04 ships with 2.2.10 + some backports, but those backports
do not include the fix f
Public bug reported:
After upgrading to IOS 11, I stopped being able to mount my ipad in
ubuntu.
The relevant log lines from gvfs-afc are:
gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc)
gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount)
gvfsd[1855]: afc: Lockd
I patched and built a package locally and confirmed the fix works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718554
Title:
Need updated libimobiledevice to mount IOS 11 devices
To manage notif
** Bug watch added: GNOME Bug Tracker #715119
https://bugzilla.gnome.org/show_bug.cgi?id=715119
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=715119
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
** Bug watch added: GNOME Bug Tracker #715119
https://bugzilla.gnome.org/show_bug.cgi?id=715119
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=715119
Importance: Unkn
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
** Bug watch added: GNOME Bug Tracker #715119
https://bugzilla.gnome.org/show_bug.cgi?id=715119
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=715119
Importance: Unkn
** Bug watch added: GNOME Bug Tracker #749788
https://bugzilla.gnome.org/show_bug.cgi?id=749788
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=749788
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
ged in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194677
Title:
gvfsd-mtp crashed with SIGSEGV in ptp_transaction_new
in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218520
Title:
gvfsd-mtp assert failure: *** Error in `/usr/lib/gvfs/gvf
in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214144
Title:
gvfsd-mtp crashed with SIGSEGV in __GI___pthread_mutex_lock
ged in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208535
Title:
gvfsd-mtp crashed with SIGFPE in g_hash_table_looku
Assuming that the clean shutdown fix in 1.17.3 addressed this. Unplug
problems are unpredictable and hard to reproduce, so I want to clean the
slate and only look at reports from new releases with that possible fix.
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langd
There are many crash on eject bugs - the main issue is that the because
the USB device is gone libmtp is left in an unpredictable state, so it's
easy for things to blow up even as we try to exit as quickly as
possible. Did you see the exact same backtrace? It might also match one
of the other eject
** Changed in: gvfs (Ubuntu)
Status: New => Fix Committed
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
That's up the the Ubuntu package maintainers, but I doubt it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175947
Title:
gvfs-copy --preserve doesn't work with MTP devices
To manage notifications
*** This bug is a duplicate of bug 1227089 ***
https://bugs.launchpad.net/bugs/1227089
** This bug has been marked a duplicate of bug 1227089
gvfsd-mtp crashed with SIGSEGV in g_hash_table_lookup()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Changed in: gvfs (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274890
Title:
gvfsd-mtp crashed with SIGABRT in g_thread_abort()
To manage notif
The 3.8.2-0ubuntu2.2 release of Nautilus fixes this problem.
** Package changed: gvfs (Ubuntu) => nautilus (Ubuntu)
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: nautilus (Ubuntu)
Assignee: Philip Langdale (langdalepl) => (unassigned)
cyanogenmod on the phone to get the Google mtp
stack.
** Package changed: coreutils (Ubuntu) => gvfs (Ubuntu)
** Changed in: gvfs (Ubuntu)
Status: New => Invalid
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
--
You received this bug not
That's unfortunate. Basically, without those google extensions, MTP can
only do full-file copies. It can read a file off the device or send a
file. It can't let you read a little bit of a file, or selectively
update part of a file. This makes it mechancially impossible to do any
incremental operati
This is the very first version with any mtp support, and a lot of fixes
have gone in since then. Please reopen if you can reproduce on 14.04 or
newer.
** Changed in: gvfs (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip La
gvfs changes are now merged upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903422
Title:
Ubuntu does not work with Samsung Galaxy phones ( Unable to open raw
device 0)
To manage notifica
Mio,
USB3: There are still compatibility issues with usb2 devices plugged
into usb3 depending on the physical controller and kernel used. So I'm
not surprised to hear there are problems. This is low level and not
related to mtp.
Copying folders: Yes, this doesn't work, due to how Nautilus handles
Mio,
USB3 would be a kernel bug. You should look for unhappy messages in
dmesg output.
Moving files: There are two answers to this one. It is physically
possible to implement a "fake" file move in the backend, although if
that's the path you want to go down it should be done in gvfs core code
and
This has always been a problem. You can't have two MTP clients talking
to one device at the same time. Rhythmbox tries to talk directly at the
same time as gvfs and two stomp on each other. It was hard to notice
before because gvfs would simply fail to connect at all using the
gphoto2 backend, and
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101986
Title:
gvfsd-mtp crashed with SIGSEGV
** Bug watch added: GNOME Bug Tracker #692318
https://bugzilla.gnome.org/show_bug.cgi?id=692318
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=692318
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
** Bug watch added: GNOME Bug Tracker #692416
https://bugzilla.gnome.org/show_bug.cgi?id=692416
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=692416
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101306
Title:
gvfsd-mtp crashed with SIGSEGV in backend_d
It's the same bug. The retracing bot will identify them as dupes when it
finally gets around to processing them.
This one's a bit weird, but until I see the re-traced backtrace I can't
tell what's really going on, but it looks an awful lot like a bug that
should have been fixed in 1.15.3, so I'm p
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117729
Title:
gvfsd-mtp crashed with SIGSEGV in g_vfs_job_
The backtrace doesn't make any sense. do_query_info never calls
try_read, and the outer frames also show clear signs of corruption, so I
don't think we can rely on much in it - as such I don't think we even
know what function the crash occured in.
--
You received this bug notification because you
When you all say you're seeing this error, you have confirmed you're
getting the same stack trace? I'm still waiting for the retracer to fill
in the blanks but I've never seen this personally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) => Philip Langdale (langdalepl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1130597
Title:
gvfsd-mtp crashed with SIGSEGV in backend_d
This happened because rhythmbox and gvfs cannot both access the same MTP
device at the same time. The MTP protocol doesn't support multiple
clients. Rhytmbox's attempt to communicate with the device kills gvfs'
session, resulting in this.
You should explicitly unmount the device in Nautilus before
This is fixed in the newer releases of gvfs, available in raring and in
my backport ppa.
** Changed in: gvfs (Ubuntu)
Status: New => Fix Committed
** Changed in: gvfs (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of U
*** This bug is a duplicate of bug 1130597 ***
https://bugs.launchpad.net/bugs/1130597
** This bug is no longer a duplicate of bug 1101306
gvfsd-mtp crashed with SIGSEGV in backend_died()
** This bug has been marked a duplicate of bug 1130597
gvfsd-mtp crashed with SIGSEGV in backend_die
*** This bug is a duplicate of bug 1130597 ***
https://bugs.launchpad.net/bugs/1130597
** This bug is no longer a duplicate of bug 1101306
gvfsd-mtp crashed with SIGSEGV in backend_died()
** This bug has been marked a duplicate of bug 1130597
gvfsd-mtp crashed with SIGSEGV in backend_die
*** This bug is a duplicate of bug 1130597 ***
https://bugs.launchpad.net/bugs/1130597
** This bug is no longer a duplicate of bug 1101306
gvfsd-mtp crashed with SIGSEGV in backend_died()
** This bug has been marked a duplicate of bug 1130597
gvfsd-mtp crashed with SIGSEGV in backend_die
1 - 100 of 196 matches
Mail list logo
