From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; X11; Linux i686) Opera
Description of problem:
When printing email from a Juno.com webmail account, konqueror will
"hang" indefinitely. Recovery requires killing konqueror.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open a Juno.com email account, of course, and send some email
2. "Sign In" to Juno.com email account using Konqueror.
3. Select "Inbox".
4. Select mail message.
5. Print the email - Select "Location" and "Print".
6. Select a printer and printer setup, etc.
7. Select "Print"
Actual Results: Konqueror "hangs"
Expected Results: printing
Mozilla and Firefox segfault printing Juno.com email. Opera can
print Juno.com email, but with its usual off-center cut-off-lines
This is one of those "Linux is not ready the desktop... for grandma..
. for whatever..." issues.
Hm, i don't have account there. How can i reproduce this problem?
could you please attach the strace log ? thanks
There appears to be a testcase over in bug #148877 ...
Created attachment 111179 [details]
strace log of konqueror printing juno.com email
trace log attached, the start is snipped off. Konqueror printing quickly runs
the load average up over 5 and CPU usage to around 50%.
There is a test file available under "Bugzilla Bug 148877 - segfault printing
Juno.com mail", except that the global-Juno.asc file is NOT required to hang
In the current development version of konqueror this works ok (well, ok -
doesn't hang... the printed output still look silly at best, with the body of
the mail cut off, apparently). It would be nice if you could test with the fc4
version, i don't have that handy right now (i will test it next week if you
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Fedora Core 3 is not maintained anymore.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release please reopen this bug and assign it to the corresponding