[Gambas-user] Gambas 3.4.2 hanging on startup (Ubuntu 12.10 with Cinnamon desktop)

[Bruce]

On Mon, 2013-07-29 at 12:18 +1000, Cam Era wrote:
> Benoît,
> 
> thanks for zeroing in on this issue. I'll check the situation out and
> report back if I can find any generic fix that can help others.
> 
> -- Con
> 
> 
> On Mon, Jul 29, 2013 at 12:15 PM, Benoît Minisini <
> gambas at ...1...> wrote:
> 
> > Le 29/07/2013 03:59, Cam Era a écrit :
> > > On Mon, Jul 29, 2013 at 11:43 AM, Benoît Minisini <
> > > gambas at ...1...> wrote:
> > >
> > >> Le 29/07/2013 03:21, Cam Era a écrit :
> > >>>
> > >>
> > >> You must get Gambas sources, or better compile and install Gambas from
> > >> sources, so that you can have debugging information.
> > >>
> > >> That may be useful to find where it freezes exactly...
> > >>
> > >> Regards,
> > >>
> > >> --
> > >> Benoît Minisini
> > >>
> > >
> > >
> > >
> > > Understood.
> > >
> > > I fetched the most recent Gambas sources, unpacked them, then followed
> > your
> > > instructions. (I didn't recompile from source them, as I have an
> > installed
> > > current version)
> > >
> > > I have the following as a result:
> > >
> > >
> > > Reading symbols from /usr/bin/gbx3...(no debugging symbols found)...done.
> > > (gdb) run
> > > Starting program: /usr/bin/gbx3
> > > [Thread debugging using libthread_db enabled]
> > > Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
> > > [New Thread 0xb14c3b40 (LWP 7734)]
> > > [New Thread 0xb0affb40 (LWP 7735)]
> > > [New Thread 0xb00ffb40 (LWP 7736)]
> > > [New Thread 0xaf46cb40 (LWP 7738)]
> > > [New Thread 0xaeb43b40 (LWP 7739)]
> > > [Thread 0xb00ffb40 (LWP 7736) exited]
> > >
> > > ^C
> > > Program received signal SIGINT, Interrupt.
> > > 0xb7fdd424 in __kernel_vsyscall ()
> > > (gdb) bt
> > > #0 0xb7fdd424 in __kernel_vsyscall ()
> > > #1 0xb7ea7690 in poll () from /lib/i386-linux-gnu/libc.so.6
> > > #2 0xae1104e8 in _httpWait () from /usr/lib/i386-linux-gnu/libcups.so.2
> > > #3 0xae110c8b in httpWait () from /usr/lib/i386-linux-gnu/libcups.so.2
> > > #4 0xae110d83 in httpRead2 () from /usr/lib/i386-linux-gnu/libcups.so.2
> > > #5 0xae111374 in httpFlush () from /usr/lib/i386-linux-gnu/libcups.so.2
> > > #6 0xae12e8ec in cupsDoIORequest () from
> > > /usr/lib/i386-linux-gnu/libcups.so.2
> > > #7 0xae12eaeb in cupsDoRequest () from
> > /usr/lib/i386-linux-gnu/libcups.so.2
> > > #8 0xae13540e in cupsGetDefault2 () from
> > > /usr/lib/i386-linux-gnu/libcups.so.2
> > > #9 0xae10530a in cupsGetDests2 () from
> > /usr/lib/i386-linux-gnu/libcups.so.2
> > > #10 0xae105363 in cupsGetDests () from
> > /usr/lib/i386-linux-gnu/libcups.so.2
> > > #11 0xb6b9d454 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
> > > #12 0xb6aea58e in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
> > > #13 0xb6b01608 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
> > > #14 0xb6b034a1 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
> > > #15 0xb6b0625a in QPrinter::init(QPrinter::PrinterMode) ()
> > > from /usr/lib/i386-linux-gnu/libQtGui.so.4
> > > #16 0xb6b06adb in QPrinter::QPrinter(QPrinter::PrinterMode) ()
> > > from /usr/lib/i386-linux-gnu/libQtGui.so.4
> > > #17 0xb739e7e0 in ?? () from /usr/lib/gambas3/gb.qt4.so
> > > #18 0x08051c69 in ?? ()
> > > #19 0x080522ff in ?? ()
> > > #20 0x080525c9 in ?? ()
> > > #21 0x08052c4c in ?? ()
> > > #22 0x0807c3e5 in ?? ()
> > > #23 0x08050f43 in ?? ()
> > > #24 0x08051585 in ?? ()
> > > #25 0x080526a0 in ?? ()
> > > #26 0x0806c94e in ?? ()
> > > #27 0x08055eb6 in ?? ()
> > > #28 0xb737f936 in ?? () from /usr/lib/gambas3/gb.qt4.so
> > > #29 0x08051c69 in ?? ()
> > > #30 0x0807c63b in ?? ()
> > > #31 0x08050f43 in ?? ()
> > > #32 0x08051585 in ?? ()
> > > #33 0x0804b44c in ?? ()
> > > #34 0xb7de04d3 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
> > > #35 0x0804b5b9 in ?? ()
> > >
> > > -- Con
> >
> > Apparently the Qt library freezes while talking with CUPS.
> >
> > I have a printer on my Ubuntu there, with CUPS installed, and I have no
> > freeze problem, so please check your printer & CUPS configuration.
> >
> > Regards,
> >
> > --
> > Benoît Minisini
> >

This happened to me several months ago. It was caused by a non-existent
network printer.  From memory, cups goes off looking for that printer
forever for some reason or other.

hth
Bruce