From mawww at kakoune.org Sun Dec 1 23:47:19 2019 From: mawww at kakoune.org (mawww at kakoune.org) Date: Mon, 02 Dec 2019 10:47:19 +1100 Subject: libxft: BGRA glyphs (color emoji) and scaling support merge request Message-ID: <75a27d6dddf11d7e0db503d6db016d5e@kakoune.org> Hello, I have created a merge request at https://gitlab.freedesktop.org/xorg/lib/libxft/merge_requests/1 that adds support for displaying bgra glyphs as provided by freetype. This includes scaling support (as those glyphs are usually only provided in high definition) for them. I have been running my system with this modified version for a month now, with only a few issues (that are fixed in the current version of the request), such as the scaling code being triggered to slant bitmap fonts. I have not noticed anything wrong since. This enables support for color emojis in xft based software, such as urxvt, st, pango with the xft backend, and emacs. I was under the impression that merge requests on gitlab were the preferred contribution method, but if needed I can post the change on this mailing list. Best regards. Maxime Coste. From lucien.gentis at univ-lorraine.fr Mon Dec 2 16:17:39 2019 From: lucien.gentis at univ-lorraine.fr (Lucien Gentis) Date: Mon, 2 Dec 2019 17:17:39 +0100 Subject: Xft and word wrapping In-Reply-To: References: Message-ID: <12edf867-ace6-3122-c1ee-8d7fe37d9b73@univ-lorraine.fr> Hello Радомир, First I recommand this reading : https://keithp.com/~keithp/talks/xtc2001/paper/ It is somehow out of date (particularly XftFont structure description is false), but it permits to understand how Xft works. In order to be sure to get a correct description of data structures, look at the Xft, fontconfig and freetype header files. *First question* : if you want the upper left corner of your text in  "0,0" , you have to pass coordinates "0, font->ascent" to XftDrawString function. font is the XftFont structure associated with your font, and ascent is the member of this structure corresponding to the difference between the top of the higher character and its base line. *Second question* : in order to determine how many pixels is a white space for a given font, I calculate the difference between the lengths of strings " e" and "e", the first string beginning with a white space : XGlyphInfo glyphInfo,gi1,gi2; XftTextExtentsUtf8 (display,font,(FcChar8 *)(" e"),strlen(" e"),&gi1); XftTextExtentsUtf8 (display,font,(FcChar8 *)("e"),strlen("e"),&gi2); spaceWidth=gi1.width-gi2.width; But be aware that if the last character of your string is a white space, it is not seen by XftTextExtentsUtf8 function ; in this case, you have to test the last character of your string, and if it's a white space, you have to add the spaceWidth calculate upward to the length in pixels calculated by XftTextExtentsUtf8. *Third question* : These are the members I use : typedef struct _XftFont {     int        ascent;  // see first question     int        descent; // difference between bottom and base line     int        height;     int        max_advance_width;     FcCharSet    *charset;     FcPattern    *pattern; // characteristics of the font ; it is                                     // constructed from a patName string like         // "Liberation Sans-12:bold:roman" passed         // to FcNameParse function. } XftFont; *Fourth question* : you have to verify if anti-aliasing is enabled for your font like this : fcResult=FcPatternGet(font,FC_ANTIALIAS ,0, &fcValue); if fcValue.u.i == 1 the anti-aliasing is enabled I think it is enabled by default ; what is the name of your font ? Le 28/11/2019 à 22:32, Радомир Хаџић a écrit : > I'm trying to implement word wrapping using Xlib and Xft. I have a few > questions and I hope some of you will answer at least some of them. > > 1. What to set the coordinates to in XftDrawString* functions? For > example, if I set them to (0,0), the top of the string is cropped. > > 2. By what amount to move the pen when we encounter a whitespace > (spaces, tabs, etc.) character? Currently, on every space I move the > cursor to the right by 5 pixels and on every tab four times that. > However the text looks uneven because of this: > > A a B b C c D d > E e F f G g H h > > I hope it's clear what I mean. > > (I have to draw whitespace strings and non-whitespace strings > separately because I have to break if the word can't fit on the line.) > > 3. What do all the fields in XftFont structure represent? > > 4. For some reason the rendered text is "ugly". It is pixelated > instead of smooth for some reason, even though I know the font is > alright and it renders just fine in xterm. What can I do about this? > _______________________________________________ > xorg at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kevinbrace at gmx.com Tue Dec 3 19:58:04 2019 From: kevinbrace at gmx.com (Kevin Brace) Date: Tue, 3 Dec 2019 20:58:04 +0100 Subject: [ANNOUNCE] xf86-video-sis 0.12.0 Message-ID: This release is a maintenance release to support X.Org X Server 1.20. Kevin Brace Brace Computer Laboratory blog https://bracecomputerlab.com --- Kevin Brace (4): Do not call xf86DisableRandR() for X Server 1.20 Fix for xf86InterceptSigIll() discontinuation in X Server 1.20 Enable SISGAMMARAMP macro on X.Org X Server Version bumped to 0.12.0 git tag: xf86-video-sis-0.12.0 https://x.org/archive/individual/driver/xf86-video-sis-0.12.0.tar.bz2 MD5: b8ec9c21758043b1480f11baec296f5d xf86-video-sis-0.12.0.tar.bz2 SHA1: d22f0d0081e222a62f9e788f5e73246c6d339f80 xf86-video-sis-0.12.0.tar.bz2 SHA256: 119d3f17d53c862ec4bf891ed696a6f1d32cdf8bd11d944a9f0ad24625333a5b xf86-video-sis-0.12.0.tar.bz2 SHA512: 5aa101e5217f15667f2c94f7a76f4afcf47717b61f5d206ce65efe35dc3f674ca294f98ca8586971c6467f31decdd94d8255ebfc7dc220fac0179afc61995952 xf86-video-sis-0.12.0.tar.bz2 PGP: https://x.org/archive/individual/driver/xf86-video-sis-0.12.0.tar.bz2.sig https://x.org/archive/individual/driver/xf86-video-sis-0.12.0.tar.gz MD5: 52d2d74982393c32a0a9c3d5d3ce99a3 xf86-video-sis-0.12.0.tar.gz SHA1: 1e4dfd77d36973a4218b8d0076d5bef2a0576a16 xf86-video-sis-0.12.0.tar.gz SHA256: 9bcc3b649001e99eb9b7f64437ee8fd65863d84bd812978fe0269180b2884702 xf86-video-sis-0.12.0.tar.gz SHA512: ddf83452ec4c1f79f4d926c0b9bb78b0cc6df4a5473b1da00fa4eb28f159491b240205d19d6d82f33169b50539d8982a529020e0d935cdeee8f37dd6bd1ece65 xf86-video-sis-0.12.0.tar.gz PGP: https://x.org/archive/individual/driver/xf86-video-sis-0.12.0.tar.gz.sig From mfabin at gmail.com Wed Dec 4 06:11:49 2019 From: mfabin at gmail.com (Fabin Mundattil) Date: Wed, 4 Dec 2019 11:41:49 +0530 Subject: Xorg freezes Message-ID: I have Ubuntu 18 running Google Chrome. Google chrome freezes my machine. I figured it out that the hardware acceleration is the issue. From what I understand, something like this shouldn't freeze Xorg. I need to disable GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors anywhere in logs either. Is this a bug in Xorg? Should I submit any more information? -- Regards Fabin M The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel at daenzer.net Wed Dec 4 09:54:13 2019 From: michel at daenzer.net (=?UTF-8?Q?Michel_D=c3=a4nzer?=) Date: Wed, 4 Dec 2019 10:54:13 +0100 Subject: Xorg freezes In-Reply-To: References: Message-ID: <9d22380b-f6c2-25ca-a296-5a56a309a84c@daenzer.net> On 2019-12-04 7:11 a.m., Fabin Mundattil wrote: > I have Ubuntu 18 running Google Chrome. Google chrome freezes my machine. I > figured it out that the hardware acceleration is the issue. From what I > understand, something like this shouldn't freeze Xorg. I need to disable > GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors > anywhere in logs either. Is this a bug in Xorg? More likely in the Mesa/kernel drivers you're using. -- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and X developer From wharms at bfs.de Wed Dec 4 10:27:42 2019 From: wharms at bfs.de (walter harms) Date: Wed, 04 Dec 2019 11:27:42 +0100 Subject: Xorg freezes In-Reply-To: References: Message-ID: <5DE78A1E.7060703@bfs.de> Am 04.12.2019 07:11, schrieb Fabin Mundattil: > I have Ubuntu 18 running Google Chrome. Google chrome freezes my machine. I > figured it out that the hardware acceleration is the issue. From what I > understand, something like this shouldn't freeze Xorg. I need to disable > GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors > anywhere in logs either. Is this a bug in Xorg? Should I submit any more > information? Hi Fabin, independent of everything: The big problem for developers is replication, if the problem is not reproduceable it is less likely that it can be fixed. So if you want to submit a problem report take the seat of the developer and ask yourself: could you replicate the problem with that information ? It helps a lot if you can reduce the number of libraries needed etc. just my 2 cents, re, wh From csoren at isd.net Wed Dec 4 17:45:47 2019 From: csoren at isd.net (Chris Sorenson) Date: Wed, 04 Dec 2019 11:45:47 -0600 Subject: Xorg freezes In-Reply-To: References: Message-ID: > > Message: 2 > Date: Wed, 4 Dec 2019 11:41:49 +0530 > From: Fabin Mundattil > To: xorg at freedesktop.org > Subject: Xorg freezes > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > I have Ubuntu 18 running Google Chrome. Google chrome freezes my > machine. I > figured it out that the hardware acceleration is the issue. From what I > understand, something like this shouldn't freeze Xorg. I need to > disable > GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors > anywhere in logs either. Is this a bug in Xorg? Should I submit any > more > information? > > -- > Regards > Fabin M > > Message: 3 > Date: Wed, 4 Dec 2019 10:54:13 +0100 > From: Michel Dänzer > To: Fabin Mundattil > Cc: xorg at freedesktop.org > Subject: Re: Xorg freezes > Message-ID: <9d22380b-f6c2-25ca-a296-5a56a309a84c at daenzer.net> > Content-Type: text/plain; charset=utf-8 > > On 2019-12-04 7:11 a.m., Fabin Mundattil wrote: >> I have Ubuntu 18 running Google Chrome. Google chrome freezes my >> machine. I >> figured it out that the hardware acceleration is the issue. From what >> I >> understand, something like this shouldn't freeze Xorg. I need to >> disable >> GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors >> anywhere in logs either. Is this a bug in Xorg? > > More likely in the Mesa/kernel drivers you're using. > > ------------------------------ > > Message: 4 > Date: Wed, 04 Dec 2019 11:27:42 +0100 > From: walter harms > To: xorg at lists.x.org > Cc: mfabin at gmail.com > Subject: Re: Xorg freezes > Message-ID: <5DE78A1E.7060703 at bfs.de> > Content-Type: text/plain; charset=UTF-8 > > > > Am 04.12.2019 07:11, schrieb Fabin Mundattil: >> I have Ubuntu 18 running Google Chrome. Google chrome freezes my >> machine. I >> figured it out that the hardware acceleration is the issue. From what >> I >> understand, something like this shouldn't freeze Xorg. I need to >> disable >> GLX, DRI2 and DRI3 in Xorg to fix the issue. I don't see any errors >> anywhere in logs either. Is this a bug in Xorg? Should I submit any >> more >> information? > > > Hi Fabin, > independent of everything: > > The big problem for developers is replication, if the problem is not > reproduceable it is less likely that it can be fixed. So if you > want to submit a problem report take the seat of the developer and > ask yourself: could you replicate the problem with that > information ? It helps a lot if you can reduce the number of > libraries needed etc. > > just my 2 cents, > > re, > wh > Regards Fabian, In particular, it would help to know what graphics hardware exists on your system. If there are binary kernel modules for that hardware from its manufacturer it would likely be best if you used those, though that is admittedly not the "free software" way. From radomirhadzic46 at gmail.com Thu Dec 5 20:28:04 2019 From: radomirhadzic46 at gmail.com (=?UTF-8?B?0KDQsNC00L7QvNC40YAg0KXQsNGf0LjRmw==?=) Date: Thu, 5 Dec 2019 21:28:04 +0100 Subject: Squares instead of tabs (Xft) Message-ID: Hello. I'm using XftDrawStringUtf8() function to display text. But this function for some reason displays tabs as squares, instead of drawing them the usual way (as spacing), which is what I want. Any way to get Xft to draw them like spacing (ideally, as 4 or 8 space characters)? From gerard.seibert at gmail.com Fri Dec 6 13:13:00 2019 From: gerard.seibert at gmail.com (Gerard E. Seibert) Date: Fri, 6 Dec 2019 08:13:00 -0500 Subject: no screens found(EE) Message-ID: <20191206081300.00003dab@gmail.com> I just recently installed FreeBSD 11.3 onto a Dell XPS 8930 PC. The PC has an Intel on board video chip. This is all the information I could solicit about the Intel chips: pciconf -lv | grep -b4 -i "vga" 354- vendor = 'Intel Corporation' 391- device = 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16)' 482- class = bridge 506- subclass = PCI-PCI 531:vgapci0 at pci0:0:2:0: class=0x030000 card=0x08591028 chip=0x3e918086 rev=0x00 hdr=0x00 616- vendor = 'Intel Corporation' 653- device = '8th Gen Core Processor Gaussian Mixture Model' 718- class = display 743: subclass = VGA 764-none0 at pci0:0:8:0: class=0x088000 card=0x08591028 chip=0x19118086 rev=0x00 hdr=0x00 847- vendor = 'Intel Corporation' 884- device = 'Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model' 991- class = base peripheral The Xorg.0.log file is available here: https://www.seibercom.net/logs/Xorg.0.log The problem I am having is that KDE will not start. It appears as if it is unable to find a 'screen'. I really don't know where to go from here. I would appreciate any help available. Thanks! -- Gerard -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From lucien.gentis at univ-lorraine.fr Mon Dec 9 17:43:56 2019 From: lucien.gentis at univ-lorraine.fr (Lucien Gentis) Date: Mon, 9 Dec 2019 18:43:56 +0100 Subject: Squares instead of tabs (Xft) In-Reply-To: References: Message-ID: <42d32a1a-05d3-0d8b-0a42-edbff8fff10d@univ-lorraine.fr> Hello, Tab is not a printable character. I think you have to scan each string you want to display in order to replace each encountered tab with a certain number of spaces. Le 05/12/2019 à 21:28, Радомир Хаџић a écrit : > Hello. > > I'm using XftDrawStringUtf8() function to display text. But this > function for some reason displays tabs as squares, instead of drawing > them the usual way (as spacing), which is what I want. > > Any way to get Xft to draw them like spacing (ideally, as 4 or 8 space > characters)? > _______________________________________________ > xorg at 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 From gerard.seibert at gmail.com Tue Dec 10 16:19:45 2019 From: gerard.seibert at gmail.com (Gerard E. Seibert) Date: Tue, 10 Dec 2019 11:19:45 -0500 Subject: Unable to get kde5 to run Message-ID: <20191210111945.00004bc1@gmail.com> FreeBSD 11.3 This is a fresh installation of "xorg" and "kde5" Everything seems normal, but kde5 will not start. The is a copy of the screen when I enter "startx": Script started on Tue Dec 10 09:52:17 2019 Command: startx xauth: file /home/gerard/.serverauth.85907 does not exist X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 11.3-RELEASE-p5 amd64 Current Operating System: FreeBSD scorpio.seibercom.net 11.3-RELEASE-p5 FreeBSD 11.3-RELEASE-p5 #0: Tue Nov 12 08:59:04 UTC 2019 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 05 December 2019 02:53:38PM Current version of pixman: 0.38.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 10 09:52:17 2019 (==) Using config directory: "/usr/local/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/local/share/X11/xorg.conf.d" xinit: connection to X server lost waiting for X server to shut down (II) Server terminated successfully (0). Closing log file. Command exit status: 0 Script done on Tue Dec 10 09:52:19 2019 The is the Xorg.0.log file: [ 3810.925] X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 3810.925] X Protocol Version 11, Revision 0 [ 3810.925] Build Operating System: FreeBSD 11.3-RELEASE-p5 amd64 [ 3810.925] Current Operating System: FreeBSD scorpio.seibercom.net 11.3-RELEASE-p5 FreeBSD 11.3-RELEASE-p5 #0: Tue Nov 12 08:59:04 UTC 2019 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 [ 3810.925] Build Date: 05 December 2019 02:53:38PM [ 3810.925] [ 3810.925] Current version of pixman: 0.38.4 [ 3810.926] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 3810.926] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 3810.926] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 10 11:02:09 2019 [ 3810.926] (==) Using config file: "/etc/X11/xorg.conf" [ 3810.926] (==) Using config directory: "/usr/local/etc/X11/xorg.conf.d" [ 3810.926] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d" [ 3810.926] (==) ServerLayout "Layout0" [ 3810.926] (**) |-->Screen "Screen0" (0) [ 3810.926] (**) | |-->Monitor "Monitor0" [ 3810.926] (**) | |-->Device "Device0" [ 3810.926] (**) | |-->GPUDevice "Device0" [ 3810.926] (**) |-->Input Device "Keyboard0" [ 3810.926] (**) |-->Input Device "Mouse0" [ 3810.926] (==) Automatically adding devices [ 3810.926] (==) Automatically enabling devices [ 3810.926] (==) Not automatically adding GPU devices [ 3810.926] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 3810.926] (==) FontPath set to: /usr/local/share/fonts/misc/, /usr/local/share/fonts/TTF/, /usr/local/share/fonts/OTF/, /usr/local/share/fonts/Type1/, /usr/local/share/fonts/100dpi/, /usr/local/share/fonts/75dpi/ [ 3810.926] (==) ModulePath set to "/usr/local/lib/xorg/modules" [ 3810.926] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [ 3810.926] (WW) Disabling Keyboard0 [ 3810.926] (WW) Disabling Mouse0 [ 3810.926] (II) Loader magic: 0x82a4b0 [ 3810.926] (II) Module ABI versions: [ 3810.926] X.Org ANSI C Emulation: 0.4 [ 3810.926] X.Org Video Driver: 20.0 [ 3810.926] X.Org XInput driver : 22.1 [ 3810.926] X.Org Server Extension : 9.0 [ 3810.926] (--) PCI: (0:0:2:0) 8086:3e91:1028:0859 rev 0, Mem @ 0x2ffe000000/16777216, 0x2fa0000000/268435456, I/O @ 0x0000f000/64 [ 3810.926] (--) PCI:*(0:1:0:0) 10de:1d01:1458:375c rev 161, Mem @ 0xeb000000/16777216, 0xa0000000/268435456, 0xb0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/65536 [ 3810.926] (II) LoadModule: "glx" [ 3810.927] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so [ 3810.927] (II) Module glx: vendor="X.Org Foundation" [ 3810.927] compiled for 1.18.4, module version = 1.0.0 [ 3810.927] ABI class: X.Org Server Extension, version 9.0 [ 3810.927] (==) AIGLX enabled [ 3810.927] (II) LoadModule: "nvidia" [ 3810.928] (II) Loading /usr/local/lib/xorg/modules/drivers/nvidia_drv.so [ 3810.928] (II) Module nvidia: vendor="NVIDIA Corporation" [ 3810.928] compiled for 1.6.99.901, module version = 1.0.0 [ 3810.928] Module class: X.Org Video Driver [ 3810.928] (II) NVIDIA dlloader X Driver 440.31 Sun Oct 27 02:13:23 UTC 2019 [ 3810.928] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 3810.928] (--) Using syscons driver with X support (version 2.0) [ 3810.928] (--) using VT number 9 [ 3810.928] (II) Loading sub module "fb" [ 3810.928] (II) LoadModule: "fb" [ 3810.928] (II) Loading /usr/local/lib/xorg/modules/libfb.so [ 3810.928] (II) Module fb: vendor="X.Org Foundation" [ 3810.928] compiled for 1.18.4, module version = 1.0.0 [ 3810.928] ABI class: X.Org ANSI C Emulation, version 0.4 [ 3810.928] (II) Loading sub module "wfb" [ 3810.928] (II) LoadModule: "wfb" [ 3810.928] (II) Loading /usr/local/lib/xorg/modules/libwfb.so [ 3810.928] (II) Module wfb: vendor="X.Org Foundation" [ 3810.928] compiled for 1.18.4, module version = 1.0.0 [ 3810.928] ABI class: X.Org ANSI C Emulation, version 0.4 [ 3810.928] (II) Loading sub module "ramdac" [ 3810.928] (II) LoadModule: "ramdac" [ 3810.928] (II) Module "ramdac" already built-in [ 3810.929] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 3810.929] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 [ 3810.929] (==) NVIDIA(0): RGB weight 888 [ 3810.929] (==) NVIDIA(0): Default visual is TrueColor [ 3810.929] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) [ 3810.929] (**) NVIDIA(0): Enabling 2D acceleration [ 3810.929] (II) Loading sub module "glxserver_nvidia" [ 3810.929] (II) LoadModule: "glxserver_nvidia" [ 3810.929] (II) Loading /usr/local/lib/xorg/modules/extensions/libglxserver_nvidia.so [ 3810.933] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation" [ 3810.933] compiled for 1.6.99.901, module version = 1.0.0 [ 3810.933] Module class: X.Org Server Extension [ 3810.933] (II) NVIDIA GLX Module 440.31 Sun Oct 27 02:11:10 UTC 2019 [ 3810.933] (II) NVIDIA: The X server does not support PRIME Render Offload. [ 3811.290] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0 [ 3811.290] (--) NVIDIA(0): DFP-0 [ 3811.290] (--) NVIDIA(0): DFP-1 (boot) [ 3811.291] (II) NVIDIA(0): NVIDIA GPU GeForce GT 1030 (GP108-A) at PCI:1:0:0 (GPU-0) [ 3811.291] (--) NVIDIA(0): Memory: 2097152 kBytes [ 3811.291] (--) NVIDIA(0): VideoBIOS: 86.08.24.00.2f [ 3811.291] (II) NVIDIA(0): Detected PCI Express Link width: 4X [ 3811.291] (--) NVIDIA(GPU-0): DFP-0: disconnected [ 3811.291] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS [ 3811.291] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock [ 3811.291] (--) NVIDIA(GPU-0): [ 3811.307] (--) NVIDIA(GPU-0): DELL SE198WFP (DFP-1): connected [ 3811.307] (--) NVIDIA(GPU-0): DELL SE198WFP (DFP-1): Internal TMDS [ 3811.307] (--) NVIDIA(GPU-0): DELL SE198WFP (DFP-1): 165.0 MHz maximum pixel clock [ 3811.307] (--) NVIDIA(GPU-0): [ 3811.311] (==) NVIDIA(0): [ 3811.311] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select" [ 3811.311] (==) NVIDIA(0): will be used as the requested mode. [ 3811.311] (==) NVIDIA(0): [ 3811.311] (II) NVIDIA(0): Validated MetaModes: [ 3811.311] (II) NVIDIA(0): "DFP-1:nvidia-auto-select" [ 3811.311] (II) NVIDIA(0): Virtual screen size determined to be 1440 x 900 [ 3811.315] (--) NVIDIA(0): DPI set to (89, 87); computed from "UseEdidDpi" X config [ 3811.315] (--) NVIDIA(0): option [ 3811.315] (--) Depth 24 pixmap format is 32 bpp [ 3811.315] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory [ 3811.315] (II) NVIDIA: access. [ 3811.334] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select" [ 3811.366] (==) NVIDIA(0): Disabling shared memory pixmaps [ 3811.366] (==) NVIDIA(0): Backing store enabled [ 3811.366] (==) NVIDIA(0): Silken mouse enabled [ 3811.366] (**) NVIDIA(0): DPMS enabled [ 3811.367] (II) Loading sub module "dri2" [ 3811.367] (II) LoadModule: "dri2" [ 3811.367] (II) Module "dri2" already built-in [ 3811.367] (II) NVIDIA(0): [DRI2] Setup complete [ 3811.367] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia [ 3811.367] (--) RandR disabled [ 3811.370] (II) Initializing extension GLX [ 3811.370] (II) Indirect GLX disabled. [ 3811.424] (II) config/devd: probing input devices... [ 3811.424] (II) config/devd: adding input device (null) (/dev/kbdmux) [ 3811.424] (II) LoadModule: "kbd" [ 3811.424] (II) Loading /usr/local/lib/xorg/modules/input/kbd_drv.so [ 3811.425] (II) Module kbd: vendor="X.Org Foundation" [ 3811.425] compiled for 1.18.4, module version = 1.9.0 [ 3811.425] Module class: X.Org XInput Driver [ 3811.425] ABI class: X.Org XInput driver, version 22.1 [ 3811.425] (II) Using input driver 'kbd' for 'kbdmux' [ 3811.425] (**) kbdmux: always reports core events [ 3811.425] (**) kbdmux: always reports core events [ 3811.425] (**) Option "Protocol" "standard" [ 3811.425] (**) Option "XkbRules" "base" [ 3811.425] (**) Option "XkbModel" "pc105" [ 3811.425] (**) Option "XkbLayout" "us" [ 3811.425] (**) Option "config_info" "devd:kbdmux" [ 3811.425] (II) XINPUT: Adding extended input device "kbdmux" (type: KEYBOARD, id 6) [ 3811.425] (II) config/devd: kbdmux is enabled, ignoring device ukbd0 [ 3811.425] (II) config/devd: adding input device (null) (/dev/sysmouse) [ 3811.425] (II) LoadModule: "mouse" [ 3811.425] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so [ 3811.425] (II) Module mouse: vendor="X.Org Foundation" [ 3811.425] compiled for 1.18.4, module version = 1.9.3 [ 3811.425] Module class: X.Org XInput Driver [ 3811.425] ABI class: X.Org XInput driver, version 22.1 [ 3811.425] (II) Using input driver 'mouse' for 'sysmouse' [ 3811.425] (**) sysmouse: always reports core events [ 3811.425] (**) Option "Device" "/dev/sysmouse" [ 3811.425] (==) sysmouse: Protocol: "Auto" [ 3811.425] (**) sysmouse: always reports core events [ 3811.425] (==) sysmouse: Emulate3Buttons, Emulate3Timeout: 50 [ 3811.425] (**) sysmouse: ZAxisMapping: buttons 4 and 5 [ 3811.425] (**) sysmouse: Buttons: 5 [ 3811.425] (**) Option "config_info" "devd:sysmouse" [ 3811.425] (II) XINPUT: Adding extended input device "sysmouse" (type: MOUSE, id 7) [ 3811.425] (**) sysmouse: (accel) keeping acceleration scheme 1 [ 3811.426] (**) sysmouse: (accel) acceleration profile 0 [ 3811.426] (**) sysmouse: (accel) acceleration factor: 2.000 [ 3811.426] (**) sysmouse: (accel) acceleration threshold: 4 [ 3811.426] (II) sysmouse: SetupAuto: hw.iftype is 4, hw.model is 0 [ 3811.426] (II) sysmouse: SetupAuto: protocol is SysMouse [ 3811.426] (II) config/devd: device /dev/ums0 already opened [ 3812.154] (II) config/devd: terminating backend... [ 3812.154] (II) UnloadModule: "mouse" [ 3812.154] (II) UnloadModule: "kbd" [ 3812.259] (II) NVIDIA(GPU-0): Deleting GPU-0 [ 3812.260] (II) Server terminated successfully (0). Closing log file. And this is the ~/.xinitrc file exec ck-launch-session startkde I am at a loss as to what I am doing wrong. -- Gerard From fredrik at kde.org Tue Dec 10 23:07:16 2019 From: fredrik at kde.org (Fredrik =?iso-8859-1?q?H=F6glund?=) Date: Wed, 11 Dec 2019 00:07:16 +0100 Subject: Unable to get kde5 to run In-Reply-To: <20191210111945.00004bc1@gmail.com> References: <20191210111945.00004bc1@gmail.com> Message-ID: <201912110007.16839.fredrik@kde.org> On Tuesday 10 December 2019, Gerard E. Seibert wrote: > FreeBSD 11.3 > > This is a fresh installation of "xorg" and "kde5" Everything seems > normal, but kde5 will not start. > [snip] > And this is the ~/.xinitrc file > > exec ck-launch-session startkde The startkde script has been replaced by the native executables startplasma-x11 and startplasma-wayland in 5.17. Regards, Fredrik From peter.hutterer at who-t.net Fri Dec 13 04:56:34 2019 From: peter.hutterer at who-t.net (Peter Hutterer) Date: Fri, 13 Dec 2019 14:56:34 +1000 Subject: [ANNOUNCE] libXpm 3.5.13 Message-ID: <20191213045634.GA2159008@jelly> libXpm is the library for handling images in the XPM format. Lest we be accused that users have to wait many years to get fixes out, let's quickly release the branch before the calendar turns over over again so it's just some years. The actual fixes here are some found by static analysers, and a build fix for Windows (which, curiously, is dated to 2012 so clearly we're at the top of the game here). Nothing overly exciting, but covscan, parfait, etc. should be a bit happier now. Alan Coopersmith (3): After fdopen(), use fclose() instead of close() in error path Update README for gitlab migration Update configure.ac bug URL for gitlab migration Benjamin Tissoires (1): parse: simplify error paths in xpmParseColors() Dave Bodenstab (1): Windows build fixes Emil Velikov (1): autogen.sh: use quoted string variables Fabrice Fontaine (1): Allow usage when fork() is not available Mihail Konev (1): autogen: add default patch prefix Peter Hutterer (3): autogen.sh: use exec instead of waiting for configure to finish parse: avoid memleak on error with STRLCAT/STRLCPY libXpm 3.5.13 git tag: libXpm-3.5.13 https://xorg.freedesktop.org/archive/individual/lib/libXpm-3.5.13.tar.bz2 MD5: 6f0ecf8d103d528cfc803aa475137afa libXpm-3.5.13.tar.bz2 SHA1: 38b1a2728adb49f4e255aba1530f51789815ffc4 libXpm-3.5.13.tar.bz2 SHA256: 9cd1da57588b6cb71450eff2273ef6b657537a9ac4d02d0014228845b935ac25 libXpm-3.5.13.tar.bz2 SHA512: 3b8f6e926272f39b1d95135c2274c00f5aaee1f9fb2ef79f71628df5edeb7ba20158819ef6a778101cc4092493a3b5b613c53634fdccadcc0fc85f0605e5e9a5 libXpm-3.5.13.tar.bz2 PGP: https://xorg.freedesktop.org/archive/individual/lib/libXpm-3.5.13.tar.bz2.sig https://xorg.freedesktop.org/archive/individual/lib/libXpm-3.5.13.tar.gz MD5: c16dd844fd169d564dbd1c1ec295c563 libXpm-3.5.13.tar.gz SHA1: b4fb88ac3b83e6530b5fef830961d7d9085a4f7f libXpm-3.5.13.tar.gz SHA256: e3dfb0fb8c1f127432f2a498c7856b37ce78a61e8da73f1aab165a73dd97ad00 libXpm-3.5.13.tar.gz SHA512: faf9c75f969da2738ab01b7a28c85ad2bb42a4421509769b56ef9ddaabb0eacb1b06553cfcb1daa03d7fdceb1d3a7c5eee078c3bc3f5e3902fec41b82d3f8d82 libXpm-3.5.13.tar.gz PGP: https://xorg.freedesktop.org/archive/individual/lib/libXpm-3.5.13.tar.gz.sig -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available URL: