Firefox and Wine silently fail to open - where do find an error report?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Firefox and Wine silently fail to open - where do find an error report?
Firefox 3.1 beta 3 won't load. When I open the application, the little bouncy icon bounces, and the task manager shows "Firefox Web Browser", but this only stays this way for about 15 seconds then just goes away. No error or anything.
I've had this identical problem when I try to open certain programs with Wine too. Is there some place I can find a detailed error report on these failures?
It's a good solution, but, unfortunately, doesn't always work. Some newer software is written without regard for that convention of *nix software, sort of like how some software these days doesn't include a manpage or a --help option. How are we supposed to figure out how to run that crap?
Sometimes it may be that the devs have simply decided to not clutter STDOUT with errors and send them all to STDERR. a simple ./program 2> /home/user/logfile might give you what you're looking for if you run into that.
Ah, true, but I know the difference between the two - I didn't say anything about using redirection to check output. I really do see a trend of software ignoring these important parts of running on a *nix system. Just me being a young old fart, I suppose.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.