Hi Sebastian, I ran gedit and printed from there. The print dialog hung as expected and thus, I have attached two backtraces:
1) Before gedit received SIGPIPE 2) After gedit received SIGPIPE The reason for two backtraces is that there is a significant time lag between (1) and (2). Meanwhile, there is no external indication (in the GUI that is) of the SIGPIPE signal being received by gedit. The attached screeenshot shows what gedit looked like during the entire time --- before *and* after receiving SIGPIPE. Thanks, Akshay http://web.cecs.pdx.edu/~akshay/ On Wed, Jun 3, 2009 at 12:13 PM, Sebastien Bacher <seb...@ubuntu.com> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please try to obtain a backtrace following the > instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload > the backtrace (as an attachment) to the bug report. This will greatly > help us in tracking down your problem. > > ** Changed in: gtk+2.0 (Ubuntu) > Importance: Undecided => Low > > ** Changed in: gtk+2.0 (Ubuntu) > Status: New => Incomplete > > ** Changed in: gtk+2.0 (Ubuntu) > Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs) > > -- > Jaunty: Printing dialog hangs when printer is not available > https://bugs.launchpad.net/bugs/382533 > You received this bug notification because you are a direct subscriber > of the bug. > ** Attachment added: "gdb-gedit-after-SIGPIPE.txt" http://launchpadlibrarian.net/27469000/gdb-gedit-after-SIGPIPE.txt ** Attachment added: "gdb-gedit-before-SIGPIPE.txt" http://launchpadlibrarian.net/27469001/gdb-gedit-before-SIGPIPE.txt ** Attachment added: "gedit-hung.png" http://launchpadlibrarian.net/27469002/gedit-hung.png -- Jaunty: Printing dialog hangs when printer is not available https://bugs.launchpad.net/bugs/382533 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
