I've also had this issue - twice - caused by leaving my desktop in
standby for > 24hrs (can't say the exact duration). Cold booting after
ensuring residual current has been expelled from the system has fixed it
on both occasions.
It sounds like #1905214. My hardware is also
Network controller [02
Adding this bug as that seems to be the exact issue here -
https://github.com/openzfs/zfs/issues/10140
Solution is "Use zfs-mount-generator instead of zfs-mount.service" ...
** Bug watch added: github.com/openzfs/zfs/issues #10140
https://github.com/openzfs/zfs/issues/10140
--
You received t
So, long story short, I believe I have run into this issue
https://github.com/zfsonlinux/pkg-zfs/issues/205
** Bug watch added: github.com/zfsonlinux/pkg-zfs/issues #205
https://github.com/zfsonlinux/pkg-zfs/issues/205
--
You received this bug notification because you are a member of Ubuntu
B
Hmm, issue still happens, and I'm now suspicious of the dependencies in
systemd.
$ systemctl list-dependencies boot.mount
boot.mount
● ├─-.mount
● ├─system.slice
● └─zfs-import.target
● └─zfs-import-cache.service
I see "boot.mount" depends on "zfs-import-cache.service", however the
timestamp
BTW, I ran the following and that seems to have solved the missing
bpool.
zpool set cachefile=/etc/zfs/zpool.cache bpool
zpool set cachefile=/etc/zfs/zpool.cache rpool
update-initramfs -u -k all
I have a hunch the zpool.cache file is getting out of sync with the
initramfs one..?
--
You received
Public bug reported:
On a new Ubuntu 20.10 ZoL root I frequently get boot failures, and I see
these errors:
[ 11.353930] systemd[1]: boot.mount: Mount process exited, code=exited,
status=1/FAILURE
[ 11.353934] systemd[1]: boot.mount: Failed with result 'exit-code'.
[ 11.354267] systemd[1]:
Thanks, raised here https://gitlab.com/sane-
project/backends/-/issues/278
** Bug watch added: gitlab.com/sane-project/backends/-/issues #278
https://gitlab.com/sane-project/backends/-/issues/278
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Very similar failure observed - the 1st page scans, but the 2nd fails.
Errors in logs are different however:
$ SANE_DEBUG_PIXMA=3 xsane
[sanei_debug] Setting debug level of pixma to 3.
[pixma] pixma is compiled with pthread support.
[pixma] pixma version 0.17.37
[pixma] Scanner model found: Nam
Attached as a file the full output for "simple-scan 3.34.1" when
scanning 2 pages from the feeder, which still has this bug.
Final few lines are here:
[+53.69s] DEBUG: scanner.vala:1345: sane_read (15300) -> (SANE_STATUS_GOOD,
15300)
[+55.00s] DEBUG: scanner.vala:1345: sane_read (15300) -> (SAN
Public bug reported:
Hello,
When scanning multiple pages from a Canon mf244dw via the LAN I only get
the first page scanned, then an error message.
Running "simple-scan -d" and looking at the output I see the following:
[+123.87s] DEBUG: scanner.vala:1321: sane_read (7651) ->
(SANE_STATUS_
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1628735/+attachment/4752979/+files/ProcEnviron.txt
** Changed in: autofs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Tags added: apport-collected xenial
** Description changed:
Autofs supports variables (e.g. $UID, $GID, $HOME, etc), which can be
used in automounter map files. One may have configuration such as
"credentials=${HOME}/.authfile,uid=${UID},gid=${GID}".
If accessing
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1628735/+attachment/4752978/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16287
Public bug reported:
Autofs supports variables (e.g. $UID, $GID, $HOME, etc), which can be
used in automounter map files. One may have configuration such as
"credentials=${HOME}/.authfile,uid=${UID},gid=${GID}".
If accessing the mount as user "foo", this should have the automounter
take credentia
Filed: https://bugzilla.gnome.org/show_bug.cgi?id=726598
** Bug watch added: GNOME Bug Tracker #726598
https://bugzilla.gnome.org/show_bug.cgi?id=726598
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
When opening a file with AESV3 256 encryption evince repeatedly prompts
for a password interactively and fails to render the document.
To recreate:
1. Encrypt a PDF with qpdf:
$ qpdf --version
qpdf version 4.2.0
Copyright (c) 2005-2013 Jay Berkenbilt
This software may be d
I had this problem on an HP envy dv7, running latest Raring release
(thought I'd take a chance on running the pre-release beta), which uses
a 3.8.0.x kernel series.
0a:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
0a:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
Solutio
I believe this bug also impacts me too.
Some simple tests made against the same remote network mount (windows
server via 100mbps Ethernet) when rsyncing a 1GB file produce quite
different results.
First when mounted via Nautilus (i.e. via /var/run/user/$user/gvfs/foo)
I get a transfer rate of und
18 matches
Mail list logo
