Re: display issue after f37 weekly patching. [closed]

On 5/4/23 12:59 PM, home user wrote: (f37) I just finished doing my weekly "dnf upgrade" patches.  I then rebooted. My workstation is acting like it has only 1 monitor (it has 2). The display looks like a pixel is about twice as big as what it should be.  That is, everything looks big. The "NVI

Re: display issue after f37 weekly patching.

On 5/4/23 12:59 PM, home user wrote: (f37) I just finished doing my weekly "dnf upgrade" patches.  I then rebooted. My workstation is acting like it has only 1 monitor (it has 2). The display looks like a pixel is about twice as big as what it should be.  That is, everything looks big. The "NVI

Re: display problem (probably OT?)

Do you know what the max supported resolution is of both monitors? If both are capable of the same resolution then it may simply be that the one with the current wrong resolution needs to be changed in the display setup to match. I think the nvidia-settings tool can also adjust the monitor resolu

Re: display problem (probably OT?)

On 4/9/22 7:37 PM, George N. White III wrote: On Sat, 9 Apr 2022 at 22:00, home user > wrote: On 4/9/22 6:28 PM, George N. White III wrote: > > Maybe this will help: > How to get a dual monitor setup with mixed DPI working on Xorg – The > Mid

Re: display problem (probably OT?)

On Sat, 2022-04-09 at 21:28 -0300, George N. White III wrote: > I think Xorg makes one big "window" large enough to include both > monitors. 96 dpi is the default. I've only used dual monitors on > Xorg a few times, and the monitors were identical. Many years ago I ran dual monitors for a while,

Re: display problem (probably OT?)

On Sat, 9 Apr 2022 at 22:00, home user wrote: > On 4/9/22 6:28 PM, George N. White III wrote: > > > > Maybe this will help: > > How to get a dual monitor setup with mixed DPI working on Xorg – The > > Midnight Sun (lguruprasad.in) > > < > https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-du

Re: display problem (probably OT?)

On 4/9/22 6:28 PM, George N. White III wrote: On Sat, 9 Apr 2022 at 21:03, home user > wrote: On 4/9/22 4:20 PM, Roger Heflin wrote: > you need to look for the section that says Screen #0/#1 and the next few > lines will the the stuff you care abou

Re: display problem (probably OT?)

On Sat, 9 Apr 2022 at 21:03, home user wrote: > On 4/9/22 4:20 PM, Roger Heflin wrote: > > you need to look for the section that says Screen #0/#1 and the next few > > lines will the the stuff you care about (size/dpi). > > > > On Sat, Apr 9, 2022 at 11:37 AM home user >

Re: display problem (probably OT?)

On 4/9/22 4:20 PM, Roger Heflin wrote: you need to look for the section that says Screen #0/#1 and the next few lines will the the stuff you care about (size/dpi). On Sat, Apr 9, 2022 at 11:37 AM home user > wrote: On 4/9/22 10:00 AM, Roger Heflin wrote:

Re: display problem (probably OT?)

you need to look for the section that says Screen #0/#1 and the next few lines will the the stuff you care about (size/dpi). On Sat, Apr 9, 2022 at 11:37 AM home user wrote: > On 4/9/22 10:00 AM, Roger Heflin wrote: > > Check that both monitors are running the same resolution. > > How do I do th

Re: display problem (probably OT?)

On 4/9/22 10:00 AM, Roger Heflin wrote: Check that both monitors are running the same resolution. How do I do that? Also run "xdpyinfo" (rpm is xdpyinfo if you don't have it installed, I don't know if this tool works on wayland or not) and see if the listed size of the screens and dpi is sim

Re: display problem (probably OT?)

Check that both monitors are running the same resolution. Also run "xdpyinfo" (rpm is xdpyinfo if you don't have it installed, I don't know if this tool works on wayland or not) and see if the listed size of the screens and dpi is similar on both monitors. I have seen some devices that the EDID

Re: display problem (probably OT?)

On Mon, 4 Apr 2022 at 23:15, home user wrote: > [... snip ...] But windows and text are obviously bigger on this new monitor > than on the remaining older Dell U2711. Is there a way of making things appear > the same size on the P2412H (too big) as on the U2711 (about right)? This problem pe

Re: display problem (probably OT?)

(replying to both of George White's posts) My e-mail service provider apparently thought both of your posts (and several other posts Fedora users list posts to other threads) were junk.  So I did not see them until a few days later.  But your attempts to help are appreciated.  The friend who g

Re: display problem (probably OT?)

On 4/2/22 8:21 PM, home user wrote: (f34; gnome (is that relevant?), NVIDIA Corporation GK106 [GeForce GTX 660], Dell U2711) This is a dual-monitor home workstation. This afternoon, the left monitor suddenly started displaying only dim vertical stripes and lines and a black background, nothin

Re: display problem (probably OT?)

On 4/3/22 9:25 PM, Tim via users wrote: On Sun, 2022-04-03 at 14:26 -0600, home user wrote: "unearthed"? I know that isn't meant literally, but I don't know what you do mean. What is "unearthed" in this context? Two-pin mains plug vs three-pin mains plug (live, neutral, earth). aaa-Ha.

Re: display problem (probably OT?)

On Sun, 2022-04-03 at 14:26 -0600, home user wrote: > "unearthed"? I know that isn't meant literally, but I don't know > what you do mean. What is "unearthed" in this context? Two-pin mains plug vs three-pin mains plug (live, neutral, earth). -- uname -rsvp Linux 3.10.0-1160.59.1.el7.x86_64

Re: display problem (probably OT?)

On Sun, 2022-04-03 at 14:35 -0600, home user wrote: > On 4/3/22 2:15 PM, Samuel Sieb wrote: > > On 4/3/22 13:09, home user wrote: > > > On 4/3/22 1:20 PM, Joe Zeff wrote: > > > > On 4/3/22 13:13, home user wrote: > > > > > Assuming it's the monitor, is it realistically possible to replace > > > >

Re: display problem (probably OT?)

On 4/3/22 2:15 PM, Samuel Sieb wrote: On 4/3/22 13:09, home user wrote: On 4/3/22 1:20 PM, Joe Zeff wrote: On 4/3/22 13:13, home user wrote: Assuming it's the monitor, is it realistically possible to replace bad components (a cpu, memory, etc.) within the monitor, or are such components avail

Re: display problem (probably OT?)

On 4/3/22 1:58 PM, Tim via users wrote: On Sun, 2022-04-03 at 13:13 -0600, home user wrote: Assuming it's the monitor, is it realistically possible to replace bad components (a cpu, memory, etc.) within the monitor, or are such components available only to monitor manufacturers? If replacement

Re: display problem (probably OT?)

On Sun, Apr 3, 2022 at 4:10 PM home user wrote: > On 4/3/22 1:20 PM, Joe Zeff wrote: > > On 4/3/22 13:13, home user wrote: > >> Assuming it's the monitor, is it realistically possible to replace bad > >> components (a cpu, memory, etc.) within the monitor, or are such > >> components available on

Re: display problem (probably OT?)

On 4/3/22 13:09, home user wrote: On 4/3/22 1:20 PM, Joe Zeff wrote: On 4/3/22 13:13, home user wrote: Assuming it's the monitor, is it realistically possible to replace bad components (a cpu, memory, etc.) within the monitor, or are such components available only to monitor manufacturers?  If

Re: display problem (probably OT?)

On 4/3/22 1:20 PM, Joe Zeff wrote: On 4/3/22 13:13, home user wrote: Assuming it's the monitor, is it realistically possible to replace bad components (a cpu, memory, etc.) within the monitor, or are such components available only to monitor manufacturers?  If replacement is possible, how can

Re: display problem (probably OT?)

On Sun, 2022-04-03 at 13:13 -0600, home user wrote: > Assuming it's the monitor, is it realistically possible to replace > bad components (a cpu, memory, etc.) within the monitor, or are such > components available only to monitor manufacturers? If replacement > is possible, how can I determine w

Re: display problem (probably OT?)

On Sun, 3 Apr 2022 at 16:20, Joe Zeff wrote: > On 4/3/22 13:13, home user wrote: > > Assuming it's the monitor, is it realistically possible to replace bad > > components (a cpu, memory, etc.) within the monitor, or are such > > components available only to monitor manufacturers? If replacement

Re: display problem (probably OT?)

On 4/3/22 13:13, home user wrote: Assuming it's the monitor, is it realistically possible to replace bad components (a cpu, memory, etc.) within the monitor, or are such components available only to monitor manufacturers?  If replacement is possible, how can I determine which components are bad

Re: display problem (probably OT?)

On 4/2/22 10:57 PM, Samuel Sieb wrote: Thank-you, Samuel. On 4/2/22 19:21, home user wrote: (f34; gnome (is that relevant?), NVIDIA Corporation GK106 [GeForce GTX 660], Dell U2711) This is a dual-monitor home workstation. This afternoon, the left monitor suddenly started displaying only dim

Re: display problem (probably OT?)

On Sat, 2 Apr 2022 at 23:21, home user wrote: > (f34; gnome (is that relevant?), NVIDIA Corporation GK106 [GeForce GTX > 660], Dell U2711) > > This is a dual-monitor home workstation. > > This afternoon, the left monitor suddenly started displaying only dim > vertical stripes and lines and a blac

Re: display problem (probably OT?)

On 4/2/22 19:21, home user wrote: (f34; gnome (is that relevant?), NVIDIA Corporation GK106 [GeForce GTX 660], Dell U2711) This is a dual-monitor home workstation. This afternoon, the left monitor suddenly started displaying only dim vertical stripes and lines and a black background, nothing

Re: Display Manager Configuration Files

On 5/11/20 10:50 pm, Ed Greshko wrote: On 05/11/2020 11:07, Stephen Morris wrote: found it is not a good idea to use systemctl to stop the current DM before enabling and starting the new DM. For future reference, the best way to change to a different DM is to use systemctl --force enable (DM

Re: Display Manager Configuration Files

On 05/11/2020 11:07, Stephen Morris wrote: found it is not a good idea to use systemctl to stop the current DM before  enabling and starting the new DM. For future reference, the best way to change to a different DM is to use systemctl --force enable (DM to switch to) Then reboot. --- The ke

Re: Display Manager Configuration Files

On 5/11/20 2:07 pm, Stephen Morris wrote: On 4/11/20 10:25 pm, Ed Greshko wrote: On 04/11/2020 17:24, Stephen Morris wrote: Hi,     Which configuration file identifies which display manager is being used, and which configuration file identifies which desktop that dm will launch?     The issue

Re: Display Manager Configuration Files

On 4/11/20 10:25 pm, Ed Greshko wrote: On 04/11/2020 17:24, Stephen Morris wrote: Hi,     Which configuration file identifies which display manager is being used, and which configuration file identifies which desktop that dm will launch?     The issue I have is, I have the Fedora Astronomy spi

Re: Display Manager Configuration Files

On 04/11/2020 17:24, Stephen Morris wrote: Hi,     Which configuration file identifies which display manager is being used, and which configuration file identifies which desktop that dm will launch?     The issue I have is, I have the Fedora Astronomy spin at F32 level. I think it is starting S

Re: Display Manager question

David wrote: > Last week, I replaced the file "default.png" in my background directory, > and was delightfully enjoying a new custom backsplash, instead of the new > fancy > one that Fedora has ( light color blue with some rectangular glass cluster > ). > > In my recent update yesterday, somethin

Re: Display Manager question

On 2020-04-07 14:04, David wrote: > Last week, I replaced the file "default.png" in my background directory, > and was delightfully enjoying a new custom backsplash, instead of the new > fancy > one that Fedora has ( light color blue with some rectangular glass cluster ). What file, full path nam

Re: Display Manager and applets

On 06/29/18 00:09, Beartooth wrote: > On Thu, 28 Jun 2018 10:33:20 +0800, Ed Greshko wrote: > > > I haven't yet in this case, but I will, yes. Any two pair of eyes > will indicate an intersection of their lines of sight, but redundancy is > often convenient, especially if the cursor has snu

Re: Display Manager and applets

On 06/28/2018 02:58 PM, Ed Greshko wrote: > On 06/29/18 00:09, Beartooth wrote: >> On Thu, 28 Jun 2018 10:33:20 +0800, Ed Greshko wrote: >> >> >> I haven't yet in this case, but I will, yes. Any two pair of eyes >> will indicate an intersection of their lines of sight, but redundancy is >> o

Re: Display Manager and applets

On 06/29/18 03:25, home user via users wrote: > I don't know what a "panel meny" He mis-typed.  "panel menu" is what he meant -- Conjecture is just a conclusion based on incomplete information. It isn't a fact. signature.asc Description: OpenPGP digital signature ___

Re: Display Manager and applets

On 06/28/2018 12:25 PM, home user via users wrote: > I use Gnome (mostly) and KDE (rarely). I'm not familiar with Mate; I don't > know what a "panel meny" is. But no, you don't need to reboot. If you have the xorg-x11-apps RPM installed, on Mate you can right-click on the panel, select "Add to

Re: Display Manager and applets

I use Gnome (mostly) and KDE (rarely). I'm not familiar with Mate; I don't know what a "panel meny" is. But no, you don't need to reboot. Regardless of which user name I log in as, I launch xeyes from ".bash_profile", and put it into the background. This way, the xeyes process and display is

Re: Display Manager and applets

On Thu, 28 Jun 2018 10:33:20 +0800, Ed Greshko wrote: > On 06/28/18 00:25, Beartooth wrote: >> Unless I'm more confused than usual, I'm currently running lxdm >> (set to MATE) on F28. I'm glad to have a display manager that works; >> but it denies me the two applets I use most. I normally res

Re: Display Manager and applets

On 06/28/18 00:25, Beartooth wrote: > Unless I'm more confused than usual, I'm currently running lxdm > (set to MATE) on F28. I'm glad to have a display manager that works; but > it denies me the two applets I use most. I normally restrict each > workspace to a single app, and keep 18 spac

Re: Display Manager and applets

On Wed, 27 Jun 2018 16:25:36 + (UTC) Beartooth wrote: > Also, eyes in each of four panels are by far the easiest way > for my ancient eyeballs to find the mouse cursor; and the current > setup has no eyes at all, afaict. I think Bill is right about xeyes, but if you can't find that, th

Re: Display Manager and applets

On Wed, 27 Jun 2018 16:25:36 + (UTC) Beartooth wrote: > Unless I'm more confused than usual, I'm currently running > lxdm (set to MATE) on F28. I'm glad to have a display manager that > works; but it denies me the two applets I use most. I normally > restrict each workspace to a single

Re: Display Manager and applets

> Also, eyes in each of four panels are by far the easiest way for > my ancient eyeballs to find the mouse cursor; and the current setup has > no eyes at all, afaict. > > Clue, please? The nearest thing I can think of is "xeyes". With help from other members of this list, I instal

Re: Display cmd within shell

On 16Jun2018 10:24, Marek Howard wrote: On Tue, 2018-06-12 at 07:52 +1000, Cameron Simpson wrote: Personally I like "set -x". I've even got a tiny line script called "set-x" which goes: #!/bin/sh set -x exec "$@" and many scripts which do variants on: trace= [ -t 2 ] && trace=set-x

Re: Display cmd within shell

On Tue, 2018-06-12 at 07:52 +1000, Cameron Simpson wrote: > Personally I like "set -x". I've even got a tiny line script called "set-x" > which goes: > > #!/bin/sh > set -x > exec "$@" > > and many scripts which do variants on: > > trace= > [ -t 2 ] && trace=set-x # at least during

Re: Display cmd within shell

> On Jun 11, 2018, at 4:50 PM, Gordon Messmer wrote: > > On 06/11/2018 02:31 PM, Bev in TX wrote: >> >> It’s an option of the builtin set command. >> >> set … >> … When options are specified, they set or unset shell attributes. …. >> -v Print shell input lines as they are read. > >

Re: Display cmd within shell

On 11Jun2018 14:02, Gordon Messmer wrote: On 06/11/2018 05:40 AM, bruce wrote: #-- this doesn't quite work.. as it generates the complete "ls... output" but it does display the cmd and the resulting num of the ls files.. (set -x; ls -al /cloud_nfs_parse/austincc*__parse.dat | wc -l ) Bash doe

Re: Display cmd within shell

On 06/11/2018 02:31 PM, Bev in TX wrote: It’s an option of the builtin set command. set … … When options are specified, they set or unset shell attributes. …. -v Print shell input lines as they are read. Yeah, that also *kinda* works.  That'll print lines as they're read, not as the

Re: Display cmd within shell

> On Jun 11, 2018, at 4:02 PM, Gordon Messmer wrote: > > On 06/11/2018 05:40 AM, bruce wrote: >> #-- this doesn't quite work.. as it generates the complete "ls... >> output" but it does display the cmd and the resulting num of the ls >> files.. >> (set -x; ls -al /cloud_nfs_parse/austincc*__par

Re: Display cmd within shell

On 06/11/2018 05:40 AM, bruce wrote: #-- this doesn't quite work.. as it generates the complete "ls... output" but it does display the cmd and the resulting num of the ls files.. (set -x; ls -al /cloud_nfs_parse/austincc*__parse.dat | wc -l ) Bash doesn't have a mode in which it echos a command

Re: Display cmd within shell

On Mon, 11 Jun 2018 at 09:41, bruce wrote: > Hi. > > Running a centos/fed box, and trying to craft a simple shell test to > run a bunch of commands where the command is displayed as well as the > output > > Ie. The following cmd might return 10 (the num of the files if the cmd > is run from the c

Re: Display cmd within shell

On Mon, Jun 11, 2018 at 08:40:59AM -0400, bruce wrote: > Running a centos/fed box, and trying to craft a simple shell test to > run a bunch of commands where the command is displayed as well as the > output > > Ie. The following cmd might return 10 (the num of the files if the cmd > is run from th

Re: Display cmd within shell

On Mon, 2018-06-11 at 08:40 -0400, bruce wrote: > Hi. > > Running a centos/fed box, and trying to craft a simple shell test to > run a bunch of commands where the command is displayed as well as the > output > > Ie. The following cmd might return 10 (the num of the files if the cmd > is run from

Re: Display cmd within shell

> On Jun 11, 2018, at 7:40 AM, bruce wrote: > > Hi. > > Running a centos/fed box, and trying to craft a simple shell test to > run a bunch of commands where the command is displayed as well as the > output > > Ie. The following cmd might return 10 (the num of the files if the cmd > is run fro

Re: Display Manager Lagging After Last Update

On 03/06/18 05:08, Stephen Morris wrote: > On 5/3/18 7:36 am, Ed Greshko wrote: >> On 03/05/18 04:18, Stephen Morris wrote: >>> As a matter of interest, which version of the nvidia drivers are you using? >> >> 390.25-3   And I don't use wayland as performance in KDE is horrible > > From the negativ

Re: Display Manager Lagging After Last Update

On 5/3/18 7:36 am, Ed Greshko wrote: On 03/05/18 04:18, Stephen Morris wrote: As a matter of interest, which version of the nvidia drivers are you using? 390.25-3   And I don't use wayland as performance in KDE is horrible From the negativo17 repositories I'm using the source code for the sa

Re: Display Manager Lagging After Last Update

On 03/05/18 04:18, Stephen Morris wrote: > As a matter of interest, which version of the nvidia drivers are you using? 390.25-3   And I don't use wayland as performance in KDE is horrible -- If simple questions can be answered with a simple google query then why are there sso many of them?

Re: Display Manager Lagging After Last Update

On 4/3/18 9:02 pm, Ed Greshko wrote: On 03/04/18 16:16, Stephen Morris wrote: Thanks Ed, I made that change and it rectified the lagging issues with gdm and gnome. Now to work out why dkms hasn't compiled the nvidia driver under the new kernel. FWIW, the lagging issues may be a byproduct of yo

Re: Display Manager Lagging After Last Update

On 03/04/18 16:16, Stephen Morris wrote: > Thanks Ed, I made that change and it rectified the lagging issues with gdm and > gnome. Now to work out why dkms hasn't compiled the nvidia driver under the > new > kernel. FWIW, the lagging issues may be a byproduct of your video driver. Anyway, whil

Re: Display Manager Lagging After Last Update

On 04/03/2018 13:39, Ed Greshko wrote: On 03/04/18 09:57, Stephen Morris wrote: Thanks Ed, I tried Gnome under Wayland and Xorg and as documented in the problem description, even though gnome shell lags with gdm, when gnome under Xorg is started the lag disappears. The only difference in my case

Re: Display Manager Lagging After Last Update

On 03/04/18 09:57, Stephen Morris wrote: > Thanks Ed, I tried Gnome under Wayland and Xorg and as documented in the > problem > description, even though gnome shell lags with gdm, when gnome under Xorg is > started the lag disappears. The only difference in my case is that the issue > was > not c

Re: Display Manager Lagging After Last Update

On 4/3/18 11:37 am, Ed Greshko wrote: On 03/04/18 08:25, Stephen Morris wrote: My issue starts with gdm, with gnome shell taking up to 800% of the cpu and causing, ctrl+alt+F2 to switch to another login to time out, and if I launch gnome from gdm the issue with gnome shell continues and causes

Re: Display Manager Lagging After Last Update

On 03/04/18 08:25, Stephen Morris wrote: > My issue starts with gdm, with gnome shell taking up to 800% of the cpu and > causing, ctrl+alt+F2 to switch to another login to time out, and if I launch > gnome > from gdm the issue with gnome shell continues and causes gnome itself to lag. > If I > lo

Re: Display Manager Lagging After Last Update

On 2/3/18 4:45 am, Jon LaBadie wrote: I had very slow logins from sddm and lightdm. Not as bad from gdm, but still not good. My culprit was staring an Xvnc server gnome session from my Mate autostart. Clue was 50 gnome processes I owned after logging into a Mate session. jl My issue starts

Re: Display Manager Lagging After Last Update

On 01/03/18 08:45, Ed Greshko wrote: On 03/01/18 05:16, Stephen Morris wrote: On 28/2/18 10:11 am, Ed Greshko wrote: On 02/28/18 04:37, Stephen Morris wrote: I might be getting confused with Ubuntu, but I thought there was a .conf file somewhere that held the specification of the default displ

Re: Display Manager Lagging After Last Update

On 03/01/18 05:16, Stephen Morris wrote: > On 28/2/18 10:11 am, Ed Greshko wrote: >> On 02/28/18 04:37, Stephen Morris wrote: >>> I might be getting confused with Ubuntu, but I thought there was a .conf >>> file >>> somewhere that held the specification of the default display manager that >>> cou

Re: Display Manager Lagging After Last Update

On 28/2/18 10:11 am, Ed Greshko wrote: On 02/28/18 04:37, Stephen Morris wrote: I might be getting confused with Ubuntu, but I thought there was a .conf file somewhere that held the specification of the default display manager that could easily be edited to swap between any of the available disp

Re: Display Manager Lagging After Last Update

On 02/28/18 05:37, Stephen Morris wrote: > > If I remember correctly, I think in F25 or F26 lightdm was the display > manager used > by default No. It depended on the "spin" or Desktop you installed.    If you installed "Workstation"  aka GNOME it has always been gdm.  If you installed the KDE

Re: Display Manager Lagging After Last Update

On 02/28/18 04:37, Stephen Morris wrote: > I might be getting confused with Ubuntu, but I thought there was a .conf file > somewhere that held the specification of the default display manager that > could > easily be edited to swap between any of the available display managers that > you > happen

Re: Display Manager Lagging After Last Update

On 28/2/18 7:46 am, Joe Zeff wrote: On 02/27/2018 12:37 PM, Stephen Morris wrote: I'm not using sddm because when I tried it, I didn't like its presentation layer, and the same applies to kdm. Have you tried lightdm? If I remember correctly, I think in F25 or F26 lightdm was the display m

Re: Display Manager Lagging After Last Update

On 02/27/2018 12:37 PM, Stephen Morris wrote: I'm not using sddm because when I tried it, I didn't like its presentation layer, and the same applies to kdm. Have you tried lightdm? ___ users mailing list -- users@lists.fedoraproject.org To unsubscri

Re: Display Manager Lagging After Last Update

On 26/2/18 9:50 pm, Ed Greshko wrote: On 02/26/18 18:47, Ed Greshko wrote: ll /etc/systemd/system/display-manager.service   will point to what you're using. systemctl status display-manager also will tell you Thanks Ed, that tells me I'm using gdm. I might be getting confused with Ubuntu,

Re: Display Manager Lagging After Last Update

On 02/26/18 18:47, Ed Greshko wrote: > ll /etc/systemd/system/display-manager.service   will point to what you're > using. systemctl status display-manager also will tell you -- A motto of mine is: When in doubt, try it out signature.asc Description: OpenPGP digital signature

Re: Display Manager Lagging After Last Update

On 02/26/18 18:39, Stephen Morris wrote: >     I have forgotten whether I'm running gdm or kdm, and I've forgotten where > to > look to find out, but since the last system update I did two days ago, when > the > display manager is displaying the list of user who can log in, cursor > movements an

Re: Display setting problem with 4k monitor

On 01/25/2017 10:01 AM, Massimo Canonico wrote: > If someone has a similar problem, I suggest to read this page: > > https://wiki.archlinux.org/index.php/HiDPI > > It helps me a lot, but I'm still having problem with the monitors. > Zooming/panning make the display blurry and (as suggested in th

Re: Display setting problem with 4k monitor

If someone has a similar problem, I suggest to read this page: https://wiki.archlinux.org/index.php/HiDPI It helps me a lot, but I'm still having problem with the monitors. Zooming/panning make the display blurry and (as suggested in the web page) I should try to adjust the "sharpness" paramet

Re: Display fedora 24 on MSI GE62 6QD

Sorry, There are the out of lspci === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)

Re: display link driver?

On 16.01.2015 03:38, CS DBA wrote: > All; > > anyone know how to get a displaylink usb monitor to work with Fedora 21? > (Asus MB168B+) > > > Thanks in advance > Support Linux with DL-3000 Series Chips https://www.change.org/p/displaylink-support-linux-with-dl-3000-series-chips airlied - a

Re: Display resolution -

On 10/02/14 13:12, Bruno Wolff III wrote: Nothing I have tried seems to work except xrandr. You don't need to use system-config-display. Just plop a similar xorg.conf file with timing data appropriate for your monitor. I though you had already collected that and should be able to use it in

Re: Display resolution -

On Thu, Oct 02, 2014 at 11:30:28 -0600, jd1008 wrote: Hi Bruno, Your conf file comment line says Xorg configuration created by system-config-display But I cannot find it in my fc20 installation. You must be running an older fedora?? The file was created a long time ago. The machine with the

Re: Display resolution -

On 10/02/2014 09:13 AM, Bruno Wolff III wrote: On Wed, Oct 01, 2014 at 19:17:19 -0400, "Bob Goodwin - Zuni, Virginia, USA" wrote: I need to swap monitors as the backlight in my old Dell monitor grows dim. I have a Viewsonic vx2035WM that Fedora can never get the resolution right for. I've go

Re: Display resolution -

On Thu, Oct 02, 2014 at 12:46:15 -0400, "Bob Goodwin - Zuni, Virginia, USA" wrote: On 10/02/14 11:13, Bruno Wolff III wrote: I have a monitor that doesn't properly do EDID and I use the following in /etc/X11/xorg.conf: # Xorg configuration created by system-config-display ]$ ll /etc/X11/xo

Re: Display resolution -

On 10/02/14 11:13, Bruno Wolff III wrote: I have a monitor that doesn't properly do EDID and I use the following in /etc/X11/xorg.conf: # Xorg configuration created by system-config-display ]$ ll /etc/X11/xorg.conf ls: cannot access /etc/X11/xorg.conf: No such file or directory # yum install

Re: Display resolution -

On Wed, Oct 01, 2014 at 19:17:19 -0400, "Bob Goodwin - Zuni, Virginia, USA" wrote: I need to swap monitors as the backlight in my old Dell monitor grows dim. I have a Viewsonic vx2035WM that Fedora can never get the resolution right for. I've gone through the following process using informati

Re: Display issues

On 03.04.2014 01:07, CS_DBA wrote: > All; > > We have a laptop running fedora 20, we plugged it into an hdmi > projector, then the fun started... > > the second monitor never connected, since then if we go to > system settings --> "Display and Monitor" we see the second monitor > (greyed out)

Re: Re: Display setting problem -

On Mon, Nov 25, 2013 at 5:50 PM, Richard Sewill wrote: > > I hesitate trying to answer this question because what I am doing may be > wrong. > > I tried the following on F18. > > I edited the line, found in file /etc/default/grub, which starts > GRUB_CMDLINE_LINUX="rd.md=0 ... rhgb quiet" > append

Re: Display setting problem

On 26.11.2013 23:58, Bob Goodwin - Zuni, Virginia, USA wrote: > Ok, it looks like it sent it to http://ur1.ca/g3pzw Thy 'lightdm.log': [+1.00s] DEBUG: Got signal from X server :0 [+1.00s] DEBUG: Connecting to XServer :0 [+1.00s] DEBUG: Starting greeter [+1.01s] DEBUG: Started session 974 with ser

Re: Display setting problem

On 26/11/13 16:38, poma wrote: Feel free to paste the content of the 'lightdm.log' athttp://fpaste.org so it can be studied. If you do, one for the "RandR" round, and one for the script of yours. poma Ok, it looks like it sent it to http://ur1.ca/g3pzw -- http://www.qrz.com/db/W2BOD Box 10 F

Re: Display setting problem

On 26.11.2013 18:06, Bob Goodwin - Zuni, Virginia, USA wrote: > On 25/11/13 18:28, poma wrote: >> "--output" selects a particular output mode, so it should work. >> Move a 'monitors.xml' so it doesn't interfere with setup, >> $ mv $HOME/.config/monitors.xml $HOME/.config/monitors.xml-backup >> and

Re: Display setting problem -

On 25/11/13 18:28, poma wrote: "--output" selects a particular output mode, so it should work. Move a 'monitors.xml' so it doesn't interfere with setup, $ mv $HOME/.config/monitors.xml $HOME/.config/monitors.xml-backup and disable that session script of yours. Check what's happening via '/var/log

Re: Display setting problem -

On 25/11/13 12:50, Richard Sewill wrote: I hesitate trying to answer this question because what I am doing may be wrong. I tried the following on F18. I edited the line, found in file /etc/default/grub, which starts GRUB_CMDLINE_LINUX="rd.md=0 ... rhgb quiet" appending strings so it had GRUB_C

Re: Display setting problem -

On 25.11.2013 22:23, Bob Goodwin - Zuni, Virginia, USA wrote: > Then when I select the "Display" GUI it offers me 1680x1050 sure enough but > does not actually select it. > > I still have to run my script to get other than 1024x768. > > It doesn't seem to pay attention to lightdm.conf? > "--o

Re: Display setting problem -

On 25/11/13 12:29, poma wrote: On 25.11.2013 17:27, Bob Goodwin - Zuni, Virginia, USA wrote: Ok, then I assume that to mean there is no better way. Please this time try to read carefully from top to bottom. http://thread.gmane.org/gmane.linux.redhat.fedora.general/425665 Ok, so I have don

Re: Re: Display setting problem -

I hesitate trying to answer this question because what I am doing may be wrong. I tried the following on F18. I edited the line, found in file /etc/default/grub, which starts GRUB_CMDLINE_LINUX="rd.md=0 ... rhgb quiet" appending strings so it had GRUB_CMDLINE_LINUX="rd.md=0 ... rhgb quiet" drm_km

Re: Display setting problem -

On 25.11.2013 17:27, Bob Goodwin - Zuni, Virginia, USA wrote: > Ok, then I assume that to mean there is no better way. > Please this time try to read carefully from top to bottom. http://thread.gmane.org/gmane.linux.redhat.fedora.general/425665 > This message is an interesting experiment in tha

Re: Re: Display setting problem -

On 11/25/2013 04:39 AM, poma wrote: On 24.11.2013 17:00, Bob Goodwin - Zuni, Virginia, USA wrote: Anyone know a better way to deal with this? As it stands it is just one of the things I do every morning after booting the computer ... This question is already answered in detail. poma Ok,

Re: Display setting problem CORRECTION-

On 24.11.2013 17:00, Bob Goodwin - Zuni, Virginia, USA wrote: > CORRECTION: Fedora-19 > > I have a ViewSonic VX2035wm LCD Display monitor on this computer that is > not recognized by Fedora-19. in order to get a reasonable display I have > to run /usr/bin/xrandr -s 1680x1050 after I am logged in

  1   2   >