The following error occurs when running my virtual box 5.1 from terminal in Debian 8 and this error when I close virtualbox:
Qt WARNING: QObject::disconnect: No such signal QApplication::screenRemoved(QScreen *)
What should I do?
The "screenRemoved" is a singnal from "QGuiApplication".
And "QApplication" iherits "QGuiApplication".
It is all good. But this method is there from Qt5.4 version.
http://doc.qt.io/qt-5/qguiapplication.html#screenRemoved
Please check your QT version. May be it is bit older.
Related
Iḿ trying to get vulkan to work but I get the following error:
vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477: failed with ERROR_INITIALIZATION_FAILED
Following command dumps:
lspci -nnk | grep -iA2 vga
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0410]
Kernel driver in use: i915
I have added the following to my grub config and initialized it
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 radeon.cik_support=0"
followed by a reboot. The result is the same error :(
what am I doing wrong, can anyone help me?
Before I forget I installed vukan and mesa vulkan drivers and am running Ubuntu 20.04 LTS on a Dell Latitude E4310. Please help, I just want to play some windows (directX11) games with Wine.
This kind of cryptic error message can happen because vulkaninfo doesn't find any supported GPU.
It is likely that your GPU is not supported by Vulkan (too old), and so you won't be able to use DXVK (DirectX to Vulkan). You still may be able to run games without Vulkan by forcing Wine to use WineD3D (DirectX to OpenGl) instead. See Xaero_Vincent's answer in this reddit thread:
In Lutris you can easily disable DXVK as a option and on steam you can
force OpenGL-based WineD3D:
PROTON_USE_WINED3D=1 %command%
You'll notice though that DirectX 10/11 games will generally run
slower under OpenGL and some games will likely have graphics
artifacts, since DXVK is more mature and further developed.
I am getting the following warning when I am launching alloy from my terminal
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by edu.mit.csail.sdg.alloy4whole.SimpleGUI (file:/home/manish/alloy/alloy4.2_2015-02-22.jar) to field java.lang.ClassLoader.usr_paths
WARNING: Please consider reporting this to the maintainers of edu.mit.csail.sdg.alloy4whole.SimpleGUI
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Loaded: libminisat.so
Loaded: libminisatprover.so
Loaded: liblingeling.so
Loaded: libglucose.so
Loaded: libcryptominisat.so
My System Configuration is following:
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Graphics Card: GTX 1050
NVIDIA-SMI 440.64 Driver Version: 440.64 CUDA Version: 10.2
Java Version:
openjdk 11.0.6 2020-01-14
OpenJDK Runtime Environment (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1)
OpenJDK 64-Bit Server VM (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1, mixed mode, sharing)
Also, my alloy is hanging my system, time and again. Thus, I am forced to restart alloy. I don't know if that has to do with this warning.
Alloy GUI visualization issue:
Try, running Java 8. Java is making significant changes that cause these warnings. Very annoying, breaking the long model of backward compatibility.
This is the reason that on MacOS we include the JVM. We could use someone that could do the same for Windows & Linux.
I am using QEMU, buildroot-2018.02.6 and Linux kernel (4.18.14), compiled all these on Ubuntu for aarch64, using gdb-multiarch to debug, but not hitting the break point in kernel code; when I set break point, I get below message:
warning: Breakpoint address adjusted from 0xffff000008f90990 to 0xff000008f90990.
Breakpoint 1 at 0xff000008f90990: file init/main.c, line 532.
Never hit the break point, tried with both hbreak and break. Please help.
Which gdb version are you using? There was a bug in gdb in this area in gdb 8.1: https://sourceware.org/bugzilla/show_bug.cgi?id=23127 -- it has been fixed in newer gdb version I think, and it wasn't present in older ones like gdb 7.
I can't use Quartus 14.1.0 with Linux Debian (wheezy and Jessie) on my 64 bits computer.
If I launch it on console I've got this message :
user#fpgaformation:/opt/altera/14.1/quartus/bin$ ./quartus
Inconsistency detected by ld.so: dl-close.c: 743: _dl_close: Assertion `map->l_init_called' failed!
And the GUI is launched correctly.
But, after some minutes of using it, quartus disappear suddenly without message on terminal but with an altera problem-window.
In this window, we can get the following report :
Problem Details
Error:
*** Fatal Error: Segment Violation at (nil)
Module: quartus
Stack Trace:
0x68cd4: fwrite + 0x34 (c.so.6)
0x1205b: showit + 0x5b (curl.so.4)
0x12388: Curl_debug + 0xe8 (curl.so.4)
0x125ff: Curl_failf + 0xdf (curl.so.4)
0x910f: Curl_resolv_timeout + 0x12f (curl.so.4)
End-trace
Executable: quartus
Comment:
None
System Information
Platform: linux64
OS name: Debian GNU/Linux
OS version: 7
Quartus II Information
Address bits: 64
Version: 14.1.0
Build: 186
Edition: Web Edition
I use also QuartusII 14.0.0 which work well on the same computer.
I know that Altera does'nt support Debian officially (only RedHat) but if somebody has a clue ?
It's a known bug in Altera. They provided me a patch to correct it :
quartusii-14.1-0.19-linux.run
The patch can be found on altera support website :
rd01272015_37
I applied it and quartus work well now. I think they will publish this correction soon.
The following Fortran code is giving me a bus error on my Mac but no errors when I run it on my Linux machine:
PROGRAM TINY
WRITE(UNIT=*, FMT=*) 'Hello, world!'
END
My understanding is that a bus error occurs when the program attempts to access impossible memory but I do not understand where such an attempt has been made in this program. My MacBook has GCC 4.4.0 and my Linux machine has GCC 4.3.2. Any ideas as to why this error occurs?
No ideas at all, just thought I'd let you know that I have no problems compiling and running the program on my Mac Pro. I compiled with G95 (GCC 4.0.4 (g95 0.91!) Dec 11 2008). Like you, I think a bus error is usually an attempt to address memory which doesn't exist.
The program runs fine on my Mac with gfortran 4.4.2. Do other Fortran programs run on your MacBook, or do they all have this problem?