On Ubuntu 22.04 when I click on the firefox's icon, the browser doesn't display.
There is the error shown
(firefox:6175): Gdk-WARNING **: 14:18:57.698: The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc'.
(Details: serial 463 error_code 11 request_code 146 (unknown) minor_code 7)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Related
I installed MPI on macOS Mojave following this tutorial on Stack Overflow. I installed openmpi-2.0.4.tar.gz.
But when I tried to run that hello world program I get error:
[My-MacBook-Pro.local:40731] [[30181,0],0] ORTE_ERROR_LOG: Bad parameter in file orted/pmix/pmix_server.c at line 262
[My-MacBook-Pro.local:40731] [[30181,0],0] ORTE_ERROR_LOG: Bad parameter in file ess_hnp_module.c at line 667
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):
pmix server init failed
--> Returned value Bad parameter (-5) instead of ORTE_SUCCESS
Does anyone know how to fix this?
export TMPDIR=/tmp
(or some other temp directory, where the directory name is not too long)
How can I invoke/simulate process/daemon crash on OSX and as result to receive crash report in
/Library/Logs/DiagnosticRepors
(e.g. opendirectoryd_2013-06-11-125032_macmini61.crash)?
I tried to make force quit for daemons using Activity Monitor but didn't receive any report. I need to crash some system or third party process (NOT developed by myself).
You can force almost any process to crash by sending it a "segmentation violation" signal.
Example: Find process id of "opendirectoryd":
$ ps -ef | grep opendirectoryd
0 15 1 0 9:14am ?? 0:01.11 /usr/libexec/opendirectoryd
^-- process id
Send signal to the process:
$ sudo kill -SEGV 15
This terminates the process and causes a diagnostic report to be written,
as can be verified in "system.log":
Oct 31 09:17:17 hostname com.apple.launchd[1] (com.apple.opendirectoryd[15]): Job appears to have crashed: Segmentation fault: 11
Oct 31 09:17:20 hostname ReportCrash[420]: Saved crash report for opendirectoryd[15] version ??? (???) to /Library/Logs/DiagnosticReports/opendirectoryd_2013-10-31-091720_localhost.crash
But note that deliberately crashing system services might cause severe problems (system instability, data loss, ...), so you should know exactly what you are doing.
Unless you can find a legitimate bug and get it to crash that way, you can't externally crash a daemon in such a fashion that it will result in a diagnostic report. All of the quit-forcing functions are exempt from diagnostic reports as they are external issues.
I'm interested in using the robot framework for test automation.
I created a test script that uses
Robot Framework v2.6.3 (powered by Python v2.6.1)
SeleniumLibrary for Robot v2.8
Selenium Server v2.3
My operating system is Mac OS X 10.6.8 (Snow Leopard).
My test runs fine on Google Chrome using the Chrome driver. Chrome, however, does not support taking page screenshots, which is a feature I can't do without.
So I tried running the test in Firefox v10.0.2, which supports page screenshots, and this does not work.
When I start the test, a Firefox window pops up, displaying a blank page, and nothing happens until I kill the pybot.
I tried both with Robot starting up the Selenium Server and starting the Selenium server myself from the command line, to no avail.
I also tried setting up a clean Firefox profile for the server to use, which didn't help either.
I also tried the more recent Selenium2Library for Robot Framework (v0.5.2), works fine in Chrome, but not in Firefox.
I also tried a much simpler, "hello world" type test, basically just opening up www.google.com - still no luck with Firefox.
In all these cases, the behavior is the same:
Empty Firefox window opens up
Robot framework prints the name of the test case, then stops
Selenium server says "Launching Firefox", then stops
The Selenium server's log file shows an endless list of this:
21:06:33.285 DEBUG [12] org.openqa.selenium.server.FrameGroupCommandQueueSet - waiting for window 'null' local frame 'null' for 1800 more secs
21:06:33.286 DEBUG [12] org.openqa.selenium.server.FrameGroupCommandQueueSet - waiting for condition for 1000 more ms
21:06:34.288 DEBUG [12] org.openqa.selenium.server.FrameGroupCommandQueueSet - got condition? : false
21:06:34.300 DEBUG [12] org.openqa.selenium.server.FrameGroupCommandQueueSet - waiting for window 'null' local frame 'null' for 1799 more secs
21:06:34.300 DEBUG [12] org.openqa.selenium.server.FrameGroupCommandQueueSet - waiting for condition for 1000 more ms
21:06:35.300 DEBUG [12] org.openqa.selenium.server.FrameGroupCommandQueueSet - got condition? : false
21:06:35.300 DEBUG [12] org.openqa.selenium.server.FrameGroupCommandQueueSet - waiting for window 'null' local frame 'null' for 1798 more secs
21:06:35.301 DEBUG [12] org.openqa.selenium.server.FrameGroupCommandQueueSet - waiting for condition for 1000 more ms
21:06:36.301 DEBUG [12] org.openqa.selenium.server.FrameGroupCommandQueueSet - got condition? : false
...and so on.
I also tried running the demo for the SeleniumLibary (http://code.google.com/p/robotframework-seleniumlibrary/wiki/Demo), with the same result.
To make sure the issue is with the Robot framework, I created a Java Selenium test which uses Firefox - this works.
Is there anybody out there experiencing the same issues? Does anyone know how to fix this? Any help is greatly appreciated.
My test script looks like this:
*** Settings ***
Resource resource.txt
*** Test Cases ***
Hello World
Open browser to http://www.google.de/
resources.txt:
*** Settings ***
Library SeleniumLibrary
#Library Selenium2Library
*** Variables ***
${BROWSER} firefox
#${BROWSER} googlechrome
*** Keywords ***
Open browser to ${URL}
Open browser ${URL} ${BROWSER}
Thanks and best regards,
Patrick
I found out that the problem is the version 2.3 of the Selenium server I was using. My tests work with the older version 2.15 of the server.
My project at work debugged under 10.6/Xcode 3.2.5 works fine but at home the same project run under Lion/Xcode 3.2.5 tosses dozens of these
unable to read unknown load command 0x26
messages in the debugger. Any ideas on what I can do to determine what GDB is complaining about? It still "seems" to work, but I have no idea what might be missing or wrong.
Note this is a regular OSX app, not iOS.
The message comes from bfd/mach-o.c:
switch (command->type)
{
case BFD_MACH_O_LC_SEGMENT:
if (bfd_mach_o_scan_read_segment_32 (abfd, command) != 0)
return -1;
break;
.....
default:
fprintf (stderr, "unable to read unknown load command 0x%lx\n",
(unsigned long) command->type);
break;
}
The warning says that BFD cannot recognize the Mach-O section load command it has encountered.
Looking at bfd/mach-o.h where known load commands are described, we find that commands there range from 0x1 to 0x18, yet nothing beyond.
Mac OS X (Lion) defines load constants in /usr/include/mach-o/loader.h (available if you've installed XCode), from 0x1 to 0x27. Therefore, the most logical explanation to seeing the warnings for load commands > 0x18 appears to be the lack of the said codes in BFD's own header.
Also, for follow-ups consider looking at: https://bugs.launchpad.net/tarantool/+bug/1018356
I upgrade to snow leopard and Xcode 3.2 this week, and since that, I'm having problems with CDT. I tried this in CDT 5 (Ganymede) and CDT 6 (Galileo).
If I try to debug the application using launcher "Standard Create Process Launcher", it delays about 10 seconds to actually get in the debugging breakpoint, which is very odd.
If I use as launcher "GDB (DSF) Create Process Launcher" it works at the speed I expect, but the variables tab that shows me what's going on in the current scope show the variable values like that:
"Failed to execute MI command:
-var-update 1 var2
Error message from debugger back end:
Variable object not found
Failed to execute MI command:
-var-update 1 var1
Error message from debugger back end:
Variable object not found"
I don't have any idea how to solve one or the other issue, any of them will let me work up to speed.