Comment 4 for bug 1814513

Hi,
Today i test it again. But same issue.

1.What is the kernel version of the host machine where you are running
Cubic?
Ans-- 4.15.0-29-generic

2.What is the kernel version inside the chroot environment in Cubic?
Ans-- 4.15.0-29-generic

3.What is the kernel version on the system where you installed the
Ans-- 4.15.0-29-generic

4.What is the kernel version on the other system where your printer is
working fine?
 Ans-- 4.15.0-43-generic

On Wed, Feb 6, 2019, 06:40 Cubic PPA <<email address hidden> wrote:

> Dibyendu,
>
>
> I had asked four questions, but you gave only one answer, so I'm ot sure
> which question you were answering?
>
> Anyway...
>
> Kernel Modules
> --------------
>
> When you run a chroot (as in Cubic) the kernel used by the chroot is the
> same kernel as on your host machine.
>
> When you install drivers/kernel modules, they are installed for the
> currently running kernel (in /lib/modules).
>
> Even if you update your kernel using dist update, the currently running
> kernel will not change in the chroot environment. Therefore, any drivers
> you install will still install only for the currently running kernel,
> not the newly updated kernel. (Take a look at /lib/modules).
>
> Eventually, when you install your customized OS onto a computer, it will
> use the ~new~ kernel (installed using dist update), but any drivers you
> had installed may not be available in that kernel (in /lib/modules).
>
> CUPS
> ----
>
> Cups is usually installed under /usr/share/cups.
> There are also drivers under /usr/lib/cups.
>
> Make sure you have the driver for your printer included on the
> customized version of Ubuntu. Compare the contents of /usr/lib/cups of
> your customized system with the contents of /usr/lib/cups on your system
> where your printer works. You may need to compare file contents as well.
> (I don't know where -or- how the drivers for various printers are
> listed). However you should look for differences between the directory
> that works, and the directory that doesn't work. The driver for your
> printer may have been accidentally or intentionally excluded from the
> package in the repositories, so you might have to file a bug with cups
> or your printer vendor, if they produce a cups file for their product.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1814513
>
> Title:
> Canon Documents printer Not working
>
> Status in Cubic:
> New
>
> Bug description:
> Today create a customized Ubuntu 16.04LTS using cubic. I already add
> Canon and Kyocera printer driver on it. Then install it on a system. Try to
> take printout from Kyocera printer, its working fine. But Canon printer not
> working, only give a single beep code. Then reinstall canon printer driver
> on the system but Canon printer not working. Try it on another system, same
> issue. Model number- Canon ImageRunner 1435iF. & Canon IR2520.
> Note: same driver working on other Ubuntu system (not customized OS).
>
> cups error Log---
>
> E [04/Feb/2019:17:19:25 +0530] [cups-deviced] PID 6014
> (gutenprint52+usb) stopped with status 1!
> E [04/Feb/2019:17:19:33 +0530] [cups-driverd] Skipping
> \"/usr/share/ppd/kyocera\": loop detected!
> W [04/Feb/2019:17:19:37 +0530] CreateProfile failed:
> org.freedesktop.ColorManager.AlreadyExists:profile id
> \'Canon-iR1435-Gray..\' already exists
> E [04/Feb/2019:17:19:39 +0530] [Job 33] Unable to add document to print
> job.
> E [04/Feb/2019:17:19:39 +0530] [Job 33] Unable to retry job using a
> supported raster format.
> E [04/Feb/2019:17:19:39 +0530] [Job 33] Unable to convert file 0 to
> printable format.
> E [04/Feb/2019:17:19:39 +0530] [Job 33] Aborting job because it cannot
> be printed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cubic/+bug/1814513/+subscriptions
>