Good Morning Guys
I did as I was told and made CodeBlocks think I have a printer on /dev/null. Now it loads without problems with or without running the cups deamon.
But I still get this strange warning in Console:
** (codeblocks:18317): WARNING **: failed request with status 1030
** (codeblocks:18317): WARNING **: failed request with status 1030
** (codeblocks:18319): WARNING **: failed request with status 1030
** (codeblocks:18319): WARNING **: failed request with status 1030
** (codeblocks:18320): WARNING **: failed request with status 1030
** (codeblocks:18320): WARNING **: failed request with status 1030
I stumbled over the cups access_log. A shame I didn't thought of this yesterday.
localhost - - [26/Oct/2005:23:29:12 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:12 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:17 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:17 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:22 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:22 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:27 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:27 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:32 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:32 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:37 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:37 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:42 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:42 +0000] "POST / HTTP/1.1" 200 72
localhost - - [26/Oct/2005:23:29:47 +0000] "POST / HTTP/1.1" 200 72
The intervals match! CodeBlocks is definetly trying to access a printer.
Thomas: You told CodeBlocks is uising wxPrinter from the wxGTK package. I will try to swapto a newer or older version and report my progress.
Yes, but Bloop reported it actually gets better/worse when playing with cups, that makes printing a likely cause, does it not?
Sure, I 'm not questioning Bloop's findings...
I just said it's strange I haven't seen/heard it before. I think cups is widely used...
Downloaded wxGTK and looked. There's not much that happens really:
Well, when I said global, I didn't mean a wxPrinter. That would be silly. Here's what's global (in sdk/printing_types.cpp):
wxPrintData* g_printData = 0;
wxPageSetupData* g_pageSetupData = 0;
But the root of the problem probably lies in the same file, specifically in InitPrinting() where the above vars are initialised. This is called on program startup. We could always postpone initialization for later, e.g. when a printing request arrives. That should solve it, would it not?