Hide Forgot
abrt version: 1.1.18 architecture: i686 Attached file: backtrace, 19653 bytes cmdline: /usr/bin/htsserver /usr/share/httrack/ path /home/don/websites lang 1 component: httrack Attached file: coredump, 10850304 bytes crash_function: __fread_chk executable: /usr/bin/htsserver kernel: 2.6.35.13-92.fc14.i686 package: httrack-3.43.9-2.fc14 rating: 4 reason: Process /usr/bin/htsserver was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1310755051 uid: 500 How to reproduce ----- 1.Tried sevral times to open WebHTTrack Website Copier via Desktop Short Cut. 2.Nothing happened. I clicked on it several times in Different Desktops. 3.Then I opened WebHTTrack Website Copier URL in Web Browser. But got page can't be found error. I then turned off some Firefox addons to see if flash was slowing down Firfox too mcuh. Firefox froze druing Restart. Then I noticed the Bug Report on WebHTTrack Website Copier.
Created attachment 513431 [details] File: backtrace
Package: httrack-3.43.9-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. WebHTTrack crashed when it began to restart my previous Website Download. 2. I get this error every time... Unable to connect. Firefox can't establish a connection to the server at redblackbiostar.localdomain:8081. 3. But, I can get to my Blog directly in Firefox with no problems. I can see that the problem is with accesses permissions. But I can't figure out what is stopping the needed access. Comment ----- I Tried several times to open WebHTTrack Website Copier via Desktop Short Cut. Nothing happened. I clicked on it several times in Different Desktops. Then I opened WebHTTrack Website Copier URL in Web Browser. But got page can't be found error. I then turned off some Firefox ad-dons to see if flash was slowing down Firefox too much. Firefox froze during Restart. Then I noticed the Bug Report on WebHTTrack Website Copier. That was last time. This time, I figured out that WebHTTrack opens up in Firefox just fine if I use the Applications Menu instead of the Desktop Shortcut that I had put on my Desktop. But, WebHTTrack still crashed when it began to restart my previous Website Download. Being Logged in or not, makes no difference with the Error. I added Port 8081 to the allowed Ports in my Firewall. But still get the same error. I changed file Permissions in all sub-folders of the target directory to read and write for all. And added an NFS Share with write permissions. This made no difference. I can see that the problem is with accesses permissions. But I can't figure out what is stopping the needed access. I am running Apache HTTP Server, Jetty Webserver and Servlet Container, sshd, tor, vsftpd, zvbid, smb, nmb, rpcsvcgssd, portreserve, ip6tables, iptables, nfs, nfslock, Port Scan Attack Detector (psad), sandbox, xguest and other apps that want to use pam_namespace require this script be run at boot, on this system. I'm not sure which one might be a problem for WebHTTrack. It worked perfectly when I first installed it. But, I may have changed some of the running services since then.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping