ubuntu karmic: a problem after upgrade from jaunty

View: New views
3 Messages — Rating Filter:   Alert me  

ubuntu karmic: a problem after upgrade from jaunty

by wpollans :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I upgraded ubuntu on my laptop from jaunty to karmic last week.  My
phone is HTC Mogul running WM 6.0.  I use synce for occasional internet
sharing and copying files between phone and laptop.

Good news:  internet sharing works; synce-pls displays a listing of the
"My Documents" directory in main memory.


Bad news:  trying to use nautilus to browse files on phone (using
synce:/// in location bar) doesn't work - it produces an icon on the
Desktop and in the tray, but no files are listed.  The following shows
up in /var/log/messages and /var/log/syslog: "gvfsd-synce[1904]:
GVFS-CRITICAL: g_mount_spec_set_with_len: assertion `value != NULL'
failed".  Browsing with nautilus worked in jaunty.

Let me know what other info you need to know.


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
SynCE-Users mailing list
SynCE-Users@...
https://lists.sourceforge.net/lists/listinfo/synce-users

Parent Message unknown Re: ubuntu karmic: a problem after upgrade from jaunty

by Chris Horne :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message



I am experiencing very similar problems, using a Palm Treo Preo having
recently upgraded to Karmic

When I connect the PDA, Sync CE Tray Icon pops up to say that the PDA is
connected.

When I try to "Explore the Filemanager" Nautilus (2.28.1) opens up,
there is a delay with the spinning disk which eventually gives up, but
there are no files shown on the Mobile Device



When I try the "View device status" menu a Treo Information window opens
up, but I also get an error message.

    Failed to retrieve partnership information: The name
org.synce.SyncEngine was not provided by any .service files

However all the information about the device status appears to be shown
correctly.



Here are the extracts from the syslog.

When the PDA is plugged in:

Nov 14 09:53:40 old-faithfull kernel: [ 1387.044075] usb 2-2: new full
speed USB device using ohci_hcd and address 5
Nov 14 09:53:40 old-faithfull kernel: [ 1387.224062] usb 2-2: device
descriptor read/64, error -62
Nov 14 09:53:41 old-faithfull kernel: [ 1387.552721] usb 2-2:
configuration #1 chosen from 1 choice
Nov 14 09:53:41 old-faithfull kernel: [ 1387.649598] rndis_host 2-2:1.0:
RNDIS_MSG_QUERY(0x00010202) failed, -47
Nov 14 09:53:41 old-faithfull kernel: [ 1387.663718] eth1: register
'rndis_host' at usb-0000:00:02.0-2, RNDIS device, 80:00:60:0f:e8:00
Nov 14 09:53:41 old-faithfull NetworkManager:    SCPlugin-Ifupdown:
devices added
(path: /sys/devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2:1.0/net/eth1,
iface: eth1)
Nov 14 09:53:41 old-faithfull NetworkManager:    SCPluginIfupdown:
locking wired connection setting
Nov 14 09:53:41 old-faithfull NetworkManager:    Ifupdown: get unmanaged
devices count: 1
Nov 14 09:53:41 old-faithfull NetworkManager: <info>  (eth1): carrier is
OFF
Nov 14 09:53:41 old-faithfull NetworkManager: <info>  (eth1): new
Ethernet device (driver: 'rndis_host')
Nov 14 09:53:41 old-faithfull NetworkManager: <info>  (eth1): exported
as /org/freedesktop/NetworkManager/Devices/4
Nov 14 09:53:41 old-faithfull dhclient: Internet Systems Consortium DHCP
Client V3.1.2
Nov 14 09:53:41 old-faithfull dhclient: Copyright 2004-2008 Internet
Systems Consortium.
Nov 14 09:53:41 old-faithfull dhclient: All rights reserved.
Nov 14 09:53:41 old-faithfull dhclient: For info, please visit
http://www.isc.org/sw/dhcp/
Nov 14 09:53:41 old-faithfull dhclient:
Nov 14 09:53:41 old-faithfull NetworkManager: <info>  (eth1): carrier
now ON (device state 1)
Nov 14 09:53:42 old-faithfull dhclient: Listening on
LPF/eth1/80:00:60:0f:e8:00
Nov 14 09:53:42 old-faithfull dhclient: Sending on
LPF/eth1/80:00:60:0f:e8:00
Nov 14 09:53:42 old-faithfull dhclient: Sending on   Socket/fallback
Nov 14 09:53:43 old-faithfull avahi-daemon[817]: Registering new address
record for fe80::8200:60ff:fe0f:e800 on eth1.*.
Nov 14 09:53:46 old-faithfull dhclient: DHCPREQUEST of 169.254.2.2 on
eth1 to 255.255.255.255 port 67
Nov 14 09:53:46 old-faithfull dhclient: DHCPACK of 169.254.2.2 from
169.254.2.1
Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Joining mDNS multicast
group on interface eth1.IPv4 with address 169.254.2.2.
Nov 14 09:53:46 old-faithfull avahi-daemon[817]: New relevant interface
eth1.IPv4 for mDNS.
Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Registering new address
record for 169.254.2.2 on eth1.IPv4.
Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Withdrawing address
record for 169.254.2.2 on eth1.
Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Leaving mDNS multicast
group on interface eth1.IPv4 with address 169.254.2.2.
Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Interface eth1.IPv4 no
longer relevant for mDNS.
Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Joining mDNS multicast
group on interface eth1.IPv4 with address 169.254.2.2.
Nov 14 09:53:46 old-faithfull avahi-daemon[817]: New relevant interface
eth1.IPv4 for mDNS.
Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Registering new address
record ftheor 169.254.2.2 on eth1.IPv4.
Nov 14 09:53:46 old-faithfull dhclient: bound to 169.254.2.2 -- renewal
in 1243005 seconds.
Nov 14 09:53:52 old-faithfull kernel: [ 1398.432036] eth1: no IPv6
routers present

When I try to browse for files

Nov 14 09:56:11 old-faithfull wpa_supplicant[1339]:
CTRL-EVENT-SCAN-RESULTS
Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: read failed, error: 104
"Connection reset by peer"
Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: Failed to read size
Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: rapi_buffer_recv failed
Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: WARNING: HRESULT =
80004005: An unspecified failure has occurred
Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: CRITICAL:
synce_gvfs_query_fs_info: Failed to get store information: An
unspecified failure has occurred


In user.log we have the following

Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: read failed, error: 104
"Connection reset by peer"
Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: Failed to read size
Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: rapi_buffer_recv failed
Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: WARNING: HRESULT =
80004005: An unspecified failure has occurred
Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: CRITICAL:
synce_gvfs_query_fs_info: Failed to get store information: An
unspecified failure has occurred

messages.log

Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: WARNING: HRESULT =
80004005: An unspecified failure has occurred
Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: CRITICAL:
synce_gvfs_query_fs_info: Failed to get store information: An
unspecified failure has occurred


Any ideas?

Chris



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
SynCE-Users mailing list
SynCE-Users@...
https://lists.sourceforge.net/lists/listinfo/synce-users

Re: ubuntu karmic: a problem after upgrade from jaunty

by Mark Ellis :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

For the record, for all ubuntu karmic users (again)


synce-gvfs is broken, synce-gvfs is always broken after an upgrade
because the gvfs developers have no support whatsoever for third part
extensions, which is ridiculous, and I wish we still used gnomevfs
because of this.

Sorry about the rant, but this really annoys me.


Secondly, the dbus auto activation for the standard karmic
synce-sync-engine package is broken. This comes traight from the debian
package, so I guess the debian one is broken too. Either edit the
file /usr/share/dbus-1/services/org.synce.SyncEngine.service and change
sync-engine to synce-sync-engine, or use the synce ppa packages. The
jaunty ones will work fine until I build all the karmic ones.

Mark



On Sat, 2009-11-14 at 11:03 +0100, Chris Horne wrote:

>
> I am experiencing very similar problems, using a Palm Treo Preo having
> recently upgraded to Karmic
>
> When I connect the PDA, Sync CE Tray Icon pops up to say that the PDA is
> connected.
>
> When I try to "Explore the Filemanager" Nautilus (2.28.1) opens up,
> there is a delay with the spinning disk which eventually gives up, but
> there are no files shown on the Mobile Device
>
>
>
> When I try the "View device status" menu a Treo Information window opens
> up, but I also get an error message.
>
>     Failed to retrieve partnership information: The name
> org.synce.SyncEngine was not provided by any .service files
>
> However all the information about the device status appears to be shown
> correctly.
>
>
>
> Here are the extracts from the syslog.
>
> When the PDA is plugged in:
>
> Nov 14 09:53:40 old-faithfull kernel: [ 1387.044075] usb 2-2: new full
> speed USB device using ohci_hcd and address 5
> Nov 14 09:53:40 old-faithfull kernel: [ 1387.224062] usb 2-2: device
> descriptor read/64, error -62
> Nov 14 09:53:41 old-faithfull kernel: [ 1387.552721] usb 2-2:
> configuration #1 chosen from 1 choice
> Nov 14 09:53:41 old-faithfull kernel: [ 1387.649598] rndis_host 2-2:1.0:
> RNDIS_MSG_QUERY(0x00010202) failed, -47
> Nov 14 09:53:41 old-faithfull kernel: [ 1387.663718] eth1: register
> 'rndis_host' at usb-0000:00:02.0-2, RNDIS device, 80:00:60:0f:e8:00
> Nov 14 09:53:41 old-faithfull NetworkManager:    SCPlugin-Ifupdown:
> devices added
> (path: /sys/devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2:1.0/net/eth1,
> iface: eth1)
> Nov 14 09:53:41 old-faithfull NetworkManager:    SCPluginIfupdown:
> locking wired connection setting
> Nov 14 09:53:41 old-faithfull NetworkManager:    Ifupdown: get unmanaged
> devices count: 1
> Nov 14 09:53:41 old-faithfull NetworkManager: <info>  (eth1): carrier is
> OFF
> Nov 14 09:53:41 old-faithfull NetworkManager: <info>  (eth1): new
> Ethernet device (driver: 'rndis_host')
> Nov 14 09:53:41 old-faithfull NetworkManager: <info>  (eth1): exported
> as /org/freedesktop/NetworkManager/Devices/4
> Nov 14 09:53:41 old-faithfull dhclient: Internet Systems Consortium DHCP
> Client V3.1.2
> Nov 14 09:53:41 old-faithfull dhclient: Copyright 2004-2008 Internet
> Systems Consortium.
> Nov 14 09:53:41 old-faithfull dhclient: All rights reserved.
> Nov 14 09:53:41 old-faithfull dhclient: For info, please visit
> http://www.isc.org/sw/dhcp/
> Nov 14 09:53:41 old-faithfull dhclient:
> Nov 14 09:53:41 old-faithfull NetworkManager: <info>  (eth1): carrier
> now ON (device state 1)
> Nov 14 09:53:42 old-faithfull dhclient: Listening on
> LPF/eth1/80:00:60:0f:e8:00
> Nov 14 09:53:42 old-faithfull dhclient: Sending on
> LPF/eth1/80:00:60:0f:e8:00
> Nov 14 09:53:42 old-faithfull dhclient: Sending on   Socket/fallback
> Nov 14 09:53:43 old-faithfull avahi-daemon[817]: Registering new address
> record for fe80::8200:60ff:fe0f:e800 on eth1.*.
> Nov 14 09:53:46 old-faithfull dhclient: DHCPREQUEST of 169.254.2.2 on
> eth1 to 255.255.255.255 port 67
> Nov 14 09:53:46 old-faithfull dhclient: DHCPACK of 169.254.2.2 from
> 169.254.2.1
> Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Joining mDNS multicast
> group on interface eth1.IPv4 with address 169.254.2.2.
> Nov 14 09:53:46 old-faithfull avahi-daemon[817]: New relevant interface
> eth1.IPv4 for mDNS.
> Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Registering new address
> record for 169.254.2.2 on eth1.IPv4.
> Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Withdrawing address
> record for 169.254.2.2 on eth1.
> Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Leaving mDNS multicast
> group on interface eth1.IPv4 with address 169.254.2.2.
> Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Interface eth1.IPv4 no
> longer relevant for mDNS.
> Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Joining mDNS multicast
> group on interface eth1.IPv4 with address 169.254.2.2.
> Nov 14 09:53:46 old-faithfull avahi-daemon[817]: New relevant interface
> eth1.IPv4 for mDNS.
> Nov 14 09:53:46 old-faithfull avahi-daemon[817]: Registering new address
> record ftheor 169.254.2.2 on eth1.IPv4.
> Nov 14 09:53:46 old-faithfull dhclient: bound to 169.254.2.2 -- renewal
> in 1243005 seconds.
> Nov 14 09:53:52 old-faithfull kernel: [ 1398.432036] eth1: no IPv6
> routers present
>
> When I try to browse for files
>
> Nov 14 09:56:11 old-faithfull wpa_supplicant[1339]:
> CTRL-EVENT-SCAN-RESULTS
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: read failed, error: 104
> "Connection reset by peer"
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: Failed to read size
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: rapi_buffer_recv failed
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: WARNING: HRESULT =
> 80004005: An unspecified failure has occurred
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: CRITICAL:
> synce_gvfs_query_fs_info: Failed to get store information: An
> unspecified failure has occurred
>
>
> In user.log we have the following
>
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: read failed, error: 104
> "Connection reset by peer"
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: Failed to read size
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: rapi_buffer_recv failed
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: WARNING: HRESULT =
> 80004005: An unspecified failure has occurred
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: CRITICAL:
> synce_gvfs_query_fs_info: Failed to get store information: An
> unspecified failure has occurred
>
> messages.log
>
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: WARNING: HRESULT =
> 80004005: An unspecified failure has occurred
> Nov 14 09:56:43 old-faithfull gvfsd-synce[2448]: CRITICAL:
> synce_gvfs_query_fs_info: Failed to get store information: An
> unspecified failure has occurred
>
>
> Any ideas?
>
> Chris
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> SynCE-Users mailing list
> SynCE-Users@...
> https://lists.sourceforge.net/lists/listinfo/synce-users


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
SynCE-Users mailing list
SynCE-Users@...
https://lists.sourceforge.net/lists/listinfo/synce-users

signature.asc (204 bytes) Download Attachment