Opened 6 years ago

Closed 15 months ago

#9475 closed defect (wontfix)

Vidalia - Crash with EXIT CODE 134

Reported by: plmlbn Owned by: chiiph
Priority: Medium Milestone:
Component: Archived/Vidalia Version: Vidalia: 0.2.21
Severity: Normal Keywords: archived-closed-2018-07-04
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Hello . . .

Using Vidalia 0.2.21 - Tor (git-17c24b3118224d65 - Kubuntu 12.04.2 (up to date) - KDE 4.10.5 (up to date)

Started tor with ./start-tor-browser - Vidalia appeared - clicked flashing Message Log button (message was Tor running) - chose icon Save All button - crash with message "Vidalia exited abnormally EXIT CODE 134"

Tried this a few times with the Save All button but only ever received the error message - nothing else - I don't really know what the Save All button saves

Tried ./start-tor-browser --debug and the messages were

"Debug enabled.
Starting Vidalia now
Launching Vidalia from: /home/?????
Aborted (core dumped)
Vidalia exited with the following return code: 134"

This parallels another bug report from a few years back but it was subsequently abandoned.

Hope this helps.
Keep up the good work.

Child Tickets

Change History (4)

comment:1 Changed 6 years ago by arma

Perhaps you have the 32-bit TBB when you're on a 64-bit platform, or vice versa?

comment:2 Changed 6 years ago by nickm

Milestone: Tor: 0.2.3.x-final

comment:3 Changed 22 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:4 Changed 15 months ago by teor

Keywords: archived-closed-2018-07-04 added
Resolution: wontfix
Status: newclosed

Close all tickets in archived components

Note: See TracTickets for help on using tickets.