Changes between Initial Version and Version 4 of Ticket #14790
- Timestamp:
- Nov 5, 2015 11:20:19 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14790
- Property Component other → network/NAT
-
Ticket #14790 – Description
initial v4 1 I recently found that VirtualBox could no longer communicate with my printer/scanner (same device). The device is attached via network ethernet cable (NAT).1 I recently found that !VirtualBox could no longer communicate with my printer/scanner (same device). The device is attached via network ethernet cable (NAT). 2 2 3 The operating system of the guest is Linux Mint release 17 (qiana) Mate 64-bit. The driver has worked fine for years. After an update of Virtualbox somewhere in version 4.x, I was able to send print commands but I could no longer communicate with the scanner.3 The operating system of the guest is Linux Mint release 17 (qiana) Mate 64-bit. The driver has worked fine for years. After an update of !Virtualbox somewhere in version 4.x, I was able to send print commands but I could no longer communicate with the scanner. 4 4 5 To help narrow down the problem, I tested the exact same operating system and printer driver with 2 different versions of VirtualBox:5 To help narrow down the problem, I tested the exact same operating system and printer driver with 2 different versions of !VirtualBox: 6 6 7 1. VirtualBox v. 4.2.32 v101581: Scanner works8 2. VirtualBox v. 5.064103037: Scanner fails7 1. !VirtualBox v. 4.2.32 `r101581`: Scanner works 8 2. !VirtualBox v. 5.0.6 `r103037`: Scanner fails 9 9 10 Scanning hasn't worked for some time; at least since version 5.0 and possibly a bit before that. I estimate that it broke sometime after 4.3. Comments in VirtualBox's forum indicate that it's a possible regression because nothing has changed except for the VirtualBox version. Every time I downgraded or upgraded VirtualBox, I always installed the corresponding guest additions for that particular version. I tested with version 5.0.8 r103449also; the problem persists.10 Scanning hasn't worked for some time; at least since version 5.0 and possibly a bit before that. I estimate that it broke sometime after 4.3. Comments in !VirtualBox's forum indicate that it's a possible regression because nothing has changed except for the !VirtualBox version. Every time I downgraded or upgraded !VirtualBox, I always installed the corresponding guest additions for that particular version. I tested with version 5.0.8 `r103449` also; the problem persists. 11 11 12 12 To replicate the problem: … … 21 21 22 22 4. There is a cups-insecure-filter error when you try to print. This is easily fixed: 23 23 {{{ 24 24 cd /usr/local/lexmark/v3/bin/ 25 25 sudo chmod 755 printfilter 26 26 }}} 27 27 Printing isn't the problem though. I include this just to be thorough. 28 28 29 5. Install any scanning program. gscan2pdf and Simple Scan both work well. On older versions of VirtualBox (up to about the 4.2 I tested, possibly up to around 4.3), scanning will work just fine. All later versions cut off access to the scanner; the scanning program will say no scanners were detected.29 5. Install any scanning program. gscan2pdf and Simple Scan both work well. On older versions of !VirtualBox (up to about the 4.2 I tested, possibly up to around 4.3), scanning will work just fine. All later versions cut off access to the scanner; the scanning program will say no scanners were detected. 30 30 31 31 // End of steps for reproducing the problem
