[Bug 275952] Re: Unread search folder removes messages as soon as their unread flag is toggled
This affects me, too, since upgrading from 10.04 to 10.10. This is from Evolution 2.28.x to 2.30.3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/275952 Title: Unread search folder removes messages as soon as their unread flag is toggled -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 647953] [NEW] evolution-data-server header file contains illegal MICRO_VERSION
Public bug reported: Binary package hint: evolution-data-server-dev evolution-data-server dev 2.28.3.1-0ubuntu5 contains an upstream bug, as far as I can see. /usr/include/evolution-data-server-2.28/libedataserver/eds-version.h contains #define EDS_MICRO_VERSION 3.1 and #define EDS_CHECK_VERSION(major,minor,micro) \ (EDS_MAJOR_VERSION (major) || \ (EDS_MAJOR_VERSION == (major) EDS_MINOR_VERSION (minor)) || \ (EDS_MAJOR_VERSION == (major) EDS_MINOR_VERSION == (minor)) \ EDS_MICRO_VERSION = (micro)) If you try to use EDS_CHECK_VERSION, the pre-processor complains with error: floating constant in preprocessor expression The problem is the MICRO_VERSION should be an integer. Looks like upstream carelessness, fixed on the 2.28 upstream eds branch. ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- evolution-data-server header file contains illegal MICRO_VERSION https://bugs.launchpad.net/bugs/647953 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 388707] Re: brasero segfault on startup
I listed steps 1,2,3 in my initial bug report: load an audio CD into secondary slave IDE device, cancel gnome handler, fire up brasero and get a segfault every time. Doesn't seem to happen with data CDs, or with the secondary master IDE device (dvd drive). Hardware: primary IDE has two hard disks, secondary IDE has DVD on master and CD burner on slave. CD-burner is branded creative CD RW and shows up in dmesg as: scsi 2:0:1:0: CD-ROMLITE-ON LTR-12101B LS3J PQ: 0 ANSI: 5 sr1: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray sr 2:0:1:0: Attached scsi CD-ROM sr1 uname -a : Linux sirocco 2.6.28-6-386 #20-Ubuntu Fri Apr 17 08:32:39 UTC 2009 i686 GNU/Linux -- brasero segfault on startup https://bugs.launchpad.net/bugs/388707 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 388707] [NEW] brasero segfault on startup
Public bug reported: Binary package hint: brasero I'm getting a segfault on brasero startup on jaunty. My system is up to date. I am running brasero 2.26.1-0ubuntu1 and libbrasero-media0 2.26.1-0ubuntu1 Rather like bug #335942, nautilus will also crash with a segfault. I can reproduce this crash every time. The steps are: 1. Put an audio CD into my slave cdrom (a cd burner). If I put it into the primary (DVD drive, not burner) I have no problems. 2. Cancel when gnome offers to fire up rhythmbox. 3. Try to start brasero from command-line (or nautilus, come to that) See attached gdb and valgrind output. I get the same stack trace from nautilus. ** Affects: brasero (Ubuntu) Importance: Undecided Status: New -- brasero segfault on startup https://bugs.launchpad.net/bugs/388707 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 388707] Re: brasero segfault on startup
** Attachment added: gdb-brasero.txt http://launchpadlibrarian.net/28040868/gdb-brasero.txt -- brasero segfault on startup https://bugs.launchpad.net/bugs/388707 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 388707] Re: brasero segfault on startup
** Attachment added: valgrind.log http://launchpadlibrarian.net/28040876/valgrind.log -- brasero segfault on startup https://bugs.launchpad.net/bugs/388707 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 15046] Re: Gnome-pilot does not start by default
Murray says I can't sync, but it's not clear whether this is just an example of the known Edgy problems (i.e. with gnome- pilot-2.0.14-0Ubuntu2) or something else. He could try installing the packages I rolled (see gnome bug 365181, comment 14) and see if that fixes matters. Failing that, it's the usual triage: kill off any running gpilotd. Run it in a terminal window. Likewise for gpilotd-control-applet if you need to run that. Then try to sync and report messages displayed at the terminal. -- Gnome-pilot does not start by default https://launchpad.net/bugs/15046 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 30015] Re: should automatically detect attached devices and use the apporpriate port
There's little point in forwarding upstream. AFAIK, it is not possible to 100% reliably determine the correct ttyUSB device, so the visor/ttyUSB support in gnome-pilot is not going to improve (ie. upstream would be WONTFIX). The correct roadmap seems to be to move to using direct libusb support. At present this is done by users by hand. I've opened upstream #395372, to outline a path allowing distributions to migrate to direct libusb usage. To make this the distribution-level default would involve 1. blacklisting the visor module. 2. installing and testing the pilot-link udev rule for libusb support (i.e. see the pilot-link libusb HOWTO) 3. making 'usb:' the default device in gnome-pilot (simple change to one of the glade files). 4. thinking about how to automatically migrate existing ttyUSB gnome-pilot configs to usb:. This would best be done by adding a 'use libusb' option to the gnome-pilot config. The distribution could enable this option by default, in which case any configured device names for USB connections would be ignored. 3 and 4 are covered by the upstream item. -- should automatically detect attached devices and use the apporpriate port https://launchpad.net/bugs/30015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
Yes, looks right.
Oddly there's one stray diff block I don't recognise:
--
@@ -1256,6 +1266,7 @@
gpcap_save_state (GnomePilotCapplet *gpcap)
{
GnomePilotCappletPrivate *priv;
+ GtkObjectClass *gppd_class;
priv = gpcap-priv;
---
This wasn't in the 02_capplet_pdialog.diff file in my edgy package, so I
don't know where it came from! It'll just cause an unused variable
warning, so it's not worth removing unless you feel like it.
--
gpilotd locks up my Palm Z22
https://launchpad.net/bugs/66355
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 19528] Re: problems syncing calendar and todo list, adresses works
See also the following upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=363102 ... which contains a patch to evolution-data-server to prevent freeing of an ical data structure by a background thread while the data is in use. This seems to be the exact cause of the crashes I was getting every time with the calendar conduit. 363102 is, IMO, a dupe of 319076. -- problems syncing calendar and todo list, adresses works https://launchpad.net/bugs/19528 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45297] Re: applet isn't transparent in transparent panels
Clearly working :) Mind you, I would say that, wouldn't I... -- applet isn't transparent in transparent panels https://launchpad.net/bugs/45297 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73149] Re: Copy from pilot works only the first time
probably an instance of upstream gnome bug 319076. -- Copy from pilot works only the first time https://launchpad.net/bugs/73149 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 30015] Re: should automatically detect attached devices and use the apporpriate port
The situation is improved in gnome-pilot 2.0.14/15, but not really fixed or fixable. IMO, it is not possible to robustly detect the correct ttyUSB port to use. The /dev/pilot symlink is the best bet, but even then I've seen situations in which it suddenly starts pointing to the wrong ttyUSB port. Last time I checked, the HAL hints weren't robust either, plausibly for the same unidentified underlying reason. At least by allowing the device name to be specified we prevent total sync failure if HAL or the udev rules get confused. The best option seem to be libusb syncing. That doesn't suffer from the ttyUSB problems. Just select 'usb:' as the device name, and it should just work (assuming you've blacklisted the visor module and installed your libusb udev rules). The pilot-link guys still consider direct libusb support as a beta feature, hence they weren't recommending that distributions dump the visor usbserial module just yet. Not sure when this is likely to change: already it seems that libusb is causing fewer problems than usbserial. At least the HAL support means we no longer have to poll sysfs. -- should automatically detect attached devices and use the apporpriate port https://launchpad.net/bugs/30015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 19528] Re: problems syncing calendar and todo list, adresses works
In my case, I was getting crashes in evolution-data-server. It would appear to be: http://bugzilla.gnome.org/show_bug.cgi?id=319076 -- problems syncing calendar and todo list, adresses works https://launchpad.net/bugs/19528 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73891] build error trying to build evolution-data-server from .dsc, .diff.gz, and tarball
Public bug reported: I was trying to rebuild evolution-data-server without optimisation, to help track down a bug triggered by a gnome-pilot synchronisation with the calendar conduit. I am having trouble with the libical part of e-d-s. It appears that the calendar/libical/configure script is not getting run. The build stops when it goes into calendar/libical and attempts to 'make all', because there isn't a Makefile there. I'm not sure where to look for problems. I seem to have a reasonable development environment (I'd no problem rebuilding the gnome-pilot .deb packages, for example). I tried installing automake1.8 and automake1.9, which I hadn't got installed, but had the same error. Any ideas? For the record, the build steps I've been using are pretty much: 1. get the .dsc, .diff.gz and tarball. 2. run dpkg-src to untar and apply the diff. 3. go into the e-d-s directory, and run 'dpkg-buildpackage -rfakeroot' I'm using the current Edgy package, AFAIK, e-d-s-0ubuntu3. ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: Unconfirmed -- build error trying to build evolution-data-server from .dsc, .diff.gz, and tarball https://launchpad.net/bugs/73891 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73891] Re: build error trying to build evolution-data-server from .dsc, .diff.gz, and tarball
Thanks for the pointer. I'm away from my dev machine at the moment, but I'll do as you suggest when I get a chance. -- build error trying to build evolution-data-server from .dsc, .diff.gz, and tarball https://launchpad.net/bugs/73891 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
I set my sync options to copy from PDA, and got a crash while syncing the calendar conduit. I did not have trouble with a copy from PDA in the address or memo conduits. I tried downgrading to the Edgy package and produced the same crashes. So it seems to be a bug in the evolution calendar backend, or conduit. I guess you'd better disable the calendar conduit for the moment. There have been reports elsewhere of the calendar conduit not working, so I suspect a general problem in that code. I didn't get the same crash as KenSentMe, my crash occured on the evolution-data-server side (icalcomponent_as_ical_string) Regards, Matt -- (gdb) bt #0 0xe410 in __kernel_vsyscall () #1 0xb75626cb in waitpid () from /lib/tls/i686/cmov/libc.so.6 #2 0xb750a281 in strtold_l () from /lib/tls/i686/cmov/libc.so.6 #3 0xb750a632 in system () from /lib/tls/i686/cmov/libc.so.6 #4 0x0804b2f9 in gnome_segv_handler (signo=11) at server.c:114 #5 signal handler called #6 pvl_head (L=0x813b3e0) at pvl.c:541 #7 0xb7d08744 in icalcomponent_as_ical_string (impl=0x807ef48) at icalcomponent.c:334 #8 0xb7169f38 in save_file_when_idle (user_data=0x80716a0) at e-cal-backend-file.c:176 #9 0xb7679aa1 in g_source_is_destroyed () from /usr/lib/libglib-2.0.so.0 #10 0xb767b802 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #11 0xb767e7df in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #12 0xb767eb89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #13 0xb7b10a23 in bonobo_main () from /usr/lib/libbonobo-2.so.0 #14 0x0804ba24 in main (argc=134643760, argv=0xbfe281b4) at server.c:393 #15 0xb74e98cc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #16 0x0804a451 in _start () -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
https://launchpad.net/distros/ubuntu/+source/gnome-pilot/+bug/19528 -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 19528] Re: problems syncing calendar and todo list, adresses works
There are two problems here. When calendar doesn't crash, but just doesn't appear to sync, you've probably got a case of: http://bugzilla.gnome.org/show_bug.cgi?id=316370 When the caledar crashes, that looks to me like something different. It is possible that it is a regression introduced with the as-yet- unofficial port of the evolution conduit code to the pilot-link 0.12.x API. I don't know. -- problems syncing calendar and todo list, adresses works https://launchpad.net/bugs/19528 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
I have built an unofficial Ubuntu package based on the recent fixes, which should be suitable for Edgy. You can try them out from: http://www.inference.phy.cam.ac.uk/mcdavey/downloads/ This build is not an official Ubuntu release. It is unsupported, but should fix two specific issues with the current Edgy packages: 1. problems with crashing the palmos device when attempting a sync. 2. problems crashing the gpilotd-control-applet when retrieving the username and deviceID in the 'add pda' step. If you have problems with these packages, feel free to open a bug on bugzilla.gnome.org. Strictly speaking, you shouldn't send them to ubuntu, because they haven't built this updated package... If you have success, feel free update this bug with any success stories. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 66355] Re: gpilotd locks up my Palm Z22
On Fri, 2006-11-24 at 15:54 +, Phil wrote: Dear Matt, thanks a lot for your great help. I now did as you said and installed the gnome-pilot in /temp/gp. Unfortunately, I now have the problem that the daemon obviously cannot be registered (see below). Sorry for bothering you again but I really do not have any clue what happens. I'm not surprised... You need to copy the file: /tmp/gp/lib/bonobo/servers/GNOME_Pilot_Daemon.server into the right location, which is probably /usr/lib/bonobo/servers/ (hint: look for other .server files...) If you want to use the applet, you'll need to copy the other .server file from /tmp/gp/lib/bonobo/servers/ Note, by the way, that /tmp/gp might well get cleared out on a reboot, so if you want to keep this configuration for any length of time you may want to install somewhere else :) Matt Matt Davey Never forget what a man says to you when he is angry. [EMAIL PROTECTED] -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
Phil, As mentioned by Daniel Holbach (2006-11-16 above), there is a testable package uploaded to Feisty. That package will contain the patch. In addition there's a link to the upstream bug at the top of this ticket and, as I mentioned, that contains a link to a downloadable tarball. The version I committed to gnome-pilot CVS is viewable here: http://cvs.gnome.org/viewcvs/gnome-pilot/gpilotd/gpilotd.c?r1=1.160r2=1.161 It's also worth mentioning that gnome-pilot 2.0.15 has just been released. It will obviously take a bit of time for this to show up in Ubuntu. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62310] Re: Gpilotd does not reply to all sync request
I've seen this a few times, and what appears to be happening is that /dev/pilot starts pointing to the 'wrong' ttyUSB device. When this happens you'll see the pi_accept_to returned -202 messages (-202 means 'timeout' in pilot-link speak). If this is a problem for you, you have two options: 1. choose /dev/ttyUSB0 or /dev/ttyUSB1, as appropriate for your pda, instead of /dev/pilot. 2. If you're running pilot-link-0.12.x, migrate to libusb syncing instead of usbserial. -- Gpilotd does not reply to all sync request https://launchpad.net/bugs/62310 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 64575] Re: Wrong character in memo category after palm sync
I agree with DB. Time to forward upstream to evo-conduits. -- Wrong character in memo category after palm sync https://launchpad.net/bugs/64575 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
Hi Phil, It looks as though gnome-pilot hasn't actually been built correctly. I don't know what steps you took (I didn't give detailed instructions, because usually people asking for patches and building packages are old hands at this stuff). You say you built gnome-pilot 1.161, but 1.161 refers to one single file from the gnome-pilot source tree. So I don't know whether you checked out the whole gnome-pilot source from CVS (I doubt it) or just dropped the updated gpilotd.c file into some other source distribution of gnome-pilot. Anyway, here are some more detailed instructions that might help you along: 1. download gnome-pilot 2.0.15 from gnome.org: http://ftp.gnome.org/pub/GNOME/sources/gnome-pilot/2.0/gnome-pilot-2.0.15.tar.gz 2. unpack the file using 'tar xzf gnome-pilot-2.0.15.tar.gz' 3. change into the gnome-pilot-2.0.15 directory. 4. build it, configuring it to put the installation somewhere that won't conflict with your system installation (so that if an updated Edgy version is released you can easily upgrade). Here's how to build it: 4a. ./configure --prefix=/tmp/gp -- or use some other location instead of /tmp/gp 4b. make make install 5. Now, start the background daemon: killall gpilotd; /tmp/gp/libexec/gpilotd 6. In another window, start the corresponding config applet: /tmp/gp/bin/gpilotd-control-applet With any luck, you'll be in business, i.e. able to configure and enable the backup conduit. You won't have Evolution conduits at this stage. If you want those, copy the .conduit files from your system installation (I'm not 100% where they go on Ubuntu, so do 'locate e-address | grep conduit') and put them into /tmp/gp/share/gnome-pilot/conduits/. These instructions are off the top of my head, so apologies if I've made some mistakes. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 71837] Re: Fatal error on Palm during synchronization with Evolution
Looks like duplicate of bug # 66355 -- Fatal error on Palm during synchronization with Evolution https://launchpad.net/bugs/71837 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 67077] Re: After one sync, connections to a Tungsten T3 device fails
Joel, silly question, but there isn't any chance you've got two versions of gpilotd on your system: one that you run from the command line and one that the applet finds? There aren't any arguments that I can think of that would affect the behaviour as you describe. One thing to check is whether your /dev/pilot symlink always points to the right ttyUSBx device. I've a vague notion I've come across cases where it sometimes gets confused, pointing to either ttyUSB1 or ttyUSB0, but not consistently. If this is the case you may want to try configuring gpilotd to use the correct ttyUSBx device rather than relying on /dev/pilot. Either that, or configure pilot-link for libusb syncing (search around for the howto) and then you can use the usb: pseudo device. -- After one sync, connections to a Tungsten T3 device fails https://launchpad.net/bugs/67077 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 65513] Re: Sync failes - Evolution/T5 - Ubuntu Edgy
This could have been forwarded to upstream evolution-conduits as an improvement suggestion... It would be better if bogus data from the palm didn't cause the app to throw an assert failure, but resulted in a log message and skipping of the record, or some such. It's a rare enough case, I guess. -- Sync failes - Evolution/T5 - Ubuntu Edgy https://launchpad.net/bugs/65513 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 67077] Re: After one sync, connections to a Tungsten T3 device fails
Joel: Indeed I only have one gpilotd. I attempted to get libusb working. - that seems fine as i got pilot-xfer -p usb: -l to work. But I did have a question about ~/.gnome2/gnome-pilot.d/gpilot I could not figure out what to set /dev/pilot to? You should be able to set it to 'usb:' using the config applet. It should even be one of the options in the drop down list. One thing I did notice is that when gpilotd is run at the command line is says: [...] (gnome-pilot:21866): gpilotd-WARNING **: Number of devices is configured to 0 [...] Which seems to imply that it doesn't read the same config as when the applet runs gpilotd. Could that be the problem since sync works after this if I run the applet and then sync? Have you edited your ~/.gnome2/gnome-pilot.d/gpilot? Is it possible that it's been mucked up so that gpilotd can't parse it? I can't think of a good reason to edit that file by hand, at least with pilot-link 0.12 and gp 2.0.14. You could try removing or moving your ~/.gnome2/gnome-pilot.d directory altogether and trying the config steps again. Matt -- After one sync, connections to a Tungsten T3 device fails https://launchpad.net/bugs/67077 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
There is more info attached to the upstream bug, but the summary so far is: some palmos devices appear to have problems if a sync is attempted immediately after the device connects to the host computer. gnome-pilot 2.0.14 uses HAL to detect a palmos device, and so tends to attempt a connection considerably faster than in 2.0.13 and earlier. It's not clear what is causing this problem, but it seems to be in the usbserial / visor module case, so configuring libusb is a good workaround. Disabling HAL before attempting a sync also appears to work. A patch is being worked on, and a testable gnome-pilot tarball can be downloaded from the upstream bug. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
It all sounds like a timing issue. There have been several reports of regressions with minor udev updates, etc. It would be interesting if someone was able to report back with their experience of disabling HAL (see comment dated 2006-10-19 13:52:30 UTC) and/or libusb syncing. It should be possible to build in an appropriate pause between HAL notification and gpilotd attempting a sync, but we need to have more of an idea of where the timing problem lies first. It would also be good (as per my previous comment) to see if the device lock-ups can be reproduced with 'pilot-xfer -t 2', by starting pilot- xfer first and then attempting a sync. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
It's somewhat unusual to see gnome-pilot failing when pilot-link is reliable (especially in this way, which seems to be in the initial handshake with the PDA). Here are a few things to try: 1. Run pilot-xfer with a '-t 2' option. (This does the handshake in a way more like gnome-pilot). 2. Run gnome-pilot with a timeout setting of zero (edit the device using the control applet, under the 'Devices' tab). This does the handshake more like the way pilot-xfer does by default. There's a slight chance that (1) will lock up your device and (2) will magically fix the problem, but I don't hold out great hope. Worth checking out, though. If that doesn't fix things, next: 3. Run gpilotd from a terminal, and enable the following pilot-link environment variables to get extra debugging. Then send us the output: PILOT_DEBUG=DEV SLP CMP PADP NET SOCK PILOT_DEBUG_LEVEL=DEBUG And finally a possible workaround to help you get syncing while we get to the bottom of this: 4. We can use pi-nredir to redirect the pda connection to the network, and configure a network sync in gnome-pilot. First configure your PDA. On my PalmOS5 device it goes like this: a. specify 'Local' hotsync. b. edit hotsync 'LANsync preferences' and specify 'LANSync' instead of 'Local HotSync'. c. edit 'Primary PC Setup' in hotsync preferences, and specify '!!' as the primary PC name, specify the IP address of the machine where you'll run gnome-pilot in the 'Primary PC Address' box -- 127.0.0.1 would be fine if you're on the same machine as your usb cable. d. enter an appropriate subnet mask. 255.255.255.0 will probably do fine. Now, open the gnome-pilot configuration applet, and delete your USB device and create a 'Network' device. Finally, press hotsync on your PDA and quickly run pi-nredir from a terminal window: pi-nredir -p /dev/pilot or '-p /dev/ttyUSBx', whatever you use. If all goes well, pi-nredir should redirect the incoming USB connection to the network and gnome-pilot should connect. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
[aside] not sure why launchpad is reporting upstream status as 'rejected'. It was accidentally marked 'invalid' by the upstream reporter, but I reopened it today. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
Jon, your output suggests that you have '/dev/pilot' configured as your device name in gnome-pilot, but that that device does not exist during the sync attempt. Is this the device name you use with pilot-xfer? If not, configure gnome-pilot using the configuration applet, and set the device name to whatever you used with pilot-xfer. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
Okay, taking a closer look, those lines are just showing that there's a gap between the usb device being detected and the creation of the /dev/pilot symlink. At the end of the output we can see the 'poll', which means we've found /dev/pilot and are trying to talk. We've made some progress. The PDA crash does seem to be caused by some internal pilot-link code that sends some unexpected data to the PDA. I'm not entirely clear of the history of this code, but it appears to be an attempt to workaround some problems with udev device creation on linux :( We're getting down to a fairly low level here, but it might be useful to see: 1. the pilot-link debugging for the 'timeout=0' gnome-pilot case, and the normal pilot-xfer case. 2. the strace output you get from gpilotd on the timeout=2 case. Run 'strace gpilotd'. It'll produce a long output. What I want to see is whether the 'poll' actually returns a timeout, or some error. As for workarounds, it might be worth seeing if you can set up a direct 'libusb' connection: http://code.pilot-link.org/README.libusb once you've got it working for pilot-xfer, you just set the usb device in gnome-pilot to 'usb:' and hey presto, you don't need the visor module anymore. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66355] Re: gpilotd locks up my Palm Z22
Strange stuff. Looks like a timing issue. I'd strongly recommend seeing if you can get libusb syncing to work. What happened when you set the timeout to zero in gnome-pilot? Does it just sit there forever trying to connect until you kill it? You didn't send output for the gpilotd+timeout=0 case above... (I know, I'm very demanding) In the pilot-xfer+timeout=2 case, did you try starting pilot-xfer BEFORE starting the sync on the PDA? That is most like the way that gpilotd tries to connect: i.e. it'll try to connect the instant the pda is detected. Another thing to do is to try disabling HAL and restarting gpilotd. (/etc/init.d/hald stop, or something like that). That should fall back to checking for new USB devices every 2 seconds, instead of getting HAL notifications. That will introduce a random element into the attempts by gpilotd to connect. You may find that gnome-pilot will connect sometimes, and fail at other times. Thanks for all your debugging. It is very helpful. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
Glad that the kernel update appears to solve this issue, and that setting a non-zero timeout appears to solve the problem with the ttyUSB devices hanging around after a sync completes. I'm pretty sure this latter issue has been solved in gnome-pilot CVS, and the timeout=0 trick is only required for pilot-link 0.12.0 pre-releases (and maybe Suse's patched 0.11.8 version). Regards, Matt -- Pb syncing treo 650 on dapper drake https://launchpad.net/bugs/38574 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 50585] Re: Can't create folders in a mh mailbox
I've just opened a bug at bugzilla.gnome.org, with a patch to fix this issue. See: http://bugzilla.gnome.org/show_bug.cgi?id=347905 -- Can't create folders in a mh mailbox https://launchpad.net/bugs/50585 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 50585] Re: Can't create folders in a mh mailbox
after reading Felix's bug, it's possible that my bug and patch is a separate issue. I use a 'mh' backend, not 'maildir'. It seems likely that our problems have a common cause, but I haven't tried verifying with a maildir backend. -- Can't create folders in a mh mailbox https://launchpad.net/bugs/50585 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 25653] Re: gnome-pilot needs to be ported to new udev world order
see also #38574. It appears that the current 2.6.15 kernel is causing the problems. There have been success stories after upgrading to 2.6.17.1, and one poster suggested a workaround is to start gpilotd a second or two after initiating the sync. (open a terminal, do 'killall gpilotd', start the sync, wait, then do '/usr/libexec/gpilotd' (sorry, that path might be wrong on Ubuntu, try 'locate gpilotd' if it isn't there). -- gnome-pilot needs to be ported to new udev world order https://launchpad.net/bugs/25653 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45986] Re: unable to bind to pilot
probably a duplicate of #38574. -- unable to bind to pilot https://launchpad.net/bugs/45986 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45297] Re: applet isn't transparent in transparent panels
fixed in gnome-pilot CVS. -- applet isn't transparent in transparent panels https://launchpad.net/bugs/45297 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
There's not much more to say on this one... it seems very likely that the problem is with the ubuntu 2.6.15 kernel package and has been fixed in more recent revisions. I'd advise building your own kernel, or raising a bug against the kernel package. -- Pb syncing treo 650 on dapper drake https://launchpad.net/bugs/38574 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 43767] Re: Crashs when syncing with TE2
What version is your kernel? Do: 'uname -r' in a terminal. The bug I referred to above claims a problem with 2.6.15 was resolved with a pre- release of the 2.6.17 kernel which has not been officially released yet. I'm not saying the problem is resolved in up-to-date dapper. I believe there may be a problem with the currently shipped dapper kernel. -- Crashs when syncing with TE2 https://launchpad.net/bugs/43767 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
Try Upgrading kernel... It seems there may well be some kernel/usbserial bugs in the ubuntu 2.6.15 kernel that is screwing up ttyUSB connections. See the following Ubuntu bug: https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/39518 -- Pb syncing treo 650 on dapper drake https://launchpad.net/bugs/38574 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46436] Re: gpilotd fails with cannot open display
see recent thread on gnome-pilot-list This bug (and #45986, and maybe others?) appears to be caused by a kernel bug. Matt Price reported a kernel oops, and it appears that unitialised memory has been retruned by the ttyUSB device. See: https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/39518 In which a user fixed a crasher sync problem by upgrading his kernel to 2.6.17-rc4 -- gpilotd fails with cannot open display https://launchpad.net/bugs/46436 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
Thanks, Franz. The strace output is indeed helpful (although it is a bit frustrating that the output doesn't appear to be complete - probably stderr hadn't finished flushing before the process died). It looks as though pilot-xfer dies in pilot-link's unixserial.c code, in the function s_open, between lines 199 and 206. My best guess at the moment is that some recent kernel-related change is the root cause. I'm not familiar with Ubuntu, but is it possible to downgrade your kernel package a few revisions and see if the problem disappears? I've also sent a message to the pilot-link guys to see if it's ringing any bells there. Matt -- Pb syncing treo 650 on dapper drake https://launchpad.net/bugs/38574 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
What version of pilot-link is shipping with Dapper? For pilot-link 0.12, I have a couple more things to try out: try using: pilot-xfer -p usb: -l (see thread here: http://www.pilot-link.org/pipermail/pilot-link-general/2006-April/002721.html) Also, for gnome-pilot, try setting the 'timeout' to zero. You'll find the timeout parameter using the configuration applet, under the 'devices' editing dialog. -- Pb syncing treo 650 on dapper drake https://launchpad.net/bugs/38574 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
Hi, a couple of points from gnome-pilot. The 'invalid free' bug has just been fixed in CVS. I don't know why it has only recently shown up (it was reported on fedora) as the problem code was rather old. Anyway, that's a straight bug. Another problem has also been fixed, which may have caused some of the unreliability problems. Frank: do you find multiple /dev/ttyUSB* devices being created and hanging around? i.e. more than just the usual two? If so, you're affected by this bug, which again has been fixed in CVS. -- Pb syncing treo 650 on dapper drake https://launchpad.net/bugs/38574 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 43767] Re: Crashs when syncing with TE2
More info please! Do you get any error message? Try starting '/usr/libexec/gpilotd' from a terminal window (you might have to kill any running gpilotd process first using 'killall gpilotd'). Cut and paste the gpilotd output after a crash. -- Crashs when syncing with TE2 https://launchpad.net/bugs/43767 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 43623] Re: Can't enable Evolution conduits due to undefined symbol: pi_buffer_free
It looks like the evolution conduit is compiled for a more recent version of pilot-link (0.12.0 pre-release) than gnome-pilot. What version of pilot-link do you have installed? If you start '/usr/libexec/gpilotd' by hand, it will display the version of pilot-link it was compiled for. do 'ldd /usr/lib/evolution/2.6/conduits/libeaddress_conduit.so' and see if there are any library dependencies missing. What version of 'libpisock' is it built against? It should be same library that you get with 'ldd /usr/libexec/gpilotd'. Is there an Evolution update you can apply? -- Can't enable Evolution conduits due to undefined symbol: pi_buffer_free https://launchpad.net/bugs/43623 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
(sorry for misspelling your name, Franz...) A couple more diagnostic tips: have you tried the 'static device node' trick mentioned above? This basically means doing something like: # mknod /dev/pilot c 188 1 # chmod 0660 /dev/pilot # chown :uucp /dev/pilot to create a /dev/pilot device node that behaves like ttyUSB1. This trick can prevent annoying timing problems caused by latency in udev device node creation. do you get reliable behaviour with pilot-link? Try pilot-xfer -p /dev/ttyUSB1 -l If it works like a dream without any problems, then it's more likely to be a gnome-pilot problem. If it has trouble, chances are your problem lies elsewhere. -- Pb syncing treo 650 on dapper drake https://launchpad.net/bugs/38574 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38622] Re: Syncing fails The base directory ...
*** This bug is a duplicate of bug 33285 *** This error may indicate that you haven't set a valid directory for backups, etc, using the gnome-pilot applet. Try starting up gpilotd-control-applet, 'Add..'ing or 'Edit..'ing a Pilot entry, and setting a 'Local basedir' field. A recent upstream bugfix _should_ mean that it is no longer possible to add a Pilot entry without setting a valid directory. Of course, the applet shouldn't be showing junk when the entry is missing. So: questions: 1. do you have a 'Local basedir' set? 2. If not, does the error go away if you configure one? 3. Is it possible to 'Add' and new Pilot using the applet without setting a valid basedir? -- Syncing fails The base directory ... https://launchpad.net/bugs/38622 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 30015] Re: should automatically detect attached devices and use the apporpriate port
CVS version of gnome-pilot does use HAL. I found, however, that the canned hal pda rules simply didn't work for me (fc5). 'lshal' showed the USB device, and the 'visor' enabled pseudo device, but didn't report the pda capability, palmos identifier, ttyUSB port or anything. The good news is that the roadmap for pilot-link / gnome-pilot is the use of libusb, in which the visor ttyUSB port will no longer be used. For the moment, CVS uses HAL to detect the USB device, and then uses its devices.xml file to recognise it as a known palm device. The user still has to supply the port name. -- should automatically detect attached devices and use the apporpriate port https://launchpad.net/bugs/30015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 30015] Re: should automatically detect attached devices and use the apporpriate port
IMO, no. #25653 complained that gpilotd was looking for /proc/bus/usb/devices, and the fix is to read /sys/bus/usb if it is available. This is now done (unless HAL is being used...) This bug, #30015, is complaining that gnome-pilot doesn't give the user any guide to choosing the correct ttyUSB device for syncing. In a perfect world, HAL would tell gpilotd where the palm device is. In practice, HAL doesn't seem to be robustly detecting the presence of a palm device, so the user is stuck having to supply the device name to gnome-pilot, and HAL is just used to tell gpilotd that a USB device (any USB device) has appeared. I haven't yet followed up with the HAL people (I am positively not a HAL guru) to see why HAL is letting me down. As soon as HAL gets to the stage where it can be relied upon to detect all palm pda devices, and distinguish between visor and non-visor (i.e. libusb) connections, I'll be more than happy to make things simple for the users. -- should automatically detect attached devices and use the apporpriate port https://launchpad.net/bugs/30015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
