Version 52227 runs; new ones don't (running Mavericks GM)

This issue was migrated from bug 9242 in our old bug tracker.

Original bug information:

Reporter: Loe Walter
Status: RESOLVED FIXED
Product: Wireshark
Component: GTK+ UI
OS: OS X 10.9
Platform: x86-64
Version: 1.11.x (Experimental)

Attachments:

: startup error

Loe Walter said:

Build Information:

52227

Present version runs flawlessly.
Installing new version crashes upon start.
Even completely uninstall en new install don't work.
Putting back 52227 trough timemachine works.

Installed xquartz 2.7.4, even newer beta, no solution.
Errors reported on fonts....

added osmacos uigtk versiondev labels

Gerald Combs said:

(In reply to comment #0)  
> Build Information:  
> 52227  
> --  
> Present version runs flawlessly.  
> Installing new version crashes upon start.  
> Even completely uninstall en new install don't work.  
> Putting back 52227 trough timemachine works.  
>  
> Installed xquartz 2.7.4, even newer beta, no solution.  
> Errors reported on fonts....  

Are you seeing the same errors listed at https://bugreports.qt-project.org/browse/QTBUG-31803 ? The 1.11 OS X 64-bit installer ships with Qt 5.1.0, which appears to be incompatible with OX X 10.9.

Gerald Combs said:

Can you try the DMG at

http://www.wireshark.org/~‍gerald/bug#9242/Wireshark%‍201.11.0%‍20r52449%‍20Qt%‍205.1.1.dmg

? It contains a Wireshark.app built against Qt 5.1.1.

Loe Walter said:

I downloaded this version and put it alongside the old version: a) error on load (dumpcap...image not found; sorry cannot copy/paste) b) no capture-device found through prefs

Thanx for r help

Gerald Combs said:

(In reply to comment #‍3)
> I downloaded this version and put it alongside the old version:
> a) error on load (dumpcap...image not found; sorry cannot copy/paste)
> b) no capture-device found through prefs

Did the application itself start up? Did you see any more font errors?

Loe Walter said:

Created attachment 11739 startup error

Loe Walter said:

See screenshot

Guy Harris said:

(In reply to comment #‍5)
> Created attachment 11739 [details]
> startup error

Points for an Edward Hopper background image. :-)

Guy Harris said:

(In reply to comment #‍5)
> Created attachment 11739 [details]
> startup error

We probably need to word-wrap messages; the pathname of the library isn't being displayed.

There's probably a Crash Reporter message in Console for dumpcap failing to start; see whether there's a dumpcap crash report in Console under User Diagnostic Reports or System Diagnostic Reports. It might have the full path of the library.

However, /tmp being in the path is Not A Good Sign; could that be the temporary location of the library during the build process, and could the script to build the app not be fixing the path (which should @‍rpath@‍ified by the script)?

Gerald Combs said:

(In reply to comment #8)  
> (In reply to comment #5)  
> > Created attachment 11739 [details]  
> > startup error  
>  
> We probably need to word-wrap messages; the pathname of the library isn't  
> being displayed.  

Done in r52473.

> However, /tmp being in the path is Not A Good Sign; could that be the  
> temporary location of the library during the build process, and could the  
> script to build the app not be fixing the path (which should @rpath@ified by  
> the script)?  

I ran "make osx-app", copied Wireshark.app to a directory, and created a .dmg by hand using hdiutil. It might be an artifact of not running "make osx-package".

Gerald Combs said:

(In reply to comment #‍8)
> However, /tmp being in the path is Not A Good Sign; could that be the
> temporary location of the library during the build process, and could the
> script to build the app not be fixing the path (which should @‍rpath@‍ified by
> the script)?

Wireshark and third-party libraries are installed in different locations on my system and osx-dmg.sh wasn't handling this properly. I checked in a fix in r52479. A resultant app bundle can be found at

http://www.wireshark.org/~‍gerald/bug#9242/Wireshark%‍201.11.0%‍20r52474%‍20Qt%‍205.1.1.dmg

Gerald Combs said:

(In reply to comment #‍0)
> Installed xquartz 2.7.4, even newer beta, no solution.
> Errors reported on fonts....

It should be noted that newer 64-bit OS X packages use Qt and don't need X11 any more. The new UI isn't anywhere close to being complete but you should at least be able to capture, view, and filter packets.

Loe Walter said:

Sorry, I have no access to this file!

Gr. Loe

Gerald Combs said:

(In reply to comment #12)  
> Sorry, I have no access to this file!  
>  
> Gr. Loe  

Oops. It should work now.

Guy Harris said:

(In reply to comment #‍11)
> It should be noted that newer 64-bit OS X packages use Qt and don't need X11
> any more. The new UI isn't anywhere close to being complete but you should
> at least be able to capture, view, and filter packets.

It works on my Mavericks GM virtual machine.

Loe Walter said:

Thanks for this!

Runs like h...!

Evan Huus said:

*** Bug #9318 (closed) has been marked as a duplicate of this bug. ***

Guy Harris said:

*** Bug #9389 (closed) has been marked as a duplicate of this bug. ***

Guy Harris said:

*** Bug #9404 (closed) has been marked as a duplicate of this bug. ***