[Bug 53684] Re: Recurrence rule dialogue is ambiguous
** Summary changed: - recurring events not displayed correctly + Recurrence rule dialogue is ambiguous -- Recurrence rule dialogue is ambiguous https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40125] Re: Doesn't bring the network back online when resuming from suspend / hibernate
Yes, I can confirm this. Resuming on a dell inspiron 2200, nm-applet claims that there are no network devices present but networking works perfectly fine. -- Doesn't bring the network back online when resuming from suspend / hibernate https://launchpad.net/bugs/40125 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40125] Re: Doesn't bring the network back online when resuming from suspend / hibernate
After a bit of googling I discovered that I need to comment out all the entries in /etc/network/interfaces except the loopback interface for n-m to work correctly. Have done so and n-m now finds interfaces on resume from suspend. Would be good if the n-m install took care of this step or at least posted a debconf warning. -- Doesn't bring the network back online when resuming from suspend / hibernate https://launchpad.net/bugs/40125 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46883] Re: No Networking after Suspend
I also had this problem. The solution was to comment out all lines in /etc/network/interfaces except the loopback interface. n-m cannot control already configured interfaces. If that does not cure the problem then you should take a look at #40125 and probably mark this bug a duplicate. -- No Networking after Suspend https://launchpad.net/bugs/46883 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40125] Re: Doesn't bring the network back online when resuming from suspend / hibernate
Correct. #46883 actually describes the problem Ealden and I were having. Have posted the solution there. -- Doesn't bring the network back online when resuming from suspend / hibernate https://launchpad.net/bugs/40125 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50296] Re: Applet says "Networking disabled" when network is up
Could you post the contents of /etc/network/interfaces. Just out of curiosity, why would you use n-m on a desktop in preference to the deafult networking configuration? -- Applet says "Networking disabled" when network is up https://launchpad.net/bugs/50296 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50296] Re: Applet says "Networking disabled" when network is up
n-m won't work with a static config; you need to comment out probably everything but your loopback interface and restart networking for n-m to work. See: https://help.ubuntu.com/community/WifiDocs/NetworkManager I think you can safely close this bug if it works, you don't appear to be suffering any of the suspend/hibernate problems laptop owners are reporting. -- Applet says "Networking disabled" when network is up https://launchpad.net/bugs/50296 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40125] Re: Doesn't bring the network back online when resuming from suspend / hibernate
Sigh, despite earlier success I faced the same problem this morning resuming laptop that had been suspended overnight. This bug seems to depend on how long the laptop is suspended, n-m can cope with being supended for short periods of time but not several hours - bizarre. Will now install the scripts John Cooper posted and see how it copes tonight. -- Doesn't bring the network back online when resuming from suspend / hibernate https://launchpad.net/bugs/40125 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40125] Re: Doesn't bring the network back online when resuming from suspend / hibernate
Was delighted to resume my laptop this morning to find n-m behaving correctly. Then I suspended the thing for 30 mins while I walked my son to school. Came back and resumed to find ..."no network inerfaces found" Aaargh!! This thing has a mind of it's own. Will leave John's scripts in place as they don't seem to be doing any harm, but n-m is still not working correctly with inspiron 2200. -- Doesn't bring the network back online when resuming from suspend / hibernate https://launchpad.net/bugs/40125 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53684] Re: recurring events not displayed correctly
-- recurring events not displayed correctly https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53684] recurring events not displayed correctly
Public bug reported: Binary package hint: evolution Dapper with Evo 2.6.1-0ubuntu7 I created a recurring event starting on Mon 24/07/06 using this rule: appointment recurs every 1 week on mon, tue, wed, thur, fri for 4 occurrences. This should give me a total of 20 events. Only the first 4 are displayed by Evo. Evo knows there are 20 events - if I publish the calendar to Icalx.com all 20 are visible, it just cannot display them correctly itself. Will attach screenshots: RecurrenceRules.png - view of the recurrence dialog EvoJuly.png showing 4 events, should be 5 visible EvoAugust.png showing 0 events, should be 15 visible IcalxJuly.png showing 5 events IcalxAugust.png showing 15 events ** Affects: evolution (Ubuntu) Importance: Untriaged Status: Unconfirmed -- recurring events not displayed correctly https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53684] Re: recurring events not displayed correctly
view of recurrence dialog -- recurring events not displayed correctly https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53684] Re: recurring events not displayed correctly
-- recurring events not displayed correctly https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53684] Re: recurring events not displayed correctly
-- recurring events not displayed correctly https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53684] Re: recurring events not displayed correctly
-- recurring events not displayed correctly https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53684] Re: recurring events not displayed correctly
I also noticed the same problem with Dates and reported a bug in the Opened Hand bugzilla: http://bugzilla.openedhand.com/show_bug.cgi?id=128 Following on from that bug report, the Dates developer has closed the bug as invalid because he believes that Evo is correctly applying the recurrence rule. In other words, the recurrence rule: appointment recurs every 1 week on mon, tue, wed, thur, fri for 4 occurrences means: appointment recurs every 1 week on mon, tue, wed, thur, fri for 4 days and not: appointment recurs every 1 week on mon, tue, wed, thur, fri for 4 weeks When I created the rule, I assumed that it meant the latter and this seems to be what Evo uses to publish the calendar. If this is not the case, then either Evo is generating an incorrect ical file and this bug needs to be retitled, or icalx.com is misinterpreting the ical file and the bug needs to be closed. Here is the VEVENT from the ics file Evo published on icalx.com: BEGIN:VEVENT UID:[EMAIL PROTECTED] DTSTAMP:20060721T115018Z DTSTART;TZID=/softwarestudio.org/Olson_20011030_5/Europe/London: 20060724T10 DTEND;TZID=/softwarestudio.org/Olson_20011030_5/Europe/London: 20060724T17 TRANSP:OPAQUE SEQUENCE:4 SUMMARY:Build Day CLASS:PRIVATE CREATED:20060721T115144 LAST-MODIFIED:20060721T115451 RRULE;X-EVOLUTION-ENDDATE=20060727T09Z:FREQ=WEEKLY;COUNT=4;INTERVAL=1; BYDAY=MO,TU,WE,TH,FR END:VEVENT In any event there is certainly room for improvement in the recurrence rule dialogue, it's very ambiguous. Will check the GNOME bugzilla and create a bug report if needed. -- recurring events not displayed correctly https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53684] Re: recurring events not displayed correctly
Created bug report upstream about recurrence rule dialogue http://bugzilla.gnome.org/show_bug.cgi?id=348400 Also found this bug which may describe the same problem: http://bugzilla.gnome.org/show_bug.cgi?id=274514 -- recurring events not displayed correctly https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53684] Re: recurring events not displayed correctly
A helpful explanation of how EDS stores calendars on the Opened Hand bugzilla prompted me to save the calendar as an ics file in Evo and open it with Mozilla Sunbird on another box. I got the same result as with Evolution, so it would appear that the problem lies with icalx.com not Evo. Can't see how to close this bug. Can a bug's owner close a bug? Does not seem obvious how and searching help.launchpad.net reveals nothing. Perhaps it should be retitled and linked to the wishlist bug I filed on GNOME bugzilla anyway. Leave it up to you. -- recurring events not displayed correctly https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53684] Re: recurring events not displayed correctly
Missed that you had already assigned this bug to the upstream bug I filed, will edit description to match upstream. -- recurring events not displayed correctly https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53684] Re: recurring events not displayed correctly
I left the GNOME bug open because it is a valid feature enhancement request for an improved recurrence rule dialogue. Has been confirmed already. It is not really an upstream version of this bug report, more of an idea that came out of tracking down what the actual problem was. I was slightly surprised that you assigned this bug to it. Perhaps at this stage, for the sake of clarity I should mark this bug REJECTED and create a new bug that describes only the feature enhancement contained in the GNOME bug? Or will simply editing the description of this bug to match the GNOME bug suffice? -- recurring events not displayed correctly https://launchpad.net/bugs/53684 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60389] Fails to start
Public bug reported: Running edgy on a dell inspiron 2200 I upgraded this morning - the only packages upgraded were the latest upstart ones - and after a reboot my laptop fails to make it to a login screen. In recovery mode interspersed among all the kernel messages, I can see that the following scripts get started: local-premount init-premount local-top local-bottom init-bottom Last kernel message I get is the lp driver being loaded, then nothing - the machine hangs. ** Affects: upstart (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Fails to start https://launchpad.net/bugs/60389 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60389] Re: Fails to start
In recovery mode the last message I got was: *setting up the console font and keymap ... then I got a command prompt. It did not seem like the normal terminal I get in recovery mode though - usually I can logout in recovery mode and it starts gdm. Have rebooted into X now, do I need to do anything else? -- Fails to start https://launchpad.net/bugs/60389 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60389] Re: Fails to start
Yes, boots fine into X - I am writing this in epiphany right now. Only the recovery mode seems different. -- Fails to start https://launchpad.net/bugs/60389 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60389] Re: Fails to start
No. I would not have a bug to report if it had ;-) What were you expecting me to see after making those changes? Bit of history on the machine in case it helps - it was only upgraded from dapper yesterday, took a while to sort out all the dep's in aptitude as I had forgotten I had removed ubuntu-desktop but once I reinstalled that everything sorted itself out. As of about midday yesterday it was an edgy box, it ran fine all day I rebooted a couple of times without problem. Only other noticeable problem I experienced was that it would not resume correctly from suspend-to-ram and I had to power it down and reboot. STR worked fine with dapper so long as I had a cdrom in the drive to overcome some weird bug in hal. Basically I had no real problems until this morning when I upgraded upstart. Here is the excerpt from aptitudes log file: Aptitude 0.4.1: log report Thu, Sep 14 2006 08:33:03 +0100 IMPORTANT: this log only lists intended actions; actions which fail due to dpkg problems may not be completed. Will install 5 packages, and remove 0 packages. === [HOLD] inkscape [UPGRADE] startup-tasks 0.2.5-1 -> 0.2.6-1 [UPGRADE] system-services 0.2.5-1 -> 0.2.6-1 [UPGRADE] upstart 0.2.5-1 -> 0.2.6-1 [UPGRADE] upstart-compat-sysv 0.2.5-1 -> 0.2.6-1 [UPGRADE] upstart-logd 0.2.5-1 -> 0.2.6-1 === Log complete. -- Fails to start https://launchpad.net/bugs/60389 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60389] Re: Fails to start
I did not notice anything particular after changing them, other than getting further than loading the lp module in recovery mode. No I am not using cryptsetup. I commented out the "console owner" line from both files and rebooted, X works fine. Bizarre. I will attach the syslog of the first boot after upgrading upstart. It's full of X related errors, seems strange that upgrading upstart would trigger this. Perhaps it's just co-incidental and something else weird happened? Nothing else but upstart was upgraded though. ** Attachment added: "syslog of the first boot after upgrading upstart" http://librarian.launchpad.net/4272373/syslog_post_upstart_upgrade -- Fails to start https://launchpad.net/bugs/60389 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57041] Re: no buffer space available
Following up from #60389 ** Attachment added: "/var/log/dmesg" http://librarian.launchpad.net/4272435/dmesg -- no buffer space available https://launchpad.net/bugs/57041 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57041] Re: no buffer space available
** Attachment added: "output of dmidecode" http://librarian.launchpad.net/4272436/dmidecode -- no buffer space available https://launchpad.net/bugs/57041 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57041] Re: no buffer space available
** Attachment added: "output of lsusb" http://librarian.launchpad.net/4272438/lsusb -- no buffer space available https://launchpad.net/bugs/57041 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57041] Re: no buffer space available
** Attachment added: "output of lspci" http://librarian.launchpad.net/4272437/lspci -- no buffer space available https://launchpad.net/bugs/57041 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57041] Re: no buffer space available
** Attachment added: "output of lspci" http://librarian.launchpad.net/4272439/lspci -- no buffer space available https://launchpad.net/bugs/57041 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57041] Re: no buffer space available
** Attachment added: "/var/log/udev" http://librarian.launchpad.net/4272440/udev -- no buffer space available https://launchpad.net/bugs/57041 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71047] eds crashes when auto-completing email address in a new email
Public bug reported: This problem only seems to happen with a freshly started machine when I try and compose a mail immediately after starting evolution. As soon as I start typing the recipients address the message composition window freezes as evo tryies to autocomplete the address. Here is the backtrace: Memory status: size: 1699840 vsize: 0 resident: 1699840 share: 0 rss: 487424 rss_rlim: 0 CPU usage: start_time: 1163064683 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-data-server-1.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xe410 in __kernel_vsyscall () #0 0xe410 in __kernel_vsyscall () #1 0xb7e5374e in wait4 () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7e53727 in wait3 () from /lib/tls/i686/cmov/libc.so.6 #3 0x0804ed62 in ?? () #4 0xbfa21370 in ?? () #5 0x in ?? () This has happened a few times now under identical circumstances, but this mornings crash was the first time that bug-buddy has noticed the crash and given me a backtrace, prior to that I have just killed evo and restarted it. ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: Unconfirmed -- eds crashes when auto-completing email address in a new email https://launchpad.net/bugs/71047 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71047] Re: eds crashes when auto-completing email address in a new email
I have installed the eds -dbg package and attached gdb to eds as per the instructions in https://wiki.ubuntu.com/Backtrace I can recreate the problem with the message composition window freezing when autocompleting email addresses, gdb's output attached. ** Attachment added: "gdb output" http://librarian.launchpad.net/5019780/gdb-eds-1.8.txt -- eds crashes when auto-completing email address in a new email https://launchpad.net/bugs/71047 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113959] help file is unreadable
Public bug reported: Binary package hint: notecase Notecase stores its help file as a notecase (.ncd) file at /usr/share/doc/notecase/help.ncd. The package in feisty installs this file gzipped which makes it unreadable to Notecase. Manually gunzip this file after installation as a workaround. ** Affects: notecase (Ubuntu) Importance: Undecided Status: Unconfirmed -- help file is unreadable https://bugs.launchpad.net/bugs/113959 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117896] Re: Loses e-mails when moving accross IMAP folders
I experienced the bug with moving mails ending up in the trash folder with my webmail.us account for the first time this morning. Previously I had only experienced that bug with my blueyonder account and was suspicious this was caused by a blueyonder server problem; I can rule this out now. log file attached. I have been running Evo in debugging mode for several weeks now and have not experienced a repeat of the issue with copies of sent mails going missing. Very frustrating, particularly as another member of my family has experienced the exact same problem with Evolution and webmail.us on 3 occasions. Will send log file to upstream bug report as well. Is someone going to link this bug report with either/both of the upstream bug reports I referred to in Comment #14? ** Attachment added: "log - move 2 messages to A4A folder but end up in trash" http://launchpadlibrarian.net/10052213/evo.log.20071017 -- Loses e-mails when moving accross IMAP folders https://bugs.launchpad.net/bugs/117896 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32164] Re: spca5xx/khubd uses 100% cpu and unable to reboot/halt
Suspend & Resume with ekiga running and webcam attached triggers this for me. ekiga 2.03 kernel 2.6.20-16-generic Logitech Communicate STX with gspca module Machine is compaq evo D510 desktop I am now running with my keyboard and mouse connected via ps/2 (with adapters) and I can kill ekiga and then khubd recovers. With USB input it was impossible to do anything other than a hard reboot with the power switch. ** Attachment added: "excerpt from /var/log/messages" http://launchpadlibrarian.net/9793350/messages -- spca5xx/khubd uses 100% cpu and unable to reboot/halt https://bugs.launchpad.net/bugs/32164 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84991] Re: Resume from suspend fails with FGLRX
I have the same issue, though in my case resume fails to work with either the open source ati driver or the binary fglrx driver so maybe this is a different problem. Hardware is a Compaq Evo 510 desktop and a Radeon 9550 [RV350 AS] AGP card. Additionally I cannot switch to Console mode and have to reboot. I have tried the two variations on /etc/default/acpi-support described above without success. Resume works if I use the vesa driver. It also worked fine previously when I was using the onboard intel 845 graphics. Both with an unmodified /etc/default/acpi-support. -- Resume from suspend fails with FGLRX https://bugs.launchpad.net/bugs/84991 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84991] Re: Resume from suspend fails with FGLRX
The problem with the Xorg ati driver appears to be a separate issue. If I disable dri resume works fine. Will add comment to #23545. Disabling dri has no effect on resuming from standby with the fglrx driver. Still stuck with that one. -- Resume from suspend fails with FGLRX https://bugs.launchpad.net/bugs/84991 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 23545] Re: No more X on resume after hibernate
I have the same issue with feisty/Xorg 7.2. Hardware is a Compaq Evo 510 desktop and a Radeon 9550 [RV350 AS] AGP card. When resuming from suspend I get a blank (but backlit) screen. I cannot switch to Console mode and have to reboot. I have tried modifying /etc/default/acpi- support but it made no difference. Resume works fine if I disable DRI. -- No more X on resume after hibernate https://bugs.launchpad.net/bugs/23545 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117896] Re: Loses e-mails when moving accross IMAP folders
Some further info: I sent myself several emails from another account for testing purposes and then proceeded to drag them back and forth between various folders until I triggered the bug again. I observed that a move operation in Evo consists of a copy followed by a delete. Every time a mail is successfully copied, the original is moved to the trash folder. I had never noticed this behaviour with Evo before, I am sure in the past that the originals must have been immediately expunged. I don't recall my trash folder filling up with copies of messages I had moved. Is this in itself a separate bug? On the occasion that the move operation failed Evo still moved the originals to the trash folder. Evo is failing to do the copy part of the operation but still continuing to move the originals to the trash folder! I guess the "bug" of not immediately expunging the originals should be viewed as a feature under such circumstances :-) The mail account in question is with blueyonder.co.uk (now virginmedia). They use Microsoft SMTPSVC. I have another IMAP account with webmail.us and have never experienced this bug with them. They run Dovecot. Is this an IMAP server workaround that has recently broken perhaps? Might be interesting to know which mail server the original bug reporter is connecting to. Couple of other things, just to clear up any confusion: I found the missing "Trash/Sent Items" folder listed in the log file by configuring Evo to show all folders, not just subscribed folders. In actual fact this is a default folder created by blueyonder, I guess at some point in the past I must have mistakenly tried to delete it; it has now been undeleted and resubscribed. I can still reproduce this bug though, so I don't think this was in any way related to the problem. In comment #10 I described the local trash folder as having no useful purpose. It is of course used by Evo, its just not the real trash folder on the imap server that the webmail interface or other mail clients like thunderbird use. -- Loses e-mails when moving accross IMAP folders https://bugs.launchpad.net/bugs/117896 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117896] Re: Loses e-mails when moving accross IMAP folders
Sorry, I should have re-read the entire bug report before posting. Having done so now it appears that you are experiencing 2 problems, possibly the same bug, possibly not. 1. You are losing mail when you move it between folders (either manually or by filter). This might be: http://bugzilla.gnome.org/show_bug.cgi?id=446276 2. You are sending mail but not getting a copy of your sent mail. This might be: http://bugzilla.gnome.org/show_bug.cgi?id=436802 I too am seeing both problems, but I am not convinced they are the same bug, for the simple reason that I only experience the first one with my blueyonder account and the second one only with my webmail.us account. Also the second one is really hard to reproduce whereas the first one usually only takes a few tries. Jerome, does any of the missing mail show up in your trash folder? Did you ever get a debug log with CAMEL_DEBUG=ALL for either of the IMAP servers you have used? Losing data is a serious issue. Could someone please bump up the importance of this bug? -- Loses e-mails when moving accross IMAP folders https://bugs.launchpad.net/bugs/117896 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117896] Re: Loses e-mails when moving accross IMAP folders
I can reproduce this bug. In my case the mails are not lost, they end up in the local trash folder. By that I mean the second trash folder in an IMAP account folder list (the one that serves no useful purpose normally, has an icon). Not the one actually on the IMAP server, nor the one listed under "On this Computer". Same setup: feisty, evo 2.10.1, imap server. Debug log attached. I came across bug report this while searching for bug reports about a slightly different problem, namely sent emails not making it to the sent items folder on an IMAP server. There is an upstream bug report that suggests they may be related: http://bugzilla.gnome.org/show_bug.cgi?id=436802 ** Attachment added: "evolution debug log file" http://launchpadlibrarian.net/8880158/evo_debug.log -- Loses e-mails when moving accross IMAP folders https://bugs.launchpad.net/bugs/117896 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117896] Re: Loses e-mails when moving accross IMAP folders
Whilst reviewing this log this morning I noticed something very strange at line 212: received: * LIST (\Marked \HasNoChildren) "/" "Trash/Sent Items" I don't have a "Sent Items" folder in any of my trash folders. The message I moved to reproduce the bug is listed at line 618. -- Loses e-mails when moving accross IMAP folders https://bugs.launchpad.net/bugs/117896 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48679] Re: Birthdays before 1969 shows as birthdays in the future 2000+
Still present in Gutsy/ Evo 2.12. I can also confirm the additional problem noted above by Barry Michels, it seems to be more than a simple locale issue - there is something seriously flawed with Evo's date calculations. For those of us with a locale setting that won't permit entering four-digit years in Evo, you can verify this by installing Openhand's Contacts which also uses EDS for storage: #apt-get install contacts Contacts uses four-digit years to edit birthdates stored in EDS. If you edit a contact record with Contacts to correct a birthdate of say 2066 to 1966 and then go to that date in 2007 in Evo's Birthdays & Anniversarys Calendar you would expect to see an entry with (41) after it to indicate that date is that contact's 41st birthday. According to Evo however that person is 38 years old in 2007. Interesting maths! I verified that Contacts stores the date correctly in EDS by installing GBirthday which also uses EDS. The dates of upcoming birthdays (and ages) that have been corrected with Contacts are displayed correctly by GBirthday. Will copy this to upstream bug. -- Birthdays before 1969 shows as birthdays in the future 2000+ https://bugs.launchpad.net/bugs/48679 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48679] Re: Birthdays before 1969 shows as birthdays in the future 2000+
After a bit of playing around with some test contacts it's obvious what Evolution's Birthdays & Anniversarys Calendar is doing with birthdates - anyone born before 1970 has the same age regardless of year they were born and is assumed to have been born in 1970. Attached screenshot shows 3 test contacts born 11th Nov in 1937, 1947 and 1957. Birthdates stored in EDS by Evo were corrected from 2037, 2047 and 2057 using Open Hand's Contacts. Evolution Calendar erroneously shows all three having the same age. GBirthday shows their correct age as calculated from birthdates stored in EDS. Is this a symptom of the same bug or should it be reported separately? Will copy upstream. ** Attachment added: "Screenshot.png" http://launchpadlibrarian.net/10333616/Screenshot.png -- Birthdays before 1969 shows as birthdays in the future 2000+ https://bugs.launchpad.net/bugs/48679 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48679] Re: Birthdays before 1969 shows as birthdays in the future 2000+
Upstream have reported that the birthday calendar age issue is known about and is being treated as a separate bug: http://bugzilla.gnome.org/show_bug.cgi?id=300584 It's marked as fixed in 2.11.x but the bug still exists in 2.12.1 Perhaps Ubuntu bug #145657 should be re-opened and an upstream bug watch added? -- Birthdays before 1969 shows as birthdays in the future 2000+ https://bugs.launchpad.net/bugs/48679 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145657] Re: Age of contacts with birthdate <1970 always looks like they were born in 1970
*** This bug is a duplicate of bug 48679 *** https://bugs.launchpad.net/bugs/48679 This is tracked upstream as a separate problem: http://bugzilla.gnome.org/show_bug.cgi?id=300584 -- Age of contacts with birthdate <1970 always looks like they were born in 1970 https://bugs.launchpad.net/bugs/145657 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109590] Re: Evolution fails to add certain birthdays to calendar
The issue with Evolution Calendar showing ages incorrectly is known upstream: http://bugzilla.gnome.org/show_bug.cgi?id=300584 If that is the only remaining problem then maybe this should be closed or marked as a dupe of bug #145657? -- Evolution fails to add certain birthdays to calendar https://bugs.launchpad.net/bugs/109590 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90147] Re: cant handle special chars in folder name
Fixed upstream in 0.9.7, Debian package installs fine in Feisty. -- cant handle special chars in folder name https://bugs.launchpad.net/bugs/90147 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115953] Re: sound-juicer crashes when "editing profiles"
This bug affects both soundjuicer and rhythmbox in feisty. As a workaround running gnome-audio-profiles-properties from a terminal works fine. -- sound-juicer crashes when "editing profiles" https://bugs.launchpad.net/bugs/115953 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71047] Re: eds crashes when auto-completing email address in a new email (with LDAP)
Daniel, I am running dapper,evo 2.8.1 and eds 1.8.1. Will have a look at the DebuggingProgramCrash page and see what I can do. It is definitely an ldap problem, I have simply disabled autocompletion from ldap servers in evo's preferences to make evo usable again. Jan, I had a look at the upstream bug report, yes looks v similar, in particular the person who added comment #16 seems to be triggering the bug the same way as me [without moving messages between folders]. http://bugzilla.gnome.org/show_bug.cgi?id=274240#c16 -- eds crashes when auto-completing email address in a new email (with LDAP) https://launchpad.net/bugs/71047 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75461] fails to start after upgrade to feisty
Public bug reported: Binary package hint: deskbar-applet Upgraded to feisty yesterday and the deskbar applet is failing to start. Here's the output from bug-buddy: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/deskbar/ModuleLoader.py", line 157, in load_all self.load (f) File "/usr/lib/python2.4/site-packages/deskbar/ModuleLoader.py", line 139, in load mod_instance = getattr (mod, handler) () File "/home/simon/.gnome2/deskbar-applet/handlers/deskbar-tracker.py", line 91, in __init__ self.bus = dbus.SessionBus() File "/var/lib/python-support/python2.4/dbus/_dbus.py", line 266, in __new__ return Bus.__new__(cls, Bus.TYPE_SESSION, use_default_mainloop, private) File "/var/lib/python-support/python2.4/dbus/_dbus.py", line 99, in __new__ bus._connection = dbus_bindings.bus_get(bus_type, private) File "dbus_bindings.pyx", line 1692, in dbus_bindings.bus_get DBusException: Failed to connect to socket /tmp/dbus-rC0viEsTEf: Connection refused ** Affects: deskbar-applet (Ubuntu) Importance: Undecided Status: Unconfirmed -- fails to start after upgrade to feisty https://launchpad.net/bugs/75461 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75461] Re: fails to start after upgrade to feisty
Having posted a bug report, deskbar has of course worked perfectly since the last time I logged in. Have not done anything in the way of upgrades or messing around with config files. The only thing I can think of was that I ran tracker-search-tool for the first time since upgrading to feisty, maybe that initialised something the deskbar tracker extension needed? Just a shot in the dark. Will close this in a week if there are no recurrences. -- fails to start after upgrade to feisty https://launchpad.net/bugs/75461 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75461] Re: fails to start after upgrade to feisty
Spoke too soon, can reproduce this reliably now, pattern is that deskbar works fine on first login from a freshly booted machine but if I logout and log back in it fails to start. I am getting error messages twice about this now, the first one with additional info about .xsession errors. Attached. ** Attachment added: "bug buddy output" http://librarian.launchpad.net/5375713/DeskbarTraceback -- fails to start after upgrade to feisty https://launchpad.net/bugs/75461 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77784] X fails to start with 2.6.20
Public bug reported: Binary package hint: linux-source-2.6.20 Running feisty on a dell inspiron 2200 with intel 915 graphics. I can only get into X with a 2.6.19 kernel. If I try booting with either of the 2.6.20 kernels [ -2, -3] my laptop locks up when gdm trys to start. Booting with quiet and splash disabled I see the following: *Starting GNOME Display Manager 52.644000 BUG: Soft lockup detected on CPU#0 ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- X fails to start with 2.6.20 https://launchpad.net/bugs/77784 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77784] Re: X fails to start with 2.6.20
** Attachment added: "syslog excerpt" http://librarian.launchpad.net/5581327/syslog -- X fails to start with 2.6.20 https://launchpad.net/bugs/77784 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77784] Re: X fails to start with 2.6.20
I can start in single user mode without problem. -- X fails to start with 2.6.20 https://launchpad.net/bugs/77784 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77784] Re: X fails to start with 2.6.20
This bug appears to be fixed in both -4 and -5. Thanks! -- X fails to start with 2.6.20 https://launchpad.net/bugs/77784 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75461] Re: fails to start after upgrade to feisty
Seems to be working OK apart from this one issue, I have the same number of dbus processes running in both instances. Are there any specific tests I can run? I see the upstream bug report has been rejected because of the same issue. Maybe reassign to dbus? -- fails to start after upgrade to feisty https://launchpad.net/bugs/75461 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
