Evolution doesn't remember online/offline mode in Feisty

Bug #120728 reported by Steinar Bang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
High
evolution (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Platform: Intel Pentium M (Dell Latitude D610),
                  Ubuntu Feisty Fawn (with all updates)
                  evolution 2.10.1-0ubuntu2
                  evolution-exchange 2.10.1-0ubuntu2
                  network-manager 0.6.4-6ubuntu7
                  network-manager-gnome 0.6.4-6ubuntu7

Bug behaviour: When evolution is switched to offline mode, changing NIC in some way, ie. plugging into a different network, or switching from the wired NIC to the WLAN NIC, will switch Evolution into online mode.

I'm using evolution with the exchange plugin. I'm using network manager to handle the NIC, the WLAN NIC, and VPNC.

The bug has been present in all linux kernel updates I've seen on this system.

This bug looks very similar to Bug #97557 which was marked as a duplicate of bug #82335 , which was reported fixed for Feisty release.

However, the bug is still present on my system, so it hasn't been fixed.

There seems to be no features for reopening bugs, so I'm reporting this as a new bug.

Related branches

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. That doesn't look like a duplicate, you manage your network using network-manager. Not sure that's a bug, using the corresponding plugin you make evolution react to the network changes, if you don't want this behaviour maybe you should just not use the option then?

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Low
Revision history for this message
Steinar Bang (sb-dod) wrote :

I don't understand. What option shouldn't I use?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Looks like there is no option to not use network-manager in fact, so maybe simply not a bug, it detects when you get online again using network-manager, why do you consider it wrong?

Revision history for this message
Steinar Bang (sb-dod) wrote :

Why I consider this behaviour wrong: When I set a program offline, be it Evolution, Gnus, Opera, or any other network application, it means "go offline and stay that way because I know better than you when it's time to switch you online again".

If you look at bug #120730 you will see that Evolution gets terribly confused if it's switched online, before it can connect to the server, and the only way to unconfuse it is to kill it, including all server processes, open a VPNC connection, and start it again.

This gets tedious if I just wish to switch from wired LAN to WLAN in my house, without Evolution going online at all. I want it to run, and run in offline mode, so that I can read cached email messages. I don't want it to go online, be confused, have to be killed, open a VPNC connection, start Evolution, switch it offline, close the VPNC connection, just to be able to read the cached email again.

And in any case, this is new behaviour with the Evolution distributed with Feisty. The Evolution distributed with both Breezy and Dapper, stayed offline until I switched it online. I used network-manager with Dapper, and it didn't affect Evolution at all (nor should it).

Revision history for this message
Sebastien Bacher (seb128) wrote :

Why shouldn't it? The integration with network-manager makes the softwares switch to offline mode when you disconnected and switch online when the network is working again which is really handy and makes sense. If you force manually a mode it should be respected though which is the bug

Changed in evolution:
status: Unconfirmed → Confirmed
Revision history for this message
Han Pilmeyer (pilux) wrote :

I have exactly the same issue. This is actually making evolution less stable than it used to be in Edgy (and Dapper).

As soon as I connect to a network, evolution tries to sync with Exchange. However it will take me some time to set up the VPN. By the time the VPN comes up, Evolution is already trying to connect and it will hang until it is killed. I've tried to wait to see if it recovers, but even after an hour it still hangs.

This is exactly why I used the "--offline" when I start Evolution, but that seems to be ignored when the network comes online.

I think that if "--offline" is specified, it should not try to change things automatically when network connect / disconnect.

Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug is similar to http://bugzilla.gnome.org/show_bug.cgi?id=329712 upstream then

Changed in evolution:
status: Unknown → Confirmed
Changed in evolution:
status: Confirmed → Fix Released
Revision history for this message
Pedro Villavicencio (pedro) wrote :

This has been fixed upstream, thanks.

Changed in evolution:
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package evolution - 2.21.90-0ubuntu1

---------------
evolution (2.21.90-0ubuntu1) hardy; urgency=low

  * New upstream version:
    New in 2.21.90:
    - Improved spam filtering and new preferences UI for
      configuring spam filtering
    Bug Fixes:
    - #324604: Ensure the print of the email
      is transformed from RFC822 or RFC2047
    - #329712: Add a new state to maintian forced offline (LP: #120728)
    - #333695: Print attendee name instead of email address if available
    - #337046: Have a ticking filename for attachment,
      if the mime doesn't carry it
    - #339156: Translation issues
    - #355864: Critical Crash warning while unchecking web calendar
    - #371011: Insert a new paragraph for signature
    - #391408: Fix contact minicards for RTL languages
    - #395939: Memory leak fix
    - #402487: Memory leak fix
    - #405777: Fix a crash when previewing mails
    - #426159: Allow users to snooze for 1+ hour 0 minutes
    - #467581: Don't cancel all threads for a vfolder based search
    - #475781: Fix memory leaks
    - #503327,503678: Return GByteArray instead of gchar*
    - #503551: Fix a crash when trying to delete unselected contact
    - #504062: Fix message list sorting
    - #507564: Fix contact view for RTL languages.
    - #509124: Check result of build_message
    - #509509: Make the status bar height as large as the task bar to eliminate
      "bouncing" when navigating the main menu
    - #509697: Ensure search folders are running before calling
      anything from this
    - #509741: Fix a crash that occurs when prompted to accept a certificate
    - #509879: Drop code to clear memo preview every 60 seconds (LP: #182805)
    - #510409: Free memory before assigning NULL
    - #511094: Set proper foreground color based on focused/non-focused canvas
    - #511105: Free allocated memory properly
    - #511232: Fixed typo Uknown -> Unknown
    - #511488: Ensure vfolder is running
    - #512020: Imposible to remove categories of weather
    Other Contributors:
    - Windows build fixes
    - Message list cairo drawing
    - Added localized screenshots
    - libsoup updates
  * debian/control:
    - updated the requirements

 -- Sebastien Bacher <email address hidden> Wed, 30 Jan 2008 10:53:19 +0100

Changed in evolution:
status: Fix Committed → Fix Released
Revision history for this message
Steinar Bang (sb-dod) wrote : Re: [Bug 120728] Re: Evolution doesn't remember online/offline mode in Feisty

> This bug was fixed in the package evolution - 2.21.90-0ubuntu1
> ---------------
> evolution (2.21.90-0ubuntu1) hardy; urgency=low

Will it be possible to get this fix into the edgy evolution as well?

Since my experience with moving from 6.06 to 7.04 was rather unpleasant,
I'm planning to stay with 7.10 until a new LTS release appears.

Revision history for this message
Sebastien Bacher (seb128) wrote :

it's not likely to be fixed in edgy, there has not been a lot of user request for that, backporting is quite some work and we have limited ressources to work on those

Changed in evolution:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.