Announcement

Collapse
No announcement yet.

Kubuntu user causes monitor to display at wrong resolution-- for just one user only.

Collapse
This topic has been answered.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Kubuntu user causes monitor to display at wrong resolution-- for just one user only.

    This morning I discovered that my screen appears to be set for the wrong resolution and displays everything larger than it should be. I assumed that this was due to a setting on the monitor, but eventually determined that both the monitor and kubuntu (display configuration) are set for 2560X1440. Eventually I tried setting up a second user, and was surprised to find that the problem was solved; for this new user everything displays properly.
    So something is wrong with the settings for my initial user but OK for the new user. Where might I look to figure this out?
  • Answer selected by taxpayer at Yesterday, 05:00 PM.

    it has to be somewhere in your .config or .local directories because everything your user is saved in one or the other (or both).

    from my notes:

    Code:
    # brute force troubleshooting...
    mv ~/.config ~/.configBORKED
    mv ~/.local ~/.localBORKED
    # logout and log back in again to force plasma to recreate the folders with default settings
    # open split views of the folders for comparison and file copy
    dolphin --split ~/.config ~/.configBORKED
    dolphin --split ~/.local ~/.localBORKED
    # copy back half of the BORKED folder contents at a time and relog to see if issue returns
    # if it does, then delete the folder again, relog, and only copy half of that previous half
    # repeat until the culprit is found, then finally, copy back everything BUT that culprit bit
    ​

    Comment


      #2
      it has to be somewhere in your .config or .local directories because everything your user is saved in one or the other (or both).

      from my notes:

      Code:
      # brute force troubleshooting...
      mv ~/.config ~/.configBORKED
      mv ~/.local ~/.localBORKED
      # logout and log back in again to force plasma to recreate the folders with default settings
      # open split views of the folders for comparison and file copy
      dolphin --split ~/.config ~/.configBORKED
      dolphin --split ~/.local ~/.localBORKED
      # copy back half of the BORKED folder contents at a time and relog to see if issue returns
      # if it does, then delete the folder again, relog, and only copy half of that previous half
      # repeat until the culprit is found, then finally, copy back everything BUT that culprit bit
      ​
      some stuff i did: https://github.com/droidgoo

      Intel® Core™ i7-14700K | 64 GiB of RAM | AMD RX 6800

      Comment


        #3
        Thanks for that. I wasn't sure which directories to delete. Turned out that the problem was in .config. Restored now.

        Comment

        Users Viewing This Topic

        Collapse

        There are 0 users viewing this topic.

        Working...
        X