Bug 767702

Summary: For Thunderbird, the offline mode doesn't mean offline
Product: Red Hat Enterprise Linux 6 Reporter: Matěj Cepl <mcepl>
Component: thunderbirdAssignee: Red Hat Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED UPSTREAM QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2CC: stransky, tpelka, vseerror
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-26 15:02:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screencast of the issue none

Description Matěj Cepl 2011-12-14 16:59:25 UTC
Created attachment 546815 [details]
screencast of the issue

Offline mode of Thunderbird (one of the biggest selling points of standalone mail apps ...) seems to be completely broken currently (thunderbird-8.0-1.el6.x86_64).

a) Clicking on the offline icon in the bottom left corner makes thunderbird to sync, but doesn't switch to offline state,
b) even when I switch offline via menu, Thunderbird doesn't recognized it and tried to access many servers which were not available obviously (maybe, because it hasn't managed to sync completely yet, but anyway ... when I am offline, I should be offline, right?).

Comment 3 RHEL Program Management 2012-05-03 05:34:46 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 4 Martin Stransky 2012-07-26 15:02:04 UTC
It's because the offline state is managed by NetworkManager, the offline button is confusing. I already reported this bug upstream.