Version: (using KDE KDE 3.1.1) Installed from: Gentoo Packages OS: Linux I have an epson cx3200. I have noticed that when the ink cartridge is empty, kprinter will crash. What happens is that the kprinter dialog shows up for one or two seconds and then crash. Now that I have replaced the ink cartridge it works again. After the two seconds delay, I get the information on my printer. For this printer, kdeprint is able to tell me the ink level. I think it has been crashing since the level has been low. When I use my printer for copying, it would give me a warning. Sorry no backtrace at hand. Next time my ink is empty, I'll do more testing.
Shouldn't it be possible to put back the empty ink cartridge for reproducing the bug and getting the backtrace?
Subject: Re: New: segfault when ink cartridge is empty > I have an epson cx3200. I have noticed that when the ink cartridge is empty, kprinter will crash. What happens is that the kprinter dialog shows up for one or two seconds and then crash. > > Now that I have replaced the ink cartridge it works again. After the two seconds delay, I get the information on my printer. For this printer, kdeprint is able to tell me the ink level. > > I think it has been crashing since the level has been low. When I use my printer for copying, it would give me a warning. Wow, never heard about such a problem. For sure, kdeprint has not a different behavior regarding the printer, according to the ink level. Can you check that it's not related to bug #56263? Michael.
I've thrown the empty cartridge, so it is not possible to use it again. I think I have updated to kde 3.1.1a and changed the cartridge more or less at the same time. So it may indeed be a bug that was fixed by the new KDE version.
Do you still have the problem?
Hard to say. I don't think so but I promise I'll check next time my ink is empty again.
Philippe, was your ink cartridge empty again in the last 19 months?
I was not able to reproduce the bug since then. The simple fact that this bug could occur looks already very strange to me and I am inclined to attribute it to something else. We can close it. I'll open it if it ever reappears. Cristian Tibirna wrote: [bugs.kde.org quoted mail]
As per Philippe's request.
Closing old Resolved status bug.