Till, in my ppa the symbol files are not up to date. I just removed
outdated entries, but not added new ones.
However, libpng-dev is included to the build by other dependecies. I see
that adding this package to control file makes this dependency more
transparent and I'll add it into my ppa.
--
@Peter:
Alternatively you could use the sources from SANE's daily git snapshots instead
of using Debian experimental branch.
This also breaks my ppa, which provides builds from SANE's daily git
snapshots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I just fixed this issue. My ppa will provide the fix tomorrow:
1.0.27+git20170901.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512027
Title:
open of device pixma:MX7600_... failed: invalid
I just committed the patch to Sane's git repository.
My ppa (https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git)
should work after the next update tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I prepared a ppa for SANE daily git snapshots here:
https://launchpad.net/~rolfbensch/+archive/sane-git.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096612
Title:
canon pixma MP970 TPU scanning
From latest Sane git self compiled sane-find-scanner is working on my
Ubuntu 12.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/601652
Title:
Cannon CanoScan 9000F not supported in Ubuntu xsane
I just tried the CS9000F with xsane on a fresh installed Ubuntu 12.10.
It is working out of the box!
If you want to install latest Sane on top of Ubuntu you should fetch
Sane 1.0.24 from git and follow the installation description Step by
step install on Linux 2.6.* and 3.* in README.linux,
It seems that there is a communication problem.
Open a terminal and activate debug messages: 'export SANE_DEBUG_PIXMA=11' and
'export SANE_DEBUG_SANEI_USB=255'.
(1) check the usb devices: 'lsusb -v usb.log'
(2) start scanimage searching your scanner: 'scanimage -L 2pixma.log'.
(3) try a scan:
Congratulations, my last post is obsolete now.
You're right, debugging sane-find-scanner is academic, when the used
scanner is working.
I have the same problem with sane-find-scanner on my Ubuntu 12.10. But
not on my LTS system with Sane compiled from git. I will check it with a
self compiled
I have no experiences with scanning from gimp.
Scanning from xsane is running perfect for me on my 64 bit Ubuntu 12.04.
Otherwise I would fix it and commit the patches to Sane git. ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please use the attached patch to fix pixma_mp810.c.
** Patch added: pixma_mp810.c.diff
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1096612/+attachment/3476847/+files/pixma_mp810.c.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
While analysing this problem dont't forget that vga16 and nvidia (and
other graphic drivers) are sharing the same primary frame buffer device
/dev/fb0
(https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/459639/comments/52).
Vga16 is the first available graphics driver at boot time, and will
This is a duplicate of bug #459639.
Robert, your comment #9 shows the main problem. vga16 and nvidia use the
same frame buffer device /dev/fb0 during boot up (see:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/459639/comments/52).
With this the start conditions in kdm.conf for the
It seems that this (https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/459639/comments/53) solved both problems (1) X server starts
randomly in failsafe when starting from cold boot and (2) boot hangs on
splash screen.
--
boot hangs on splash screen, does not show kdm
I found the reason for this problem. The kernel initialises the
framebuffer /dev/fb0 device with the vesa driver (vga16fb) before it
starts loading the nvidia driver. You can see this in the attached
syslog file.
** Attachment added: syslog
http://launchpadlibrarian.net/51976046/syslog
--
I patched kdm.conf with a sleep before any other commands will be
executed. For debugging kdm.conf wites 2 messages into syslog: start
kdm and sleep and resume kdm after sleep. Maybe you need to extend
the sleep time, if your graphic card takes more time to load the nvidia
driver than mine. I
Here is a syslog file with the debug messages from kdm. It shows that
kdm starts before the nvidia drivers are loaded and the sleeping time
before kdm resumes.
** Attachment added: syslog_with_patch
http://launchpadlibrarian.net/51977120/syslog_with_patch
--
[Karmic] X server starts randomly
Addendum to my last comment.
It seems that this problem occurs:
- only at a cold boot.
- never at a warm boot (reboot).
- only with proprietray NVIDIA graphics driver (never with nouveau).
--
boot hangs on splash screen, doesn't switch to KDM
https://bugs.launchpad.net/bugs/538524
You received
This is also not fixed for me. I have the same symptoms as Alvin
described.
I'm using a fresh installed Kubuntu with the latest upgrades. X server
runs with NVIDIA driver.
--
boot hangs on splash screen, doesn't switch to KDM
https://bugs.launchpad.net/bugs/538524
You received this bug
I just installed Lucid Beta2 Server with separated Raid1 for /boot. Grub
has been installed on both hard disks.
While creating the md devices, the newly added superblocks are available
as free raid devices. To avoid faulty configurations please hide them.
--
grub-installer fails to install on a
20 matches
Mail list logo
