Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog
On Thu, 2018-09-06 at 10:10 -0500, Chris wrote: > On Thu, 2018-09-06 at 16:00 +0200, Michel Dänzer wrote: > > On 2018-09-06 1:53 p.m., Chris wrote: > > > On Thu, 2018-09-06 at 12:21 +0200, Michel Dänzer wrote: > > > > On 2018-09-05 9:16 p.m., Adam Jackson wrote: > > > > > On Sat, 2018-09-01 at 10:24 -0500, Chris wrote: > > > > > > > > > > > When starting Evolution this is output to syslog and > > > > > > periodically > > > > > > after it's running: > > > > > > > > > > > > https://pastebin.com/zndBukUG > > > > > > > > > > Evolution, or something it provokes, is asking the server for > > > > > the > > > > > list > > > > > of available video modes. It's doing so with > > > > > XRRGetScreenResources(), > > > > > apparently, which prompts the X server to go re-check every > > > > > available > > > > > output to see if anything has changed. This is silly, it > > > > > should > > > > > be > > > > > using XRRGetScreenResourcesCurrent() and relying on hotplug > > > > > events > > > > > to > > > > > trigger re-polling. Now, maybe the X server shouldn't print > > > > > the > > > > > modes > > > > > in the log when that happens, [...] > > > > > > > > FWIW, it probably shouldn't indeed, at least not at the default > > > > log > > > > verbosity. > > > > > > > > > > AFAICT my rsyslog.conf it's the default. I don't know if > > > uncommenting > > > these lines would help or not: > > > > > > ### Debugging ### > > > # $DebugFile /var/log/rsyslog-debug > > > # $DebugLevel 2 > > > > > > # syslog.* /var/log/syslog.debug;RSYSLOG_DebugFormat > > > # $DebugFile /var/log/syslog.debug > > > # $DebugLevel 2 > > > > Yeah, sorry, different meaning of "should" — the code definitely > > always > > has printed these by default, it just arguably shouldn't. > > > > Anyway, Adam is right that the client shouldn't use this > > functionality > > in the first place. > > > > Besides the bug report submitted at Ubuntu Launchpad that I mentioned > in my original post I've also submitted them as noted below. > > https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1788739 > > https://bugs.freedesktop.org/show_bug.cgi?id=107841 > > https://gitlab.gnome.org/GNOME/gdm/issues/418 > > The reasoning for this is I'm just not exactly who's purview this > would > come under. > I thought I'd add that this also happens when starting and stopping XFE xfe: Installed: 1.42-1 Candidate: 1.42-1 -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 19:44:42 up 13:06, 1 user, load average: 0.58, 0.49, 0.54 Description:Ubuntu 18.04.1 LTS, kernel 4.15.0-34-generic signature.asc Description: This is a digitally signed message part ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Xorg.O.log (WW) message
Hello: I have this message in my Xorg.O.log: [code] [34.298] (WW) Unresolved symbol: fbGetGCPrivateKey [/code] I'm running Devuan ASCII with two NVidia caards for three monitors and using proprietary drivers. I have searched all over the web and have found a great deal on posts/instances in which this same error is cited (as an entry in a Xorg.0.log file) but have not been able to find out why it is there and if has some significance. After all, it is labelled as a warning ie: (WW). It is (apparently) innocuous as my NVidia cards are working properly (save for an artifacts issue reserved for another post). I'd appreciate if someone could give me some insight on this. Thanks in advance. ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
[Bug 107992] xf86-video-amdgpu-18.1.0: video freezes in firefox
https://bugs.freedesktop.org/show_bug.cgi?id=107992 --- Comment #11 from Michel Dänzer --- I suspect this is the same issue as bug 108008 => https://gitlab.freedesktop.org/xorg/lib/libx11/issues/79 . -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org https://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: DRM leases + X = SW only OpenGL acceleration on child X server
Michel Dänzer writes: > Looks like drmAuthMagic returns an error for the leased FD in the Xorg > process. > > Keith, was this working for you? At one point, I'm nearly certain it was, but I haven't messed with this in a while. -- -keith signature.asc Description: PGP signature ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: font files not read/processed when they are symlinks?
Alan Coopersmith writes: > Correct - since the X server is often run with raised privileges, it > was fixed last year to use O_NOFOLLOW to not follow symbolic links > when handling font files: > > https://gitlab.freedesktop.org/xorg/lib/libxfont/commit/7b377456f95d2ec3ead40 > f4fb74ea620191f88c8 thanks a lot indeed! That clarifies everything: actually I wasn't 100% sure that the reason was this; now I can "close" the issue: no stow with X font files. ciao -g ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: font files not read/processed when they are symlinks?
On 09/24/18 04:51 AM, baldu...@units.it wrote: Might it be that font files are NOT read/loaded by the X server when they are symbolic links? Correct - since the X server is often run with raised privileges, it was fixed last year to use O_NOFOLLOW to not follow symbolic links when handling font files: https://gitlab.freedesktop.org/xorg/lib/libxfont/commit/7b377456f95d2ec3ead40f4fb74ea620191f88c8 -- -Alan Coopersmith- alan.coopersm...@oracle.com Oracle Solaris Engineering - https://blogs.oracle.com/alanc ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
font files not read/processed when they are symlinks?
hello
apologies if I'm missing something blatant here...
Might it be that font files are NOT read/loaded by the X server when
they are symbolic links?
I have recently migrated from a fontpath layout where all files were
"physically" (ie "real" regular files) present under the font
directories
/usr/Xorg/share/fonts/X11/{100dpi,75dpi,OTF,TTF,Type1,cyrillic,encodings,misc,util}
to a "stow based" (https://www.gnu.org/software/stow/) fontpath layout
where all files under the font directories
/usr/share/fonts/X11/{100dpi,75dpi,OTF,TTF,Type1,cyrillic,encodings,misc,util}
are actually symlinks to individual, package specific locations
elsewhere in the system.
After the switch (including, of course, editing xorg.conf for the new
font paths under /usr/share/fonts/X11 and running
mkfontscale/mkfontdir in the /usr/share/fonts/X11/* dirs) xlsfonts
shows me only ~250 fonts (where it showed ~5000 in the previous
layout) and clients relying on xserver for fonts look more or less
ugly.
If I edit xorg.conf and point the FontPath entries to the directories
where the *actual* font files live (everything else unchanged and
mkfontscale/mkfontdir run in the corresponding individual dirs), then
everything is restored back to normality (~5000 fonts listed by
xlsfonts, clients with usual look etc)
AFAICS, it looks like font files aren't read/processed correctly by
the server when they are symlinks: is that possible?
After googling around without success, I have tried to dig into the
server (and libX11) sources to find where the font files are actually
opened and read, but I got lost in the jungle...
Could anybody point me to the code (xserver,libX11,...?) where font
files parsing/loading is actually performed?
Or simply answer the question regarding the different results I obtain
when font files are/aren't symbolic links?
thanks a lot for any hint
ciao
gabriele
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
Re: DRM leases + X = SW only OpenGL acceleration on child X server
On 2018-09-24 12:04 p.m., Raimonds Cicans wrote: > On 24.09.2018 12:17, Michel Dänzer wrote: >> On 2018-09-23 11:18 p.m., Raimonds Cicans wrote: >>> Hi! >>> >>> I am playing with new "DRM leases" feature. >>> I am trying to implement single video card multi-seat. >>> >>> Questions: >>> >>> 1) is HW accelerated OpenGL possible at all on child X server? >>> >>> 2) if answer for first question is "yes", then what can cause following >>> behaviour? >>> >>> DISPLAY=:100 glxgears # Main X server. Works without problem >>> >>> DISPLAY=:101 glxgears # Child X server. Get following errors >>> libGL error: failed to authenticate magic 1 >>> libGL error: failed to load driver: radeonsi >> >> Please attach both Xorg log files and the output of >> >> LIBGL_DEBUG=verbose DISPLAY=:101 glxgears >> >> > > All files attached. Looks like drmAuthMagic returns an error for the leased FD in the Xorg process. Keith, was this working for you? -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: DRM leases + X = SW only OpenGL acceleration on child X server
On 24.09.2018 12:17, Michel Dänzer wrote: > On 2018-09-23 11:18 p.m., Raimonds Cicans wrote: >> Hi! >> >> I am playing with new "DRM leases" feature. >> I am trying to implement single video card multi-seat. >> >> Questions: >> >> 1) is HW accelerated OpenGL possible at all on child X server? >> >> 2) if answer for first question is "yes", then what can cause following >> behaviour? >> >> DISPLAY=:100 glxgears # Main X server. Works without problem >> >> DISPLAY=:101 glxgears # Child X server. Get following errors >> libGL error: failed to authenticate magic 1 >> libGL error: failed to load driver: radeonsi > > Please attach both Xorg log files and the output of > > LIBGL_DEBUG=verbose DISPLAY=:101 glxgears > > All files attached. Raimonds Cicans libGL: screen 0 does not appear to be DRI3 capable libGL error: failed to authenticate magic 1 libGL error: failed to load driver: radeonsi libGL: OpenDriver: trying /usr/lib64/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib64/dri/swrast_dri.so libGL: Can't open configuration file /root/.drirc: No such file or directory. libGL: Can't open configuration file /root/.drirc: No such file or directory. 21166 frames in 5.0 seconds = 4233.000 FPS 21394 frames in 5.0 seconds = 4278.703 FPS 21387 frames in 5.0 seconds = 4277.371 FPS 21365 frames in 5.0 seconds = 4272.890 FPS [ 432.059] X.Org X Server 1.20.1 X Protocol Version 11, Revision 0 [ 432.059] Build Operating System: Linux 4.16.12-gentoo-myrc00 x86_64 Gentoo [ 432.059] Current Operating System: Linux fast 4.16.12-gentoo-myrc00 #2 SMP Tue May 29 17:31:22 EEST 2018 x86_64 [ 432.059] Kernel command line: BOOT_IMAGE=/root/boot/kernel-genkernel-x86_64-4.16.12-gentoo-myrc00 root=/dev/mapper/root ro rootflags=subvol=root crypt_root=UUID=e9ea634b-d43b-41a7-b4ff-8f71ff025690 root=/dev/mapper/root real_init=/usr/lib/systemd/systemd net.ifnames=0 hugepagesz=2M hugepages=512 hugepagesz=1G hugepages=4 [ 432.059] Build Date: 19 September 2018 01:24:40AM [ 432.059] [ 432.059] Current version of pixman: 0.34.0 [ 432.059]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 432.059] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 432.059] (==) Log file: "/var/log/Xorg.100.log", Time: Mon Sep 24 12:47:39 2018 [ 432.060] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 432.060] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 432.060] (==) No Layout section. Using the first Screen section. [ 432.060] (==) No screen section available. Using defaults. [ 432.060] (**) |-->Screen "Default Screen Section" (0) [ 432.060] (**) | |-->Monitor "" [ 432.060] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 432.060] (==) Automatically adding devices [ 432.060] (==) Automatically enabling devices [ 432.060] (==) Automatically adding GPU devices [ 432.060] (==) Max clients allowed: 256, resource mask: 0x1f [ 432.060] (==) FontPath set to: /usr/share/fonts/misc/, /usr/share/fonts/TTF/, /usr/share/fonts/OTF/, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ [ 432.060] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 432.060] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 432.060] (II) Loader magic: 0x55c7d5cd8d00 [ 432.060] (II) Module ABI versions: [ 432.060]X.Org ANSI C Emulation: 0.4 [ 432.060]X.Org Video Driver: 24.0 [ 432.060]X.Org XInput driver : 24.1 [ 432.060]X.Org Server Extension : 10.0 [ 432.060] (--) using VT number 2 [ 432.060] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 432.061] (II) xfree86: Adding drm device (/dev/dri/card0) [ 432.062] (II) xfree86: Adding drm device (/dev/dri/card1) [ 432.063] (--) PCI:*(1@0:0:0) 1002:67df:1043:0521 rev 231, Mem @ 0x22/8589934592, 0x21/2097152, 0xdfe0/262144, I/O @ 0xe000/256, BIOS @ 0x/131072 [ 432.063] (--) PCI: (2@0:0:0) 1002:67df:1043:0521 rev 231, Mem @ 0x24/8589934592, 0x26/2097152, 0xdfd0/262144, I/O @ 0xd000/256, BIOS @ 0x/131072 [ 432.063] (II) LoadModule: "glx" [ 432.063] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 432.064] (II) Module glx: vendor="X.Org Foundation" [ 432.064]compiled for 1.20.1, module version = 1.0.0 [ 432.064]ABI class: X.Org Server Extension, version 10.0 [ 432.064] (II) Applying OutputClass "AMDgpu" to /dev/dri/card0 [ 432.064]loading driver: amdgpu [ 432.064] (II) Applying
Re: DRM leases + X = SW only OpenGL acceleration on child X server
On 2018-09-23 11:18 p.m., Raimonds Cicans wrote: > Hi! > > I am playing with new "DRM leases" feature. > I am trying to implement single video card multi-seat. > > Questions: > > 1) is HW accelerated OpenGL possible at all on child X server? > > 2) if answer for first question is "yes", then what can cause following > behaviour? > > DISPLAY=:100 glxgears # Main X server. Works without problem > > DISPLAY=:101 glxgears # Child X server. Get following errors > libGL error: failed to authenticate magic 1 > libGL error: failed to load driver: radeonsi Please attach both Xorg log files and the output of LIBGL_DEBUG=verbose DISPLAY=:101 glxgears -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
[Bug 108037] Turning monitors off and on again makes the kernel panic and system freeze
https://bugs.freedesktop.org/show_bug.cgi?id=108037 Michel Dänzer changed: What|Removed |Added Product|xorg|DRI Assignee|xorg-driver-ati@lists.x.org |dri-devel@lists.freedesktop ||.org Version|git |unspecified Component|Driver/AMDgpu |DRM/AMDgpu QA Contact|xorg-t...@lists.x.org | -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org https://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 108037] Turning monitors off and on again makes the kernel panic and system freeze
https://bugs.freedesktop.org/show_bug.cgi?id=108037 Michel Dänzer changed: What|Removed |Added CC||harry.wentl...@amd.com, ||sunpeng...@amd.com --- Comment #1 from Michel Dänzer --- Can you bisect? P.S. FYI, this is what's called an oops, not a panic. -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org https://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 108037] New: Turning monitors off and on again makes the kernel panic and system freeze
https://bugs.freedesktop.org/show_bug.cgi?id=108037 Bug ID: 108037 Summary: Turning monitors off and on again makes the kernel panic and system freeze Product: xorg Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/AMDgpu Assignee: xorg-driver-ati@lists.x.org Reporter: oyvi...@everdot.org QA Contact: xorg-t...@lists.x.org Created attachment 141707 --> https://bugs.freedesktop.org/attachment.cgi?id=141707=edit kernel panic messages >have 3 displays connected with DisplayPort >turn them off >turn them on again later >kernel crashes, RIP: 0010:dal_gpio_service_open+0x1c5/0x220 [amdgpu] This was with 4.19.0-rc4 on Fedora 29. Graphics card RX 570. This is new, did not use to be a problem before. Isn't a problem with 4.18.5. /var/log/messages did have a backtrace which is attached. A small interesting detail from the log was that the machine appeared to function normally until 2 minutes before reboot which is what makes me sure it was turning the monitors on that made the kernel panic. -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org https://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: XLIB_SKIP_ARGB_VISUALS and Qt OpenGL application with mesa
Thanks for your help, we indeed add a call to fmt.setAlphaBufferSize(1); Mathieu Westphal On Fri, Sep 21, 2018 at 8:11 PM Alan Coopersmith < alan.coopersm...@oracle.com> wrote: > On 09/21/18 10:54 AM, Adam Jackson wrote: > >> Since Composite is not enabled by default, it is not expected that > >> this issue will be visible to most users. > > > > Whatever documentation this is, is severely out of date. Composite's > > been enabled by default since xserver 1.4 in 2007 or so. > > That quote comes from the X11R6.8.2 release notes from 2005: > ftp://www.x.org/pub/X11R6.8.2/doc/RELNOTES5.html > > It holds no relevance to anything today. > > -- > -Alan Coopersmith- alan.coopersm...@oracle.com > Oracle Solaris Engineering - https://blogs.oracle.com/alanc > ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
