[vidalia-users] vidalia-users Digest, Vol 17, Issue 4

Wed Feb 25 20:51:45 CET 2009

OK, I don't know why I didn't check this before, but the problem with float not working is that cmath is not present when compiling with MIPSPro. I've attached a patch that adds an ifdef and fixes the problem.

I still don't know why the main window never shows up, though. I know that it's not my Qt implementation (4.3.0) being broken - other Qt apps work fine. I've forced the tray-detection to always return true, but that doesn't work either. I'll need to get Visual Studio going on a Windows box to investigate further, though, since it's hard to do serious debugging with no tools other than nano. and I'm not really familiar with Qt. Hopefully I will be able to reproduce the bug and fix it quickly with a real IDE.

Does anyone know if there is a prebaked Vidalia VS project that I could grab, instead of having to compile Qt, etc, etc? I can take care of the DLL dependencies with the binary Win32 package, I would think.

     -Matt

-----Original Message-----
From: vidalia-users-bounces at lists.vidalia-project.net on behalf of vidalia-users-request at lists.vidalia-project.net
Sent: Fri 2/20/2009 11:00 AM
To: vidalia-users at lists.vidalia-project.net
Subject: vidalia-users Digest, Vol 17, Issue 4

Send vidalia-users mailing list submissions to
	vidalia-users at lists.vidalia-project.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.vidalia-project.net/cgi-bin/mailman/listinfo/vidalia-users

or, via email, send a message with subject or body 'help' to
	vidalia-users-request at lists.vidalia-project.net

You can reach the person managing the list at
	vidalia-users-owner at lists.vidalia-project.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of vidalia-users digest..."

Today's Topics:

   1. Re: vidalia-users Digest, Vol 17, Issue 3 (Matthew Saunier)
   2. Re: vidalia-users Digest, Vol 17, Issue 3 (Matt Edman)
   3. Re: Vidalia and IRIX (Matt Edman)

----------------------------------------------------------------------

Message: 1
Date: Thu, 19 Feb 2009 13:57:14 +0000
From: Matthew Saunier <msaunier at kaitain.net>
Subject: Re: [vidalia-users] vidalia-users Digest, Vol 17, Issue 3
To: vidalia-users at lists.vidalia-project.net
Message-ID: <6EB5CEF6-4029-46D7-8C49-1564BE75FA49 at kaitain.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

If there is, it's undocumented. It also wouldn't really help, as the  
real problem is that Vidalia assumes that a notification area is  
present without checking.

Are there any maintainers on this list? I'm serious about wanting to  
join the project and eliminate these irritating problems. It would  
even help non-SGI people in the end. I'm forging ahead with my  
changes, and would like to see the rest of the userbase benefit, not  
just me.

In a related note, it seems that Vidalia treats SIGHUP the same as  
SIGKILL, which means that SIGHUP is available for repurposing. Most  
every daemon uses it as an "attention" signal (usually results in the  
configuration file being re-read), and causing Vidalia to display  
it's GUI seems consistent with this.

	-Matt

On Feb 19, 2009, at 11:00 AM, vidalia-users-request at lists.vidalia- 
project.net wrote:

> Send vidalia-users mailing list submissions to
> 	vidalia-users at lists.vidalia-project.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.vidalia-project.net/cgi-bin/mailman/listinfo/vidalia- 
> users
>
> or, via email, send a message with subject or body 'help' to
> 	vidalia-users-request at lists.vidalia-project.net
>
> You can reach the person managing the list at
> 	vidalia-users-owner at lists.vidalia-project.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of vidalia-users digest..."
>
>
> Today's Topics:
>
>    1. Re: Vidalia and IRIX (Jon Arden)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 19 Feb 2009 01:23:04 +0800
> From: "Jon Arden" <itsmejonny at email2me.net>
> Subject: Re: [vidalia-users] Vidalia and IRIX
> To: "Vidalia support and discussion"
> 	<vidalia-users at lists.vidalia-project.net>
> Message-ID: <20090218172304.08162B113B at ws4-4.us4.outblaze.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
>> ----- Original Message -----
>> From: "Adna rim" <adnarim at lavabit.com>
>> To: vidalia-users at lists.vidalia-project.net
>> Subject: Re: [vidalia-users] Vidalia and IRIX
>> Date: Tue, 17 Feb 2009 15:36:15 +0100
>>
>> in windows version you can use the dos prompt for tor and use  
>> provoxy too without using vidalia...often seems faster/smoother
>> Hi,
>> there is already a config-option to show the gui on start but it
>> doesn't work if no systray is there. I also had the problem with
>> e17 which also doesn't have a systray/notfication-area and filed a
>> bugreport for this issue a while ago:
>> http://trac.vidalia-project.net/ticket/455 .
>>
>> greets
>>
>> _______________________________________________
>> vidalia-users mailing list
>> vidalia-users at lists.vidalia-project.net
>> http://lists.vidalia-project.net/cgi-bin/mailman/listinfo/vidalia- 
>> users
>
>>
>
>
> -- 
> Email2me....  The email service that cares.  It is FREE.
> http://www.email2me.com
>
>
> ------------------------------
>
> _______________________________________________
> vidalia-users mailing list
> vidalia-users at lists.vidalia-project.net
> http://lists.vidalia-project.net/cgi-bin/mailman/listinfo/vidalia- 
> users
>
> End of vidalia-users Digest, Vol 17, Issue 3
> ********************************************

------------------------------

Message: 2
Date: Thu, 19 Feb 2009 14:25:51 -0500
From: Matt Edman <edmanm at vidalia-project.net>
Subject: Re: [vidalia-users] vidalia-users Digest, Vol 17, Issue 3
To: Vidalia support and discussion
	<vidalia-users at lists.vidalia-project.net>
Message-ID: <20090219192551.GC23840 at pasiphae.cs.rpi.edu>
Content-Type: text/plain; charset=us-ascii

On Thu, Feb 19, 2009 at 01:57:14PM +0000, Matthew Saunier wrote:
> If there is, it's undocumented. It also wouldn't really help, as the  
> real problem is that Vidalia assumes that a notification area is  
> present without checking.

It does check, but seems to be getting a bogus response. (I mentioned this
in a previous email, so I'm just summarizing here.)

> Are there any maintainers on this list? I'm serious about wanting to  
> join the project and eliminate these irritating problems. It would  
> even help non-SGI people in the end. I'm forging ahead with my  
> changes, and would like to see the rest of the userbase benefit, not  
> just me.

The best place to go is #vidalia on irc.oftc.net.

> In a related note, it seems that Vidalia treats SIGHUP the same as  
> SIGKILL, which means that SIGHUP is available for repurposing. Most  
> every daemon uses it as an "attention" signal (usually results in the  
> configuration file being re-read), and causing Vidalia to display  
> it's GUI seems consistent with this.

Yeah, Vidalia currently doesn't do anything to handle signals, including
SIGHUP. Rather than specifically handling SIGHUP to mean "show the main
window", I think the better solution would be to figure out why the main
window isn't appearing for you in the first place.

--Matt

------------------------------

Message: 3
Date: Thu, 19 Feb 2009 14:11:08 -0500
From: Matt Edman <edmanm at vidalia-project.net>
Subject: Re: [vidalia-users] Vidalia and IRIX
To: Vidalia support and discussion
	<vidalia-users at lists.vidalia-project.net>
Message-ID: <20090219191108.GB23840 at pasiphae.cs.rpi.edu>
Content-Type: text/plain; charset=us-ascii

On Tue, Feb 17, 2009 at 02:05:52PM +0000, Matthew Saunier wrote:
> 	Hello, all. I've been working on porting Vidalia to IRIX, and have a 
> patch that allows Vidalia to compile with MIPSPro.
>
> 	It turns out to be pretty trivial, there's one spot where a variable 
> is redeclared in a foreach, which was no good - the fix there was to  
> change the variable name in the foreach. The other issue is that  
> SGI's math library handles floor differently, so I had to change  
> floor to trunc in the 4 places where it's used.

Thanks for the patch. I took a quick look through it and noticed a couple
things. Your changes to servicesettings.cpp were actually made in Vidalia
trunk in r3235 back in October 2008. Unforuntaely, it never got backported
to the 0.1.x branch. I've done that just now. Thanks for pointing that out.

Second, your changes to tormapwidget.cpp don't actually apply to trunk
since the map-related files moved around a bit with the recent integration
of KDE's Marble widget. It's usually best to make sure a patch applies to
SVN trunk, rather than a previously released tarball.

Also, the switch from floor() to trunc() changes the results slightly. The
differences may not be enough to affect relay placemarks locations much,
but I'd like to avoid changing the behavior if possible. Can
you paste the build errors that you get when trying to build without
patching tormapwidget.cpp? Does IRIX prefer a different function that does
the same thing as floor()? 

> 	The larger issue is that while Vidalia compiles and runs, our window 
> manager, 4Dwm, is pretty close to being plain X11, and as such has no  
> concept of a notification area. I've poked around some, and it looks  
> like Vidalia wants to minimize to the tray / dock upon startup. The  
> result is that while any initial dialogs (could not connect to Tor,  
> etc) pop up and Vidalia starts Tor properly, there's no way to get to  
> the GUI. Our Qt implementation simply gets rid of the window, with no  
> way to get it back.

This is odd. If you look in mainwindow.cpp, Vidalia asks Qt if the current
window manager supports a system notification area. If it doesn't, Vidalia
will remove the "Hide" button and "Show this window on startup" checkbox,
and always show the main window. Perhaps Qt's
QSystemTrayIcon::isSystemTrayAvailable() is lying on your window manager?

Does your ~/.vidalia/vidalia.conf have a line in it that starts with
"ShowMainWindowAtStart"?

> 	I think that the hack for this is to hard-set the "Show this window  
> on start" pref in the code that reads the preferences, but the proper  
> solution would be either to check the host type for IRIX at startup  
> and have an if-then at every point in the code that minimizes to the  
> notification area , or to add the option when Vidalia is invoked from  
> the commandline while it is already running to connect to the  
> existing instance. In other words, change the window from "There is  
> another instance of Vidalia running, are you sure you want to start  
> another one?" to  "There is another instance of Vidalia running, do  
> you want to start another one or do you want to connect to the  
> running instance?", which would send a signal to the running Vidalia  
> to pop up the GUI. (Sidebar: Is SIGHUP used in Vidalia? That'd seem  
> to be a logical choice...)
> 
> 	Anyway, I don't know if this is the right place to discuss code  
> changes - if it isn't, let me know. I'd like to join as a  
> contributor, but all I'd want to do is get it running properly on  
> IRIX and test new releases. 

Great! I'm always happy to have more contributors. The best place for
development discussion is usually in our IRC channel (#vidalia on
irc.oftc.net). It's more active than this mailing list, and most of the
development discussion happens there.

--Matt

------------------------------

_______________________________________________
vidalia-users mailing list
vidalia-users at lists.vidalia-project.net
http://lists.vidalia-project.net/cgi-bin/mailman/listinfo/vidalia-users

End of vidalia-users Digest, Vol 17, Issue 4
********************************************

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 9469 bytes
Desc: not available
Url : http://lists.vidalia-project.net/pipermail/vidalia-users/attachments/20090225/0be6e491/attachment.bin 