Opened 6 years ago

Closed 6 years ago

#3957 closed defect (fixed)

Vidalia 0.2.x does not display warning-level status events to the user

Reported by: rransom Owned by: chiiph
Priority: Medium Milestone:
Component: Archived/Vidalia Version:
Severity: Keywords:
Cc: erinn Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I started TBB for Linux on a Debian Live CD, and Tor got stuck in an early bootstrap phase (‘I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.’) for a few minutes. Vidalia did not show me Tor's warning-level events indicating that the computer's clock was skewed until I opened the ‘Message Log’.

I see at least two possible solutions:

  1. Get Vidalia 0.3.x stabilized ASAP.
  2. Make the ‘Message Log’ button in Vidalia 0.2.x start flashing when Tor emits a warning-level event and the ‘Message Log’ window is not open. Make the ‘Message Log’ window's title bar and/or taskbar button start flashing when Tor emits a warning-level event and the ‘Message Log’ window is open, but not focused. Make the ‘Vidalia Control Panel’ window's title bar and/or taskbar button start flashing when Tor emits a warning-level event, the ‘Message Log’ window is closed, and the ‘Vidalia Control Panel’ window is not focused.

Child Tickets

Change History (3)

comment:1 in reply to:  description ; Changed 6 years ago by arma

Replying to rransom:

  1. Get Vidalia 0.3.x stabilized ASAP.

What does Vidalia 0.3.x have that resolves this issue?

comment:2 in reply to:  1 Changed 6 years ago by rransom

Replying to arma:

Replying to rransom:

  1. Get Vidalia 0.3.x stabilized ASAP.

What does Vidalia 0.3.x have that resolves this issue?

Vidalia 0.3.x shows what Vidalia 0.2.x calls the 'Basic' 'Message Log' in its main window by default.

comment:3 Changed 6 years ago by chiiph

Resolution: fixed
Status: newclosed

I implemented the flashing button solution. The idea is to mark 0.3.X stable in the near future, so I think we are good to go with this one.

The fix is in my branch chiiph/bug3957_flash, and it will be out with 0.2.18.

Note: See TracTickets for help on using tickets.