Weird glitch: Cinnamon windows cutting off when too large

[tpo100ckid]

i don't know why this happens, but it bothers me to no end. having it happen on any given installation of Linux Mint for me is inconsistent
after a popup window is launched anywhere anything that goes over a certain window size is cut off

can anyone help with fixing this? thanks

[mikeflan]

This is probably a graphics card problem. Please type this in a terminal:

Code: Select all

inxi -Fxxxrz

Post the output in "Code" tags. The button that inserts these tags is marked </>

Also start Driver Manager and report back what it shows or says.

[tpo100ckid]

here's the output of inxi -Fxxxrz. sorry for taking so long, only saw this now

Code: Select all

System:
  Kernel: 5.4.0-77-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 5.0.3 wm: muffin 5.0.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: LENOVO product: 81V7 v: Lenovo IdeaPad S145-15API 
  serial: <filter> Chassis: type: 10 v: Lenovo IdeaPad S145-15API 
  serial: <filter> 
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40679WIN serial: <filter> 
  UEFI: LENOVO v: BUCN25WW date: 05/19/2020 
Battery:
  ID-1: BAT0 charge: 22.4 Wh condition: 22.4/30.0 Wh (75%) volts: 8.1/7.4 
  model: LGC L16L2PB2 type: Li-poly serial: <filter> status: Full 
  cycles: 514 
CPU:
  Topology: Quad Core model: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx 
  bits: 64 type: MT MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 33537 
  Speed: 1394 MHz min/max: 1400/2100 MHz boost: enabled Core speeds (MHz): 
  1: 1395 2: 1394 3: 1393 4: 1396 5: 1395 6: 1397 7: 1395 8: 1395 
Graphics:
  Device-1: AMD Picasso vendor: Lenovo driver: amdgpu v: kernel 
  bus ID: 02:00.0 chip ID: 1002:15d8 
  Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz 
  OpenGL: renderer: AMD RAVEN (DRM 3.35.0 5.4.0-77-generic LLVM 11.0.0) 
  v: 4.6 Mesa 20.2.6 direct render: Yes 
Audio:
  Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Lenovo 
  driver: snd_hda_intel v: kernel bus ID: 02:00.1 chip ID: 1002:15de 
  Device-2: AMD Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel 
  v: kernel bus ID: 02:00.6 chip ID: 1022:15e3 
  Sound Server: ALSA v: k5.4.0-77-generic 
Network:
  Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter 
  vendor: Lenovo driver: ath10k_pci v: kernel bus ID: 01:00.0 
  chip ID: 168c:0042 
  IF: wlp1s0 state: up mac: <filter> 
  Device-2: Qualcomm Atheros type: USB driver: btusb bus ID: 3-2:3 
  chip ID: 0cf3:e500 
Drives:
  Local Storage: total: 931.51 GiB used: 23.11 GiB (2.5%) 
  ID-1: /dev/sda vendor: Western Digital model: WD10SPZX-24Z10 
  size: 931.51 GiB speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> 
  rev: 1A05 scheme: GPT 
Partition:
  ID-1: / size: 915.40 GiB used: 23.10 GiB (2.5%) fs: ext4 dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 52.9 C mobo: N/A gpu: amdgpu temp: 52 C 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/megasync.list 
  1: deb https://mega.nz/linux/MEGAsync/xUbuntu_20.04/ ./
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com uma main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:
  Processes: 279 Uptime: 3h 02m Memory: 9.67 GiB used: 3.96 GiB (40.9%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

also, driver manager says i don't have anything to install

[mikeflan]

You have an onboard graphics card (I think). If I were you I would wait for someone in the know to post what you should do. You can go to the Lenovo website and look for a Linux driver for that card. And another thing - if that computer is as new as I think it is you could try the 5.8 kernel if it is available. But again, I would wait for better advice.

[senjoz]

System:
Kernel: 5.4.0-77-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 5.0.3 wm: muffin 5.0.1 dm: LightDM 1.30.0
Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal

At this moment Linux Mint 20.2 Uma is still in beta phase. If you think that a bug is present, you can report it
on Github at https://github.com/linuxmint/mint20.2-beta. You can also try kernel 5.11.

Regards, Jože

[tpo100ckid]

At this moment Linux Mint 20.2 Uma is still in beta phase.

no, no, this isn't new. i've exeprienced this bug since mint 20.0..

You can also try kernel 5.11.

i'll experiment with kernels and see if that works, thank you two

[Moonstone Man]

At this moment Linux Mint 20.2 Uma is still in beta phase.

no, no, this isn't new. i've exeprienced this bug since mint 20.0..

That's irrelevant. You need to go to github if your current problem is with LM 20.2 beta. Would you go to a mechanic and ask them to fix a problem on your previous car?

[tpo100ckid]

so, i got mainline (ubuntu kernel installer app) to try out some different kernels
whilst installing, it complained about missing firmware
so, i download and copy some to a system folder following advice from askubuntu.com
one of the three that i tried also gave out errors during installation with wording that explains little to nothing and that i'm too tired to debug and doubt have any impact on this specifically

report on different kernels and if they made the bug go away:

5.13: the problem is still here but didn't show up until the second time i had to start mint with it
slightly less awful, though - doesn't seem to apply to windowed firefox
5.11: haven't tested yet due to feeling discouraged from what happened with 5.13, hope this is understandable
5.8: same as above. i don't plan on giving up, i'll just probably test these out later than sooner

[Larry78723]

How about posting the results of the following command:

Code: Select all

inxi -Gxx

[tpo100ckid]

How about posting the results of the following command:

Code: Select all

inxi -Gxx

alright:

Code: Select all

Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso vendor: Lenovo driver: amdgpu v: kernel 
           bus ID: 02:00.0 chip ID: 1002:15d8 
           Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: AMD RAVEN (DRM 3.41.0 5.13.0-051300-generic LLVM 11.0.0) v: 4.6 Mesa 20.2.6 
           direct render: Yes 

[tpo100ckid]

I found out what triggers this on Firefox, but not at all what causes it to happen elsewhere, much less what the root of the problem actually is.
Any time I cause a popup to open (e.g. save image as), it shows up.
Or, this might actually have other triggers. I'm not sure.

[Larry78723]

What theme are you using? If it's not a standard theme, it can cause strange problems.

[tpo100ckid]

i usually use mint-y, but it happens with other themes too

[motoryzen]

no, no, this isn't new. i've exeprienced this bug since mint 20.0

" That is irrelevant"

Actually it could be quite relevant since the problem has been going on since mint 20 which launched about a year ago.

Would you go to a mechanic and ask them to fix a problem on your previous car?

He is simply stating a fact that the problem didn't begin with an Alpha or Beta version of Linux Mint. So it could be plenty relevant. It could be the same as saying " I've encountered this same problem old more longer-generation-timeline of this make and model of truck too. Both trucks are f150's regardless of the year model. *shrugs*.

How do you know it's irrelevant if he HAS encountered the same problem since Mint 20? ( which could mean either with Mint 20 also..or Mint 20.0 and 20.1 too).

I'm not saying you're wrong for suggesting the OP visit the applicable github url and report this problem given the OP is dealing with a not-finalized version of Mint. I agree there, but given the posts so far as of 6:59 central time 7-5-21...it doesn't seem enough or all applicable troubleshooting options have been exhausted yet to confirm if the fact that he's on an alpha or beta Mint version as being the main or most solid core part of the problem to back up your " That is irrelevant" claim.

Patience man....Patience.

[tpo100ckid]

He is simply stating a fact that the problem didn't begin with an Alpha or Beta version of Linux Mint. So it could be plenty relevant. (....)

(this is petty and unrelated, but too bad) she, please don't assume (when in doubt, they)
..either way, thanks for pointing out the shittiness in what kadaitcha man's post

[motoryzen]

He is simply stating a fact that the problem didn't begin with an Alpha or Beta version of Linux Mint. So it could be plenty relevant. (....)

(this is petty and unrelated, but too bad) she, please don't assume (when in doubt, they)
..either way, thanks for pointing out the shittiness in what kadaitcha man's post

petty and unrelated

+

she, please don't assume (when in doubt, they)

No it isn't " they" because it's one..person asking for help.

"They " = more than one person. Sorry, but that is first and second grade grammar 101.

So..there's nothing inaccurate about it other than what you just spelled out of you , the OP, being female. Thus, I'm sorry about the incorrect guess. No big deal.no harm or foul. We can't see each other's real faces on here so that simple mistake could happen depending on many things. If someone thought I was female, I'd just say " I'm male btw " and shrug it off..because my user name can be either male or female given it's basically a gender-not-involved type of nickname

*shrugs*

Honestly speaking about Kadaicha Man, he knows his stuff very well and has proven that often. So I'm not doubting what Kadaicha Man said was accurate or correct. He just has had a bad habit of saying things that just is rude sounding or wanting to seem like he wants to bait people into arguments. That's why I've had to put him on Foe list often.

But it's whatever, all of us on this planet don't get along with everyone. It's inevitable *shrugs*. However, that doesn't mean anyone ( including me) should be afraid of standing up for or against someone if the situation calls for it. Kadaicha Man sometimes has no problem trying to be Mr. " I'm always right, get over it" even to the point of being condescending or rude. So...I backed up your point of how what you said about regular mint vs beta could be relevant. All good vibes meant.

[SMG]

report on different kernels and if they made the bug go away:

5.13: the problem is still here but didn't show up until the second time i had to start mint with it
slightly less awful, though - doesn't seem to apply to windowed firefox
5.11: haven't tested yet due to feeling discouraged from what happened with 5.13, hope this is understandable
5.8: same as above. i don't plan on giving up, i'll just probably test these out later than sooner

I do not know if it would make a difference in your situation, but we normally recommend staying with Ubuntu-maintained kernels when possible. (Sometimes very new software needs mainline kernels to get very new drivers.) Ubuntu-maintained kernels have been known to have patches and bug-fixes that are not in mainline kernels.

The kernels in Update Manager (5.4, 5.8, and 5.11) are Ubuntu-maintained and can be seen by selecting View > Linux Kernels and clicking Continue.

[senjoz]

no, no, this isn't new. i've exeprienced this bug since mint 20.0.

5.13: the problem is still here but didn't show up until the second time i had to start mint with it

i usually use mint-y, but it happens with other themes too

Was the problem present right after fresh Mint installation or has it appeared after you made some changes to the GUI or after the update? If you boot in a live session from a USB stick, is the problem also present?

Regards, Jože

[tpo100ckid]

Was the problem present right after fresh Mint installation or has it appeared after you made some changes to the GUI or after the update? If you boot in a live session from a USB stick, is the problem also present?

Regards, Jože

usually starts a few hours after a fresh mint install if not a day
doesn't happen on a live usb stick

[SMG]

usually starts a few hours after a fresh mint install if not a day
doesn't happen on a live usb stick

Sounds like it could be a memory-related issue.

Plugging Cinnamon memory leaks and handling situations where there are other leaks which may not yet have been found are part of the changes in Cinnamon for LM20.2. However, you would have to wait until the final version of LM20.2 to know if the issue still exists.

Does restarting Cinnamon (Ctl-Alt-Esc) clear the issue?