Bug 10407

Summary:	vidalia crashes with segfault when run as user
Product:	Mageia	Reporter:	Pavel Kreuzt <pkreuzt>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	cazzaniga.sandro, fundawang, h.goebel
Version:	3	Keywords:	Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	vidalia-0.3.1-3.mga3.src.rpm	CVE:
Status comment:

Description Pavel Kreuzt 2013-06-03 05:17:02 CEST

Vidalia tries to start tor at first launch, being unconfigured, and after the error pop-ups are closed, it segfaults with:

[43632.218090] vidalia[7860]: segfault at 0 ip 0000003afc0c54fd sp 00007fffd9bc47b0 error 4 in libQtCore.so.4.8.4[3afc000000+2ca000]

The configuration tabs don't work correctly either, configuring a proxy application to start with tor doesn't work anyway: with privoxy as proxy and user config paths, it isn't started. In a single shell it works correctly, so the problem seems to be vidalia.


Version: vidalia-0.3.1-3.mga3


Steps to Reproduce:
1. Start vidalia
2. See dmesg
3.

Reproducible: 

Steps to Reproduce:

Comment 1 Pavel Kreuzt 2013-06-03 05:22:25 CEST

It seems the node list is empty even with tor running and connected. The network map shows no marks. Circuit list seems to work.

Manuel Hiebel 2013-06-08 16:42:30 CEST

Keywords: (none) => Triaged
CC: (none) => cazzaniga.sandro, fundawang

Hartmut Goebel 2013-12-07 16:22:43 CET

CC: (none) => h.goebel
Summary: vidalia doesn't work correctly => vidalia crashes with segfault when run as user

Comment 2 Marja Van Waes 2015-03-31 16:04:12 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD