Open Ethanol6 opened 2 years ago
Mintulix
commented
2 years ago Thanks for bringing this up - I have similar problems after suspend with two logged-in accounts; nemo starts then with a long delay, sometimes the panel and desktop don't react at all. Never found out how to reproduce this reliably, perhaps the 45 minutes do the trick.
Ethanol6
commented
2 years ago Thanks for bringing this up - I have similar problems after suspend with two logged-in accounts; nemo starts then with a long delay, sometimes the panel and desktop don't react at all. Never found out how to reproduce this reliably, perhaps the 45 minutes do the trick.
45 minutes is a ballpark figure. I haven't found out the exact amount of time, it fluctuates a bit, but it's enough time to let the issue happen. Unfortunately Mint Report does not ever notice this happening either so I haven't gotten a stack trace yet.
bobe84
commented
2 years ago I have this issue for many releases already, since i regulary use 2 user accounts on the system, i went ahead and created a shortcut for restarting cinnamon with CTRL+ALT+F12.
Ethanol6
commented
2 years ago I have this issue for many releases already, since i regulary use 2 user accounts on the system, i went ahead and created a shortcut for restarting cinnamon with CTRL+ALT+F12.
This is the only release I have had this issue with. I've run 2 user accounts before but never had to restart Cinnamon when switching between them. Very rarely I would have to run cinnamon-unlock-desktop though.
bobe84
commented
2 years ago What commands shall i run to share my config?
I am on stable 20.2 Mint with Cinnamon. Gigabyte Aorus b550 pro ac 5800x + 48GB RAM RX550 GPU
Monitor is connected via HDMI. Prior to this setup, i had different MB Gigabyte B450M DS3H with other specs same.
And i am pretty much sure that bug is the same as i have for already 1 year running Linux Mint.
I can confirm that it needs cinnamon --replace after couple of standby/resumes and when switching between user accounts. And yes it is only present if you are simultaneously logged in into 2 user accounts.
Whatever you guys need, i can provide any kind of logs, just tell me which ones.
gt4w4al
commented
2 years ago I am also facing this issue. It's difficult to reproduce. Often it's coming after Suspend, but not always. I have 3 accounts on the family computer. My wife is facing the trouble very often (more than once a day), but on my account it's quite rare (once a month) but it still happens.
In default keyboard shortcuts, we have the Ctrl+Alt+Esc to restart Cinnamon, and it solves the issue. Good spare wheel if you can remember the shortcut. How can we report this bug to be solved by the relevant people ?
If it can help, here is some information about my computer. As bobe84, do not hesitate to ask for more.
(but explain very in detail what you want, I am fresh new on Linux and english is not my language !)
nounours@Fixe:~$ inxi -Fxxxrz
System:
Kernel: 5.13.0-21-generic x86_64 bits: 64 compiler: N/A
Desktop: Cinnamon 5.0.7 wm: muffin 5.0.2 dm: LightDM 1.30.0
Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal
Machine:
Type: Desktop Mobo: Micro-Star model: B460M-A PRO (MS-7C88) v: 1.0
serial:
bobe84
commented
2 years ago Here is my config. I do run stable release, still did not upgrade to beta... but the issue is the same:
System:
Kernel: 5.11.0-43-generic x86_64 bits: 64 compiler: N/A
Desktop: Cinnamon 5.0.7 wm: muffin 5.0.2 dm: LightDM 1.30.0
Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal
Machine:
Type: Desktop System: Gigabyte product: B550 AORUS PRO AC v: N/A
serial: N/A
Mobo: Gigabyte model: B550 AORUS PRO AC serial: N/A
UEFI: American Megatrends LLC. v: F14e date: 10/14/2021
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial:
gt4w4al
commented
2 years ago Not same kernel nor same processor (AMD for you, Intel for me). Display bug from Cinnamon.
How do we know this issue is taken into account ? I guess the kind developpers have tons of things to solve... Once again, do not hesitate if we can bring further information.
mtwebster
commented
2 years ago We're very much aware of this, and other related issues. Unfortunately, when a bug is difficult to reproduce, it makes it difficult to fix. I've never run into this issue, for instance, though I am continuing to try.
gt4w4al
commented
2 years ago Good ! It makes me happy ! I can easily understand the situation, and I know this bug is not easy to explain and so reproduce.
These days, it happens quite often after user switch (always about 10 s after switching), but without "wake up from Suspend". I don't know if the 45 minutes are necessary, but it's true I don't reproduce the bug when working 5 min on a user session. I am french, so I don't know if Suspend is the good word. I understand this is a "stand-by on RAM".
bobe84
commented
2 years ago @mtwebster I am quite advanced when it comes to linux and i am developer/system engineer so, i think i can help.
From my perspective the issue is either muffin or screensaver.
Please point me how to debug and what logs i could be sending.
mtwebster
commented
2 years ago I'm pretty sure this isn't a muffin issue, though I guess I can never rule anything out.
to all:
There's a way to keep the screensaver running for debugging purposes and there's a verbose mode:
cinnamon-screensaver --hold --debugThen work as normal until the issue manifests, then check the output there, to look for errors.
If the issue doesn't manifest when running the screensaver this way (which I'm worried may be the case), you can check the system journal after it happens - this won't have verbose logging, but it will show warnings/errors.
To collect journal contents after the problem occurs:
journalctl --since=-1h > logsThis will send the last 1hr to the file 'logs', which you can then upload to some paste site (dpaste.org, etc...) - please don't paste here. Check the contents to make sure there is no personal info or anything else you don't want shared.
I've also been running into this issue: https://github.com/systemd/systemd/issues/16146 while working on this bug, and I'm not sure if it's related or not, but it can occur after a suspend. Symptoms include: No network, having to enter your password twice if you lock the screen, click the switch-users button, then log right back into that account (normally the screensaver should unlock automatically in this situation). A reliable way to check if you've encountered this is to run loginctl list-users - it should return a list of users that are currently logged in (and possibly lightdm, the login manager).
There's a pending fix for this in Ubuntu, that should make its way to Mint 20 soon. Like I said, I'm not sure this is related, as it breaks the session in different ways than the OP issue is, but just mentioning it, in case you see the aforementioned symptoms. ref: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1944711
gt4w4al
commented
2 years ago --hold
"Keep the process running.Normally cinnamon-screensaver will exit after being idle for 10 seconds."
This matches pretty well with the delay to see the bug.
My wife's screensaver was off, but on my session it was set to 15 min. Both of our "Power management settings" were set to 10 min for screen off, and 15 min for sleeping. This is not a laptop but a "desktop" PC. Maybe my screensaver was just starting before sleeping, and that's why my wife had more trouble than me (when waking up the PC to switch to her session)... So I will run this command and wait. Do I have to run the command for each of us ? (on each session I mean?)
mtwebster
commented
2 years ago It probably wouldn't hurt to get as much data as possible. If for some reason you can no longer reproduce it using --hold, I'd still like you to try the journal route as well for collecting info.
Thanks
bobe84
commented
2 years ago For those who want to capture cinnamon-screensaver output i suggest running following in screen session:
python3 -u /usr/bin/cinnamon-screensaver --hold --debug | tee cinnamon-screensaver.log
gt4w4al
commented
2 years ago Last bug tonight... History :
cinnamon-screensaver --hold --debugjournalctl --since=-1h > logsHere is the log file, available 24h, but do not hesitate if you need more http://dpaste.org/rAME
I hope I managed to follow your instructions. I have just a few skills in computers, and I have switched to Linux since 2 months only. Do not hesitate to correct me if I made a mistake.
gt4w4al
commented
2 years ago Copy of my terminal after
cinnamon-screensaver --hold --debug
if there is any debug interest in this
bobe84
commented
2 years ago Happened now, here are the logs.
PLease let us know what more could we provide.
journalctl.log
cinnamon-screensaver.1.log
I cannot minimize windows and cannot change focus. All the windows just get piled up like this, whatever i try to launch.
To clarify: I have 2 user accounts, Work and private one In the morning i resume the machine from standby and login into my private account. After that i login into Work account. During the day i switch from one to another with CTRL+ALT+F7 or F8 I do not log-out from the accounts, they remain logged in, just switching between them. After some time, it happens that FIRST account logged in gets this problem. Most of the time it is Private one(could it be UID connected?)
When i hit CTRL+ALT+ESC everything is back to normal.
@ all you have this problem Can you confirm that this is the same behaviour you exibit? I am on stable 20.2 Linux Mint.
gt4w4al
commented
2 years ago So am I. Same bug for me. If I open new windows, I am not sure they display once 1 or 2 windows are already stuck. Often the bug happen after a session switch, but not always.
clefebvre
commented
2 years ago Since it's not a regression nor a blocker I moved it to Cinnamon.
Michael is on it and we'll issue an update if/when this gets fixed.
In the meantime I added this to the roadmap under Maintenance so we keep an eye on its progress.
gt4w4al
commented
2 years ago Thanks clefebvre for organisation. When I looked for some help on Github, I found this tread https://github.com/linuxmint/cinnamon/issues/10159 Isn't it relevant to merge Issues #10159 and #10570 ? (1 solution, 2 issues closed ! 982 remaining !)
mtwebster
commented
2 years ago Can you guys share ~/.xsession-errors content when this issue occurs?
Also, can you test with window effects disabled: cinnamon-settings->effects->desktop effects->Window effects.
Thanks
gt4w4al
commented
2 years ago I just had the bug twice when I opened the 2 others sessions on the computer for toggling windows effects... .xsession-errors on the first account, named "Ecole" http://dpaste.org/Re6n Second bug on account named "Souris" http://dpaste.org/hWmM
I had the bug when I sat in front of the PC, on my session, but no bug anymore when coming back from these 2 sessions, after toggling the windows effects, to write this post in Github.
I will keep you informed if the windows effects changes something.
mtwebster
commented
2 years ago can you paste the file 'dump' from this command:
dconf dump /org/cinnamon/ > dumpI mentioned using dpaste, but you can actually just drag text files into your response here, that's simpler (and permanent in case someone has to refer back later).
gt4w4al
commented
2 years ago Here you are : I launched this command but not after a bug at this time
[/] app-menu-label='' command-history=['garage', 'r'] desklet-snap-interval=25 desktop-effects-close-effect='traditional' desktop-effects-close-time=120 desktop-effects-close-transition='easeOutQuad' desktop-effects-map-effect='traditional' desktop-effects-map-time=100 desktop-effects-map-transition='easeOutQuad' desktop-effects-maximize-effect='none' desktop-effects-maximize-time=100 desktop-effects-maximize-transition='easeInExpo' desktop-effects-minimize-effect='traditional' desktop-effects-minimize-time=160 desktop-effects-minimize-transition='easeInQuad' desktop-effects-tile-effect='none' desktop-effects-tile-time=100 desktop-effects-tile-transition='easeInQuad' desktop-effects-unmaximize-effect='none' desktop-effects-unmaximize-time=100 desktop-effects-unmaximize-transition='easeNone' enabled-applets=['panel1:left:0:menu@cinnamon.org:14', 'panel1:left:1:show-desktop@cinnamon.org:15', 'panel1:left:2:grouped-window-list@cinnamon.org:16', 'panel1:right:3:systray@cinnamon.org:17', 'panel1:right:4:xapp-status@cinnamon.org:18', 'panel1:right:5:notifications@cinnamon.org:19', 'panel1:right:6:printers@cinnamon.org:20', 'panel1:right:7:removable-drives@cinnamon.org:21', 'panel1:right:8:keyboard@cinnamon.org:22', 'panel1:right:9:favorites@cinnamon.org:23', 'panel1:right:10:network@cinnamon.org:24', 'panel1:right:11:sound@cinnamon.org:25', 'panel1:right:12:power@cinnamon.org:26', 'panel1:right:13:calendar@cinnamon.org:27', 'panel1:right:2:qredshift@quintao:28:orient'] enabled-desklets=@as [] hotcorner-layout=['expo:false:0', 'scale:false:0', 'scale:false:0', 'desktop:false:0'] next-applet-id=31 panel-edit-mode=false panel-zone-icon-sizes='[{"panelId": 1, "left": 0, "center": 0, "right": 24}]' panel-zone-symbolic-icon-sizes='[{"panelId": 1, "left": 28, "center": 28, "right": 28}]' panel-zone-text-sizes='[{"panelId": 1, "left": 0.0, "center": 0.0, "right": 0.0}]' panels-enabled=['1:0:left'] panels-height=['1:60'] workspace-expo-view-as-grid=true
[cinnamon-session] quit-time-delay=60
[desktop/applications/calculator] exec='gnome-calculator'
[desktop/applications/terminal] exec='gnome-terminal'
[desktop/background] picture-options='stretched' picture-uri="file:///home/nounours/Fonds d'écran/Ferrari.jpg"
[desktop/background/slideshow] delay=15 image-source="directory:///home/nounours/Fonds d'écran" slideshow-enabled=false
[desktop/interface] cursor-blink-time=1200 cursor-size=24 gtk-theme='Mint-Y-Aqua' icon-theme='Mint-Y-Aqua' scaling-factor=uint32 0
[desktop/keybindings/media-keys]
area-screenshot-clip=['
[desktop/media-handling] autorun-never=false autorun-x-content-ignore=['x-content/blank-dvd'] autorun-x-content-open-folder=@as [] autorun-x-content-start-app=['x-content/unix-software', 'x-content/blank-dvd', 'x-content/image-dcf']
[desktop/screensaver] lock-enabled=false
[desktop/session] idle-delay=uint32 0
[desktop/sound] event-sounds=false
[desktop/wm/preferences] theme='Mint-Y'
[launcher] check-frequency=300 memory-limit=2048
[muffin] desktop-effects=false workspace-cycle=false
[settings-daemon/peripherals/keyboard] delay=uint32 500 numlock-state='on' repeat-interval=uint32 30
[settings-daemon/peripherals/mouse] custom-acceleration=true custom-threshold=true double-click=400 drag-threshold=8 motion-acceleration=7.1687500000000002 motion-threshold=10
[settings-daemon/peripherals/touchpad] motion-threshold=1 touchpad-enabled=false
[settings-daemon/plugins/power] lock-on-suspend=false sleep-display-ac=600 sleep-inactive-ac-timeout=900
[theme] name='Mint-Y-Dark-Aqua'
gt4w4al
commented
2 years ago By the way, my wife said she faced the bug today, so with window effect disable.
Mintulix
commented
2 years ago It seems the bug described above (nemo 2821) has nothing to do with this one, so please ignore the link.
gt4w4al
commented
2 years ago It seems much better now under Mint 20.3. My wife reported some occurrence but lower and I didn't catch a clue for the moment. No bug on my session. Do you still have the issue ? Is it fixed ?
gt4w4al
commented
2 years ago I talked to early... I just had the bug now, although not switching sessions. Working on the PC 15 min since last Suspend exit.
journalctl --since=-20min > logs
-- Logs begin at Fri 2021-11-26 18:16:54 CET, end at Sat 2022-01-22 17:02:47 CET. --
janv. 22 16:51:07 Fixe dbus-daemon[850]: [system] Activating service name='org.debian.apt' requested by ':1.483' (uid=1000 pid=39944 comm="mintinstall " label="unconfined") (using servicehelper)
janv. 22 16:51:07 Fixe AptDaemon[40158]: INFO: Initializing daemon
janv. 22 16:51:07 Fixe org.debian.apt[40158]: 16:51:07 AptDaemon [INFO]: Initializing daemon
janv. 22 16:51:07 Fixe dbus-daemon[850]: [system] Successfully activated service 'org.debian.apt'
janv. 22 16:51:07 Fixe AptDaemon[40158]: INFO: InstallPackages() was called: dbus.Array([dbus.String('sane-airscan')], signature=dbus.Signature('s'))
janv. 22 16:51:07 Fixe org.debian.apt[40158]: /usr/lib/python3/dist-packages/aptdaemon/worker/pkworker.py:35: PyGIWarning: PackageKitGlib was imported without specifying a version first. Use gi.require_version('PackageKitGlib', '1.0') before import to ensure that the right version gets loaded.
janv. 22 16:51:07 Fixe org.debian.apt[40158]: from gi.repository import PackageKitGlib as pk
janv. 22 16:51:07 Fixe org.debian.apt[40158]: 16:51:07 AptDaemon [INFO]: InstallPackages() was called: dbus.Array([dbus.String('sane-airscan')], signature=dbus.Signature('s'))
janv. 22 16:51:07 Fixe AptDaemon.Trans[40158]: INFO: Simulate was called
janv. 22 16:51:07 Fixe org.debian.apt[40158]: 16:51:07 AptDaemon.Trans [INFO]: Simulate was called
janv. 22 16:51:07 Fixe AptDaemon.Worker[40158]: INFO: Simulating trans: /org/debian/apt/transaction/4371050da5fe4a69b1b59df1424b524b
janv. 22 16:51:07 Fixe org.debian.apt[40158]: 16:51:07 AptDaemon.Worker [INFO]: Simulating trans: /org/debian/apt/transaction/4371050da5fe4a69b1b59df1424b524b
janv. 22 16:51:08 Fixe AptDaemon.Worker[40158]: INFO: Committing packages: dbus.Array([dbus.String('sane-airscan')], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s'))
janv. 22 16:51:08 Fixe org.debian.apt[40158]: 16:51:08 AptDaemon.Worker [INFO]: Committing packages: dbus.Array([dbus.String('sane-airscan')], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s'))
janv. 22 16:51:08 Fixe AptDaemon.Trans[40158]: INFO: Queuing transaction /org/debian/apt/transaction/4371050da5fe4a69b1b59df1424b524b
janv. 22 16:51:08 Fixe org.debian.apt[40158]: 16:51:08 AptDaemon.Trans [INFO]: Queuing transaction /org/debian/apt/transaction/4371050da5fe4a69b1b59df1424b524b
janv. 22 16:51:10 Fixe polkitd(authority=local)[867]: Operator of unix-session:c4 successfully authenticated as unix-user:nounours to gain TEMPORARY authorization for action org.debian.apt.install-or-remove-packages for system-bus-name::1.483 [mintinstall] (owned by unix-user:nounours)
janv. 22 16:51:10 Fixe AptDaemon.Worker[40158]: INFO: Processing transaction /org/debian/apt/transaction/4371050da5fe4a69b1b59df1424b524b
janv. 22 16:51:10 Fixe org.debian.apt[40158]: 16:51:10 AptDaemon.Worker [INFO]: Processing transaction /org/debian/apt/transaction/4371050da5fe4a69b1b59df1424b524b
janv. 22 16:51:11 Fixe systemd[13098]: Started debconf communication service.
janv. 22 16:51:13 Fixe dbus-daemon[850]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.487' (uid=0 pid=40607 comm="/usr/bin/gdbus call --system --dest org.freedeskto" label="unconfined")
janv. 22 16:51:13 Fixe systemd[1]: Starting PackageKit Daemon...
janv. 22 16:51:13 Fixe PackageKit[40610]: daemon start
janv. 22 16:51:13 Fixe dbus-daemon[850]: [system] Successfully activated service 'org.freedesktop.PackageKit'
janv. 22 16:51:13 Fixe systemd[1]: Started PackageKit Daemon.
janv. 22 16:51:13 Fixe AptDaemon.Worker[40158]: INFO: Finished transaction /org/debian/apt/transaction/4371050da5fe4a69b1b59df1424b524b
janv. 22 16:51:13 Fixe org.debian.apt[40158]: /usr/lib/python3/dist-packages/aptdaemon/progress.py:490: Warning: Source ID 31 was not found when attempting to remove it
janv. 22 16:51:13 Fixe org.debian.apt[40158]: GLib.source_remove(id)
janv. 22 16:51:13 Fixe org.debian.apt[40158]: /usr/lib/python3/dist-packages/aptdaemon/progress.py:490: Warning: Source ID 32 was not found when attempting to remove it
janv. 22 16:51:13 Fixe org.debian.apt[40158]: GLib.source_remove(id)
janv. 22 16:51:13 Fixe org.debian.apt[40158]: 16:51:13 AptDaemon.Worker [INFO]: Finished transaction /org/debian/apt/transaction/4371050da5fe4a69b1b59df1424b524b
janv. 22 16:51:38 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=2a01:0e0a:05dd:8890:873a:220c:dc36:498f DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=781913 PROTO=UDP SPT=8612 DPT=8612 LEN=24
janv. 22 16:51:38 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=2a01:0e0a:05dd:8890:873a:220c:dc36:498f DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=371635 PROTO=UDP SPT=8612 DPT=8610 LEN=24
janv. 22 16:51:38 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=2a01:0e0a:05dd:8890:735b:6092:33e7:e516 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=870242 PROTO=UDP SPT=8612 DPT=8612 LEN=24
janv. 22 16:51:38 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=2a01:0e0a:05dd:8890:735b:6092:33e7:e516 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=182884 PROTO=UDP SPT=8612 DPT=8610 LEN=24
janv. 22 16:51:38 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:b8e4:eee7:0dbd:412d DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=159761 PROTO=UDP SPT=8612 DPT=8612 LEN=24
janv. 22 16:51:38 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:b8e4:eee7:0dbd:412d DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=198170 PROTO=UDP SPT=8612 DPT=8610 LEN=24
janv. 22 16:51:38 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=2a01:0e0a:05dd:8890:873a:220c:dc36:498f DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=781913 PROTO=UDP SPT=8612 DPT=8612 LEN=24
janv. 22 16:51:38 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=2a01:0e0a:05dd:8890:873a:220c:dc36:498f DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=371635 PROTO=UDP SPT=8612 DPT=8610 LEN=24
janv. 22 16:51:38 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=2a01:0e0a:05dd:8890:735b:6092:33e7:e516 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=870242 PROTO=UDP SPT=8612 DPT=8612 LEN=24
janv. 22 16:51:38 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=2a01:0e0a:05dd:8890:735b:6092:33e7:e516 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=182884 PROTO=UDP SPT=8612 DPT=8610 LEN=24
janv. 22 16:51:39 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:18:0c:ac:2f:e9:d9:08:00 SRC=192.168.1.35 DST=192.168.1.194 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=50425 PROTO=UDP SPT=8612 DPT=8612 LEN=40
janv. 22 16:51:39 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:18:0c:ac:2f:e9:d9:08:00 SRC=192.168.1.35 DST=192.168.1.194 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=5465 PROTO=UDP SPT=8612 DPT=8612 LEN=40
janv. 22 16:51:42 Fixe sudo[40638]: souris : TTY=unknown ; PWD=/home/souris ; USER=root ; COMMAND=/usr/lib/linuxmint/mintUpdate/dpkg_lock_check.sh
janv. 22 16:51:42 Fixe sudo[40638]: pam_unix(sudo:session): session opened for user root by (uid=0)
janv. 22 16:51:42 Fixe sudo[40638]: pam_unix(sudo:session): session closed for user root
janv. 22 16:51:45 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:20:66:cf:5e:d5:88:08:00 SRC=192.168.1.254 DST=192.168.1.194 LEN=1305 TOS=0x00 PREC=0x00 TTL=64 ID=2877 DF PROTO=UDP SPT=3702 DPT=40947 LEN=1285
janv. 22 16:51:45 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:20:66:cf:5e:d5:88:08:00 SRC=192.168.1.254 DST=192.168.1.194 LEN=1305 TOS=0x00 PREC=0x00 TTL=64 ID=2882 DF PROTO=UDP SPT=3702 DPT=40947 LEN=1285
janv. 22 16:51:45 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:20:66:cf:5e:d5:88:08:00 SRC=192.168.1.254 DST=192.168.1.194 LEN=1305 TOS=0x00 PREC=0x00 TTL=64 ID=2901 DF PROTO=UDP SPT=3702 DPT=40947 LEN=1285
janv. 22 16:51:45 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:18:0c:ac:2f:e9:d9:08:00 SRC=192.168.1.35 DST=192.168.1.194 LEN=1367 TOS=0x00 PREC=0x00 TTL=64 ID=8670 PROTO=UDP SPT=3702 DPT=40947 LEN=1347
janv. 22 16:51:45 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:20:66:cf:5e:d5:88:08:00 SRC=192.168.1.254 DST=192.168.1.194 LEN=1305 TOS=0x00 PREC=0x00 TTL=64 ID=2902 DF PROTO=UDP SPT=3702 DPT=40947 LEN=1285
janv. 22 16:51:45 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:18:0c:ac:2f:e9:d9:08:00 SRC=192.168.1.35 DST=192.168.1.194 LEN=1367 TOS=0x00 PREC=0x00 TTL=64 ID=42923 PROTO=UDP SPT=3702 DPT=40947 LEN=1347
janv. 22 16:51:45 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:20:66:cf:5e:d5:88:08:00 SRC=192.168.1.254 DST=192.168.1.194 LEN=1305 TOS=0x00 PREC=0x00 TTL=64 ID=2910 DF PROTO=UDP SPT=3702 DPT=40947 LEN=1285
janv. 22 16:51:45 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:20:66:cf:5e:d5:88:08:00 SRC=192.168.1.254 DST=192.168.1.194 LEN=1305 TOS=0x00 PREC=0x00 TTL=64 ID=2911 DF PROTO=UDP SPT=3702 DPT=40947 LEN=1285
janv. 22 16:51:59 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:18:0c:ac:2f:e9:d9:86:dd SRC=fe80:0000:0000:0000:1a0c:acff:fe2f:e9d9 DST=fe80:0000:0000:0000:b8e4:eee7:0dbd:412d LEN=1402 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=3702 DPT=37627 LEN=1362
janv. 22 16:52:02 Fixe sudo[40679]: nounours : TTY=unknown ; PWD=/home/nounours ; USER=root ; COMMAND=/usr/lib/linuxmint/mintUpdate/dpkg_lock_check.sh
janv. 22 16:52:02 Fixe sudo[40679]: pam_unix(sudo:session): session opened for user root by (uid=0)
janv. 22 16:52:02 Fixe sudo[40679]: pam_unix(sudo:session): session closed for user root
janv. 22 16:52:06 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:18:0c:ac:2f:e9:d9:08:00 SRC=192.168.1.35 DST=192.168.1.194 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=14653 PROTO=UDP SPT=8612 DPT=8612 LEN=40
janv. 22 16:52:11 Fixe pk-debconf-help[40176]: No active connections, exiting
janv. 22 16:52:11 Fixe systemd[13098]: pk-debconf-helper.service: Succeeded.
janv. 22 16:52:19 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=b0:a4:60:5f:39:e4:18:0c:ac:2f:e9:d9:86:dd SRC=2a01:0e0a:05dd:8890:1a0c:acff:fe2f:e9d9 DST=2a01:0e0a:05dd:8890:873a:220c:dc36:498f LEN=1402 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=3702 DPT=48257 LEN=1362
janv. 22 16:52:22 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:7f:ff:fa:00:06:78:66:6d:72:08:00 SRC=192.168.1.79 DST=239.255.255.250 LEN=82 TOS=0x00 PREC=0x00 TTL=4 ID=25481 DF PROTO=UDP SPT=3423 DPT=3423 LEN=62
janv. 22 16:52:54 Fixe wpa_supplicant[874]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-68 noise=9999 txrate=81000
janv. 22 16:52:54 Fixe kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:7f:ff:fa:00:06:78:66:6d:72:08:00 SRC=192.168.1.79 DST=239.255.255.250 LEN=82 TOS=0x00 PREC=0x00 TTL=4 ID=28287 DF PROTO=UDP SPT=3423 DPT=3423 LEN=62
janv. 22 16:53:18 Fixe kernel: simple-scan[40698]: segfault at 0 ip 00007f419f00c1a4 sp 00007ffc17bf79a8 error 4 in libgtk-3.so.0.2404.16[7f419ef6f000+36f000]
janv. 22 16:53:18 Fixe kernel: Code: 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 d0 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 d8 00 00 00 0f 1f 00 f3 0f 1e fa <48> 8b 07 ff a0 e0 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 e8
janv. 22 16:53:19 Fixe systemd[1]: Created slice system-systemd\x2dcoredump.slice.
janv. 22 16:53:19 Fixe systemd[1]: Started Process Core Dump (PID 40730/UID 0).
janv. 22 16:53:19 Fixe systemd-coredump[40731]: Process 40698 (simple-scan) of user 1000 dumped core.
Stack trace of thread 40698:
#0 0x00007f419f00c1a4 n/a (libgtk-3.so.0 + 0x1221a4)
#1 0x000055f6e55fb868 n/a (simple-scan + 0x2f868)
#2 0x00007f419ea6b802 g_closure_invoke (libgobject-2.0.so.0 + 0x14802)
#3 0x00007f419ea7f814 n/a (libgobject-2.0.so.0 + 0x28814)
#4 0x00007f419ea8abbe g_signal_emit_valist (libgobject-2.0.so.0 + 0x33bbe)
#5 0x00007f419ea8b0f3 g_signal_emit (libgobject-2.0.so.0 + 0x340f3)
#6 0x000055f6e5601cde n/a (simple-scan + 0x35cde)
#7 0x00007f419f6ed04e g_main_context_dispatch (libglib-2.0.so.0 + 0x5204e)
#8 0x00007f419f6ed400 n/a (libglib-2.0.so.0 + 0x52400)
#9 0x00007f419f6ed4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3)
#10 0x00007f419eb9a05a g_application_run (libgio-2.0.so.0 + 0xe305a)
#11 0x000055f6e55fd97b n/a (simple-scan + 0x3197b)
#12 0x00007f419e71a0b3 __libc_start_main (libc.so.6 + 0x270b3)
#13 0x000055f6e55dc18e n/a (simple-scan + 0x1018e)
Stack trace of thread 40700:
#0 0x00007f419e808aff __GI___poll (libc.so.6 + 0x115aff)
#1 0x00007f419f6ed36e n/a (libglib-2.0.so.0 + 0x5236e)
#2 0x00007f419f6ed4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3)
#3 0x00007f419f6ed4f1 n/a (libglib-2.0.so.0 + 0x524f1)
#4 0x00007f419f716ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5 0x00007f419e666609 start_thread (libpthread.so.0 + 0x9609)
#6 0x00007f419e815293 __clone (libc.so.6 + 0x122293)
Stack trace of thread 40704:
#0 0x00007f419e808aff __GI___poll (libc.so.6 + 0x115aff)
#1 0x00007f419dc191a2 n/a (libusb-1.0.so.0 + 0x111a2)
#2 0x00007f419e666609 start_thread (libpthread.so.0 + 0x9609)
#3 0x00007f419e815293 __clone (libc.so.6 + 0x122293)
Stack trace of thread 40729:
#0 0x00007f419e80e89d syscall (libc.so.6 + 0x11b89d)
#1 0x00007f419f73a746 g_cond_wait_until (libglib-2.0.so.0 + 0x9f746)
#2 0x00007f419f6bd581 n/a (libglib-2.0.so.0 + 0x22581)
#3 0x00007f419f7174ca n/a (libglib-2.0.so.0 + 0x7c4ca)
#4 0x00007f419f716ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5 0x00007f419e666609 start_thread (libpthread.so.0 + 0x9609)
#6 0x00007f419e815293 __clone (libc.so.6 + 0x122293)
Stack trace of thread 40703:
#0 0x00007f419e808aff __GI___poll (libc.so.6 + 0x115aff)
#1 0x00007f419f6ed36e n/a (libglib-2.0.so.0 + 0x5236e)
#2 0x00007f419f6ed4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3)
#3 0x00007f419ae5299d n/a (libdconfsettings.so + 0xa99d)
#4 0x00007f419f716ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5 0x00007f419e666609 start_thread (libpthread.so.0 + 0x9609)
#6 0x00007f419e815293 __clone (libc.so.6 + 0x122293)
Stack trace of thread 40701:
#0 0x00007f419e808aff __GI___poll (libc.so.6 + 0x115aff)
#1 0x00007f419f6ed36e n/a (libglib-2.0.so.0 + 0x5236e)
#2 0x00007f419f6ed6f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3)
#3 0x00007f419ebd5f8a n/a (libgio-2.0.so.0 + 0x11ef8a)
#4 0x00007f419f716ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5 0x00007f419e666609 start_thread (libpthread.so.0 + 0x9609)
#6 0x00007f419e815293 __clone (libc.so.6 + 0x122293)janv. 22 16:53:19 Fixe systemd[1]: systemd-coredump@0-40730-0.service: Succeeded.
janv. 22 16:53:23 Fixe systemd[13098]: vte-spawn-b9e8ada6-1525-4292-a0c6-3dcd99f47c35.scope: Succeeded.
janv. 22 16:53:23 Fixe systemd[13098]: gnome-terminal-server.service: Succeeded.
janv. 22 16:56:18 Fixe PackageKit[40610]: daemon quit
janv. 22 16:56:18 Fixe systemd[1]: packagekit.service: Succeeded.
janv. 22 16:57:20 Fixe NetworkManager[851]:
Mintulix
commented
2 years ago This is much better now! There was one event I had to restart Cinnamon and one time the cinnamon-unlock-desktop message since a few days. No more lags during Nemo start. So, not perfect, but the besetting issue seems to be gone.
mtwebster
commented
2 years ago Hi, I have some packages to test if anyone's willing:
https://www.dropbox.com/sh/deyy53m7rnxm3f4/AABjmitmNINtul543_ZDksTRa?dl=0
Download them, then open a terminal in that folder, and run:
sudo dpkg -i *.debThen make sure the old version isn't still running:
cinnamon-screensaver-command -eIn Mint, if you have any issues, the update manager can restore the 'official' versions.
Built from: https://github.com/linuxmint/cinnamon-screensaver/tree/pam-shutdown
Please let me know how they work out.
Thanks!
bobe84
commented
2 years ago @mtwebster I am running these packages since last night and this morning bug replicated itself without any difference. So this is no bugfix.
mtwebster
commented
2 years ago Thanks for checking it.
Interestingly when working on this stuff the last few days, occasionally firefox blows up on me, goes transparent, causes all sorts of desktop rendering issues until I kill it. It doesn't quite sound like the same issue here (since restarting resolves that, but it doesn't fix firefox for me), but I may as well eliminate it as something to consider.
Is anyone not using firefox?
I know this is a pain, but can you guys exit firefox before going thru the steps to reproduce this? Thanks
bobe84
commented
2 years ago This machine i am currently on is non-negotiable. I manage about 1000 baremetal servers over it (not bragging) just saying it will remain as is.
I will try it on one laptop i have as spare.
So, just to re-iterate, you want us to try working without FF and see if the issue appears again?
EDIT: If we manage to find the root cause of this, this will be the best DE for me and i believe for others also. I am also ready to donate money for the team.
mtwebster
commented
2 years ago Understood, I wouldn't ask that of anyone.
Curious also, are you on an ESR or the current (97)?
I want to see if the issue occurs if firefox is not one of the programs still running when the machine is suspended/resumed/user-switched.
It may be unrelated (which would suck, because that's another bug) but I don't want to assume it's not, even if some of the details vary.
bobe84
commented
2 years ago I am basically running everything stock as much as i can. I am running HWE kernel but it was the same when i was running regular kernel. EDIT: Firefox is v97 currently. EDIT2: I have no issues with displaying anything. All browsers, everything works very good and is very stable except when i need to restart cinnamon. ( which i got used to honestly )
I typically update on sunday evening.
I can provide all the info you may need ofc. Just give me all the commands and info you require.
I have old laptop Dell Latitude E5470 and it is having the same issue with integrated Intel video card.
Can i get some kind of debugging info WHEN this happens, i can login into terminal and obtain whatever you need from there.
bobe84
commented
2 years ago May i note that this has been happening like 2 years already.
Maybe even more!!! So it is not a bug that was introduced recently.
EDIT: I will for sure try to kill firefox when going to sleep.
@mtwebster Will let you know how it behaves without FF running when going to sleep.
Mintulix
commented
2 years ago @mtwebster "Unfortunately" I can't help anymore with this issue, because for me the ugly bug is gone since upgrading to LM 20.3. A few times I had the cinnamon-unlock-desktop message when switching users, but it's really rare. No more restarting Cinnamon a few times a week, no more nemo-start lagging after a crash. Also no issues with FF (now 97.0.1). I'm testing your screensaver-patch, right now there was no problem yet, but the unlock-desktop message was not reproducible at all before, too.
gt4w4al
commented
2 years ago Hi Sorry, I have big network issues at home at the moment...
I am not sure I understood what Michael wants with the packages. When I open GDebi I have an error : "Breaks the existing package "cinnamon-screensaver" due to its dependancy libcscreensaver0 (=5.2.0+una)" or "The dependency can't be satisfied : libcscreensaver0 (=5.2.0+una)"
So I can't install none of these 3 packages. Sorry. That's my penguin level...
But : I don't use Firefox ! Nor my wife. We are using Opera. This bug has disappeared for us since we switched to Una.
bobe84
commented
2 years ago I can confirm that this bug is still here without using FF.
Can anybody point me to turn on how to turn on as much debugging i can on every component of cinnamon?
Mintulix
commented
2 years ago @bobe84 Just to clarify - you're still on Uma, right? At least with your productive machine, I assume. What about testing with your spare laptop and Una? Two users here (me included) think this was 'accidentally' fixed in LM 20.3.
bobe84
commented
2 years ago I am on Una since it was released. I have been upgrading this os for 1 year. Cannot remember exactly which version was installed originally. But yes i am on LM 20.3 now and i do have the same issue as i have been having for past 2 years.
mtwebster
commented
2 years ago Can you check your ~/.xsession-errors from when this happens? (Someone did above but they've expired on the paste site).
This is where all Cinnamon logging goes, and many other user processes. You can try https://github.com/Cobinja/CinnDevTools as well which allows you to enable additional window manager debugging.
I'm definitely open to more eyes on this - it's pretty frustrating trying to fix a bug you can't reproduce.
What I'd really like to know what windows may exist when this happens - beyond windows for open applications. You can attach to the log - tail -f ~/.xsession-errors, Then turn on the "Geometry" or "Window state" switches on that applet. It will continually report on windows. If you see a suspect window, you can switch to a tty while the issue is occurring and run DISPLAY=:0 xprop -id <id> and maybe identify the window.
bobe84
commented
2 years ago Allright, here are some probably not interesting logs.
dmesg.log
journal_system.log
journal_user.log
processes.log
xsession-errors.log
I have just enabled the applet for debugging and turned all options on it.
Does it report to .xsession-errors?
EDIT: I will provide .xsession-errors once it happens again.
For your information Melange (SUPER + L ) is not usable because i cannot focus on it(neither with ALT+TAB nor with clicking on it)
mtwebster
commented
2 years ago If you turn them all on you'll be flooded - only turn on specific ones at a time when possible. Maybe start with the two I recommended.
Yes it'll go into .xsession-errors - like I said, run:
tail -f ~/.xsession-errorsand you can see that extra logging as it gets reported.
Disable your extensions - I see you have 'transparent panels' and 'smart-panel'. Things like that need to be eliminated as a variable.
bobe84
commented
2 years ago Did disable those, however not seeing any influx of extra log data.
I'll restart and will report once i have some valid info. @mtwebster Thanks for the guidance!
Ethanol6
commented
2 years ago I've been on 20.2 since reporting this issue in order to avoid it. Upgraded again to 20.3 a few days ago and the issue continues. Today both users have experienced the issue when switching from another user to theirs. Both users had been logged on before and were switching back to their session.
Here's the .xsession-errors
@mtwebster How do I install this applet (https://github.com/Cobinja/CinnDevTools)? I've copied the folder into the cinnamon applets folder for my user but it doesn't show up as an applet to add to my panel.
bobe84
commented
2 years ago (cinnamon:2034795): St-WARNING **: 14:26:52.397: Did not find double property 'opacity'
(cinnamon:2034795): Cjs-CRITICAL **: 01:04:29.787: Object St.BoxLayout (0x559d8b6cf760), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. == Stack trace for context 0x559d8b2ca1d0 ==
(cinnamon:2034795): Clutter-CRITICAL : 01:04:29.788: clutter_container_get_children: assertion 'CLUTTER_IS_CONTAINER (container)' failed Message: 01:04:29.790: Existing monitor config (/home/work/.config/cinnamon-monitors.xml) not found during hotplug or laptop lid event. Looking for legacy configuration (monitors.xml) cinnamon-session[1651054]: WARNING: t+100488,79387s: Detected that screensaver has appeared on the bus (END)
Literally i got nothing. 1:04 is when i resumed from sleep and this is all what we have in logs. Prior to that, last message is at 14:26
mtwebster
commented
2 years ago @Ethanol6 The actual applet folder should be placed in ~/.local/share/cinnamon/applets, not the parent folder (which is what you get from github (CinnDevTools).
~/.local/share/cinnamon/applets/cinn-dev-tools@cobinja.de@mtwebster Thanks, I downloaded the applet again and that seems to have worked, though the applet itself is on the panel, my mouse just clicks on whatever is behind the applets menu so I haven't been able to add anything new to my logs.
Here's a new log. This one occurred without any other users logged in, which seemed to trigger this issue before. The login screen was unresponsive so I ran cinnamon-unlock-desktop over SSH on another machine. Once the desktop was unlocked the usual problematic behavior was present. Alt+F2 then r (without being able to see the command window) resolved the issue.
.xsession-errors March 1
This log was extremely long so I grabbed the most recent portion of it. I'd be interested to know if this issue affects LMDE as well, seems like everyone references LM 20.X with this issue.
Mint 20.3 beta Cinnamon Cinnamon 5.2.6 muffin 5.2.0
Observation
After returning from suspend and logging-in to my user account, application windows do not display on the desktop. Applications will launch and be displayed in the panel. Hovering over their icons in the panel will display the preview and clicking the preview or panel icon will sometimes make the window appear on the desktop. The application window is unresponsive to any input and cannot be closed itself.
Steps to reproduce
Create a second user account. Then switch to the second user account. Do not Log Out of the first account, just switch users. From the second account suspend the computer for 45+ minutes. After returning from suspend, log back into the first account.
OR
Switch to the second user account. Do stuff for 45+ minutes. Switch back to the first account.
This is reproducible on Fedora 35 Cinnamon spin as well.
Expected Behaviour
Windows on the desktop should be responsive and Cinnamon should not require restarting
Potential security risk
Windows on the desktop are not responsive, but the menu and panel still act normally. I opened the Users and Groups app, the Authenticate window does not display but an icon for it is present in the panel. Manually clicking the panel icon can make the Authenticate window appear but it is completely inactive, clicking on the window to bring focus to it does nothing but the window border is coloured as if it is focused. The Authentication window must be the only window, or else it does not appear focused.
If you type your password, instead the Desktop search box shows up and your password in plain text is typed into it. If you don't realize what is happening you could give your Administrator password away. Turning off desktop icons removes the search function.
Fix
Restarting Cinnamon must be done blind as no windows are displayed on the screen, even the "Enter a Command" window after pressing Alt+F2. Since this doesn't display a running app in the panel it is uncertain whether pressing Alt+F2 is doing anything at all but typing "r" and pressing Enter does restart Cinnamon and everything works normally after that.