[Bug 1292041] Re: Lockscreen doesn't turn off the screen
For me, the screen blanks, then the monitor goes into low-power mode when it's supposed to. But then, at some point later (I haven't pinpointed exactly when), the monitor comes out of powersave mode, and stays on. The screen stays blanked, but the monitor is on full-power mode. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1045899] Re: Maximum number of clients reached
Another clue may be that this is a laptop, and I only see the problem when I'm docked with an external monitor setup (so I have two screens). I never see this problem without the external/dual screen. I have a desktop machine with only a single screen, but identical software setup, which stays up for weeks and never sees this problem. I've attached the script I run (basically just call xplanet to generate a new image every 5min, and nautilus automatically picks it up), and I've added nautilus to the affected list. ** Attachment added: "desktop background update script" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1045899/+attachment/3432200/+files/xplanet-gnome ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1045899 Title: Maximum number of clients reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1045899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1045899] Re: Maximum number of clients reached
** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1045899 Title: Maximum number of clients reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1045899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 934582] Re: Apparent "hide_status_icon_on_unity.patch" regression
Sorry it took so long, but I can confirm that the problem is gone with the new gnome-settings-daemon package. Thanks Sebastien! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/934582 Title: Apparent "hide_status_icon_on_unity.patch" regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934582/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 934582] Re: Apparent "hide_status_icon_on_unity.patch" regression
> btw you guys should really drop the 'all' whitelist, that's what is creating those bugs for you... Sebastien, are you joking or trolling? You aren't seriously suggesting that we should simply stop using any software that doesn't support the indicator system, simply because the Ubuntu switch to Unity/indicators is complicated and has caused bugs interacting with software written for gnome, are you? It would be much easier for me to simply quit using Unity instead, but in general, I like where Ubuntu is going with Unity, and want to support & help fix bugs, not just work around and ignore them. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/934582 Title: Apparent "hide_status_icon_on_unity.patch" regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934582/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 934582] Re: Apparent "hide_status_icon_on_unity.patch" regression
Heh, I'm also seeing the duplicate nm-applet icons now as well. Both nm-applet icons are functional as well, which is a bit different than the power/battery icons. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/934582 Title: Apparent "hide_status_icon_on_unity.patch" regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934582/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 934582] Re: Apparent "hide_status_icon_on_unity.patch" regression
Same here, unity session, always happens. Note that as in the previous bug report, this happens when the dconf "/desktop/unity/panel/systray- whitelist" key is set to "all" (which is really the only sane value for it, given that lots of software only supports the gnome systray, and does not support the indicator system). And I suppose this is an apropos place to once again plead for a "systray-blacklist" key, which would be *far* more useful than systray- whitelist :). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/934582 Title: Apparent "hide_status_icon_on_unity.patch" regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934582/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 833397] Re: indicator power displayed twice on panel
I'm not sure what the appropriate way to report a regression is, but I created a new bug, and provided this bug number in it: https://bugs.launchpad.net/bugs/934582 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/833397 Title: indicator power displayed twice on panel To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/833397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 934582] [NEW] Apparent "hide_status_icon_on_unity.patch" regression
Public bug reported: Bug #833397, fixed in Oneiric, seems to be back in version 3.3.5-0ubuntu3. I now see both the gnome power status applet icon and the indicator one (although only the indicator icon is functional). ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: precise ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/934582 Title: Apparent "hide_status_icon_on_unity.patch" regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934582/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 833397] Re: indicator power displayed twice on panel
** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/833397 Title: indicator power displayed twice on panel To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/833397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 833397] Re: indicator power displayed twice on panel
This bug seems to have regressed back into gnome-settings-daemon 3.3.5-0ubuntu3 in Precise. I now see a duplicate gnome battery applet icon in addition to the indicator one. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/833397 Title: indicator power displayed twice on panel To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/833397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 325973] Re: gnome-session keeps respawning nautilus when no desktop is drawed
@Sebastien: Ooh, excellent idea. Here's my story ;) I don't want nautilus to draw the desktop because it doesn't give me a useful desktop context menu, or even any way to create a useful desktop context menu. And if it's drawing the desktop, it won't allow any other software to give me a desktop menu. So I just turn show_desktop off, and run xfdesktop instead (which gives me a context menu I can customize any way I want). I don't particularly care if Nautilus is running or not, as long as it's not sucking up too many resources. I just want a desktop menu I can control/customize. -- gnome-session keeps respawning nautilus when no desktop is drawed https://bugs.launchpad.net/bugs/325973 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 325973] Re: gnome-session keeps respawning nautilus when no desktop is drawed
I agree with Chris that a proper fix ought to be committed, rather than just another workaround. If nobody cares about the "show_desktop" option enough to fix it, maybe it should just be disabled (i.e. remove the gconf key, and just always show the desktop). Personally, losing this option would annoy me enough to make me finally dump the GNOME desktop altogether, but it's at least a solution, and it's better than just continuing to ship a broken Nautilus. The option is certainly useless in its currently broken state, so just disabling it shouldn't be much of a leap. -- gnome-session keeps respawning nautilus when no desktop is drawed https://bugs.launchpad.net/bugs/325973 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 150432] Re: gnome-keyring-daemon does not survive suspend/resume.
Umm. Nevermind. Turns out PIBKAC... A while back, I changed /etc/defaults/acpi-support to restart dbus on resume, 'cause that was the only way I could get network-manager to resume itself. That was killing gnome-keyring-daemon as well as gnome- power-manager :o( Sorry for the false alarm. My bad. ** Changed in: gnome-keyring (Ubuntu) Status: Incomplete => Invalid -- gnome-keyring-daemon does not survive suspend/resume. https://bugs.launchpad.net/bugs/150432 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 150072] Re: nautilus crashed on login with SIGSEGV in g_slice_alloc()
Unfortunately, no. I've never been able to get it to crash, nor consume 100% CPU when running it from a command line after login. I've only ever seen it happen when logging in (and since it's not in my session, I can't even figure out why it's running). -- nautilus crashed on login with SIGSEGV in g_slice_alloc() https://bugs.launchpad.net/bugs/150072 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 150072] Re: nautilus crashed on login with SIGSEGV in g_slice_alloc()
Hmm. I don't even know how nautilus is being run on login, much less how to start it up under valgrind. AFAICT, I don't see any reason that nautilus should even be trying to start up. It's not in my session script, I'm not using it to manage my desktop, etc... Anyway, I'd be happy to try running nautilus under valgrind on login, if you can explain how I can do so. -- nautilus crashed on login with SIGSEGV in g_slice_alloc() https://bugs.launchpad.net/bugs/150072 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 150432] Re: gnome-keyring-daemon does not survive suspend/resume.
Well, the keyring stores all kinds of useful information, like WPA/WEP keys, ssh key passphrases, etc.. The way I first noticed that the daemon wasn't running is that Network Manager couldn't just resume my wireless connection, but would always ask for the WAP's WPA passphrase (since it couldn't get it from the keyring). Same thing goes for using ssh (can't rely on the keyring to provide ssh-agent with the passphrase for the ssh key in question). -- gnome-keyring-daemon does not survive suspend/resume. https://bugs.launchpad.net/bugs/150432 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 150432] gnome-keyring-daemon does not survive suspend/resume.
Public bug reported: Binary package hint: gnome-keyring gnome-keyring-daemon is running before suspend, but is no longer running upon resume. Doesn't survive suspend to disk or ram. ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- gnome-keyring-daemon does not survive suspend/resume. https://bugs.launchpad.net/bugs/150432 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150072] nautilus crashed on login with SIGSEGV in g_slice_alloc()
Public bug reported: Binary package hint: nautilus Latest Gutsy update as of today. When I log in, Nautilus will either eat up 100% of CPU, or it will segfault. I can subsequently run Nautilus via the "Places" menu, and browse around w/out problem. Possibly relevant out-of-ordinary details: I have the "/apps/nautilus/preferences/show_desktop" gconf key set to false, and I'm running xfdesktop to draw the root window. I'm also running compiz fusion. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sat Oct 6 22:58:33 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/nautilus NonfreeKernelModules: cdrom Package: nautilus 1:2.20.0-0ubuntu6 PackageArchitecture: i386 ProcCmdline: nautilus --no-default-window --sm-client-id default2 ProcCwd: /home/brett ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 Signal: 11 SourcePackage: nautilus Stacktrace: #0 0xb75706fe in g_slice_alloc () from /usr/lib/libglib-2.0.so.0 #1 0xb7575cb3 in g_string_sized_new () from /usr/lib/libglib-2.0.so.0 #2 0xb7575d25 in g_string_new () from /usr/lib/libglib-2.0.so.0 #3 0xb75456a3 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x in ?? () StacktraceTop: g_slice_alloc () from /usr/lib/libglib-2.0.so.0 g_string_sized_new () from /usr/lib/libglib-2.0.so.0 g_string_new () from /usr/lib/libglib-2.0.so.0 ?? () from /usr/lib/libglib-2.0.so.0 ?? () Title: nautilus crashed with SIGSEGV in g_slice_alloc() Uname: Linux river 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner scard video ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash -- nautilus crashed on login with SIGSEGV in g_slice_alloc() https://bugs.launchpad.net/bugs/150072 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150072] Re: nautilus crashed on login with SIGSEGV in g_slice_alloc()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/9850414/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/9850415/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/9850416/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/9850417/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/9850418/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/9850419/Registers.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/9850420/ThreadStacktrace.txt ** Visibility changed to: Public -- nautilus crashed on login with SIGSEGV in g_slice_alloc() https://bugs.launchpad.net/bugs/150072 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device
I'll also confirm this same bug with a Tungsten T5. Adding a due date to all todos sucks, but seems to work around the problem. Sadly, I'm guessing this won't get fixed in time for the feisty release :o( -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-pilot-conduits in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 33285] Re: Can´t sync Evolution with T5
I can confirm that my T5 syncs reliably on edgy. -- Can´t sync Evolution with T5 https://launchpad.net/bugs/33285 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 33285] Re: Can´t sync Evolution with T 5
** Bug 39587 has been marked a duplicate of this bug -- Can´t sync Evolution with T5 https://launchpad.net/malone/bugs/33285 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39587] Re: [dapper] gpilotd does not recognize USB sync attempt (regression since gnome-pilot_2.0.13-0ubuntu14)
*** This bug is a duplicate of bug 33285 *** I confirmed that mounting usbfs on /proc/bus/usb fixes the problem, so this is a duplicate of 33285. ** This bug has been marked a duplicate of bug 33285 Can´t sync Evolution with T5 -- [dapper] gpilotd does not recognize USB sync attempt (regression since gnome-pilot_2.0.13-0ubuntu14) https://launchpad.net/malone/bugs/39587 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39587] [dapper] gpilotd does not recognize USB sync attempt (regression since gnome-pilot_2.0.13-0ubuntu14)
Public bug reported: Affects: gnome-pilot (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: Syncing more-or-less worked in the previous version of gnome-pilot, but broke completely with dist-upgrade I did around April 12 (gnome-pilot 2.0.13-0ubuntu16) I think I was running 2.0.13-0ubuntu14 before. FWIW, I tried changing the device gpilotd is supposed to be watching to /dev/ttyUSB0, and that didn't work either. I can sync the pilot with jpilot/pilot-link, so I think the problem is isolated to gpilotd, or bonobo, or something gnome-pilot'ish :) Hopefully helpful additional info: kill gpilotd and start it running on a console: $ kill 14832;gpilotd --sm-disable gpilotd-Message: gnome-pilot 2.0.13 starting... gpilotd-Message: compiled for pilot-link version 0.11.8 gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network] gpilotd-Message: Activating CORBA server gpilotd-Message: bonobo_activation_active_server_register = 0 gpilotd-Message: Watching USB (/dev/ttyUSB1) gpilotd-Message: corba: get_pilots(...) gpilotd-Message: corba: get_pilots(...) gpilotd-Message: Client seems ok gpilotd-Message: Client seems ok gpilotd-Message: monitor_on(pilot_name="MyPilot",client_id = IOR:01001b00...) gpilotd-Message: corba: notify_on(event_type=CONNECT,callback=IOR:01001b00...) gpilotd-Message: corba: notify_on(event_type=CONDUIT,callback=IOR:01001b00...) gpilotd-Message: corba: notify_on(event_type=DISCONNECT,callback=IOR:01001b00...) gpilotd-Message: Found 4766, 0001 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0502, 0736 gpilotd-Message: Using net TRUE gpilotd-Message: Found 091e, 0004 gpilotd-Message: Using net TRUE gpilotd-Message: Found 082d, 0100 gpilotd-Message: Using net FALSE gpilotd-Message: Found 082d, 0200 gpilotd-Message: Using net TRUE gpilotd-Message: Found 082d, 0300 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0c88, 0021 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0001 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0002 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0003 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0020 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0031 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0040 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0050 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0060 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0061 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0070 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0080 gpilotd-Message: Using net TRUE gpilotd-Message: Found 04e8, 8001 gpilotd-Message: Using net TRUE gpilotd-Message: Found 04e8, 6601 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0038 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0066 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0095 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 009a gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00c9 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00da gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00e9 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0144 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0169 gpilotd-Message: Using net TRUE gpilotd-Message: Found 12ef, 0100 gpilotd-Message: Using net TRUE Then I push the hotsync button on my palm, while watching /var/log/syslog: Apr 14 11:41:50 localhost kernel: [4630258.127000] usb 4-1: new full speed USB device using uhci_hcd and address 15 Apr 14 11:41:50 localhost kernel: [4630258.259000] visor 4-1:1.0: Handspring Visor / Palm OS converter detected Apr 14 11:41:50 localhost kernel: [4630258.26] usb 4-1: Handspring Visor / Palm OS converter now attached to ttyUSB0 Apr 14 11:41:50 localhost kernel: [4630258.26] usb 4-1: Handspring Visor / Palm OS converter now attached to ttyUSB1 And nothing happens. No output from gpilotd at all, nothing in syslog. Finally it times out, and I get the USB disconnect in syslog: Apr 14 11:41:54 localhost kernel: [4630262.421000] usb 4-1: USB disconnect, address 15 Apr 14 11:41:54 localhost kernel: [4630262.421000] visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0 Apr 14 11:41:54 localhost kernel: [4630262.421000] visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1 Apr 14 11:41:54 localhost kernel: [4630262.421000] visor 4-1:1.0: device disconnected -- [dapper] gpilotd does not recognize USB sync attempt (regression since gnome-pilot_2.0.13-0ubuntu14) https://launchpad.net/malone/bugs/39587 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
