You are not logged in.
Hi folks,
I am trying to use the Xojo Rapid Application Development Environment under archlinux with the KDE desktop. While at first it seems tu run, there is a point where my application just hangs in KDE but on the exactly same machine only using Gnome as desktop it runs flawlessly. Remember - packages installed are the same!
The xojo IDE is free to use and download, only compiling apps for standalone use is for $, so this can be reproduced really easy. Download the xojo IDE and on the first page choose the Example For 'Printing and Reporting' -> 'Reporting' -> GasReport -> GasReport.xojo_binary_project. The simply click on the 'Run' button in the main program. Under Gnome this gives you a graphic report of gas prices - but under KDE, it simply hangs forever.
I really don't know where to start here. Anybody a clue what could be different here between gnome and KDE? Again, same machine, same packages installed...
Greetings
Harvey
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
tap gdb and/or strace into it and see where it stalls (and whether that's aconstant position)?
Offline
tap gdb and/or strace into it and see where it stalls (and whether that's aconstant position)?
gdb used like described here does not deliver any useful outpute. The trace file stay empty.
The strace used like here gives an output. Will try to generate this in Gnome as well and see if I can figure out where it differs. I have done this for KDE but my knowledge of debug traces is rather small
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
Ensure the xojo executable is actually a binary and not some bash/python/… script.
Offline
AFAICT it is:
harvey@gruenix ~/Documents/scripts $ file /opt/xojo/Xojo
/opt/xojo/Xojo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, not stripped
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
Completely empty? And you did run "thread apply all bt full" in gdb?
Offline
Here is what I did:
harvey@gruenix ~/Documents/scripts $ gdb /opt/xojo/Xojo
GNU gdb (GDB) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /opt/xojo/Xojo...(no debugging symbols found)...done.
(gdb) run
Starting program: /opt/xojo/Xojo
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe9ab2700 (LWP 1751)]
[New Thread 0x7fffe92b1700 (LWP 1752)]
libocci.so.10.1: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden[XOJO] Unable to load plugin OraclePlugin.xojo_plugin
[New Thread 0x7fffc953d700 (LWP 1780)]
Then I open the faulty Example and move on to the part in question - the Xojo IDE hangs. gdb's output till then
Could not load libwebkitgtk-3
(Xojo:1747): Gtk-WARNING **: 18:37:19.255: gtk_menu_attach_to_widget(): menu already attached to GtkImageMenuItem
[New Thread 0x7fffc8d3c700 (LWP 1793)]
[Thread 0x7fffc8d3c700 (LWP 1793) exited]
[New Thread 0x7fffc8d3c700 (LWP 1839)]
[Thread 0x7fffc8d3c700 (LWP 1839) exited]
[Thread 0x7fffc953d700 (LWP 1780) exited]
[Thread 0x7fffe92b1700 (LWP 1752) exited]
[Thread 0x7ffff7f8d9c0 (LWP 1747) exited]
[Inferior 1 (process 1747) exited normally]
(gdb) set logging file trace.log
(gdb) set logging on
Copying output to trace.log.
(gdb) thread apply all bt full
(gdb) set logging off
Done logging to trace.log.
(gdb) quit
If I don't misunderstand something this is exactly the way the wiki describes. And it results in an empty trace.log
harvey@gruenix ~/Documents/scripts $ ls -la trace.log
-rw-r--r-- 1 harvey harvey 0 27. Jun 18:40 trace.log
no debugging symbols found... could it be this is why?
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
[Inferior 1 (process 1747) exited normally]
The process doesn't hang, it terminated ("normally")
I assume the window closes badly and the compositor misses that? Does the window disappear when you suspend the compositor (SHIFT+Alt+F12)?
Offline
[Inferior 1 (process 1747) exited normally]
The process doesn't hang, it terminated ("normally")
I assume the window closes badly and the compositor misses that? Does the window disappear when you suspend the compositor (SHIFT+Alt+F12)?
There should be a window displayed, but it isn't. The IDE just hangs around there until I press the close button.
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
I meant the IDE window - it should be gone after the process terminated. If you still see one, it might be a zombie (this can happen w/ compositors or wayland - the connection between "window" and "process" is even more loose than it's w/ X11 anyway)
When the IDE "hangs", is the PID still listed by "ps"?
Did you try w/o compositing (the thing that makes shadows and transparency etc)?
The remaining question of course would be why the process terminates when you run stuff.
If that's not the case: can you interact w/ the IDE window while the gas price window is displayed on gnome?
Offline
Seth,
first, thank you for your patience!
I meant the IDE window - it should be gone after the process terminated. If you still see one, it might be a zombie (this can happen w/ compositors or wayland - the connection between "window" and "process" is even more loose than it's w/ X11 anyway)
When running the GasReport the IDE goes into 'debug mode'. The GasReport should be displayed in a different window, and in the IDE you have a button to stop the running program. This button does nothing in my case the IDE just seems not to react to it while the GasReport is running. But I can interact with all controls from the IDE. I just click the close button and the IDE terminates normal.
Looking into this with SystemMonitor does show the IDE starts another process 'DebugMyApplication' with no window title and if I close the IDE this process stays in memory (zombie?) while the IDE process itself disappears.
When the IDE "hangs", is the PID still listed by "ps"?
See above. The 'DebugMyApplication' process seems to remain while the IDE disappears.
Did you try w/o compositing (the thing that makes shadows and transparency etc)?
Disabling compositing completely and even falling back to Xrender does not change the behaviour.
If that's not the case: can you interact w/ the IDE window while the gas price window is displayed on gnome?
See above: I can interact with all controls from the IDE
Now here comes something funny:
If I start the IDE from the konsole with
LD_DEBUG=files /opt/xojo/Xojo > xojo.log 2>&1
then the GasReport Window appears - but with no data in it. SystemMonitor now shows a process 'DebugMyApplication' with the window title 'GasReport'. It can be closed normally and disappears from system monitor then. Hmmm....
Greetings
Harvey
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
The interesting process will be "DebugMyApplication" - does it wait for an ioctl response (marked with "D" in ps)?
Can you gdb into that PID and see what it's doing?
The DE relation seems weird in this case - does it work in eg. an openbox session?
Does xojo have some look and feel integration?
env | grep -ie '(kde|plasma)'
Unset every variable that would let it know that this is KDE.
Offline
Seth,
The interesting process will be "DebugMyApplication" - does it wait for an ioctl response (marked with "D" in ps)?
harvey@gruenix ~/Documents/scripts $ ps aux | grep DebugMy
202:harvey 5861 0.2 0.9 404604 35452 pts/1 Sl+ 11:40 0:00 /tmp/DebugMyApplication/DebugMyApplication
Can you gdb into that PID and see what it's doing?
Attaching to process 5861
ptrace: The operation ist not allowed
So - seems not possible.
The DE relation seems weird in this case - does it work in eg. an openbox session?
Nope - same behaviour.
Does xojo have some look and feel integration?
harvey@gruenix ~/Documents/scripts $ env | grep -ie plasma
16:DESKTOP_SESSION=/usr/share/xsessions/plasma
harvey@gruenix ~/Documents/scripts $ env | grep -ie kde
2:KDE_FULL_SESSION=true
23:XDG_SESSION_DESKTOP=KDE
34:XDG_CURRENT_DESKTOP=KDE
48:KDE_SESSION_UID=1000
49:KDE_SESSION_VERSION=5
harvey@gruenix ~/Documents/scripts $ env | grep -ie xojo
... no output ...
So no xojo mentioned. Was this what I should look for here?
Unset every variable that would let it know that this is KDE.
Tried this:
harvey@gruenix ~/Documents/scripts $ unset {KDE_FULL_SESSION,XDG_SESSION_DESKTOP,XDG_CURRENT_DESKTOP,KDE_SESSION_UID,KDE_SESSION_VERSION,DESKTOP_SESSION}
same behaviour
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
Just a hunch, but are you utilizing the global menu implementation of plasma or similar? That can lead to issues with proprietary tools.
Edit: Oh just saw you mention you could reproduce this in openbox, then this shouldn't be relevant, but also makes this very strange.
Last edited by V1del (2018-06-29 10:41:02)
Offline
Attaching to process 5861
ptrace: The operation ist not allowedSo - seems not possible.
"Not allowed" - where there is a bash, there is a way.
echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
(iow: write "0" into ptrace_scope, but you need root permissions)
Is gnome a wayland session? Does it work w/ gnome on xorg?
Offline
Seth,
thank you for this lesson in debugging
echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
(iow: write "0" into ptrace_scope, but you need root permissions)
Attaching to process 1563
[New LWP 1568]
[New LWP 1569]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x00007f4f2c42c0f9 in syscall () from /usr/lib/libc.so.6
(gdb)
So I tried to get a trace.log - and here is what i get:
Thread 3 (Thread 0x7f4f1bfff700 (LWP 1569)):
#0 0x00007f4f2c426ea9 in poll () at /usr/lib/libc.so.6
#1 0x00007f4f2a0ac523 in () at /usr/lib/libglib-2.0.so.0
#2 0x00007f4f2a0ac8e2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3 0x00007f4f2b23f348 in () at /usr/lib/libgio-2.0.so.0
#4 0x00007f4f2a0d4a2a in () at /usr/lib/libglib-2.0.so.0
#5 0x00007f4f29167075 in start_thread () at /usr/lib/libpthread.so.0
#6 0x00007f4f2c43153f in clone () at /usr/lib/libc.so.6
Thread 2 (Thread 0x7f4f20832700 (LWP 1568)):
#0 0x00007f4f2c426ea9 in poll () at /usr/lib/libc.so.6
#1 0x00007f4f2a0ac523 in () at /usr/lib/libglib-2.0.so.0
#2 0x00007f4f2a0ac63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#3 0x00007f4f2a0ac692 in () at /usr/lib/libglib-2.0.so.0
#4 0x00007f4f2a0d4a2a in () at /usr/lib/libglib-2.0.so.0
#5 0x00007f4f29167075 in start_thread () at /usr/lib/libpthread.so.0
#6 0x00007f4f2c43153f in clone () at /usr/lib/libc.so.6
Thread 1 (Thread 0x7f4f2ed219c0 (LWP 1563)):
#0 0x00007f4f2c42c0f9 in syscall () at /usr/lib/libc.so.6
#1 0x00007f4f2a0f3411 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2 0x00007f4f2a0d4bc0 in g_once_init_enter () at /usr/lib/libglib-2.0.so.0
#3 0x00007f4f1a888279 in gdk_screen_get_type () at /usr/lib/libgdk-x11-2.0.so
#4 0x00007f4f1a8b5489 in gdk_screen_get_height_mm () at /usr/lib/libgdk-x11-2.0.so
#5 0x0000000000513c7d in Reports.RBReport.PixelsPerInch%i8%o<Reports.RBReport>b ()
#6 0x00000000005112b7 in Reports.RBReport.FontScale%f8%o<Reports.RBReport> ()
#7 0x0000000000540166 in Reports.Controls.RBReportLabel.Render%%o<Reports.Controls.RBReportLabel>o<Reports.RptRect>o<Reports.ReportAPI>o<Reports.ReportGroupAPI> ()
#8 0x0000000000521c81 in Reports.RBReportSection.Render%%o<Reports.RBReportSection>o<Reports.RptRect>o<Reports.ReportAPI>o<Reports.ReportGroupAPI> ()
#9 0x00000000005143d0 in Reports.RBReport.PlacePageHeader%%o<Reports.RBReport> ()
#10 0x0000000000516769 in Reports.RBReport.StartPage%%o<Reports.RBReport> ()
#11 0x00000000005149ef in Reports.RBReport.Run%b%o<Reports.RBReport>o<Reports.Dataset>o<PrinterSetup> ()
#12 0x0000000000598197 in ReportWindow.ReportWindow.Event_Open%%o<ReportWindow.ReportWindow> () at ReportWindow:64
#13 0x00007f4f2ca1f6a1 in FireWindowOpenEvents ()
at /tmp/DebugMyApplication/DebugMyApplication Libs/XojoGUIFramework64.so
#14 0x0000000000483ef8 in Window.Constructor%%o<Window> ()
#15 0x000000000059db44 in ReportWindow.ReportWindow%o<ReportWindow.ReportWindow>% () at ReportWindow:108
#16 0x00000000005c8078 in _MakeDefaultView () at #main:97
#17 0x00000000005c82bd in _LateStartup () at #main:122
#18 0x00007f4f2ca0cd73 in RunFrameworkInitialization ()
at /tmp/DebugMyApplication/DebugMyApplication Libs/XojoGUIFramework64.so
#19 0x000000000055c6e0 in REALbasic._RunFrameworkInitialization%%p ()
#20 0x00000000005c8613 in _Main () at #main:129
#21 0x00000000005c7743 in main ()
Don't know if this helps...
Is gnome a wayland session? Does it work w/ gnome on xorg?
No wayland on this machine.
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
Unless you're using the nvidia blob, gnome will default to a wayland session.
The code hangs when the program tries to calculate the screen DPI - this is very related to the display server, so please be absolutely sure reg. wayland ./. X11
Otherwise check and compare "xrandr -q", "xdpyinfo" and the xorg logs.
Is this by any chance an optimus system?
Offline
Seth,
Unless you're using the nvidia blob, gnome will default to a wayland session.
I do not have nvidia on this laptop, it is an intel machine with only intel graphics. And I explicitely choose 'Gnome on Xorg' in sddm menu when testing with gnome.
The code hangs when the program tries to calculate the screen DPI - this is very related to the display server, so please be absolutely sure reg. wayland ./. X11
Until now I am absoluteley sure not to run wayland. I never installed it.
Otherwise check and compare "xrandr -q", "xdpyinfo" and the xorg logs.
harvey@gruenix ~/Documents/scripts $ xrandr -q
Screen 0: minimum 8 x 8, current 3520 x 1080, maximum 32767 x 32767
LVDS1 connected primary 1600x900+1920+0 (normal left inverted right x axis y axis) 350mm x 190mm
1600x900 59.98*+ 59.82 50.00
1400x900 59.88
1368x768 60.00 59.88 59.85
1280x800 59.81 59.91
1280x720 59.86 60.00 59.74
1024x768 60.00
1024x576 60.00 59.90 59.82
960x540 60.00 59.63 59.82
800x600 60.32 56.25
864x486 60.00 59.92 59.57
800x450 60.00
640x480 59.94
720x405 59.51 60.00 58.99
640x360 59.84 59.32 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
1920x1080 60.00*+ 50.00 59.94
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1280x800 59.91
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
832x624 74.55
800x600 75.00 60.32
720x576 50.00
720x576i 50.00
720x480 60.00 59.94
720x480i 60.00 59.94
640x480 75.00 60.00 59.94
720x400 70.08
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
and xdpyinfo:
harvey@gruenix ~/Documents/scripts $ xdpyinfo
name of display: :0
version number: 11.0
vendor string: The X.Org Foundation
vendor release number: 12000000
X.Org version: 1.20.0
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding: 32, LSBFirst, 32
image byte order: LSBFirst
number of supported pixmap formats: 7
supported pixmap formats:
depth 1, bits_per_pixel 1, scanline_pad 32
depth 4, bits_per_pixel 8, scanline_pad 32
depth 8, bits_per_pixel 8, scanline_pad 32
depth 15, bits_per_pixel 16, scanline_pad 32
depth 16, bits_per_pixel 16, scanline_pad 32
depth 24, bits_per_pixel 32, scanline_pad 32
depth 32, bits_per_pixel 32, scanline_pad 32
keycode range: minimum 8, maximum 255
focus: window 0x3800007, revert to PointerRoot
number of extensions: 28
BIG-REQUESTS
Composite
DAMAGE
DOUBLE-BUFFER
DPMS
DRI2
DRI3
GLX
Generic Event Extension
MIT-SCREEN-SAVER
MIT-SHM
Present
RANDR
RECORD
RENDER
SECURITY
SHAPE
SYNC
X-Resource
XC-MISC
XFIXES
XFree86-DGA
XFree86-VidModeExtension
XINERAMA
XInputExtension
XKEYBOARD
XTEST
XVideo
default screen number: 0
number of screens: 1
screen #0:
dimensions: 3520x1080 pixels (928x285 millimeters)
resolution: 96x96 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
root window id: 0xf9
depth of root window: 24 planes
number of colormaps: minimum 1, maximum 1
default colormap: 0x22
default number of colormap cells: 256
preallocated pixels: black 0, white 16777215
options: backing-store WHEN MAPPED, save-unders NO
largest cursor: 256x256
current input event mask: 0xfa8031
KeyPressMask EnterWindowMask LeaveWindowMask
ExposureMask StructureNotifyMask SubstructureNotifyMask
SubstructureRedirectMask FocusChangeMask PropertyChangeMask
ColormapChangeMask
number of visuals: 58
default visual id: 0x20
visual:
visual id: 0x20
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x21
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xc1
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xc2
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xc3
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xc4
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xc5
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xc6
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xc7
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xc8
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xc9
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xca
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xcb
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xcc
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xcd
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xce
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xcf
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xd0
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xd1
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xd2
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xd3
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xd4
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xd5
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xd6
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xd7
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xd8
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xd9
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xda
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xdb
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xdc
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xdd
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xde
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xdf
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xe0
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xe1
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xe2
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xe3
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xe4
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xe5
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xe6
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xe7
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xe8
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xe9
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xea
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xeb
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xec
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xed
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xee
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0x72
class: TrueColor
depth: 32 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xef
class: TrueColor
depth: 32 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xf0
class: TrueColor
depth: 32 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xf1
class: TrueColor
depth: 32 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xf2
class: TrueColor
depth: 32 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xf3
class: TrueColor
depth: 32 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xf4
class: TrueColor
depth: 32 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xf5
class: TrueColor
depth: 32 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xf6
class: TrueColor
depth: 32 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
visual:
visual id: 0xf7
class: TrueColor
depth: 32 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
I use a 2-Monitor setup and from what I see there is a chance that this is the culprit. I don't have the time now but tomorrow I will disconnect the external monitor and create a new user profile (just to make sure neither gnome nor kde remember the 2nd monitor). Lets see what happens then.
Is this by any chance an optimus system?
No. See above - pure intel.
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
I built a completely new archlinux system on real hardware just to be sure. I installed packages part by part just to see what happens. And the conclusion is: it does not work
At a certain point I got an error message telling me that the Xojo IDE tries to load libgdk-x11-2.0.so.0 (part of gtk2), I guess for calculating the (real) display and this fails, resulting in the DebugMyApplication hanging. Seems the Xojo folks have forgotten some gtk2-links in the IDE code... I can't debug this any further, I think somebody has to look into the source code of the IDE...
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
Until now I am absoluteley sure not to run wayland. I never installed it.
Yes, you did.
wayland was a dependency for mesa for years, also gtk3 has it as a dependency since a few gnome versions.
I think somebody has to look into the source code of the IDE...
As this is proprietary code, that someone has to be from Xojo, Inc.
Maybe you could post on their forum ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Until now I am absoluteley sure not to run wayland. I never installed it.
Yes, you did.
wayland was a dependency for mesa for years, also gtk3 has it as a dependency since a few gnome versions.
Ok. How do I make sure I don't use it by 'accident'? Will it be used on new installs by default? Don't think so. Still have explicitely to choose in the login manager. Or does sddm use wayland by default?
As this is proprietary code, that someone has to be from Xojo, Inc.
Maybe you could post on their forum ?
I did in parallel here. But I feel for the more technical point the archlinux forum is always the better choice.
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline