[Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
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 [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX200 [8086:0084] Kernel driver in use: iwlwifi Kernel modules: iwlwifi I will try the kernel parameter `btusb.enable_autosuspend=0` but (touch wood) won't be able to replicate for another week as this system is my daily-driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904764] Re: failed boot mount, and systemd ordering cycle on zfs-import.target
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904764 Title: failed boot mount, and systemd ordering cycle on zfs-import.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904764] Re: failed boot mount, and systemd ordering cycle on zfs-import.target
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904764 Title: failed boot mount, and systemd ordering cycle on zfs-import.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904764] Re: failed boot mount, and systemd ordering cycle on zfs-import.target
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 timestamps show otherwise $ journalctl -f -u boot.mount -- Logs begin at Sat 2020-11-14 20:41:30 EST. -- Nov 19 22:20:45 test systemd[1]: Mounting /boot... Nov 19 22:20:45 test systemd[1]: Mounted /boot. -- Reboot -- Nov 19 22:21:34 test systemd[1]: Mounting /boot... Nov 19 22:21:35 test systemd[1]: Mounted /boot. -- Reboot -- Nov 20 16:19:07 test mount[1265]: filesystem 'bpool/BOOT/ubuntu_o9gk00' cannot be mounted, unable to open the dataset Nov 20 16:19:07 test systemd[1]: boot.mount: Mount process exited, code=exited, status=1/FAILURE Nov 20 16:19:07 test systemd[1]: boot.mount: Failed with result 'exit-code'. Nov 20 16:19:07 test systemd[1]: Failed to mount /boot. Nov 20 16:19:52 test systemd[1]: Mounting /boot... Nov 20 16:19:52 test systemd[1]: Mounted /boot. $ systemctl status zfs-import-cache.service ● zfs-import-cache.service - Import ZFS pools by cache file Loaded: loaded (/lib/systemd/system/zfs-import-cache.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2020-11-20 16:19:08 EST; 16min ago Docs: man:zpool(8) Main PID: 2084 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 18936) Memory: 0B CGroup: /system.slice/zfs-import-cache.service Nov 20 16:19:08 test systemd[1]: Starting Import ZFS pools by cache file... Nov 20 16:19:08 test systemd[1]: Finished Import ZFS pools by cache file. So mount ran at 16:19:07 (and failed) yet zfs-import-cache didn't complete until 16:19:08. That's rather odd... $ journalctl -f -u zfs-import-cache.service -- Logs begin at Sat 2020-11-14 20:41:30 EST. -- Nov 19 22:21:34 test systemd[1]: Finished Import ZFS pools by cache file. -- Reboot -- Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found ordering cycle on zfs-import.target/start Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found dependency on zfs-import-cache.service/start Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found dependency on cryptsetup.target/start Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found dependency on systemd-cryptsetup@cryptoswap.service/start Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found dependency on systemd-random-seed.service/start Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found dependency on var-lib.mount/start Nov 20 16:19:07 test systemd[1]: var-lib.mount: Job zfs-import.target/start deleted to break ordering cycle starting with var-lib.mount/start Nov 20 16:19:08 test systemd[1]: Starting Import ZFS pools by cache file... Nov 20 16:19:08 test systemd[1]: Finished Import ZFS pools by cache file. Now I see zfs-import-cache was "deleted" by systemd at 16:19:07 to break an ordering cycle, which I think explains the above - but this seems wrong? If I then look at the prior zfs-import-cache log, I can see cryptsetup@cryptoswap.service was "deleted", thus enabling /boot to mount correctly: Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found ordering cycle on systemd-cryptsetup@cryptoswap.service/start Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on systemd-random-seed.service/start Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on var-lib.mount/start Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on zfs-load-key-rpool.service/start Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on zfs-import.target/start Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on zfs-import-cache.service/start Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on zfs-load-module.service/start Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on cryptsetup.target/start Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Job systemd-cryptsetup@cryptoswap.service/start deleted to break ordering cycle starting with cryptsetup.target/start Nov 19 22:21:34 test systemd[1]: Starting Import ZFS pools by cache file... Nov 19 22:21:34 test systemd[1]: Finished Import ZFS pools by cache file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904764 Title: failed boot mount, and systemd ordering cycle on zfs-import.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904764] Re: failed boot mount, and systemd ordering cycle on zfs-import.target
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904764 Title: failed boot mount, and systemd ordering cycle on zfs-import.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904764] [NEW] failed boot mount, and systemd ordering cycle on zfs-import.target
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]: Failed to mount /boot. [ 11.354307] systemd[1]: Dependency failed for /boot/efi. [ 11.354327] systemd[1]: Dependency failed for /boot/grub. [ 11.354344] systemd[1]: Dependency failed for Local File Systems. [ 11.354365] systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. [ 11.354367] systemd[1]: local-fs.target: Triggering OnFailure= dependencies. [ 11.355088] systemd[1]: var-lib.mount: Found ordering cycle on zfs-import.target/start [ 11.355090] systemd[1]: var-lib.mount: Found dependency on zfs-import-cache.service/start [ 11.355091] systemd[1]: var-lib.mount: Found dependency on zfs-load-module.service/start [ 11.355093] systemd[1]: var-lib.mount: Found dependency on cryptsetup.target/start [ 11.355094] systemd[1]: var-lib.mount: Found dependency on systemd-cryptsetup@cryptoswap.service/start [ 11.355096] systemd[1]: var-lib.mount: Found dependency on systemd-random-seed.service/start [ 11.355097] systemd[1]: var-lib.mount: Found dependency on var-lib.mount/start [ 11.355099] systemd[1]: var-lib.mount: Job zfs-import.target/start deleted to break ordering cycle starting with var-lib.mount/start [ 11.355819] systemd[1]: boot-grub.mount: Job boot-grub.mount/start failed with result 'dependency'. [ 11.355823] systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed with result 'dependency'. Journalctl shows "filesystem 'bpool/BOOT/ubuntu_o9gk00' cannot be mounted, unable to open the dataset" for boot.mount I can manually start boot.mount from the console, which then lets the boot process complete. N.B. "zfs list" is NAME USED AVAIL REFER MOUNTPOINT bpool 402M 1.36G 96K /boot bpool/BOOT 401M 1.36G 96K none bpool/BOOT/ubuntu_o9gk00 401M 1.36G 201M /boot rpool 171G 720G 192K / rpool/ROOT9.26G 720G 192K none rpool/ROOT/ubuntu_1.57G 720G 5.16G / rpool/ROOT/ubuntu_o9gk00 7.69G 720G 4.24G / rpool/ROOT/ubuntu_o9gk00/srv 192K 720G 192K /srv rpool/ROOT/ubuntu_o9gk00/usr 1.02M 720G 192K /usr rpool/ROOT/ubuntu_o9gk00/usr/local 852K 720G 388K /usr/local rpool/ROOT/ubuntu_o9gk00/var 2.09G 720G 192K /var rpool/ROOT/ubuntu_o9gk00/var/games 192K 720G 192K /var/games rpool/ROOT/ubuntu_o9gk00/var/lib 1.85G 720G 1.42G /var/lib rpool/ROOT/ubuntu_o9gk00/var/lib/AccountsService 1.39M 720G 496K /var/lib/AccountsService rpool/ROOT/ubuntu_o9gk00/var/lib/NetworkManager 3.39M 720G 292K /var/lib/NetworkManager rpool/ROOT/ubuntu_o9gk00/var/lib/apt 87.2M 720G 78.0M /var/lib/apt rpool/ROOT/ubuntu_o9gk00/var/lib/dpkg 148M 720G 63.6M /var/lib/dpkg rpool/ROOT/ubuntu_o9gk00/var/log 223M 720G 94.2M /var/log rpool/ROOT/ubuntu_o9gk00/var/mail 1.19M 720G 224K /var/mail rpool/ROOT/ubuntu_o9gk00/var/snap 940K 720G 500K /var/snap rpool/ROOT/ubuntu_o9gk00/var/spool26.7M 720G 5.52M /var/spool rpool/ROOT/ubuntu_o9gk00/var/www 192K 720G 192K /var/www rpool/USERDATA 162G 720G 192K / rpool/USERDATA/chris_hwz0bd162G 720G 156G /home/chris rpool/USERDATA/root_hwz0bd2.91M 720G 804K /root rpool/keystore 518M 720G 48.1M - ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Description changed: 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]: Failed to mount /boot. + [ 11.354307] systemd[1]: Dependency failed for /boot/efi. + [ 11.354327] systemd[1]: Dependency failed for /boot/grub. + [ 11.354344] systemd[1]: Dependency failed for Local File Systems. + [ 11.354365] systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. + [ 11.354367] systemd[1]: local-fs.target: Triggering OnFailure= dependencies. + [ 11.355088] systemd[
[Bug 1759889] Re: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759889 Title: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759889] Re: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw
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: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_find_scanners() found 1 devices (xsane:6919): Gdk-CRITICAL **: 12:08:35.630: IA__gdk_drawable_unref: assertion 'GDK_IS_DRAWABLE (drawable)' failed (xsane:6919): Gdk-CRITICAL **: 12:08:35.630: IA__gdk_drawable_unref: assertion 'GDK_IS_DRAWABLE (drawable)' failed [pixma] Scanner model found: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_open(): Canon i-SENSYS MF240 Series [pixma] *iclass_open* This is a generation 2 scanner. * [pixma] Trying to clear the interrupt buffer... [pixma] no packets in buffer [xsane] ERROR: xsane-startimage not found. Looks like xsane is not installed correct. [pixma] Reader task started [pixma] Reader task id=140132160792320 (threaded) [pixma] [pixma] pixma_scan(): start [pixma] line_size=7680 image_size=32256000 channels=3 depth=8 [pixma] dpi=300x300 offset=(0,0) dimension=2560x4200 [pixma] gamma_table=0x55deb339ae38 source=1 [pixma] threshold=127 threshold_curve=0 [pixma] adf-wait=0 [pixma] ADF page count: 0 [pixma] Setting non-blocking mode [pixma] raw_width = 2560 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_scan* start scanning * [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_finish_scan* wait for next page from ADF * [pixma] WARNING:image size mismatches [pixma] 32256000 expected (4200 lines) but 25489920 received (3319 lines) [pixma] pixma_read_image(): completed (underrun detected) [pixma] Reader task terminated [pixma] pixma_close(): Canon i-SENSYS MF240 Series vs $ SANE_DEBUG_PIXMA=3 simple-scan [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: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_find_scanners() found 1 devices [pixma] Scanner model found: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_open(): Canon i-SENSYS MF240 Series [pixma] *iclass_open* This is a generation 2 scanner. * [pixma] Trying to clear the interrupt buffer... [pixma] no packets in buffer [pixma] Reader task started [pixma] Reader task id=140424282892032 (threaded) [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] [pixma] pixma_scan(): start [pixma] line_size=1280 image_size=2112000 channels=1 depth=8 [pixma] dpi=150x150 offset=(0,0) dimension=1275x1650 [pixma] gamma_table=0x7fb6fc28db88 source=1 [pixma] threshold=127 threshold_curve=0 [pixma] adf-wait=0 [pixma] ADF page count: 0 [pixma] raw_width = 1280 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_scan* start scanning * [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_finish_scan* wait for next page from ADF * [pixma] pixma_read_image():completed [pixma] Reader task termin
[Bug 1759889] Re: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw
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) -> (SANE_STATUS_GOOD, 7649) [+55.00s] DEBUG: scanner.vala:1345: sane_read (15301) -> (SANE_STATUS_EOF, 0) [+55.00s] DEBUG: scanner.vala:1241: sane_start (page=1, pass=0) -> SANE_STATUS_GOOD [+55.00s] DEBUG: scanner.vala:1258: sane_get_parameters () -> SANE_STATUS_GOOD [+55.00s] DEBUG: scanner.vala:1270: Parameters: format=SANE_FRAME_RGB last_frame=SANE_TRUE bytes_per_line=7650 pixels_per_line=2550 lines=3300 depth=8 [+55.00s] DEBUG: autosave-manager.vala:349: Autosaving page pixels to /home/test-machine/.cache/simple-scan/autosaves/496152848.pixels [+55.02s] DEBUG: autosave-manager.vala:281: Autosaving book information [+55.02s] DEBUG: autosave-manager.vala:298: Autosaving page page-0 [+55.02s] CRITICAL: page_finish: assertion 'self != NULL' failed [+55.02s] DEBUG: simple-scan.vala:350: Page is 2550 pixels wide, 3300 pixels high, 8 bits per pixel [+55.03s] DEBUG: simple-scan.vala:284: Getting color profile for device pixma:MF240_canon-mfc.lan [+55.04s] DEBUG: simple-scan.vala:304: Unable to find colord device pixma:MF240_canon-mfc.lan: property match 'Serial'='sane:pixma:MF240_canon-mfc.lan' does not exist [+56.00s] DEBUG: scanner.vala:1345: sane_read (7651) -> (SANE_STATUS_NO_DOCS, 0) [+56.00s] DEBUG: scanner.vala:1214: sane_cancel () ** Attachment added: "output.txt" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+attachment/5356478/+files/output.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759889 Title: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759889] [NEW] Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw
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_CANCELLED, 0) [+123.87s] WARNING: scanner.vala:1337: Unable to read frame from device: Operation was cancelled [+123.87s] DEBUG: scanner.vala:768: sane_cancel () [+123.87s] DEBUG: scanner.vala:771: sane_close () I do notice that the scanner is already feeding in the second page before the first page has completely rendered on screen - perhaps it's going too fast? Thanks ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759889 Title: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628735] ProcEnviron.txt
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628735 Title: Autofs variables do not work with kernel 4.4.0-38.57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1628735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628735] Re: Autofs variables do not work with kernel 4.4.0-38.57
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 the mount as user "foo", this should have the automounter
take credentials from ~foo/.authfile and mount it as being owned by
foo:foo.
On kernel 4.4.0-36.55 and earlier this all works as expected.
- It no longer works with kernel 4.4.0-38.57 and instead these variables
- are always as user "root".
+ It no longer works with kernel 4.4.0-38.57 and instead these variables are
always as user "root".
+ ---
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-10-02 (0 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
+ Package: linux
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
+ Tags: xenial
+ Uname: Linux 4.4.0-38-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1628735/+attachment/4752977/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628735
Title:
Autofs variables do not work with kernel 4.4.0-38.57
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1628735/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628735] JournalErrors.txt
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/1628735 Title: Autofs variables do not work with kernel 4.4.0-38.57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1628735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628735] [NEW] Autofs variables do not work with kernel 4.4.0-38.57
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 credentials from ~foo/.authfile and mount it as being owned by
foo:foo.
On kernel 4.4.0-36.55 and earlier this all works as expected.
It no longer works with kernel 4.4.0-38.57 and instead these variables
are always as user "root".
** Affects: autofs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628735
Title:
Autofs variables do not work with kernel 4.4.0-38.57
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1628735/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293282] Re: evince cannot open pdf with AESV3 256 encryption
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/bugs/1293282 Title: evince cannot open pdf with AESV3 256 encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1293282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293282] [NEW] evince cannot open pdf with AESV3 256 encryption
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 distributed under the terms of version 2 of the Artistic License which may be found in the source distribution. It is provided "as is" without express or implied warranty. $ qpdf --encrypt "wibble" "wobble" 256 -- plain.pdf encrypted.pdf $ egrep -a AES encrypted.pdf << /CF << /StdCF << /AuthEvent /DocOpen /CFM /AESV3 /Length 32 >> >> /Filter /Standard /Length 256 ... 2. Check it opens with Adobe Acrobat 3. Attempt to open with evince: $ evince --version GNOME Document Viewer 3.10.0 $ evince encrypted.pdf (evince:17902): EvinceDocument-CRITICAL **: ev_document_get_n_pages: assertion 'EV_IS_DOCUMENT (document)' failed Syntax Error: Invalid encryption key length Command Line Error: Incorrect password Syntax Error: Invalid encryption key length Command Line Error: Incorrect password (evince:17902): Gtk-CRITICAL **: gtk_widget_get_toplevel: assertion 'GTK_IS_WIDGET (widget)' failed ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293282 Title: evince cannot open pdf with AESV3 256 encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1293282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049466] Re: Need support of Ralink RT3290 wifi support
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 Solution for me was in #8 above: # git clone git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git # cp linux-firmware/rt3290.bin /lib/firmware/ # shutdown -r now Hopefully the "linux-firmware" .deb will eventually include this. Raring is using 1.104, which doesn't include rt3290.bin yet. This has got wireless working correctly, however there are still 2 minor (for me) problems. 1) Bluetooth isn't working 2) The "airplane mode" keyboard toggle doesn't do anything -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049466 Title: Need support of Ralink RT3290 wifi support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1049466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075923] Re: nautilus hangs copying large directories from a samba share
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 under 3MB/s. Then when using a permanent mount (i.e. mount -t cifs //foo/bar /mnt/bar) I get a transfer rate of over 9MB/s, which is nearly saturating the Ethernet link. I've repeated these checks in reverse order to eliminate the effects of caching, and it seems that gvfs is having the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075923 Title: nautilus hangs copying large directories from a samba share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1075923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
