Initialization of applications GTK vs. Qt
I am running the Mate desktop on CentOS 7 and trying to get fcitx working so I can switch between two western keyboards and typing pinyin. Unfortunately the instructions on the net are lacking and the graphical configuration tool for fcitx is missing from EPEL. At this stage, I have, with the support of one person on the CentOS mailing list who types Japanese, got it working in: - terminal windows and - an application using Qt, KeePassX. I have not been able to get three applications using GTK working: Firefox, Thunderbird and LibreOffice. I can get them working when I have the three environment variables preceding the name of the application but not when launched from the desktop. I suspect GTK and Qt applications are initialized differently - perhaps by X - but I do not know how to resolve this. Any pointers or ideas for further research are appreciated! Thank you.___ 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: Xrandr and external monitor (H)
On January 5, 2025 7:32:48 PM GMT-05:00, Muhammad Ahsan wrote: > >> I just checked to log file and found: >> >> [22.361] (==) Matched modesetting as autoconfigured driver 0 >> [22.361] (II) LoadModule: "modesetting" >> [22.361] (II) Loading >> /usr/lib64/xorg/modules/drivers/modesetting_drv.so [22.371] (II) >> Module modesetting: vendor="X.Org Foundation" [22.371] (II) >> modesetting: Driver for Modesetting Kernel Drivers: kms >> >> Does this not mean the modesetting driver /is/ loaded or am I missing >> something? > >Indeed the driver is loaded, however in the very first pastebin log, >this module wasn't loaded (ref. https://pastebin.com/a9an6Y7M). >I have missed the second log file link/attachment >(attachment-0001.ksh). >Looking at it confirms modesetting's successful loading. > >Can you provide more details about the external screen(s) you are >trying >to attach e.g. make, model, resolution etc.? > >Best >--- >Ahsan >--- > > >> >> -- >> >> Subject: Digest Footer >> >> ___ >> xorg mailing list >> xorg@lists.x.org >> https://lists.x.org/mailman/listinfo/xorg >> >> >> -- >> >> End of xorg Digest, Vol 233, Issue 7 >> Note that the pastebin file is not mine. The external monitor is an Acer S230HL monitor running at 1920 x 1200 and connected via HDMI at bot ends, ie. including the laptop HDMI port which xrandr misidentifies as DP-1. The Dell Inspiron 7570 laptop has a UHD display running at 3840 x 2880 pixels.
Re: Xrandr and external monitor (H)
On January 5, 2025 9:14:28 PM GMT-05:00, H wrote: >On January 5, 2025 7:32:48 PM GMT-05:00, Muhammad Ahsan > wrote: >> > >>> I just checked to log file and found: >>> >>> [22.361] (==) Matched modesetting as autoconfigured driver 0 >>> [22.361] (II) LoadModule: "modesetting" >>> [22.361] (II) Loading >>> /usr/lib64/xorg/modules/drivers/modesetting_drv.so [22.371] (II) >>> Module modesetting: vendor="X.Org Foundation" [22.371] (II) >>> modesetting: Driver for Modesetting Kernel Drivers: kms >>> >>> Does this not mean the modesetting driver /is/ loaded or am I >missing >>> something? >> >>Indeed the driver is loaded, however in the very first pastebin log, >>this module wasn't loaded (ref. https://pastebin.com/a9an6Y7M). >>I have missed the second log file link/attachment >>(attachment-0001.ksh). >>Looking at it confirms modesetting's successful loading. >> >>Can you provide more details about the external screen(s) you are >>trying >>to attach e.g. make, model, resolution etc.? >> >>Best >>--- >>Ahsan >>--- >> >> >>> >>> -- >>> >>> Subject: Digest Footer >>> >>> ___ >>> xorg mailing list >>> xorg@lists.x.org >>> https://lists.x.org/mailman/listinfo/xorg >>> >>> >>> -- >>> >>> End of xorg Digest, Vol 233, Issue 7 >>> > >Note that the pastebin file is not mine. The external monitor is an >Acer S230HL monitor running at 1920 x 1200 and connected via HDMI at >bot ends, ie. including the laptop HDMI port which xrandr misidentifies >as DP-1. The Dell Inspiron 7570 laptop has a UHD display running at >3840 x 2880 pixels. Typo: the laptop display runs at 3840 x 2160 pixels.
Re: Xrandr and external monitor
On January 3, 2025 5:20:38 AM EST, Fungal-net wrote:
>On Friday, January 3rd, 2025 at 12:49 AM, H
>wrote:
>> Forgot to attach the file but doing it now.
>
>I have a shortcut function in my zsh which looks for (EE) in Xorg.log
>The first thing I would do after seeing this log is to install the xorg
>xf86 packages for fbdev and vesa then attempt to run again and rescan
>for errors. Subsequent errors and warnings would be meaningless after
>the first. In the arch ecosystem those pkgs are marked as
>xf86-video-{fbdev,vesa} on debian/rh may have slightly different names.
What would the function be of fbdev and vesa?
Quick googling suggests the former is deprecated and replaced by DRM and I am
afraid I do not understand the role vesa would play with the nouveau driver in
use? Are both vesa and nouveau needed?
Re: Xrandr and external monitor
On January 1, 2025 9:29:07 PM GMT-05:00, Fungal-net wrote: > >> Should I do any troubleshooting with xinerama before I try the Nvidia >driver? If so, what would be worthwhile trying? > >No xinerama is irrelevant, it would still work making a 640x480 screen >work as left screen to a 1920-x1080 screen, taking your window from one >with the mouse and dragging it to the other. > >I think installing the proper nvidia firmware and rebooting will solve >your problems. So you believe this has nothing to with X but rather is a noveau driver problem? If so, I should probably bring it to their attention.
Re: Xrandr and external monitor
On January 1, 2025 8:22:03 PM GMT-05:00, Fungal-net wrote: > >> > The monitor is an Acer S230HL monitor. >> > >> > I am using the nouveau driver and inxi reports the presence of both >> > Intel UHD Graphics 620 and Nvidia GM108M (GeForce 940MX). >> >> >> The kernel is: >> Linux dell 5.14.0-503.15.1.el9_5.x86_64 #1 SMP PREEMPT_DYNAMIC Tue >Nov 26 17:24:29 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux > >https://forums.rockylinux.org/t/nvidia-drivers-on-rocky-linux/12366 > >Basically the misc-nonfree-firmware pkg from debian should be available >through rocky >According to the instructions for nvidia above should make it work. >I don't have any experience with any rh related systems, not even a vm >out of curiosity >5.14 is not even an LTS kernel, it is an abandoned kernel for years ... > 5.10 5.15 6.6 >are among the lts I've had better lack with with old and new hw. > >Make sure that after installing and your rpm thing reconstructs your >kernel images it is >best to reboot for the effects to be realized. > >Basically the kernel and udev is what works and identifies the screens, >mesa and X just use what is there. xinerama is what handles the output >of 2 or more screens to construct a multi-monitor arrangement. Should I do any troubleshooting with xinerama before I try the Nvidia driver? If so, what would be worthwhile trying?
Fwd: Re: Xrandr and external monitor
With the possibility of an update of xorg, I'd like to bring up my problem again. I am looking for suggestions on how I should debug this to find if this is a xorg problem or the issue lies somewhere else. Thanks. Original Message From: H Sent: January 2, 2025 2:48:08 PM GMT-05:00 To: xorg@lists.x.org, Alan Coopersmith , xorg Mailing List Subject: Re: Xrandr and external monitor On January 2, 2025 11:58:06 AM EST, Alan Coopersmith wrote: >On 1/1/25 12:27, H wrote: >> I just discovered running xrandr --listmonitors that, while the >internal laptop monitor is labeled eDP-1, xrandr identifies the >external monitor as using DP-1 although it uses the laptop >HDMI-connector. Further, while mate hardware display monitor also >identifies it as using DP-1 - possibly based on xrandr output - the >monitor itself tells me it is connected using its HDMI1 connector. >xrandr does report the correct display resolution, though. >> >> Thus, it looks like xrandr misreads the configuration feeding it to >mate. > >The xrandr program and GUIs like the mate monitor configuration use >libXrandr to >get the configuration information - all it does is ask the Xserver for >the >information provided by the video driver. If these programs are >showing the >wrong config it's because the Xorg video driver module has provided >them with >the wrong information. (You don't say what Xorg video driver you're >using >- modesetting or something more specific to the hardware - the >Xorg.0.log >should list that and may list the output config detected by it.) So the problem could lie with x or with the video driver, the latter reporting to X? According to X.org.log I am running X Server 1.20.11. One of my concerns is why X reports that DP-1 connection is used with the external monitor whereas it in reality uses HDMI without any adapters. That suggests something is reported incorrectly which could conceivably lead to some other problem. I am attaching X.org.log which to me seems to suggest that it is using the noveau driver. Note that I just tried to disconnect/reconnect the external monitor but could not find any log of that connection towards the end of the log.
Re: Xrandr and external monitor
On January 2, 2025 2:48:08 PM EST, H wrote: >On January 2, 2025 11:58:06 AM EST, Alan Coopersmith > wrote: >>On 1/1/25 12:27, H wrote: >>> I just discovered running xrandr --listmonitors that, while the >>internal laptop monitor is labeled eDP-1, xrandr identifies the >>external monitor as using DP-1 although it uses the laptop >>HDMI-connector. Further, while mate hardware display monitor also >>identifies it as using DP-1 - possibly based on xrandr output - the >>monitor itself tells me it is connected using its HDMI1 connector. >>xrandr does report the correct display resolution, though. >>> >>> Thus, it looks like xrandr misreads the configuration feeding it to >>mate. >> >>The xrandr program and GUIs like the mate monitor configuration use >>libXrandr to >>get the configuration information - all it does is ask the Xserver for >>the >>information provided by the video driver. If these programs are >>showing the >>wrong config it's because the Xorg video driver module has provided >>them with >>the wrong information. (You don't say what Xorg video driver you're >>using >>- modesetting or something more specific to the hardware - the >>Xorg.0.log >>should list that and may list the output config detected by it.) > >So the problem could lie with x or with the video driver, the latter >reporting to X? According to X.org.log I am running X Server 1.20.11. > >One of my concerns is why X reports that DP-1 connection is used with >the external monitor whereas it in reality uses HDMI without any >adapters. That suggests something is reported incorrectly which could >conceivably lead to some other problem. > >I am attaching X.org.log which to me seems to suggest that it is using >the noveau driver. Note that I just tried to disconnect/reconnect the >external monitor but could not find any log of that connection towards >the end of the log. Forgot to attach the file but doing it now.[22.099] X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 [22.099] Build Operating System: 5.10.219-208.866.amzn2.x86_64 [22.099] Current Operating System: Linux dell 5.14.0-503.15.1.el9_5.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Nov 26 17:24:29 UTC 2024 x86_64 [22.099] Kernel command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.0-503.15.1.el9_5.x86_64 root=/dev/mapper/rl-root ro crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rl-swap rd.luks.uuid=luks-2ed902bc-a984-451b-9e94-a3f86d25c649 rd.lvm.lv=rl/root rd.lvm.lv=rl/swap vconsole.font=ter-v32n pcie_aspm=off [22.099] Build Date: 10 April 2024 12:00:00AM [22.099] Build ID: xorg-x11-server 1.20.11-26.el9 [22.099] Current version of pixman: 0.40.0 [22.099]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [22.099] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [22.099] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 1 14:41:04 2025 [22.100] (==) Using config directory: "/etc/X11/xorg.conf.d" [22.100] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [22.101] (==) No Layout section. Using the first Screen section. [22.101] (==) No screen section available. Using defaults. [22.101] (**) |-->Screen "Default Screen Section" (0) [22.101] (**) | |-->Monitor "" [22.101] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [22.102] (==) Automatically adding devices [22.102] (==) Automatically enabling devices [22.102] (==) Automatically adding GPU devices [22.102] (==) Automatically binding GPU devices [22.102] (==) Max clients allowed: 256, resource mask: 0x1f [22.102] (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins [22.102] (==) ModulePath set to "/usr/lib64/xorg/modules" [22.102] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [22.102] (II) Loader magic: 0x558ef6317d40 [22.102] (II) Module ABI versions: [22.102]X.Org ANSI C Emulation: 0.4 [22.102]X.Org Video Driver: 24.1 [22.102]X.Org XInput driver : 24.1 [22.102]X.Org Server Extension : 10.0 [22.102] (++) using VT number 1 [22.102] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [22.103] (II) xfree86: Adding drm device (/dev/dri/card1) [22.111] (II) xfree86: Adding
Re: Xrandr and external monitor
On January 2, 2025 11:58:06 AM EST, Alan Coopersmith wrote: >On 1/1/25 12:27, H wrote: >> I just discovered running xrandr --listmonitors that, while the >internal laptop monitor is labeled eDP-1, xrandr identifies the >external monitor as using DP-1 although it uses the laptop >HDMI-connector. Further, while mate hardware display monitor also >identifies it as using DP-1 - possibly based on xrandr output - the >monitor itself tells me it is connected using its HDMI1 connector. >xrandr does report the correct display resolution, though. >> >> Thus, it looks like xrandr misreads the configuration feeding it to >mate. > >The xrandr program and GUIs like the mate monitor configuration use >libXrandr to >get the configuration information - all it does is ask the Xserver for >the >information provided by the video driver. If these programs are >showing the >wrong config it's because the Xorg video driver module has provided >them with >the wrong information. (You don't say what Xorg video driver you're >using >- modesetting or something more specific to the hardware - the >Xorg.0.log >should list that and may list the output config detected by it.) So the problem could lie with x or with the video driver, the latter reporting to X? According to X.org.log I am running X Server 1.20.11. One of my concerns is why X reports that DP-1 connection is used with the external monitor whereas it in reality uses HDMI without any adapters. That suggests something is reported incorrectly which could conceivably lead to some other problem. I am attaching X.org.log which to me seems to suggest that it is using the noveau driver. Note that I just tried to disconnect/reconnect the external monitor but could not find any log of that connection towards the end of the log.
Re: Xrandr and external monitor
On January 1, 2025 5:53:06 PM EST, Fungal-net wrote: > >> I just discovered running xrandr --listmonitors that, while the >internal laptop monitor is labeled eDP-1, xrandr identifies the >external monitor as using DP-1 although it uses the laptop >HDMI-connector. Further, while mate hardware display monitor also >identifies it as using DP-1 - possibly based on xrandr output - the >monitor itself tells me it is connected using its HDMI1 connector. >xrandr does report the correct display resolution, though. > >Are both ends of the cable hdmi, no adaptors? Usually hdmi - hdmi or >dp - dp seem pretty accurate, while when you go from one to the other >they are a bit unreliable. Is the monitor on before you boot, or are >you connecting while the system has booted? > >Pretty much all guis use xrandr output. Since you are not listing the >make and model of the monitor do a search and see if firmware are >available specific to this monitor. Also which kernel are you using >(different versions tend to behave a little different). >In most cases the chipset in the monitor provides the firmware needed >to properly identify itself in the system, but I've seen many >deviations. Do you also have svga plugs on both? > >Last question, are gfx native intel/amd or is there something like >nvidia involved? It is not a good day to be mean to a stranger but >tomorrow I may say "ask nvidia then " :) Thank you for your quick reply. Yes, I am using an HDMI-HDMI cable with no adapters. I have tried bot booting with the external monitor already attached and attaching/reattaching it later. No SVGA plugs. The monitor is an Acer S230HL monitor. I am using the nouveau driver and inxi reports the presence of both Intel UHD Graphics 620 and Nvidia GM108M (GeForce 940MX).
Re: Xrandr and external monitor
On January 1, 2025 6:20:20 PM EST, H wrote: >On January 1, 2025 5:53:06 PM EST, Fungal-net > wrote: >> >>> I just discovered running xrandr --listmonitors that, while the >>internal laptop monitor is labeled eDP-1, xrandr identifies the >>external monitor as using DP-1 although it uses the laptop >>HDMI-connector. Further, while mate hardware display monitor also >>identifies it as using DP-1 - possibly based on xrandr output - the >>monitor itself tells me it is connected using its HDMI1 connector. >>xrandr does report the correct display resolution, though. >> >>Are both ends of the cable hdmi, no adaptors? Usually hdmi - hdmi or >>dp - dp seem pretty accurate, while when you go from one to the other >>they are a bit unreliable. Is the monitor on before you boot, or are >>you connecting while the system has booted? >> >>Pretty much all guis use xrandr output. Since you are not listing the >>make and model of the monitor do a search and see if firmware are >>available specific to this monitor. Also which kernel are you using >>(different versions tend to behave a little different). >>In most cases the chipset in the monitor provides the firmware needed >>to properly identify itself in the system, but I've seen many >>deviations. Do you also have svga plugs on both? >> >>Last question, are gfx native intel/amd or is there something like >>nvidia involved? It is not a good day to be mean to a stranger but >>tomorrow I may say "ask nvidia then " :) > >Thank you for your quick reply. Yes, I am using an HDMI-HDMI cable with >no adapters. I have tried bot booting with the external monitor already >attached and attaching/reattaching it later. No SVGA plugs. > >The monitor is an Acer S230HL monitor. > >I am using the nouveau driver and inxi reports the presence of both >Intel UHD Graphics 620 and Nvidia GM108M (GeForce 940MX). The kernel is: Linux dell 5.14.0-503.15.1.el9_5.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Nov 26 17:24:29 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Re: Xrandr and external monitor (H)
On January 1, 2025 7:14:41 PM EST, Muhammad Ahsan wrote: >Just my two cents. > >In the good old days, when I faced similar problems, I used to manually >set >the resolution and location of external monitor. Here is a sample >command from >one of my old scripts: > >$ xrandr --output LVDS1 --mode 1366x768 --rate 60 --right-of HDMI1 > >You can try adopting the above to your own setup and setting the >resolution >manually. > >Another possibility is to install Nvidia proprietary graphics driver >and see >if it makes any difference. > >HTH! Yes, I have done so using xrandr. However, it does not work by just listing the resolution 1920 x 1080 for the external monitor, I have to add scale 2x2 to the xrandr command. Even so, the wallpaper background scales oddly, does not repeat in a consistent fashion on the display, and, while I can drag a window opened on the laptop display over to the external monitor and it looks ok, if I maximize it, it does not fill the entire monitor but only 1/4. If I open eg. a terminal window, it also scales to 1/4 of the surface. Clearly there is/are bug(s) but where? I surmise it's because the laptop display is UHD at 3840 x 2160 and the external monitor runs at /lower/ resolution. Most often the opposite is true. I would love to help find the bug/bugs and get this working!
Re: Xrandr and external monitor (H)
On January 4, 2025 10:24:38 AM EST, Muhammad Ahsan wrote:
>As per log, you seem to be missing the `modesetting` driver. On Debian
>based distros, this is provided via `xserver-xorg-core` package. Can
>you ensure that this package is installed?
>
>
>
>On Sat, 04 Jan 2025 12:00:02 +
>xorg-requ...@lists.x.org wrote:
>
>> Send xorg mailing list submissions to
>> xorg@lists.x.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.x.org/mailman/listinfo/xorg
>> or, via email, send a message with subject or body 'help' to
>> xorg-requ...@lists.x.org
>>
>> You can reach the person managing the list at
>> xorg-ow...@lists.x.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of xorg digest..."
>>
>>
>> Today's Topics:
>>
>>1. Re: Xrandr and external monitor (H)
>>
>>
>>
>--
>>
>> Message: 1
>> Date: Fri, 03 Jan 2025 15:52:03 -0500
>> From: H
>> To: xorg@lists.x.org
>> Subject: Re: Xrandr and external monitor
>> Message-ID: <81a2cba6-177c-4d5a-b816-338ea1f8d...@meddatainc.com>
>> Content-Type: text/plain; charset=utf-8
>>
>> On January 3, 2025 5:20:38 AM EST, Fungal-net
>> wrote:
>> >On Friday, January 3rd, 2025 at 12:49 AM, H
>> >wrote:
>> >> Forgot to attach the file but doing it now.
>> >
>> >I have a shortcut function in my zsh which looks for (EE) in
>> >Xorg.log The first thing I would do after seeing this log is to
>> >install the xorg xf86 packages for fbdev and vesa then attempt to
>> >run again and rescan for errors. Subsequent errors and warnings
>> >would be meaningless after the first. In the arch ecosystem those
>> >pkgs are marked as xf86-video-{fbdev,vesa} on debian/rh may have
>> >slightly different names.
>>
>> What would the function be of fbdev and vesa?
>>
>> Quick googling suggests the former is deprecated and replaced by DRM
>> and I am afraid I do not understand the role vesa would play with the
>> nouveau driver in use? Are both vesa and nouveau needed?
>>
>>
>> --
>>
>> Subject: Digest Footer
>>
>> ___
>> xorg mailing list
>> xorg@lists.x.org
>> https://lists.x.org/mailman/listinfo/xorg
>>
>>
>> --
>>
>> End of xorg Digest, Vol 233, Issue 6
>>
I just checked to log file and found:
[22.361] (==) Matched modesetting as autoconfigured driver 0
[22.361] (II) LoadModule: "modesetting"
[22.361] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[22.371] (II) Module modesetting: vendor="X.Org Foundation"
[22.371] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
Does this not mean the modesetting driver /is/ loaded or am I missing something?
Re: Xrandr and external monitor (H)
On January 5, 2025 9:14:28 PM GMT-05:00, H wrote: >On January 5, 2025 7:32:48 PM GMT-05:00, Muhammad Ahsan > wrote: >> > >>> I just checked to log file and found: >>> >>> [22.361] (==) Matched modesetting as autoconfigured driver 0 >>> [22.361] (II) LoadModule: "modesetting" >>> [22.361] (II) Loading >>> /usr/lib64/xorg/modules/drivers/modesetting_drv.so [22.371] (II) >>> Module modesetting: vendor="X.Org Foundation" [22.371] (II) >>> modesetting: Driver for Modesetting Kernel Drivers: kms >>> >>> Does this not mean the modesetting driver /is/ loaded or am I >missing >>> something? >> >>Indeed the driver is loaded, however in the very first pastebin log, >>this module wasn't loaded (ref. https://pastebin.com/a9an6Y7M). >>I have missed the second log file link/attachment >>(attachment-0001.ksh). >>Looking at it confirms modesetting's successful loading. >> >>Can you provide more details about the external screen(s) you are >>trying >>to attach e.g. make, model, resolution etc.? >> >>Best >>--- >>Ahsan >>--- >> >> >>> >>> -- >>> >>> Subject: Digest Footer >>> >>> ___ >>> xorg mailing list >>> xorg@lists.x.org >>> https://lists.x.org/mailman/listinfo/xorg >>> >>> >>> -- >>> >>> End of xorg Digest, Vol 233, Issue 7 >>> > >Note that the pastebin file is not mine. The external monitor is an >Acer S230HL monitor running at 1920 x 1200 and connected via HDMI at >bot ends, ie. including the laptop HDMI port which xrandr misidentifies >as DP-1. The Dell Inspiron 7570 laptop has a UHD display running at >3840 x 2880 pixels. Muhammad (and others), Do you have any ideas on the below? It would be great to hopefully fix this.
Xrandr and external monitor
Running the latest version of Rocky Linux fully updated and Mate on a Dell Inspiron 7570 laptop with a UHD display, i.e. 3840 x 2160 pixels. I would like to attach two external monitors and initially experimented with a Dell dock model 3100 and the latest version of the DisplayLink and evdi drivers. However, although the Mate display applet shows the correct resolution for the laptop display itself and for the external monitor which is running at 1920 x 1080 pixels, the resolution on the second, external display is more like 640 x 480 pixels. While I initially thought this was due to a bug in the DisplayLink/evdi drivers, I see the same issue when I connect the monitor directly to the HDMI output on the laptop itself, ie. DisplayLink/evdi are presumably not involved although they are installed, nor is the dock of course. I just discovered running xrandr --listmonitors that, while the internal laptop monitor is labeled eDP-1, xrandr identifies the external monitor as using DP-1 although it uses the laptop HDMI-connector. Further, while mate hardware display monitor also identifies it as using DP-1 - possibly based on xrandr output - the monitor itself tells me it is connected using its HDMI1 connector. xrandr does report the correct display resolution, though. Thus, it looks like xrandr misreads the configuration feeding it to mate. But, I guess it could also be the BIOS perhaps? I just updated the BIOS to the very latest version and saw no difference. Could this be an X11 bug (I am indeed running X11 and not Wayland)? How should I troubleshoot it? Appreciate ideas!
Re: Re[2]: looking for help on multimonitor setup
On March 11, 2025 4:11:54 PM EDT, Guy Rouillier wrote: >On 3/9/2025 7:33:57 AM, "Marco Moock" wrote: >>Have you tried to change the output directly and removing the custom >>xorg.conf? >I've been silently observing this conversation. I've been using Ubuntu > >MATE >and Linux Mint MATE for years without an xorg.conf (and many years >before >that with an xorg.conf.) I don't remember when the conf file became >optional. >I've been able to get the multi-monitor set up I want by using the GUI >desktop >configuration tools. > >-- >Guy Rouillier > >> I am taking the opportunity to jump in with my related problem. My laptop running Rocky Linux 9 and Mate desktop has a UHD display running at 3840 x 2160 resolution whereas my external monitor runs at 1920 x 1080. I cannot get the external monitor to use this latter resolution, at startup it seems to default to 640 x 480 or similar Does anyone have experience with an external display running at a lower resolution than the laptop display itself?
Re: looking for help on multimonitor setup
On March 11, 2025 11:18:03 PM EDT, Django Reinhard wrote: >Hi, > >> Does anyone have experience with an external display running at a >lower >> resolution than the laptop display itself? > >Not with a laptop, but my second pc has 2 monitors connected with >different >resolution. KDE does recognize them correctly and I can position them >by drag >and drop in the screen settings. No problem so far. > >My problem was/is, that I'm looking for a desktop that spans multiple >monitors, which apparently does not exists for the reason of different >sized >monitors. I understand your issue but did not know if a laptop was involved. I am hoping to find someone with a laptop with a UHD display and an external monitor running at a /lower/ resolution. I need to be able to establish where the problem lies, with: (1) Mate; (2) X; or (3) the video driver...
Sending the clipboard content to another application
Hello list, warning: I'm a beginner in X GUI matters. The only thing I managed is to send give the input focus and sending the Ctrl+v key (from Emacs under XFCE) to other windows. This is working in principle but my target application (Ansys, a tcl/tk frame) requires additionally a Return key to digest the input. The problem is now that the Return key arrives earlier then the clipboard content and I don't have any idea how to wait for the right moment to send it. Thanks Dieter -- Best wishes H. Dieter Wilhelm Darmstadt, Germany ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
xserver-xorg-ati does not reactivate monitor after hibernate
I'm running Linux Mint 17.2 with a Radeon HD 5770 card. When I restart the computer after hibernating, the monitor remains in low-energy mode. That means it is not receiving a signal from the card. I have tried pressing Ctrl+Alt+Del, which should bring up the Quit dialog with the Shutdown button as focus. And sure enough, after I press RETURN, the computer shuts down. I have also tried Ctrl+Alt+F1 but the monitor remains off. If I type blindly, I can log in and enter `sudo shutdown -r now` and sure enough, the computer reboots. Everything seems to be working but the monitor signal. What can I do to fix this? -- Don't stop where the ink does. Shawn ___ 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
