Turning off one monitor moves all windows to second monitor

Screen resolution, 3D Acceleration, nVidia, ATI
Forum rules
Before you post please read this
Post Reply
Shinbobikal
Level 1
Level 1
Posts: 12
Joined: Fri Jul 10, 2020 1:21 pm

Turning off one monitor moves all windows to second monitor

Post by Shinbobikal »

I installed a fresh and updated Linux Mint 20 Cinnamon and noticed that when I turn off my monitor (1920x1080), which is connected via DisplayPort (Graphics card + monitor), all windows are moved to my second monitor (1366x768, card: DisplayPort -> monitor: VGA).
This doesn't happen the other way around (turning off other screen), even when changing the "main monitor" setting.
Changing the virtual xserver-location of the screens also doesn't change anything (it's not the common "all windows on first screen" problem).

This would somehow be expected if the second monitor would be turned on, but it's off.

On Ubuntu 19.10 and I think Mint 19 this didn't happen and I'd like the windows to stay where they are if I turn off my monitor.

Edit: When the screensaver starts or the system is locked the windows aren't moved.

Code: Select all

Graphics:
  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] 
  vendor: Tul driver: amdgpu v: kernel bus ID: 2b:00.0 chip ID: 1002:731f 
  Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,radeon,vesa resolution: 1366x768~60Hz 
  OpenGL: renderer: AMD Radeon RX 5700 XT (NAVI10 DRM 3.35.0 
  5.4.0-40-generic LLVM 10.0.0) 
  v: 4.6 Mesa 20.0.8 direct render: Yes
Any ideas?
Top
Shinbobikal
Level 1
Level 1
Posts: 12
Joined: Fri Jul 10, 2020 1:21 pm

Re: Turning off one monitor moves all windows to second monitor

Post by Shinbobikal »

Don't know if that's the same root course, but when the windows are moved, the background image on the main monitor is cropped to the size of the second monitor and the remaining space is black.
Top
User avatar
SMG
Level 11
Level 11
Posts: 3737
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Turning off one monitor moves all windows to second monitor

Post by SMG »

Please provide the full inxi -Fxxxrz and some information about the monitors. Are they both the same? The information you provided only shows one monitor attached.

Which monitor is the one listed as the Primary in the Displays app? If you turn off the primary display then I think it would be expected that all windows go to the one remaining display.
LM20.1 Cinnamon
Top
Shinbobikal
Level 1
Level 1
Posts: 12
Joined: Fri Jul 10, 2020 1:21 pm

Re: Turning off one monitor moves all windows to second monitor

Post by Shinbobikal »

> Please provide the full inxi -Fxxxrz
I don't know how info about audio, drives, network or repos would help here.

Here the full output of System and Graphics:

Code: Select all

System:    Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 4.6.7 wm: muffin 4.6.3 
           dm: LightDM 1.30.0 Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: Tul 
           driver: amdgpu v: kernel bus ID: 2b:00.0 chip ID: 1002:731f 
           Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: AMD Radeon RX 5700 XT (NAVI10 DRM 3.39.0 5.4.0-56-generic LLVM 11.0.0) 
           v: 4.6 Mesa 20.0.8 direct render: Yes
> and some information about the monitors. Are they both the same?
Main monitor: Iiyama 1920x1080 DisplayPort -> DisplayPort
Second monitor: Fujitsu 1366x768, card: DisplayPort -> monitor: VGA

> The information you provided only shows one monitor attached.
inxi only shows my secondary monitor, never the primary

> Which monitor is the one listed as the Primary in the Displays app?
My main monitor (1920x1080) is marked as primary.

> If you turn off the primary display then I think it would be expected that all windows go to the one remaining display.
Well, but that's not what I want, especially when the second monitor is off, it works as I intend on Ubuntu 19.10 and I think Mint 19.

I tested again and turning off the main monitor doesn't move the windows, only when I turn the main monitor on again the windows are moved to the second monitor so I think it's probably a bug.
There would be no reason I can think of the windows should be moved from the monitor I'm turning on again.
Top
User avatar
SMG
Level 11
Level 11
Posts: 3737
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Turning off one monitor moves all windows to second monitor

Post by SMG »

Shinbobikal wrote: ↑
Wed Dec 02, 2020 12:21 pm
 > Please provide the full inxi -Fxxxrz
I don't know how info about audio, drives, network or repos would help here.
You asked for help and I asked for the information you are supposed to provide in your first post according to the forum rules, specifically section 5 of READ: How To Get Help!.

I do not even know what type of computer and processor you have. AMD graphics are in the kernel. Maybe a newer kernel would be more appropriate for your situation, but I am not able to make that recommendation because you have not supplied the information necessary to make that type of recommendation.

The system information you provided is showing N/A for the compiler. That is not what is usually in that field, so it is possible you have made modifications to your system which is a factor in this issue. I can usually glean whether someone might have made modifications from either repo information or the Info section of inxi.

It is unusual to only have one monitor show up in inxi yet both of them to show up in the Displays app. It can often indicate an issue related to graphics drivers. In addition to the possibility of updated graphics drivers in the kernel, there are also updated drivers available for your specific card AMD Radeon™ RX 5700 XT Drivers & Support.

By the way, support for the ports on your graphic card come from the graphics driver (as well as the actual hardware). So whether or not the card remembers you had a monitor attached and turned on or off and relays that information to Mint is something handled by the graphics driver and the memory of the card.

There is also the oddball chance that which displayport is being used might be a factor. Sometimes what works doesn't seem to follow the rules of logic.

In addition, how the drives are partitioned and how full the partitions are can play a role in graphics-related issues. I can't speak to your situation since you have decided not to provide that information.
LM20.1 Cinnamon
Top
Shinbobikal
Level 1
Level 1
Posts: 12
Joined: Fri Jul 10, 2020 1:21 pm

Re: Turning off one monitor moves all windows to second monitor

Post by Shinbobikal »

> Maybe a newer kernel would be more appropriate for your situation
I tried the newest kernel 5.9.12, nothing changed

> so it is possible you have made modifications to your system which is a factor in this issue
The problem even occurs with a Live-Session from the default Mint 20 Install-ISO
(Should have tested it earlier, sry)

> there are also updated drivers available for your specific card
I don't really want to use the Radeon driver from AMD, I tried Mesa 20.2.3 - kisak-mesa PPA and it's the same

> By the way, support for the ports on your graphic card come from the graphics driver (as well as the actual hardware). So whether or not the card remembers you had a monitor attached and turned on or off and relays that information to Mint is something handled by the graphics driver and the memory of the card.
Yes, but, as I said, it works as I intend on Ubuntu 19.10 and Mint 19 with the same mesa and kernel version

> There is also the oddball chance that which displayport is being used might be a factor.
I tried switching the displayport positions and used cables but nothing changed
Top
User avatar
SMG
Level 11
Level 11
Posts: 3737
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Turning off one monitor moves all windows to second monitor

Post by SMG »

Shinbobikal wrote: ↑
Thu Dec 03, 2020 7:57 am
 > Maybe a newer kernel would be more appropriate for your situation
I tried the newest kernel 5.9.12, nothing changed
I was going to recommend trying the 5.8 kernel which is available to you in Update Manager. That 5.8 kernel is currently being supported by Ubuntu (and thus in Ubuntu and Mint systems) while I'm not aware there is system support for the 5.9 kernel.
Shinbobikal wrote: ↑
Thu Dec 03, 2020 7:57 am
 > there are also updated drivers available for your specific card
I don't really want to use the Radeon driver from AMD, I tried Mesa 20.2.3 - kisak-mesa PPA and it's the same
Your card does not use the radeon driver and I did not make a suggestion that it should.

Your card uses the amdgpu driver which AMD makes available as open-source and is included in the Linux kernel. If you check your graphics info, you will see v: kernel after the driver which means the driver came from the kernel.

The link I provided is to the latest AMD driver for your card which is an updated version of the amdgpu driver you are currently using. As AMD fixes bugs and makes improvements they change the driver modules. I do not know the schedule for when those changes make their way in to the amdgpu driver supplied by the kernel. Therefore it may be possible to get a newer driver by installing the files from the AMD website than it is from installing a newer kernel version.

You can check the amdgpu version your computer is using with apt show xserver-xorg-video-amdgpu and then compare that version number with the version in the AMD download files to see what differences there might be. You can check mesa versions with glxinfo -B.

Note: The version number of the AMD website file is not the driver version number. It is a combination of the year it was released and which release during the year it was. You will have to download the file and open it to see which version files are included.
Shinbobikal wrote: ↑
Thu Dec 03, 2020 7:57 am
 > By the way, support for the ports on your graphic card come from the graphics driver (as well as the actual hardware). So whether or not the card remembers you had a monitor attached and turned on or off and relays that information to Mint is something handled by the graphics driver and the memory of the card.
Yes, but, as I said, it works as I intend on Ubuntu 19.10 and Mint 19 with the same mesa and kernel version
I do not know anything about what is used in Ubuntu 19.10. Depending upon which version of Mint 19 you are using, there may be a different version of Xorg being used, so just because the kernel and mesa versions are the same does not preclude there being other differences.
LM20.1 Cinnamon
Top
Shinbobikal
Level 1
Level 1
Posts: 12
Joined: Fri Jul 10, 2020 1:21 pm

Re: Turning off one monitor moves all windows to second monitor

Post by Shinbobikal »

> I was going to recommend trying the 5.8 kernel which is available to you in Update Manager. That 5.8 kernel is currently being supported by Ubuntu (and thus in Ubuntu and Mint systems) while I'm not aware there is system support for the 5.9 kernel.
It's the same with 5.8. For 5.9 I used https://kernel.ubuntu.com/~kernel-ppa/mainline/

Looking through ~.xsession-errors I saw the following errors occuring when I turn my main monitor back on and the windows are moved:

Code: Select all

xrandr-plugin-Message: 15:29:37.570: Existing monitor config (/home/user/.config/cinnamon-monitors.xml) not found during hotplug or laptop lid event. Looking for legacy configuration (monitors.xml)
Cinnamon warning: Log level 16: STACK_OP_LOWER_BELOW: window 0x4000196 not in stack

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.743: Object St.Icon (0x5577e8ccd7f0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:200 (0x7fecc408c1a8 @ 215)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.743: Object St.BoxLayout (0x5577e8caefa0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:201 (0x7fecc408c1a8 @ 255)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.743: Object St.BoxLayout (0x5577e8caefa0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:202 (0x7fecc408c1a8 @ 305)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.743: Object St.BoxLayout (0x5577e8caefa0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:203 (0x7fecc408c1a8 @ 355)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.743: Object St.Icon (0x5577ea9e8030), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:200 (0x7fecc408c1a8 @ 215)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.743: Object St.BoxLayout (0x5577ea9f3770), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:201 (0x7fecc408c1a8 @ 255)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.743: Object St.BoxLayout (0x5577ea9f3770), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:202 (0x7fecc408c1a8 @ 305)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.743: Object St.BoxLayout (0x5577ea9f3770), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:203 (0x7fecc408c1a8 @ 355)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.792: Object St.Icon (0x5577e8ccd7f0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:200 (0x7fecc408c1a8 @ 215)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.821: Object St.BoxLayout (0x5577e8caefa0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:201 (0x7fecc408c1a8 @ 255)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.821: Object St.BoxLayout (0x5577e8caefa0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:202 (0x7fecc408c1a8 @ 305)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.821: Object St.BoxLayout (0x5577e8caefa0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:203 (0x7fecc408c1a8 @ 355)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.821: Object St.Icon (0x5577ea9e8030), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:200 (0x7fecc408c1a8 @ 215)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.821: Object St.BoxLayout (0x5577ea9f3770), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:201 (0x7fecc408c1a8 @ 255)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.821: Object St.BoxLayout (0x5577ea9f3770), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:202 (0x7fecc408c1a8 @ 305)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.821: Object St.BoxLayout (0x5577ea9f3770), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:203 (0x7fecc408c1a8 @ 355)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.863: Object St.Icon (0x5577e8ccd7f0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:200 (0x7fecc408c1a8 @ 215)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.863: Object St.BoxLayout (0x5577e8caefa0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:201 (0x7fecc408c1a8 @ 255)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.863: Object St.BoxLayout (0x5577e8caefa0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:202 (0x7fecc408c1a8 @ 305)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.863: Object St.BoxLayout (0x5577e8caefa0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:203 (0x7fecc408c1a8 @ 355)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.863: Object St.Icon (0x5577ea9e8030), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:200 (0x7fecc408c1a8 @ 215)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.863: Object St.BoxLayout (0x5577ea9f3770), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:201 (0x7fecc408c1a8 @ 255)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.863: Object St.BoxLayout (0x5577ea9f3770), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:202 (0x7fecc408c1a8 @ 305)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.863: Object St.BoxLayout (0x5577ea9f3770), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:203 (0x7fecc408c1a8 @ 355)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.867: Object St.Icon (0x5577e8ccd7f0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:200 (0x7fecc408c1a8 @ 215)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.867: Object St.BoxLayout (0x5577e8caefa0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:201 (0x7fecc408c1a8 @ 255)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.867: Object St.BoxLayout (0x5577e8caefa0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:202 (0x7fecc408c1a8 @ 305)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.867: Object St.BoxLayout (0x5577e8caefa0), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:203 (0x7fecc408c1a8 @ 355)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.867: Object St.Icon (0x5577ea9e8030), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:200 (0x7fecc408c1a8 @ 215)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.867: Object St.BoxLayout (0x5577ea9f3770), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:201 (0x7fecc408c1a8 @ 255)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.867: Object St.BoxLayout (0x5577ea9f3770), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:202 (0x7fecc408c1a8 @ 305)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)

(cinnamon:1863): Cjs-CRITICAL **: 15:29:38.867: Object St.BoxLayout (0x5577ea9f3770), has been already finalized. Impossible to set any property to it.
== Stack trace for context 0x5577e8004020 ==
#0 0x7ffe58d1ed90 b   /usr/share/cinnamon/js/ui/osdWindow.js:203 (0x7fecc408c1a8 @ 355)
#1 0x7ffe58d1ee50 b   self-hosted:916 (0x7fecc42e6670 @ 367)
#2 0x7ffe58d1ef40 b   resource:///org/cinnamon/cjs/modules/signals.js:142 (0x7fecc42d8098 @ 386)
#3 0x5577e829d060 i   /usr/share/cinnamon/js/ui/layout.js:155 (0x7fecc40ce808 @ 52)
#4 0x7ffe58d1fc20 b   self-hosted:916 (0x7fecc42e6670 @ 367)
The file .config/cinnamon-monitors.xml clearly exists with valid content (recreated to be sure)...
Last edited by Shinbobikal on Sat Dec 05, 2020 4:33 pm, edited 1 time in total.
Top
User avatar
SMG
Level 11
Level 11
Posts: 3737
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Turning off one monitor moves all windows to second monitor

Post by SMG »

Shinbobikal wrote: ↑
Sat Dec 05, 2020 10:38 am
For newer kernels I use https://kernel.ubuntu.com/~kernel-ppa/mainline/
Supported kernels are ones tested with the operating system software and made available through updated packages (via terminal or Update Manager). That site is just a listing of compiled kernels. If you are using an unsupported kernel then you are on your own to troubleshoot issues.

I have given you all the ideas I have on this issue.
LM20.1 Cinnamon
Top
Shinbobikal
Level 1
Level 1
Posts: 12
Joined: Fri Jul 10, 2020 1:21 pm

Re: Turning off one monitor moves all windows to second monitor

Post by Shinbobikal »

SMG wrote: ↑
Sat Dec 05, 2020 4:04 pm
 If you are using an unsupported kernel then you are on your own to troubleshoot issues.
I already wrote it's the same with 5.8
I'm going to test the other things you mentioned but from the error log I believe it's something with cinnamon
Top
Post Reply

Return to “Graphics Cards & Monitors”