[Bug 1862926] Re: Request for update: SANE 1.0.29
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862926 Title: Request for update: SANE 1.0.29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
@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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512027] Re: open of device pixma:MX7600_... failed: invalid argument
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 argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1512027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1080787] Re: hp scanner 5300c does no longer work after upgrading to quantal
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. https://bugs.launchpad.net/bugs/1080787 Title: hp scanner 5300c does no longer work after upgrading to quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1080787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096612] Re: canon pixma MP970 TPU scanning stopped working
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 stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1096612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601652] Re: Cannon CanoScan 9000F not supported in Ubuntu xsane
>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 To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/601652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601652] Re: Cannon CanoScan 9000F not supported in Ubuntu xsane
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. https://bugs.launchpad.net/bugs/601652 Title: Cannon CanoScan 9000F not supported in Ubuntu xsane To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/601652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601652] Re: Cannon CanoScan 9000F not supported in Ubuntu xsane
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 version next week. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/601652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601652] Re: Cannon CanoScan 9000F not supported in Ubuntu xsane
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 2>pixma.log'. (3) try a scan: 'export SANE_DEBUG_PIXMA=4' and 'scanimage 2>scan.log >scan.pnm' Please provide the logfiles here or in the Sane-devel mailing list: sane-de...@lists.alioth.debian.org. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/601652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601652] Re: 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, which comes with the source files. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/601652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096612] Re: canon pixma MP970 TPU scanning stopped working
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096612 Title: canon pixma MP970 TPU scanning stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1096612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459639] Re: X server starts randomly in failsafe when starting from cold boot
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 be replaced by other graphic drivers later on. In kdm.conf the watched event "graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1" isn't secure if a 2nd graphics driver is used. To fix this, a new event should be emitted from all graphics drivers or from upstart or from udev or ... as start condition for kdm.conf. And upstart must know if there is any other graphics installed beside vga16 (ok, typically on every home and business pc, but what's about small systems and servers). -- X server starts randomly in failsafe when starting from cold boot https://bugs.launchpad.net/bugs/459639 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585930] Re: kdm starts before nvidia driver is fully loaded
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 graphics device doesn't work if nvidia kernel driver isn't loaded or is still loading. This problem does not only affect nvidia kernel drivers. I think this is an essential problem of startup. -- kdm starts before nvidia driver is fully loaded https://bugs.launchpad.net/bugs/585930 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 578732] Re: boot hangs on splash screen, does not show kdm
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 https://bugs.launchpad.net/bugs/578732 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 459639] Re: [Karmic] X server starts randomly in failsafe when starting from cold boot
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 in failsafe when starting from cold boot https://bugs.launchpad.net/bugs/459639 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459639] Re: [Karmic] X server starts randomly in failsafe when starting from cold boot
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 respawn kdm, so I can cancel the message boxes if any error occurs and kdm will start up later. This is only a workaround! Does anybody has an idea how to recognise a ready loaded graphics driver from the kernel? Looking for /dev/fb0 is not safe for every hardware configuration. A solution should work with any free and proprietary graphics driver. ** Patch added: "kdm.patch" http://launchpadlibrarian.net/51976665/kdm.patch -- [Karmic] X server starts randomly in failsafe when starting from cold boot https://bugs.launchpad.net/bugs/459639 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459639] Re: [Karmic] X server starts randomly in failsafe when starting from cold boot
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 -- [Karmic] X server starts randomly in failsafe when starting from cold boot https://bugs.launchpad.net/bugs/459639 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538524] Re: boot hangs on splash screen, doesn't switch to KDM
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538524] Re: boot hangs on splash screen, doesn't switch to KDM
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527401] Re: grub-installer fails to install on a raid1 array
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 raid1 array https://bugs.launchpad.net/bugs/527401 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
