[Bug 1249074] Re: xsane no device available and crash

2015-02-05 Thread Cristiano Nunes
** Changed in: xsane (Ubuntu) Status: Confirmed = Fix Released ** Changed in: sane-backends (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1249074] Re: xsane no device available and crash

2014-05-21 Thread Cristiano Nunes
Today, a new update libsane_1.0.23-0ubuntu3 fixed the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249074 Title: xsane no device available and crash To manage notifications about

[Bug 1249074] Re: xsane no device available and crash

2014-05-21 Thread Cristiano Nunes
Today, a new update libsane_1.0.23-0ubuntu3.1 fixed the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249074 Title: xsane no device available and crash To manage notifications

[Bug 1249074] Re: xsane no device available and crash

2014-05-18 Thread FransSchreuder
This bug still exists in Ubuntu 14.04 LTS. Xsane as well as scanimage and simple-scan crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249074 Title: xsane no device available and crash To

[Bug 1249074] Re: xsane no device available and crash

2014-05-18 Thread FransSchreuder
What works for me is to install libsane-common and libsane (debian package) https://launchpad.net/ubuntu/raring/amd64/libsane-common/1.0.23-0ubuntu1 https://launchpad.net/ubuntu/raring/amd64/libsane/1.0.23-0ubuntu1 My scanner is now working again in Ubuntu 14.04 ** Also affects: sane-backends

[Bug 1249074] Re: xsane no device available and crash

2014-05-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (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/1249074

[Bug 1249074] Re: xsane no device available and crash

2014-05-18 Thread Cristiano Nunes
I have this same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249074 Title: xsane no device available and crash To manage notifications about this bug go to:

[Bug 1249074] Re: xsane no device available and crash

2014-05-18 Thread Cristiano Nunes
I have this same problem. Based on FransSchreuder solution, I found a temporary workaround: I extracted the file: libsane-genesys.so.1.0.23 To directory: /usr/lib/x86_64-linux-gnu/sane/libsane-genesys.so.1.0.23 From package: libsane_1.0.23-0ubuntu1_amd64.deb This avoid problems with package

[Bug 1249074] Re: xsane no device available and crash

2014-02-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xsane (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/1249074 Title:

[Bug 1249074] Re: xsane no device available and crash

2013-11-07 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people

[Bug 1249074] Re: xsane no device available and crash

2013-11-07 Thread Quinn Balazs
** Package changed: ubuntu = xsane (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249074 Title: xsane no device available and crash To manage notifications about this bug go to: