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