[Bug 183846] Re: google calendar source does not show all events
I switched to caldav, and at first it looked like recurring events still didn't show up, but when I went back in the calendar to the days the recurring events started, they appeared everywhere they were supposed to be. So now I'm happy. :) -- google calendar source does not show all events https://bugs.launchpad.net/bugs/183846 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 258864] Re: gvfsd-trash crashed with SIGSEGV in g_idle_funcs()
*** This bug is a duplicate of bug 251910 *** https://bugs.launchpad.net/bugs/251910 Hi. I'm pretty sure this is a duplicate of bug #251910. ** This bug has been marked a duplicate of bug 251910 gvfsd-trash crashed with SIGSEGV in g_idle_funcs() -- gvfsd-trash crashed with SIGSEGV in g_idle_funcs() https://bugs.launchpad.net/bugs/258864 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 252046] Re: gvfs-hal-volume-monitor crashed with SIGSEGV in strlen()
I can only duplicate this bug when I have used the ``powertop'' application to disable HAL's polling of the CD drive and then change a CD. So, steps for me to duplicate: 1) insert CD into CD-ROM drive. 2) run ``sudo powertop'' 3) after a while, at least on my laptop which is an HP Pavilion DV2815NR, powertop tells you to not let HAL poll the CD-ROM drive. 4) then eject the CD-ROM and re-insert it. 5) the open Rhythmbox. That's when this crash happens for me. -- gvfs-hal-volume-monitor crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/252046 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 256676] Re: gvfsd-trash crashed with SIGSEGV in g_idle_funcs()
This same thing happened to me on amd64. I don't know how to get at the data from apport or how to duplicate the bug. -- gvfsd-trash crashed with SIGSEGV in g_idle_funcs() https://bugs.launchpad.net/bugs/256676 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 205690] Re: cannot browse folders over the internet
$ /usr/lib/gvfs/gvfsd -r [...] $ gvfs-mount sftp://email Added new job source 0x642820 (GVfsBackendSftp) Queued new job 0x643830 (GVfsJobMount) send_reply, failed: 0 register_mount_callback, mount_reply: 0x63d0e0, error: (nil) gvfsd-ssh does not seem to be running anywhere. Perhaps this is part of the problem? ssh gets invoked like so: ssh -oForwardX11 no -oForwardAgent no -oClearAllForwardings yes -oProtocol 2 -oNoHostAuthenticationForLocalhost yes -l username -s host sftp Attaching gdb to the running ssh didn't seem to do anything. It tried to load some symbols, remarking that no debugging symbols were found, and then just waited at the (gdb) prompt and didn't do anything else. It was probably waiting for me to do something, except I don't know how to use gdb. -- cannot browse folders over the internet https://bugs.launchpad.net/bugs/205690 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 205690] Re: cannot browse folders over the internet
I am also on x86_64 (I think I noticed somebody earlier mention that). 2.6.24-19-generic #1 SMP Fri Jul 11 21:01:46 UTC 2008 x86_64 GNU/Linux -- cannot browse folders over the internet https://bugs.launchpad.net/bugs/205690 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
