** Description changed:
systemd.mount constantly unmounts an in use sshfs drive!
Sep 09 11:20:01 $HOSTNAME systemd[4613]: pathtomount.mount: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit UNIT has successfully
** Description changed:
systemd.mount constantly unmounts an in use sshfs drive!
- mount has successfully entered the 'dead' state.
+ Sep 09 11:20:01 $HOSTNAME systemd[4613]: pathtomount.mount: Succeeded.
+ ░░ Subject: Unit succeeded
+ ░░ Defined-By: systemd
+ ░░ Support: http://www.ubuntu.co
** Description changed:
systemd.mount constantly unmounts an in use sshfs drive!
mount has successfully entered the 'dead' state.
+
+ Change my kernel and the issue *seems* to have subsided.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: systemd 247.3-3ubuntu3.4
ProcVersi
** Description changed:
systemd.mount constantly unmounts an in use sshfs drive!
mount has successfully entered the 'dead' state. -What the hell I WAS
USING IT!
I had this drive originally in auto.sshfs but when the application I was
using accessing files on the drive just up and v
** Description changed:
systemd.mount constantly unmounts an in use sshfs drive!
mount has successfully entered the 'dead' state. -What the hell I WAS
USING IT!
I had this drive originally in auto.sshfs but when the application I was
using accessing files on the drive just up and v
** Description changed:
systemd.mount constantly unmounts an in use sshfs drive!
mount has successfully entered the 'dead' state. -What the hell I WAS
USING IT!
I had this drive originally in auto.sshfs but when the application I was
using accessing files on the drive just up and v
Public bug reported:
systemd.mount constantly unmounts an in use sshfs drive!
mount has successfully entered the 'dead' state. -What the hell I WAS
USING IT!
I had this drive originally in auto.sshfs but when the application I was
using accessing files on the drive just up and vanished I thought
Public bug reported:
Changing display settings hard locks the machine (no reisub save).
Installing nouveau-firmware allows changes to be made without hard lock
ups but the screen using nouveau draws the mouse cursor and will launch
apps on it but does not draw anything on screen. Dmesg is flooded
[ 46.504672] xfce4-session[1220]: segfault at 0 ip 7f52d3e7fb7e sp
7ffd390d35f8 error 4 in libc-2.31.so[7f52d3d1e000+178000]
I had added a Firefox complaint but it looks to have been removed or
Firefox didn't submit correctly before it died. Basically says two cards
from the same vendor
** Description changed:
Install 20.04 or 21.04, install the proprietary drivers. Add a second
XScreen so you can enable the primary GPU and its screens and
applications start to crash. System is unusable.
-
- [ 46.504672] xfce4-session[1220]: segfault at 0 ip 7f52d3e7fb7e sp
- 7ff
** Description changed:
- Install 20.04 or 21.04...survive the open source drivers crashing and
- bugging out (or hard locking the system) to install the proprietary
- drivers. Add a second XScreen so you can enable the primary GPU and its
- screens and applications start to crash. You can't actua
** Description changed:
Install 20.04 or 21.04...survive the open source drivers crashing and
bugging out (or hard locking the system) to install the proprietary
drivers. Add a second XScreen so you can enable the primary GPU and its
screens and applications start to crash. You can't actua
Public bug reported:
Install 20.04 or 21.04...survive the open source drivers crashing and
bugging out (or hard locking the system) to install the proprietary
drivers. Add a second XScreen so you can enable the primary GPU and its
screens and applications start to crash. You can't actually use the
13 matches
Mail list logo
