First of all, I was unsure whether this should go in General Support or in Installation. The problem is occurring on my first boot of a freshly installed F12 system, but the immediate problem seems to be more concerned with Automatic Bug Reporting Tool and/or Bugzilla plugin.
That more immediate problem is: when I run the tool to report a crash, it complains that the Bugzilla Plugin is not properly configured. So I look at Edit->Plugins->Bugzilla just as it suggests, and I see a bugzilla URL that looks right, and blank Login and Password.
However, since I just did the F12 installation, which presumably is designed for any user, not a developer or member of the F12 project, there is no reason to assume that I even HAVE a login. So this is the first question: what Login and Password are they expecting here? Is there a special Login for the ABRT?
Has anyone noticed ABRT not being able to connect to Bugzilla or the remote Core Dump analysis server? Since my upgrade during the beta phase of F15 I have been unable to file bug reports from ABRT's traces, nor has it offered me the option to file bugs to bugzilla. What it does, however, is offer me to analyse the Core Dump and backtrace of the crash using either the remote server or locally with GDB. Needless to say I'm clueless in GDB, and it requires a LOT of debug symbols found in the corresponding debug packages. But trying to use the remote analysis server always results in a message of the server being busy and to try again later. IIRC the last time I was able to file a bug through ABRT was in 13, has anyone been able to do so in 15?
when ever i try to install updates i get shown an error & the updates stop the error i get says "librpmio.so.0 is needed by package abrt-1.0.3-1.fc12.i686 (updates) librpm.so.0 is needed by package abrt-1.0.3-1.fc12.i686 (updates)"
So last night suddenly my computer started running really slow. Like it would take a couple of minutes for a window to open. I tried to start System Monitor to see what was going on, but couldn't get it to launch. At first I thought something had grabbed the CPU, but eventually I discovered that something was writing a massive amount to the hard disk. The intensive disk activity continued for about 20 minutes as I watched nervously. Just as the disk activity suddenly stopped ABRT popped up a message that disappeared to fast to read fully, but it said something about a file that was too large.
This morning I discovered that about 9 GB of my hard disk had been used up. Using "find -size +1G" I found an 8.6 GB file in /var/spool/abrt /ccpp-1291706342-2244/ called "coredump."I don't know what a coredump is or how to look inside the file to see what might have caused its creation. But I do know that ABRT has not said a word about the incident.
Whenever I log into Fedora, an icon (a triangle with an exclamation mark) pops up in the main panel . When I move the mouse over it, the following is displayed. ABRT service not running. I restarted the service from the service configuration window but there was no difference. How do I configure it to run alway
I can't find how to clear ABRT cache (other than to forcibly 'rm -rf /var/cache/abrt/'). How does one clear out the pile (which has grown to 1.2 GB here)?
I have fedora 12 32 bits installed on a Macbook pro (intel core duo) I did "yum update" this morning, I have restarted the system and got the following message:Starting abrt daemon: abrtd: Failed to start: got sig 2 FAILEDI have browsed in the web but I cannot find useful information. Then I typed:$rpm -qa | grep abrt
Every time I login I get the abrt flashing light at the top of the screen, but nothing comes up. When I try to run it manually from Applications->System Tools->Automatic Bug Reporting Tool I get a popup with:
Quote:
Error while loading the dumplist. org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)Is anybody else seeing this? If so, any idea as to what's going on? How to fix it?
I could just dump abrt since it's hardly a necessity, but I'm inclined not to as I think it's a good idea which could potentially be of great benefit to us all.
Since upgrading last week we keep getting a red icon warning msg for the ABRT system - it's not really something we want to have activated - is there any way to turn it off ?
I had a major foul-up a couple of days ago, and I now have thousands of bug reports in the abrt applet. I'm trying to delete them individually, but it's taking forever. Is there a way to mass delete these reports to clean things up? I looked at abrt-cli and it has a --delete command, but only does them one at a time, too.
Question about the bug reporting system that I think is called ABRT Struggling with F15 and want to file a bug report, but the backtrace thingy says I should remove sensitive data first. Obviously a good idea, but the report is full of what to a non-programmer looks like gibberish - things like what I guess are hexadecimal numbers or memory addresses, none of which I understand. Can any of that incomprehensible stuff contain sensitive data, like encryption keys or anything someone would need to crack a machine? If I remove all of that then the bug report will be pretty sparse.
(Same question applies to SMOLT - machine profie report - as well) Or is "sensitive" just about the human readable data in the reports?
When I installed F11 I chose to install Bugzilla with it. It is installed and working great, but It is not the newest version, and apparently the repositories I have installed do not have the newest version. Anyone know what repository I could get this from, if its possible?
I have recently upgraded from FC12 to FC13, and last week I updated all packages using YUM. The system is running as a VM inside CentOS 5.5 using KVM. SELinux is enforcing, using the targeted policy. Bugzilla is version 3.6.1 and was NOT installed using RPM or YUM.
Bugzilla was working OK on this machine until SELinux was upgraded last week from 3.7.19-28 to 3.7.19-33, and is still broken after testing 3.7.19-37 from the testing repo. With SELinux in enforcing mode, apache returns error 500 when I browse to the main bugzilla page. The apache error log shows this:-
Code: [Mon Jul 19 13:15:08 2010] [error] [client 192.168.40.1] (13)Permission denied: exec of '/var/www/html/bugzilla/index.cgi' failed Nothing, and I mean absolutely nothing, is recorded in /var/log/audit/audit.log, /var/log/messages or /var/log/secure.
I installed Fedora 12 onto my PC today and I've tried installing a set of updates and get the following
A package could not be found that allows the action to complete.
librpmio.so.0 is needed by package abrt-1.0.8-2.fc12.i686 librpm.so.0 is needed by package abrt-1.0.8-2.fc12.i686 : librpmio.so.0 is needed by package abrt-1.0.8-2.fc12.i686 librpm.so.0 is needed by package abrt-1.0.8-2.fc12.i686
E: Error occured while processing abrt (CollectFileProvides) E: Problem with MergeFileProvides /var/lib/apt/lists/download.fedoraproject.org_pub_fedora_linux_update s_12_x86%5f64_repodata_repomd.xml E: The package lists or status file could not be parsed or opened.
frequently getting a red symbol on my taskbar with the message "crash detected in abrt-gui ...".What program is producing this? There is no indication of what action I'm supposed to take, so the message is not useful. It also seems to violate a basic principle that any program producing an error message should announce its own name.
installing Bugzilla on CentOS 5.5 step by step? I want to learn how to install on my own pc, cause I will have to install it later on this semester for my professor.
I Installed Bugzilla 3.2 on Centos 5.3.I have other window 2003 server (Domain Controller).But it is Windows Small Business Server 2003.i have many OU on that.I want to integrate Bugzilla 3.2 with LDAP.
I installed Bugzilla on a Fedora 11 system and got it running. In the Admin options I set it to redirect all hits to SSL port 443.
This was a mistake.
After I saved that setting, every single request on all browsers seem to loop infinitely and the browser stops it - but I can't access any of the pages.
Does anybody know where that setting is set? Is it configured in Apache for that VHost? All I've found on the subject is changing the setting in Admin Options.
I loaded CentOS 5.5, Apache and Bugzilla with all the trimmings. My checksetup.pl finishes with no errors. I think the issue is on the Apache side of the equation. I can surf to localhost/test/index.html but cannot surf to localhost/bugzilla/index.html. I have commented out my <Directory> calls for /var/www/html/bugzilla. Restarted everything, cleared browser cash, validated that the test directory, bugzilla directory and both index.html files have the same settings. I can file:// to both index.html files but can't http:// to the bugzilla version. I get a 403 error. What can cause Apache to ignore a directory in this case?
