| 2023-04-27 18:42:31 |
Vlad Ziganshin |
description |
Situation - while browsing I want to save page's url to desktop (likely any folder).
I drag the url (by padlock icon in the address bar) onto my desktop folder to save shortcut to the page (for later view, to share it etc).
The ubuntu user session (Wayland) will lock up and crash (bringing me back to user login screen) the moment I move the mouse (dragging the url) to FF windows boundary. Sometimes I'll get as far hovering over open desktop area but it'll crash withing seconds from me starting the task.
No shortcut is saved to the desktop.
FireFox can't restore session when launched again after login to system (I tried even restarting the pc before attempts at launching FF again). All you get is black/blank FF window and spinning cursor.
Initially, the only way to get FF working again appeared to be to kill open FF window, switch to in private mode - this one will start fine and the next time FF would start normally. The session from before the crash would be gone though, really annoying for anyone with multiple open tabs. I'm quite certain that this was the reason why I'd given up on FF snap in 22.04 (normal/legacy install did not have the problem) but the same (?) problem on 23.04 forced me to have a closer look at what's going on, recovery options and to sing up/report the bug.
What I've also noticed is that if following the crash I'd open in private FF windows 1st (instead of trying to open normal browser session only to have to terminate the browser showing blank window) and only then start normal FF session, FF would restore my tabs from before the crash. This is of little use now that I have to figure how to go back to my old session (I'll backtrack it somehow but this is pita). I'm tempted to pull the plug on snap FF again and move back to less fancy but more resilient setup (and with greater functionality).
Btw, the same crash can be triggered when doing drag and drop from bookmark or history manager in FF.
Chromium snap install does not crash the login/Wayland session but url drag and drop attempt just does nothing anyway, no file is left on the desktop. Quite a basic functionality that works from any browser on Windows or macOS, seems like a great omission. An unfortunate choice if limited interactivity with user's own file system was just inherent to snap packaged software. I understand security but it's personal computer desktop environment 1st.
I'm not sure of any security impact but this surely does not look good and is definitely a risk of data/work lost (luckily I did not have whole lot of open windows besides terminal). |
Situation - while browsing I want to save page's url to desktop (likely any folder).
I drag the url (by padlock icon in the address bar) onto my desktop folder to save shortcut to the page (for later view, to share it etc).
The ubuntu user session (Wayland) will lock up and crash (bringing me back to user login screen) the moment I move the mouse (dragging the url) to FF windows boundary. Sometimes I'll get as far hovering over open desktop area but it'll crash withing seconds from me starting the task.
No shortcut is saved to the desktop.
FireFox can't restore session when launched again after login to system (I tried even restarting the pc before attempts at launching FF again). All you get is black/blank FF window and spinning cursor.
Initially, the only way to get FF working again appeared to be to kill open FF window, switch to in private mode - this one will start fine and the next time FF would start normally. The session from before the crash would be gone though, really annoying for anyone with multiple open tabs. I'm quite certain that this was the reason why I'd given up on FF snap in 22.04 (normal/legacy install did not have the problem) but the same (?) problem on 23.04 forced me to have a closer look at what's going on, recovery options and to sing up/report the bug.
What I've also noticed is that if following the crash I'd open in private FF windows 1st (instead of trying to open normal browser session only to have to terminate the browser showing blank window) and only then start normal FF session, FF would restore my tabs from before the crash. This is of little use now that I have to figure how to go back to my old session (I'll backtrack it somehow but this is pita). I'm tempted to pull the plug on snap FF again and move back to less fancy but more resilient setup (and with greater functionality).
Btw, the same crash can be triggered when doing drag and drop from bookmark or history manager in FF.
Chromium snap install does not crash the login/Wayland session but url drag and drop attempt just does nothing anyway, no file is left on the desktop. Quite a basic functionality that works from any browser on Windows or macOS, seems like a great omission. An unfortunate choice if limited interactivity with user's own file system was just inherent to snap packaged software. I understand security but it's personal computer desktop environment 1st.
I'm not sure of any security impact but this surely does not look good and is definitely a risk of data/work lost (luckily I did not have whole lot of open windows besides terminal). |
|
