On 2020-02-15, Mick wrote: > On Saturday, 15 February 2020 04:54:21 GMT Dale wrote: >> Howdy, >> >> I first discovered this with Seamonkey. I then tested this with Firefox >> and got the same results. When I go to File and select Print, the print >> dialog window pops up for just a second and then the web browser >> crashes. Both seem to use the same print software. I tried a different >> version of Seamonkey but it does the same. I also tested a fresh >> profile of Seamonkey as well, Firefox also. I don't print from Firefox >> much. Also, if I select Print Preview from the menu, it opens normally >> but as soon as I click print, crash. >> >> I then tried a newer unstable version of cups just in case it would >> help. After that, I opened Kwrite and tried to print. Its print dialog >> opened and waited for me to hit print. LOo did the same. However, both >> of those use a different software or at least they look very different >> to print with. >> >> Usually going back a version or up a version fixes things like this. >> Given that this didn't work in this case, I'm not sure where to go. Two >> versions of Seamonkey and Firefox both crash. A newer version of cups >> and it still crashes. I did a search on BGO and didn't find anything >> except for a fixed version of Chrome which I don't have on here. I >> suspect it uses different software to print anyway. So no help there. >> Forums had a thread that was from 2010. It mentioned a USE flag which >> cups doesn't even have anymore. No solution on the forums. >> >> One other thing that may or may not be related. I did a emerge -e world >> a week or so ago. Before that, I could print fine. The reason I did >> that was because I switched to a new gcc and I just wanted to be sure >> everything was stable. I went from gcc-8 to gcc-9. It may not have >> been needed but it was cold here and I didn't mind the extra heat. >> Plus, it sometimes fixes other quirks I may not even see. Here is the >> info for Seamonkey, Firefox and cups. [...] >> >> I'm not sure if the printing is done within Seamonkey itself or if >> Seamonkey and Firefox use some common external print software. I'd >> think the later since both behave the same way. I'm just not sure. >> >> Any ideas or thoughts??
Try getting a backtrace with gdb, and build involved packages with debug symbols as needed to get a more detailed backtrace. With the backtrace, you will at least have an idea of where it is crashing. If you need documentation on this, the following page is probably a good place to start: https://wiki.gentoo.org/wiki/Debugging_with_GDB -- Nuno Silva
