Asked by email to associate this bug report to a package; launchpad
won't let me select rmlint-gui, I can only select rmlint.
** Package changed: ubuntu => rmlint (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
rmlint-gui (a.k.a. Shreeder) 2.9.0-2 on top of Ubuntu 20.04 LTS Focal
Fossa runs but it appears to scan a given directory too quickly, without
scanning nor detecting subdirectories, and always reporting no
duplicates. Command line rmlint seems to be working as usual though.
@ Chris Rainey: no such a thing in my system.
@ PeterPall: the scanner works properly now, it only didn't on the very
first time using it. Weird, isn't it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ PeterPall: regarding the Epson scanner, yes it could be the firmware
upload, the first root scan took time, I thought it was the scanner
warming up longer than usual and not catching up, but I allowed time and
it finally went through, so You may very well be right. I did not run
lsusb -v, just a
Hi Peter, if the above is addressed to me, the Epson scanner works for regular
users after the first scan as root, I do not get the reason why, but this is
it.
Thank You for stepping in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Michael, sudo is enough for driver installation, if You did not sudo
that is why install failed. Root is the real system administrator, not
needed for this task.
REegards, Luca
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi again, Epson Perfection 4490 Photo, new Ubuntu Mate 19.04 install,
iscan-bundle-1.0.0.x64.deb.tar.gz driver, make sure to add the line
'epkowa'to the /etc/sane.d/dll.conf file first; xsane gave a 'Access to
resource has been denied' message as a regular user, same with 'sudo
xsane' from a
Hi all, Brother MFC-1910W, new Ubuntu Mate 19.04 install, Brother
drivers from
https://support.brother.com/g/b/downloadend.aspx?c=as_ot=en=mfc1910w_eu_as=128=dlf006893_000=4=625=true
at first the scanner was not detected, my previous workaround involving
libsane-extras is not an option anymore,
Hi Michael, are You installing as root or sudo?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Title:
Many 3rd party scanner drivers are broken by a sane change
To manage notifications
Hi James, glad it worked!
Hi all, on Ubuntu 18.04, with a multifunction HP printer/scanner I could
only run the scanner as root; it was not my system and the relevant
files were already /usr/lib/x86_64-linux-gnu/sane, don't know if they
were there by default or if the owner of the system put them
Back to normal, THA!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791765
Title:
Indicator applet just displays "No Indicators" message
To manage notifications about this bug go to:
Same here, upgraded from BB as soon as CC became available on a test
system, never had the pleasure to see the indicators, which were working
fine on the previous version. Cheers, Luca
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ Peter Bennet: hi there, I have a brother4 driven scanner too, all I
did was to run the latest brother installer and install the libsane-
extras package adding the line "brother4" to the file /etc/sane.d/dll.d
/libsane-extras to get control of the otherwise not detected scanner.
YMMV
--
You
After a bunch of Bionic updates the Brother MFC 1910W scanner gave up
working; I have had to install the libsane-extras package and add the
line "brother4" to the file /etc/sane.d/dll.d/libsane-extras to regain
control of the device. Weird enough the Epson scanner wasn't affected by
the updates.
Clean Ubuntu bionic install, the Brother4 worked out or the box, while
the Epson iscan needed the well known workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707352
Title:
the change from
Double checked, brscan4 symlinks required! To sum it up:
a) install libsane-extras
b) install brscan4
c) 'sudo ln -sfr /usr/lib64/sane/libsane-brother*
/usr/lib/x86_64-linux-gnu/sane'
d) execute 'lsusb' to get VendorId (04f9) and ProductID
e) create '/etc/udev/hwdb.d/brother4.hwdb'
content:
Hi Staedtler, I didn't refresh the page before posting, so I didn't see Your
post #76. Believe it or not the congrats go to You, I would have never done it
without brainstorming with You, and Your posts #71 and 72 have been
elightening. Regarding the /etc/sane.d/dll.d/libsane-extras file, I
This is regarding post #54, I went to https://forum.ubuntu-
it.org/viewtopic.php?f=9=624458 and it turns out that it's a false
alarm, since the user reporting libsane1 failure on ubuntu 16.04 was in
fact running 17.10.
--
You received this bug notification because you are a member of Ubuntu
More on this, everything works as a user with simple-scan and gscan2pdf
too, with both the Epson and the Brother scanners on I can select
between peripherals. Again a public thank You to Staedtler for his help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
To be precise: "v049f is vendor ID, and p035d is product ID" should read
"049f is vendor ID, and 035d is product ID", as in usb:vp, where
the Xs are the outcome of lsusb.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Staedtler, bingo it is. I did try what You suggest, no joy, but the
information that You collected (and that I couldn't even imagine of),
have put me on the right track. Here's what works for me:
1) I created a /etc/udev/hwdb.d/brother4.hwdb file with the lines
usb:v04F9p035D*
Good monday Staedtler, here it is. Regards, Luca
'sane-find-scanner' gave 'found USB scanner (vendor=0x04f9 [Brother],
product=0x035d [MFC-1910W]) at libusb:002:003'
-
'udevadm info -a /dev/bus/usb/002/003' gave
looking at
Hi Staedtler, attached the xsane diff file. I'm out of ideas as well,
but thank You for Your time and effort.
** Attachment added: "diff.xsane.txt"
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+attachment/5010365/+files/diff.xsane.txt
--
You received this bug
Hi Staedtler, attached is the diff file, it's beyond my understanding
:-) even more since scanimage -L does not detect the scanner even as
root, although the scanner itself works running xsane from a root
terminal.
** Attachment added: "scanimage -L output diff"
My bad: the 'ENV' line is on by default, not the 'SYMLINK', my
apologies. Following is the content of the 60-brother-mfp-type1.rules
installed by the brother-udev-rule-type1 package. Uncommenting the
options at the bottom doesn't make any difference: the scanner only
works with xsane as true root.
Hi Staedtler, did that, and fought with several rules files before to no
joy. What You suggest is pretty much the same as what the brother-udev-
rule-type1 package does with a 60 sane something rules file, except that
in the Brother installer script only the line 'SYMLINK' is active, the
rest of
The message is too big perhaps. I'll post again in small chuncks as soon as I
have the chance.
In the meanwhile a 16.04 user reported the scanner failure, apparently due to a
libsane1 update.
See https://forum.ubuntu-it.org/viewtopic.php?f=9=624458 page two, this is
what he gets with
Hi Staedtler, I knew You were right, but I gave it a try; too bad
Brother sold a linux supported product while in fact they give no
support, and not a good after sale service for a 10 months old product.
This is (in short) the debugging output:
'sane-find-scanner' output
-- snip
Hy all, just here to write that after exchanging a bunch of useless
emails with a kind chap from Brother customer support, he finally
redirected me to the "lab technicians", who wrote to me "read the faq,
or check over internet if there are solutions from the community".
--
You received this bug
Hi staedtler-przyborski, I created the /etc/udev/rules.d/79-udev-
brother.rules file as suggested, no joy. I have written to Brother
support, asking if they're planning the release of drivers libsane1
compliant; I've had an automatic reply suggesting to install the non
working driver... hope I'll
Yep, vuescan is the commercial software I was referring to in my
previous post, and yes, I tried the ugly workaround as soon as Hans
Schwimmbeck posted it, and it used to work, but it prevents from
updating too many packages due to a daisy chain of dependencies; I do
not even know if I could
Further tested the Brother MFC-1910W with gscan2pdf, no joy even as
root. Also tested with a commercial scanning software, a 13.5 MB
download supporting current and "vintage" scanners, the Brother MFC-
1910W works out of the box as a user. :-((
--
You received this bug notification because you
Tried to configure the Brother MFC-1910W as a network scanner, same
outcome: it only work with xsane (no simple-scan) as the true root user
(no sudo xscan). TBC
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@staedtler-przyborski
I'm on xorg... I forgot to mention: the Brother scanner only works as root AND
with xsane, simple-scan doesn't work at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Hi staedtler-przyborski, and thank You for taking the time to further
investigate the matter. Yes indeed, I did try to install the brother-
udev-rule-type1 package You kindly linked, also tinkering with the
various settings, and tested with a later release too, even if both
weren't needed in
Thank You for Your time Hans, I do not like 0777 as well, but I was shooting in
the dark. As stated, I tried
## Brother MFC-1910W
ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="035d", MODE="0666",
GROUP="scanner", ENV{libsane_matched}="yes" (or 0660 0664 0777 modes)
which should be the equivalent
PS I'm on brscan 4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Title:
Many 3rd party scanner drivers are broken by a sane change
To manage notifications about this bug go to:
The Brother MFC-1910W printer-fax-scanner, brscan4 based, does not work
with the symlink trick, the scanner is detected by sane-find-scanner,
but is not listed by scanimage -l, and will only work after enabling the
root account and issuing the 'su root' and 'xsane' commands in a
terminal; a simple
I can confirm that the Epson Perfection 4490 Photo scanner, iscan-
gt-x750-bundle-1.0.0.x64 based, works by creating symlinks of the
/usr/lib/sane/libsane-epkowa* files into the /usr/lib/x86_64-linux-
gnu/sane directory by issuing the command 'sudo ln -sfr /usr/lib/sane
/libsane-epkowa*
Cross posting from https://bugs.launchpad.net/ubuntu/+source/sane-
backends/+bug/1707352?comments=all
On artful, libsane1 1.0.27-1~experimental2ubuntu2.1, in short: the Epson
4490 Photo scanner doesn't work, the Brother MDC-1910W scanner only
works as root; both were fully working on zesty. In
Hi there, I uninstalled the ugly workaround and purged the zesty
packages sane, libsane, xsane, scanner drivers, and all the bells and
whistles; reinstalled libsane1 1.0.27-1~experimental2ubuntu2.1, sane,
xsane, simple-scan, Brother and Epson drivers with no issues. In short:
the Epson 4490 Photo
Still on the ugly workaround, while the Epson 4490 scanner keeps
working, I further tested with my Brother MFC 1910W printer/scanner,
which used to work on zesty. Xsane doesn't see the scanner, it only
works as root, that isn't even running sudo xsane, but taking the risk
to assign a password to
The ugly workaround from Hans Schwimmbeck works for me with the Epson
4490 scanner (iscan gtx 750 bundle). During install I was required to
allow the uninstall of the colord package, which I did, reinstalling it
soon after; strangely the removal of colord didn't remove gnome related
stuff as
Dear Jeremy, if this "Please keep the comments respectful." is addressed
to me, since english is not my first language I want to clarify that I
did not mean to be unrespectful; what I mean is that this looks more
like a wart rather than a bug to me, please don't take this personal,
and I'm ready
Installing xenial lts right now, but what if libsane1 will survive
despite the fact that it breaks compatibility with many scanners out in
the wild?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
...obsolete by an arbitrary development (mis)decision.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707352
Title:
the change from libsane to libsane1 broke many (all?) 3rd party plug-
ins for
Installed libsane1 1.0.27-1~experimental2ubuntu2 and the Epson driver
doesn't complain about the unmet dependancies anymore, it won't properly
install however, resulting in a broken package, impossible to fix, only
option is to remove it. This is not a bug IMHO, renaming the package is
"operator
Hi all, as a workaround on ubuntu artful I got rolled back to libsane
libsane-common from zesty, that is 1.0.25+git20150528-1ubuntu4, and xsane
xsane-common 0999.3ubuntu2, locked to those releases; my Epson Perfection 4490
scanner (third party epkowa backend) would only run as root; added the
After a few days of testing I want to tell to all of us struggling with
a hardy kernel on top of gutsy that the best way to go is to install
hardy: everything works much better in hardy than in gutsy with updated
kernel, wicd a must AFAICT. I also have to say that things are working
better than
Hello world, I've set up a wpa2 with tkip/aes encryption network and the
rt73 dongle is working via network manager in hardy with
2.6.24-16-generic kernel (32-bit); I tried to open 35 tabs at once in
firefox while downloading ubuntu's updates and playing videos from
websites, it's been working so
Sorry to verify that the rt2570 dongle above mentioned does not work
period. Regarding the rt73 dongle: upon restart both network manager
and/or manual configuration ask for wpa password while the network is
configured for wpa2, I switched to wicd and it works much better now: it
retains the
Hi everybody, I took a test drive on gutsy with hardy's 2.6.24-16
generic 32-bit kernel: my rt73 dongle works (wep 128, no network
manager); the other dongle I own wich is rt2570 based does not work at
all as usual; I could not test on a fresh install of hardy as trying to
open the network
More on the previous post: I booted hardy and did not bother to try
manual network configuration but went the network manager route; I can
now confirm that the rt73 stick works (it's on right now) while the
rt2570 does not (still talking of wep as wpa has never been an option
with my hardware),
Dear You all, I own an Asus WL-167G wi-fi dongle rt2570 based and it
does not work with hardy's 2.6.24-12-generic kernel 32-bit installed on
top of gutsy; I also have a D-Link DWL-G122 dongle rt73 based dongle
that works very well with the very same kernel on the same computer;
however a full
More about the above post: I did test the dongles on another box, an
Athlon 2800 running gutsy, I've installed hardy's 2.6.24-12 kernel and
the WL-167G stick does not work as on the other machine (Intel dual
core); also the D-Link DWL-G122 worked fine for a bunch of minutes and
then died, I've had
hi there, running gutsy with a 2.6.24-5 hardy kernel, tested with both a
rt2570 and a rt73 usb sticks with no positive outcome: both cards go off
(no blinking led, no connection) after a bunch of minutes online, the
only way to restore a connection is to restart the computer as simply
Public bug reported:
I'm running gutsy with hardy's 2.6.24-5 kernel complete with
headers/sources and related build essentials/libc etc packages: no way
to compile source code from mercurial v4l-dvb-kernel: error code 2, and,
by the way, as a matter of fact no way to compile the serialmonkey
I do agree, but the rt2500usb module works pretty well in both fedora
7-8 and suse 10.3, please have a look at
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-
modules-2.6.22/+bug/18
--
wusb54g doesn't work with 7.10
https://bugs.launchpad.net/bugs/156841
You received this bug
Daniel
This looks similar with bug #147811. I have the same problem.
I do agree with ^that^, this is the same that's happening to me
I have posted my log files on the other bug report.
regarding Your dmesg:
[ 218.108000] ieee80211_init: failed to initialize WME (err=-17)
[ 218.12]
Vittorio, I get this very same problem with/without wep, could You please post
the outputs of the following commands:
lsusb
dmesg
ifconfig
iwconfig
Daniel, forgive me for double posting here and on
https://bugs.launchpad.net/bugs/18
This looks similar with bug #147811. I have the same
Thank You for taking the time to deal with this.
Yes. But rt2x00 is a driver for several chips. So if rt2x00 is update,
it may help you too.
I'm sorry it does not help; I also took a test with the latest 2.6.22-14 kernel
with no success, the only thing I spotted is from dmesg:
[EMAIL
Hi there, as a new kernel is out I was coming to give You an update, and
here it is; thank You for pointing me to
https://bugs.launchpad.net/bugs/139070 but the stick I'm talking about
is an rt25 card not an rt73 one. So, new kernel, same behaviour, here it
is the details:
[EMAIL PROTECTED]:~$
Id2ndR wrote:
Hi,
According to $ modinfo rt2500usb | grep -i v0b05p1706
The module should be loaded with your device.
Is your device using rt73 with cvs version ?
What are the loaded module ($ lsmod | grep rt) with cvs version ?
I'm not at the box now, anyhow: yes the rt2500usb module
I came across the same misbeheaviour on a desktop with an nvidia 6600
card: after changing resolution I have to run Synaptic and reinstall the
nvidia-glx package, after this voodoo like procedure the resolution
stays as set even after log out.
--
when switching to dual-monitor, log out, log in,
Public bug reported:
Stick details as from lsusb: Bus 005 Device 004: ID 0b05:1706 ASUSTek
Computer, Inc., this thing used to work out of the box in feisty. It
does not work in gutsy with kernel 2.6.22-12-generic i686 (and
previous): card is detected but signal strenght stays at zero and no way
Ben, thank You for Your attention. Of course there's a typo in my last
post: 2.6.2.-rc6 should read 2.6.20-rc6, moreover I'm running
2.6.20-8-generic i686 at the moment and it is fine so far.
--
sata_via not working anymore - kernel 2.6.20
https://launchpad.net/bugs/80297
--
ubuntu-bugs
With the feisty 2.6.2.-rc6 kernel sata via is back to normal! However I
downloaded the stable 2.6.20 kernel and compiled it with the feisty
2.6.20-rc6 config file and the resulting kernel would go past the sata
via initialization but will stop at the raid initialization stage.
Compiled again with
Public bug reported:
Binary package hint: linux-source-2.6.20
Both kernel 2.6.19 (Ubuntu and Fedora) and 2.6.20 (Ubuntu) do not boot:
when probing sata hardware the system is unable to correctly identify
the hard disks on a system with a PCI Via VT6420 sata raid controller
and a couple of
I may add that these very same computers where working fine with both
Ubuntu kernel 2.6.17 and Fedora 2.6.16.
--
sata_via not working anymore - kernel 2.6.20
https://launchpad.net/bugs/80297
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
69 matches
Mail list logo
