User forums > Using Code::Blocks

Codeblocks reports: ** (codeblocks:12654): WARNING **: failed request with statu

<< < (3/4) > >>

Bloop:
OK! I reinstalled cups and again I have to wait forever for codeblocks to load. Same behavior as displayed on the screenshot.

So I took a deeper look into cups config files but found nothing. Well since I have no printers I had no need to run the cups daemon.

Now I get the message "failed request with status 1030" instead of "failed request with status 1280". Codeblocks lags a lot, but seams to work.

I am confused!

Bloop:
Oh I'm sorry!

I forgot to say that I started the cups deamon. As a result the failed request changed and codeblocks seemed to work.

thomas:
This lag is probably because Code::Blocks waits for a response from cups. Since fiddling with cups can make it worse or better, that seems proven now.

Rick: Am I right that Code::Blocks
a) probably uses wxPrinter
b) does not do anything with it if nothing is printed?

If that is the case, however, one has to wonder why Bloop is having a problem (started a print job by accident some time earlier?). If, however, Code::Blocks indeed does something with the printing system every time at startup, one should consider moving that.

Bloop: Even if you do not have a printer, why don't you try and run printconf and install a printer on locally connected-->custom device /dev/null? I haven't tried myself, but probably cups will just take /dev/null for valid and will answer "yep, I am ready" right away each time it is asked, so Code::Blocks won't hang or lag any more.

mandrav:

--- Quote ---a) probably uses wxPrinter
b) does not do anything with it if nothing is printed?
--- End quote ---

Yes, it uses wxPrinter.
BUT only when printing, not on startup (except for a static global variable - maybe that's the cause). If there's a bug, it's wxGTK's. No code to access the printer is called until there's a printing request.

With that said, I 've never seen this in Ubuntu whether I configured a printer or not...

thomas:
Hmm, a static global will run the constructor, no idea what goes on in the constructor then. Could we do without the global?


--- Quote from: mandrav on October 27, 2005, 09:18:20 am ---With that said, I 've never seen this in Ubuntu whether I configured a printer or not...
--- End quote ---
Yes, but Bloop reported it actually gets better/worse when playing with cups, that makes printing a likely cause, does it not?

UPDATE:
Downloaded wxGTK and looked. There's not much that happens really:

wxPrinter::wxPrinter(wxPrintDialogData *data)
{
    m_pimpl = wxPrintFactory::GetFactory()->CreatePrinter( data );
}
...
wxPrinterBase* wxGnomePrintFactory::CreatePrinter( wxPrintDialogData *data )
{
    return new wxGnomePrinter( data );
}
...
wxGnomePrinter::wxGnomePrinter( wxPrintDialogData *data ) :
    wxPrinterBase( data )
{
    m_gpc = NULL;
    m_native_preview = false;
}
...
wxPrinterBase::wxPrinterBase(wxPrintDialogData *data)
{
    m_currentPrintout = (wxPrintout *) NULL;
    sm_abortWindow = (wxWindow *) NULL;
    sm_abortIt = false;
    if (data)
        m_printDialogData = (*data);
    sm_lastError = wxPRINTER_NO_ERROR;
}

Navigation

[0] Message Index

[#] Next page

[*] Previous page