Re: Sane Scanner Resolution Configuration
by Mike Flannigan
Sure thing.
The 'xsane.rc' file at
~/.sane/xsane
is copied here:
http://www.mflan.com/temp/xsane.rc
There is also a 'xsane.mdf' file in there, but
I don't think you need that.
There is also a 'CANON:Canoscan9000FMarkII.drc'
file in there and it is copied here:
http://www.mflan.com/temp/CANON:Canoscan9000FMarkII.drc
Mike
On 7/21/20 10:09 PM, users-request(a)lists.fedoraproject.org wrote:
> Thanks Mike, that's interesting, my Xsane ver 0.999 doesn't provide
> the same functionality. Where your gui has the resolution dropdown to
> let you select between the supported resolutions, my gui has two
> entries, a horizontal resolution and a vertical resolution, and both
> of them are disabled, so that the only way to change it is to manually
> changed the corresponding two lines in the configuration file. I'm now
> wondering whether the Epson driver is having an impact, as in order to
> see and use the Epson scanner xsane seems to be using the settings I
> put in the config file created by the install of Epson's imagescan
> software.
> Are you able to supply the config file, or the resolution part of the
> config file, for your scanner, which if it is stored in the same
> location as it is for me, is in ~/.sane/xsane? I just wanted to see
> how it is set up for you and whether or not I can replicate that in my
> configuration.
3 years, 8 months
bizzare dual-monitor behavior
by Greg Woods
Let me start by saying I have used this same setup literally for years now
and have not seen this new issue until yesterday.
I have a dual monitor setup. One of the monitors is controlled by a KVM
switch; the machines that have only a single graphics port use this monitor
via the KVM switch. The other monitor has two HDMI ports that are connected
to two computers directly, bypassing the KVM switch; I just switch the
second monitor manually between the two as needed.
What used to happen when I switched to a different computer is that I can
use the new computer using the first monitor, the mouse and the keyboard,
just as usual. The second monitor, unaffected by the KVM switch, will
continue to show the image it is getting from the dual-monitor system. I am
used to this; sometimes I even use it to my advantage when the monitor is
showing a web page or something that I can still see while working on a
different computer.
But, what is now happening (since yesterday) is that when I switch to a
second computer, the non-KVM-switched monitor now flashes off and on every
few seconds (and just keeps doing this seemingly forever; I did leave it
this way for more than 15 minutes last night) . This is INCREDIBLY annoying
and makes it impossible to make any use of the image displayed there.
Another oddity is that this is NOT happening with the other dual-monitor
machine. That system is a Dell laptop in a dock. The system with the issue
is a fairly new desktop (which did not exhibit the issue for the first few
days of use, it suddenly started yesterday). Both systems are running
Fedora 32 (but of course they have very different hardware).
I normally use GNOME on Xorg, but I have tried plain GNOME (Wayland) and
Cinnamon too and the problem exists there as well. I briefly tried Plasma,
but that results in a solid green screen, and when I switch back to the
two-monitor system, the first monitor is solid green too and none of the
keys respond, so I had to use a remote ssh shutdown to recover.
Has anyone ever seen anything like this and know what I could do to stop it?
Thanks,
--Greg
3 years, 8 months
Printing failure -
by Bob Goodwin
Earlier today I discovered that I could not print from this Fedora 32.
It has always printed without a problem. The printer is Ethernet
connected to my LAN. I have gone through the setup with cups, the
fedora/gnome admin app, and now the Brother liinux install tool.
Cups shows:
HLL5100DN <http://localhost:631/printers/HLL5100DN> HLL5100DN
Brother HLL5100DN for CUPS Paused - "could not create directory
"/root/BRF": Permission denied"
The Brother install tool quits when it tries to make a test print and
finds it can't see the printer:
lpadmin -p HLL5100DN -v cups-brf:/ -E
Test Print? [y/N] ->y
wait 5s.
lpr -P HLL5100DN /usr/share/cups/data/testprint
ls: cannot access '/etc/udev/rules.d/*.rules': No such file or directory
ls: cannot access '/etc/udev/rules.d/*.rules': No such file or directory
Hit Enter/Return key.
I began writing this yesterday, this morning we tried and were able to
print from a Mac portable via wifi so that says the printer works at
least. Something is corrupted in my computer it appears?
And doing "ctrl p" fails with:
> Cups shows:
> HLL5100DN <http://localhost:631/printers/HLL5100DN> HLL5100DN
> Brother HLL5100DN for CUPS Paused - "could not create directory
> "/root/BRF": Permission denied"
>
>
> The Brother install tool quits when it tries to make a test print and
> finds it can't see the printer:
>
> lpadmin -p HLL5100DN -v cups-brf:/ -E
> Test Print? [y/N] ->y
Any thoughts on what to do? Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
FEDORA-32/64bit LINUX XFCE Fastmail POP3
3 years, 8 months
Alternatives link broken after package upgrade
by Terry Polzin
I've been dealing with this issue on a couple of my Fedora 32 machines.
It appears that the upgrade of icedtea-web
from icedtea-web-1.8.2-3.fc31.x86_64 to
icedtea-web-2.0.0-pre.0.3.alpha13.patched1.fc32.x86_64 breaks the
alternatives link to javaws.x86_64.
I have to downgrade icedtea-web to be able to run JNLPs
3 years, 8 months
podman and PCI passthrough
by Mauricio Tavares
What is the argument I need to properly pass a PCI or PCIe
device to a podman container at runtime (podman-run)?
3 years, 8 months
Re: Sane Scanner Resolution Configuration
by Mike Flannigan
My XSane ver 0.999 allows changing the resolution
by selecting the dropdown on the main screen and
selecting 75, 150, 300, 600, etc.
http://www.mflan.com/temp/res1.jpg
Mike
On 7/21/20 4:08 AM, users-request(a)lists.fedoraproject.org wrote:
> Subject:
> Sane Scanner Resolution Configuration
> From:
> Stephen Morris <samorris(a)netspace.net.au>
> Date:
> 7/21/20, 4:08 AM
>
> To:
> fedora <users(a)lists.fedoraproject.org>
>
>
> Hi,
> Having installed imagescan from Epson, and installed sane and
> xsane, and edited the imagescan config file to specify the network
> settings of my printer all-in-one, I now have xsane finding my
> scanner, but this has highlighted a problem.
> Having run xsane it has created Epson:ET-3700.drc in path
> ~/.sane/xsane, which contains all the options used by xsane for
> scanning. Two of the options are for the horizontal and vertical scan
> resolution, which by default are set to 75. These options are
> reflected in the xsane gui, but they are disabled so I can't alter
> them from the gui, I have to edit the config file and specify the
> resolution I want in there.
> Where can I find documentation on the format of that xsane config
> file, that would tell me how I get the list of resolutions the scanner
> supports into that config file so that they are selectable by a
> dropdown in the xsane gui?
>
> regards,
> Steve
3 years, 8 months
More portal nonsense?
by Tom Horsley
Imagine my surprise to find this in my daily logwatch:
df: /root/.cache/doc: Operation not permitted
So I check it out:
[root@zooty ~]# mount | fgrep doc
portal on /root/.cache/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
More nonsense from portal and flatpak being dragged in?
3 years, 8 months
F32 nftables hiccups
by ja
I have been attempting to use nft/nftables
to blacklist ssh connections and have come across
two problems.
nftables-0.9.3-3.fc32.x86_64
kernel-5.7.8-200.fc32.x86_64
1. The "limit rate" syntax does not work correctly unless
the "burst" value is set.
counter add @saddr_rate { ip saddr timeout 2m limit rate over 4/minute burst 1 packets} counter \
update @saddr_blacklist { ip saddr timeout 10m } counter drop
2. The following syntax is not accepted by nft
update @connection_count { ip saddr ct count over 3 } \
add @saddr_blacklist { ip saddr timeout 1m } drop
nft_harting.nft:80:3-52: Error: Could not process rule: Operation not supported
update @connection_count { ip saddr ct count over 3 } \
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I have been following a Debian mail list (amongst many)
https://unix.stackexchange.com/questions/581964/create-dynamic-blacklist-...
which implies that both of the above should work with the kernel/nft F32 versions installed.
I attach the output of nft list ruleset
(with the offending rule "{ ip saddr ct count over 3 }" commented out)
(It includes the "set" definitions used above)
Can anyone see any deliberate mistakes?
John
3 years, 8 months
Re: virtual box win7
by Ed Greshko
On 2020-07-21 16:27, Stephen Morris wrote:
Replying to an errant reply to a mailing list post which replied to me directly and not the list.
> On 21/7/20 8:42 am, Ed Greshko wrote:
>> On 2020-07-21 05:47, Patrick Dupre wrote:
>>> Hello,
>>>
>>> I am trying to have my virtual box recognizing the USB devices,
>>> but I get <no device recognized>
>>>
>>> I installed
>>> Oracle_VM_VirtualBox_Extension_Pack-5.0.40.vbox-extpack
>>>
>>> which is supposed to provide the UBS 2.0 and 3.0 drivers
>>>
>>> My devices are recognize by linux.
>>>
>>> Any idea?
>> Where did you obtain VirtualBox?
>>
>> Does the version you installed match the Extension Pack?
>>
>> rpmFusion supplies 6.10 so you'd need Oracle_VM_VirtualBox_Extension_Pack-6.1.10.vbox-extpack
> Hi Patrick, I'm using Virtualbox 6.1.12 R139181 under Windows 10, which I got from the Oracle web site. I have also just updated the extension pack to also 6.1.12, but I don't think the extension pack is what provides usb support (I thought the main usage of the extension pack is to get shared folders available) I thought the usb support was natively built in to virtualbox. In the machine settings in the usb section, I have 'Enable USB Controller' ticked, and then within that I have the radio button 'USB 3.0 (xHCI) Controller' selected, but that does not enable usb in virtualbox, any device inserted into a usb port is "mounted" under windows, and then I have to click on the usb icon in the virtualbox taskbar and then select the inserted device from the popup list to get the device into the linux virtual machine. Then once finised with the device do the same thing again to give the device back to windows.
Please see https://www.virtualbox.org/manual/ch01.html#intro-installing
as to information of what the extension pack provides....
Partially, from the page...
Extension packs. Additional extension packs can be downloaded which extend the functionality of the Oracle VM VirtualBox base package. Currently, Oracle provides a single extension pack, available from: http://www.virtualbox.org. The extension pack provides the following added functionality:
The virtual USB 2.0 (EHCI) device. See Section 3.11.1, “USB Settings”.
The virtual USB 3.0 (xHCI) device. See Section 3.11.1, “USB Settings”.
--
The key to getting good answers is to ask good questions.
3 years, 8 months