I now tried to change it in the kde settings/display. I set it to 30 Hz (to be able to use the apply button), and the blur was gone. Changed it to 60 Hz what makes the screen even clearer.
I also tried to change the resolution in kde settings/display, blur is gone.
Everytime the monitor settings are changing, it will be set to the right settings. But if I then switch screens, these settings are been overwritten!?
No change. All the font settings I also tried before.
yes the settings are being resetted, but i have no idea why…
and what do you mean exactly with switching screens?
If I turn the second monitor off and then back on. The normal state should be off. So I could turn it on if needed.
I can do the “switch” by uncheck the “active” box in settings/display (and then back). Or I can do it with the systray-app. I do it with the systray tool, but the result is the same.
I don’t even need to “switch”. If I am on the “unifying displays” (backtranslated from german - it is the same display on both screens), then I only need to press the same status:“unifying displays”, and the blur is back.
Luckily now I know how to get rid of it (just changing refresh-rate once and back again), but sure it would be great to figure out what causes this and how to avoid this behaviour in the first place.
it might sound a little bit curious, but can you check with a different hdmi-cable if the problem persist ? “magic” malfunction caused by chinese-crackers-cables are a common problem.
Sounds not that curios 
but I don’t want to work at the cable management right now. And as I stated, this problem did not occur on the manjaro-xfce setup. So, I doubt it for now.
maybe compare the nvidia.conf from xfce live usb session with yours that is posted above …
also installing the drivers for the intel graphic could be tried out, you have nothing to lose
install them:
sudo mhwd -i pci video-linux
reboot
That’s a good idea. I will start a live system later. And the intel graphic I will install on my test partition.
So, there is no difference in the nvidia.conf from the xfce system.
And installing the intel drivers on the test installation did also not change anything in the behaviour.
If you have any other idea, I will try it. But if not, I although want to thank you very much for your time and help.
At least I can work on my second screen without blur - only have to do this Hz change everytime I use it.
Maybe this issue is qt related (I think xfce does not use it, or not build on it) or plasma related. I read an article about plasma 5.26 should solve a problem with blurry displaying applications after scaling. Maybe this will help?
Since I am new to manjaro (as first arch based system) I would like to know if “rolling release” in this case means, that sooner or later a new version of kde plasma will become available on every manjaro system too?
Just if someone can see anything in this, here is again the output of “journalctl -b0 -p4 --no-pager” in exact the moments when I switch to my second screen and it is getting blurry:
Aug 08 03:57:01 ManjaroTower kernel: BUG: scheduling while atomic: irq/129-s-nvidi/493/0x00000002
Aug 08 03:57:01 ManjaroTower kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device rfkill qrtr nvidia_uvm(POE) nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel joydev hid_cherry kvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec irqbypass snd_hda_core crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel r8169 snd_pcm aesni_intel mei_hdcp mei_wdt snd_timer crypto_simd iTCO_wdt realtek cryptd intel_pmc_bxt mdio_devres iTCO_vendor_support rapl mousedev at24 mei_me mxm_wmi drm_kms_helper intel_cstate syscopyarea i2c_i801 snd sysfillrect libphy intel_uncore psmouse soundcore sysimgblt fb_sys_fops pcspkr i2c_smbus mei intel_pch_thermal wmi video mac_hid acpi_pad drm fuse crypto_user bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_logitech_hidpp hid_logitech_dj
Aug 08 03:57:01 ManjaroTower kernel: usbhid serio_raw atkbd libps2 vivaldi_fmap crc32c_intel sr_mod cdrom xhci_pci xhci_pci_renesas i8042 serio
Aug 08 03:57:01 ManjaroTower kernel: Preemption disabled at:
Aug 08 03:57:01 ManjaroTower kernel: [<0000000000000000>] 0x0
Aug 08 03:57:01 ManjaroTower kernel: CPU: 0 PID: 493 Comm: irq/129-s-nvidi Tainted: P W OE 5.19.0-1-rt10-MANJARO #1
Aug 08 03:57:01 ManjaroTower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B150 Pro4/D3, BIOS P2.30 07/18/2016
Aug 08 03:57:01 ManjaroTower kernel: Call Trace:
Aug 08 03:57:01 ManjaroTower kernel: <TASK>
Aug 08 03:57:01 ManjaroTower kernel: dump_stack_lvl+0x44/0x5c
Aug 08 03:57:01 ManjaroTower kernel: __schedule_bug.cold+0x81/0x8e
Aug 08 03:57:01 ManjaroTower kernel: __schedule+0xdcb/0x11d0
Aug 08 03:57:01 ManjaroTower kernel: ? push_rt_tasks+0x13/0x20
Aug 08 03:57:01 ManjaroTower kernel: ? raw_spin_rq_unlock+0x17/0x70
Aug 08 03:57:01 ManjaroTower kernel: ? rt_mutex_setprio+0x199/0x490
Aug 08 03:57:01 ManjaroTower kernel: schedule_rtlock+0x1e/0x40
Aug 08 03:57:01 ManjaroTower kernel: rtlock_slowlock_locked+0x3d1/0xf90
Aug 08 03:57:01 ManjaroTower kernel: rt_read_lock+0x6a/0x1b0
Aug 08 03:57:01 ManjaroTower kernel: ep_poll_callback+0x3b/0x230
Aug 08 03:57:01 ManjaroTower kernel: ? _nv012128rm+0x40/0x90 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: __wake_up_common+0x70/0x140
Aug 08 03:57:01 ManjaroTower kernel: __wake_up_common_lock+0x76/0xb0
Aug 08 03:57:01 ManjaroTower kernel: _nv034999rm+0x59/0x80 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? _nv033052rm+0xab/0xc0 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? _nv031273rm+0xf4/0x120 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? _nv023112rm+0x5dd/0x11d0 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? _nv023112rm+0x5eb/0x11d0 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? _nv023583rm+0x8c/0x1a0 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? _nv026094rm+0x5e/0xc0 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? _nv010474rm+0x19f/0x310 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? _nv026104rm+0x14f/0x1b0 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? _nv000649rm+0x10b/0x140 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? disable_irq_nosync+0x10/0x10
Aug 08 03:57:01 ManjaroTower kernel: ? rm_isr_bh+0x1c/0x60 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? nvidia_isr_kthread_bh+0x1b/0x40 [nvidia]
Aug 08 03:57:01 ManjaroTower kernel: ? irq_thread_fn+0x1c/0x60
Aug 08 03:57:01 ManjaroTower kernel: ? irq_thread+0xfd/0x1b0
Aug 08 03:57:01 ManjaroTower kernel: ? irq_finalize_oneshot.part.0+0xd0/0xd0
Aug 08 03:57:01 ManjaroTower kernel: ? irq_thread_check_affinity+0xd0/0xd0
Aug 08 03:57:01 ManjaroTower kernel: ? kthread+0x107/0x130
Aug 08 03:57:01 ManjaroTower kernel: ? kthread_complete_and_exit+0x20/0x20
Aug 08 03:57:01 ManjaroTower kernel: ? ret_from_fork+0x1f/0x30
Aug 08 03:57:01 ManjaroTower kernel: </TASK>
Aug 08 03:57:02 ManjaroTower kernel: BUG: scheduling while atomic: irq/129-s-nvidi/493/0x00000002
Aug 08 03:57:02 ManjaroTower kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device rfkill qrtr nvidia_uvm(POE) nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel joydev hid_cherry kvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec irqbypass snd_hda_core crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel r8169 snd_pcm aesni_intel mei_hdcp mei_wdt snd_timer crypto_simd iTCO_wdt realtek cryptd intel_pmc_bxt mdio_devres iTCO_vendor_support rapl mousedev at24 mei_me mxm_wmi drm_kms_helper intel_cstate syscopyarea i2c_i801 snd sysfillrect libphy intel_uncore psmouse soundcore sysimgblt fb_sys_fops pcspkr i2c_smbus mei intel_pch_thermal wmi video mac_hid acpi_pad drm fuse crypto_user bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_logitech_hidpp hid_logitech_dj
Aug 08 03:57:02 ManjaroTower kernel: usbhid serio_raw atkbd libps2 vivaldi_fmap crc32c_intel sr_mod cdrom xhci_pci xhci_pci_renesas i8042 serio
Aug 08 03:57:02 ManjaroTower kernel: Preemption disabled at:
Aug 08 03:57:02 ManjaroTower kernel: [<0000000000000000>] 0x0
Aug 08 03:57:02 ManjaroTower kernel: CPU: 0 PID: 493 Comm: irq/129-s-nvidi Tainted: P W OE 5.19.0-1-rt10-MANJARO #1
Aug 08 03:57:02 ManjaroTower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B150 Pro4/D3, BIOS P2.30 07/18/2016
Aug 08 03:57:02 ManjaroTower kernel: Call Trace:
Aug 08 03:57:02 ManjaroTower kernel: <TASK>
Aug 08 03:57:02 ManjaroTower kernel: dump_stack_lvl+0x44/0x5c
Aug 08 03:57:02 ManjaroTower kernel: __schedule_bug.cold+0x81/0x8e
Aug 08 03:57:02 ManjaroTower kernel: __schedule+0xdcb/0x11d0
Aug 08 03:57:02 ManjaroTower kernel: ? push_rt_tasks+0x13/0x20
Aug 08 03:57:02 ManjaroTower kernel: ? raw_spin_rq_unlock+0x17/0x70
Aug 08 03:57:02 ManjaroTower kernel: ? rt_mutex_setprio+0x199/0x490
Aug 08 03:57:02 ManjaroTower kernel: schedule_rtlock+0x1e/0x40
Aug 08 03:57:02 ManjaroTower kernel: rtlock_slowlock_locked+0x3d1/0xf90
Aug 08 03:57:02 ManjaroTower kernel: ? os_acquire_spinlock+0xe/0x20 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _nv034990rm+0xc/0x20 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _raw_spin_unlock_irqrestore+0x23/0x60
Aug 08 03:57:02 ManjaroTower kernel: rt_spin_lock+0x3f/0x60
Aug 08 03:57:02 ManjaroTower kernel: __wake_up_common_lock+0x60/0xb0
Aug 08 03:57:02 ManjaroTower kernel: ep_poll_callback+0x100/0x230
Aug 08 03:57:02 ManjaroTower kernel: __wake_up_common+0x70/0x140
Aug 08 03:57:02 ManjaroTower kernel: __wake_up_common_lock+0x76/0xb0
Aug 08 03:57:02 ManjaroTower kernel: _nv034999rm+0x59/0x80 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _nv033052rm+0xab/0xc0 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _nv031273rm+0xf4/0x120 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _nv022978rm+0x6b/0xb0 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _nv022978rm+0x76/0xb0 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _nv023112rm+0xf47/0x11d0 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _nv023583rm+0x8c/0x1a0 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _nv026094rm+0x5e/0xc0 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _nv010474rm+0x19f/0x310 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _nv026104rm+0x14f/0x1b0 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? _nv000649rm+0x10b/0x140 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? disable_irq_nosync+0x10/0x10
Aug 08 03:57:02 ManjaroTower kernel: ? rm_isr_bh+0x1c/0x60 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? nvidia_isr_kthread_bh+0x1b/0x40 [nvidia]
Aug 08 03:57:02 ManjaroTower kernel: ? irq_thread_fn+0x1c/0x60
Aug 08 03:57:02 ManjaroTower kernel: ? irq_thread+0xfd/0x1b0
Aug 08 03:57:02 ManjaroTower kernel: ? irq_finalize_oneshot.part.0+0xd0/0xd0
Aug 08 03:57:02 ManjaroTower kernel: ? irq_thread_check_affinity+0xd0/0xd0
Aug 08 03:57:02 ManjaroTower kernel: ? kthread+0x107/0x130
Aug 08 03:57:02 ManjaroTower kernel: ? kthread_complete_and_exit+0x20/0x20
Aug 08 03:57:02 ManjaroTower kernel: ? ret_from_fork+0x1f/0x30
Aug 08 03:57:02 ManjaroTower kernel: </TASK>
Aug 08 03:57:04 ManjaroTower kernel: BUG: scheduling while atomic: irq/129-s-nvidi/493/0x00000002
Aug 08 03:57:04 ManjaroTower kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device rfkill qrtr nvidia_uvm(POE) nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel joydev hid_cherry kvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec irqbypass snd_hda_core crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel r8169 snd_pcm aesni_intel mei_hdcp mei_wdt snd_timer crypto_simd iTCO_wdt realtek cryptd intel_pmc_bxt mdio_devres iTCO_vendor_support rapl mousedev at24 mei_me mxm_wmi drm_kms_helper intel_cstate syscopyarea i2c_i801 snd sysfillrect libphy intel_uncore psmouse soundcore sysimgblt fb_sys_fops pcspkr i2c_smbus mei intel_pch_thermal wmi video mac_hid acpi_pad drm fuse crypto_user bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_logitech_hidpp hid_logitech_dj
Aug 08 03:57:04 ManjaroTower kernel: usbhid serio_raw atkbd libps2 vivaldi_fmap crc32c_intel sr_mod cdrom xhci_pci xhci_pci_renesas i8042 serio
Aug 08 03:57:04 ManjaroTower kernel: Preemption disabled at:
Aug 08 03:57:04 ManjaroTower kernel: [<0000000000000000>] 0x0
Aug 08 03:57:04 ManjaroTower kernel: CPU: 0 PID: 493 Comm: irq/129-s-nvidi Tainted: P W OE 5.19.0-1-rt10-MANJARO #1
Aug 08 03:57:04 ManjaroTower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B150 Pro4/D3, BIOS P2.30 07/18/2016
Aug 08 03:57:04 ManjaroTower kernel: Call Trace:
Aug 08 03:57:04 ManjaroTower kernel: <TASK>
Aug 08 03:57:04 ManjaroTower kernel: dump_stack_lvl+0x44/0x5c
Aug 08 03:57:04 ManjaroTower kernel: __schedule_bug.cold+0x81/0x8e
Aug 08 03:57:04 ManjaroTower kernel: __schedule+0xdcb/0x11d0
Aug 08 03:57:04 ManjaroTower kernel: ? push_rt_tasks+0x13/0x20
Aug 08 03:57:04 ManjaroTower kernel: ? raw_spin_rq_unlock+0x17/0x70
Aug 08 03:57:04 ManjaroTower kernel: ? rt_mutex_setprio+0x199/0x490
Aug 08 03:57:04 ManjaroTower kernel: schedule_rtlock+0x1e/0x40
Aug 08 03:57:04 ManjaroTower kernel: rtlock_slowlock_locked+0x3d1/0xf90
Aug 08 03:57:04 ManjaroTower kernel: ? os_acquire_spinlock+0xe/0x20 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _nv034990rm+0xc/0x20 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _raw_spin_unlock_irqrestore+0x23/0x60
Aug 08 03:57:04 ManjaroTower kernel: rt_spin_lock+0x3f/0x60
Aug 08 03:57:04 ManjaroTower kernel: __wake_up_common_lock+0x60/0xb0
Aug 08 03:57:04 ManjaroTower kernel: ep_poll_callback+0x100/0x230
Aug 08 03:57:04 ManjaroTower kernel: __wake_up_common+0x70/0x140
Aug 08 03:57:04 ManjaroTower kernel: __wake_up_common_lock+0x76/0xb0
Aug 08 03:57:04 ManjaroTower kernel: _nv034999rm+0x59/0x80 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _nv033052rm+0xab/0xc0 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _nv031273rm+0xf4/0x120 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _nv022978rm+0x6b/0xb0 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _nv022978rm+0x76/0xb0 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _nv023112rm+0xf47/0x11d0 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _nv023583rm+0x8c/0x1a0 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _nv026094rm+0x5e/0xc0 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _nv010474rm+0x19f/0x310 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _nv026104rm+0x14f/0x1b0 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? _nv000649rm+0x10b/0x140 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? disable_irq_nosync+0x10/0x10
Aug 08 03:57:04 ManjaroTower kernel: ? rm_isr_bh+0x1c/0x60 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? nvidia_isr_kthread_bh+0x1b/0x40 [nvidia]
Aug 08 03:57:04 ManjaroTower kernel: ? irq_thread_fn+0x1c/0x60
Aug 08 03:57:04 ManjaroTower kernel: ? irq_thread+0xfd/0x1b0
Aug 08 03:57:04 ManjaroTower kernel: ? irq_finalize_oneshot.part.0+0xd0/0xd0
Aug 08 03:57:04 ManjaroTower kernel: ? irq_thread_check_affinity+0xd0/0xd0
Aug 08 03:57:04 ManjaroTower kernel: ? kthread+0x107/0x130
Aug 08 03:57:04 ManjaroTower kernel: ? kthread_complete_and_exit+0x20/0x20
Aug 08 03:57:04 ManjaroTower kernel: ? ret_from_fork+0x1f/0x30
Aug 08 03:57:04 ManjaroTower kernel: </TASK>There is mentioned BUG at least in two lines. But I understand not, what these outputs are telling.
And here is the output at the moment I change the refresh-rate and it’s getting clear again:
Aug 08 04:02:11 ManjaroTower systemsettings5[30336]: kf.coreaddons: "Could not load plugin from kcm_kscreen: Die dynamische Bibliothek konnte nicht gefunden werden."
Aug 08 04:02:11 ManjaroTower plasmashell[664]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1"
Aug 08 04:02:11 ManjaroTower plasmashell[664]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Aug 08 04:02:11 ManjaroTower plasmashell[664]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1"
Aug 08 04:02:11 ManjaroTower plasmashell[664]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Aug 08 04:02:11 ManjaroTower plasmashell[664]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Aug 08 04:02:11 ManjaroTower plasmashell[664]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Aug 08 04:02:14 ManjaroTower kwin_x11[619]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 37922, resource id: 73400328, major code: 18 (ChangeProperty), minor code: 0i have really no idea what to do next…
in the first logs you are still using the 5.19 kernel so switch back to the 5.15
and in the second logs there is really nothing pointing to it… except you have there pulseaudio issues … either use pulse or better switch to pipewire, since youre planning it to use as a audio machine:
sudo pacman -S manjaro-pipewire
it will give you pulse dependency issues, so remove them first, then run the command again, and select wireplumber, then reboot
yes its very possible that the issue will be fixed with some update - either with a plasma related or nvidia related, but who knows when it will happen
I just have installed manjaro-pipewire. There are just left “pulseaudio-ctl pulseaudio-qt lib32-libpulse libpulse” and I don’t know if these are needed.
I will switch back to 5.15.
So, should we let it as it is for now? At least it is solved partial. We can assume, that the blur comes from a missetting of the refresh-rate on the second monitor when switching. And I know how to fix it manually everytime I switch. Just set in settings->display the rate on another rate and back to hit apply, and the screen is clear again.
We don’t know what causes this behaviour, but I can live with it. And if a future update will fix this, I will be still more happy
I’d say, for know it’s fine.
as i already posted, check with a good, high quality hdmi-cable and do not trust chinese-crackers.
wrong detection of the frequency to an external device is a typical indication that the hardware-connection between the devices does not work properly
you can remove also these 2 pulse leftovers:
pulseaudio-ctl pulseaudio-qt
you could test with different cables as olli suggests, just to be sure that its not hardware related… and how is the nvidia connected, via riser cable?
The cable is the original Samsung cable, that came with the monitor. I don’t know what “riser cable” is. And I don’t want to change the cable right now. This would mean to reinstall the cable managment which for now is no option for me.
And don’t you think this would be an issue on xfce also?
The main monitor is a 4k Samsung, connected via a 15m HDMI to the nvidia card.
The second monitor is a Full-HD Samsung, connected via a 1.5m HDMI cable to a HDMI-DisplayPort-Adapter to my nvidia.
“pulseaudio-qt” seems to be needed by kdeconnect. So I removed pulseaudio-ctl only.
i meant with riser how the nvidia gpu is connected, via riser cable, or directly in the motherboard
if you dont use kdeconnect you may remove it also …
It’s directly connected to the motherboard.
I use kdeconnect. Just for filetransfer, but I let the package in place.
So, I have changed the cable. Same problem. I have switched inputs and got my first screen connected over the DP-Adapter and the second screen directly via HDMI. Same problem. So I now can exclude the cable and the adapter.
And when I switched inputs my main screen got to “screen 1” and my second screen got to “screen 0”. So the order is not a thing.
But I have found out, that indeed it’s the refresh rate, that will be changed when the monitor is deativated and then activated again (or “scanned” again, when I hit the “two screens-button” in the taskbar although both screens are on).
Here is an output of “qdbus org.kde.KWin /KWin supportInformation” (one portion of it).
Here is the output before doing anything (both screens on):
Screens
=======
Multi-Head: no
Active screen follows mouse: yes
Number of Screens: 2
Screen 0:
---------
Name: HDMI-0
Geometry: 0,0,1920x1080
Scale: 1
Refresh Rate: 60000
Screen 1:
---------
Name: DP-1
Geometry: 0,0,1920x1080
Scale: 1
Refresh Rate: 60000Here after hitting the “two screens button” in the task bar (same effect as deativating-reactivating screen):
Screens
=======
Multi-Head: no
Active screen follows mouse: yes
Number of Screens: 2
Screen 0:
---------
Name: HDMI-0
Geometry: 0,0,1920x1080
Scale: 1
Refresh Rate: 60000
Screen 1:
---------
Name: DP-1
Geometry: 0,0,1920x1080
Scale: 1
Refresh Rate: 60053The refresh rate will be changed from 60.000 to 60.053 unbelievable, that this little change does have an impact like this.
Is there anybody of you that has two screens (and maybe better though one of it 4k one Full-HD) who can compare the output of the above command before and after “switching” screens?
I would like to know if this is a software bug or maybe bad communication from the monitor itself???
There is no absolute need for it. I’m happy already, but I’m really curios.
EDIT: here is a part of “xrandr -q --verbose” output after triggering the issue:
1920x1080 (0x1ea) 74.250MHz +HSync +VSync Interlace *current
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.75KHz
v: height 1080 start 1084 end 1094 total 1124 clock 60.05HzSo the difference isn’t that little. The qdbus information only gives the refresh rate of the vertical screen, but in the horizontal it’s half of what it’s supposed to.
Hi,
I just want to let you know what I did as a little workaround regarding this issue:
I downloaded the mini-app “text command” into my taskbar and set the command xrandr --output DP-1 --mode 1920x1080 --rate 60 to it. So now everytime I switch to my second monitor, I then hit this button and can work with a clear screen.
And I want to thank you for all your time and help.