Giter Site home page Giter Site logo

abrt / abrt Goto Github PK

View Code? Open in Web Editor NEW
230.0 230.0 77.0 30.11 MB

Automatic bug detection and reporting tool

License: GNU General Public License v2.0

Emacs Lisp 0.02% Augeas 0.26% Shell 27.69% Makefile 2.65% C 47.81% Python 20.47% M4 0.98% Logos 0.12%

abrt's Introduction

Translation status Build status Coverity Scan build status

ABRT

A set of tools to help users detect and report application crashes.

About

Its main purpose is to ease the process of reporting an issue and finding a solution.

The solution in this context might be a bugzilla ticket, knowledge base article or a suggestion to update a package to a version containing a fix.

This repository is one among a suite of related projects. The following diagram summarizes the dependencies between the individual packages comprising the ABRT suite.

flowchart BT
    abrt-java-connector --> abrt
    abrt-java-connector -. build .-> satyr
    abrt:::focus --> libreport & satyr
    abrt-java-connector --> libreport
    gnome-abrt --> abrt & libreport
    reportd --> libreport
    libreport --> satyr
    retrace-server[Retrace Server] -. "optional, for<br>packages only" .-> faf
    faf["ABRT Analytics (FAF)"] --> satyr

click abrt "https://github.com/abrt/abrt" "abrt GitHub repository" _blank
click abrt-java-connector "https://github.com/abrt/abrt-java-connector" "abrt-java-connector GitHub repository" _blank
click faf "https://github.com/abrt/faf" "ABRT Analytics GitHub repository" _blank
click gnome-abrt "https://github.com/abrt/gnome-abrt" "gnome-abrt GitHub repository" _blank
click libreport "https://github.com/abrt/libreport" "libreport GitHub repository" _blank
click reportd "https://github.com/abrt/reportd" "reportd GitHub repository" _blank
click satyr "https://github.com/abrt/satyr" "satyr GitHub repository" _blank
click retrace-server "https://github.com/abrt/retrace-server" "Retrace Server GitHub repository" _blank

classDef focus stroke-width: 4

Documentation

Every ABRT program and configuration file has a man page describing it. It is also possible to read the ABRT documentation online. For contributors and developers, there are also wiki pages describing some topics to deeper technical details.

Development

Running

ABRT consist of several services and many small utilities. While The utilities can be successfully run from the source directories after build, the services often uses the utilities to do actions and expect the utilities installed in the system directories. Hence to run the services, it is recommended to install ABRT first and run them as system services. The instructions how to build and install ABRT can be found in INSTALL.md

Technologies

abrt's People

Contributors

credmon avatar dvlasenk avatar ernestask avatar fabaff avatar hadess avatar jcpunk avatar jfilak avatar juliusmilan avatar kdudka avatar logan5 avatar marusak avatar mgrabovsky avatar michalfabik avatar mkutlak avatar mlichvar avatar mmilata avatar mostafadaneshvar avatar mozeq avatar msrb avatar mtoman avatar mzidek-gh avatar pkubatrh avatar rbuj avatar scop avatar sorki avatar vpodzime avatar wlindauer avatar xsuchy avatar yurchor avatar zoltanh721 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

abrt's Issues

apps run under root is not reported

Opened '20090226T16:06:20' by psklenar as https://fedorahosted.org/abrt/ticket/25

  1. [nonroot]# gparted , it ask for root passwd
  2. it starts under root
  3. [root]# kill it with SIGSEGV under root
  4. [nonroot session]# Very nice graphic exclamation point starts blinking
  5. [nonroot]# click on that "!"
  6. [nonroot] there is no report in graphic tool :( :(

F10,crash-catcher-0.0.1-6.fc10.i386

Revelation (Python app) not caught

Opened '20090226T19:09:24' by adamwill as https://fedorahosted.org/abrt/ticket/34

Crashes in Revelation (password management app) don't seem to be caught. Note that it's a python app so it's running via python (shows up as 'python /usr/bin/revelation' in a ps aux).

revelation-0.4.11-7.x86_64
python-2.6-4.fc11.x86_64

testing with current Rawhide and c-c installed as per Test Day instructions. Crashes in other apps are caught.

Do not show icon when the GUI is running

Opened '20090311T16:56:08' by mnowak as https://fedorahosted.org/abrt/ticket/43

When e.g. the GUI is running and some other app crashed, the icon will pop up, which allows you to open another GUI, which is bad, but also asks you whether you wanna refresh the list in current window.

Proposal:

  • no unhide of icon
  • no dialog
  • refresh the list but keep the cursor position in the list
  • display the new item in bold text

The deadlock occours while attempting to create the lock

Opened '20090226T11:58:55' by koca as https://fedorahosted.org/abrt/ticket/4

Hi,[[BR]]

when I SIGSEGV a vim application nothing happened. I have cc-applet running as well as the daemon. It looks like the daemon is waiting for the lock. [[BR]]
.....[[BR]]
CDebugDump::Lock(): waiting...[[BR]]
CDebugDump::Lock(): waiting...[[BR]]
CDebugDump::Lock(): waiting...[[BR]]
CDebugDump::Lock(): waiting...[[BR]]
CDebugDump::Lock(): waiting...[[BR]]
....[[BR]]
[[BR]]
[[BR]]
Additional info:[[BR]]
$ cc-gui [[BR]]
/usr/share/crash-catcher/CCMainWindow.py:30: GtkWarning: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead
self.wTree = gtk.glade.XML(self.gladefile)
loading DumpList[[BR]]
ERROR:dbus.proxies:Introspect error on :1.53:/com/redhat/crash_catcher: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Generating of first report never ends

Opened '20090305T14:24:17' by mnowak as https://fedorahosted.org/abrt/ticket/38

abrt-0.0.1-13.fc11.x86_64

  • crash app (htop in my case)
  • open the viewer
  • click "Save" (shouldn't it be "Generate"?)

From terminal:

Creating report
CDebugDump::Lock(): waiting...done.
CDebugDump::Lock(): waiting...done.
Loaded plugins: dellsysidplugin2, refresh-packagekit
Excluding Packages in global exclude list
Finished
enabling rawhide-debuginfo
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished
enabling rpmfusion-free-rawhide-debuginfo
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished
enabling rpmfusion-nonfree-rawhide-debuginfo
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished
There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them.
--> Running transaction check
---> Package glibc-debuginfo.x86_64 0:2.9.90-8.1 set to be updated
---> Package htop-debuginfo.x86_64 0:0.8.1-4.fc11 set to be updated
---> Package ncurses-debuginfo.x86_64 0:5.7-2.20090207.fc11 set to be updated
--> Finished Dependency Resolution

Package Arch Version Repository Size

Installing:
htop-debuginfo x86_64 0.8.1-4.fc11 rawhide-debuginfo 185 k
Updating:
glibc-debuginfo x86_64 2.9.90-8.1 rawhide-debuginfo 22 M
ncurses-debuginfo x86_64 5.7-2.20090207.fc11 rawhide-debuginfo 1.2 M

Transaction Summary

Install 1 Package(s)
Update 2 Package(s)
Remove 0 Package(s)

Total download size: 23 M

Downloading Packages:

Total 1.0 MB/s | 23 MB 00:22
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : ncurses-debuginfo 1/5
Installing : htop-debuginfo 2/5
Updating : glibc-debuginfo 3/5
Cleanup : ncurses-debuginfo 4/5
Cleanup : glibc-debuginfo 5/5

Installed:
htop-debuginfo.x86_64 0:0.8.1-4.fc11

Updated:
glibc-debuginfo.x86_64 0:2.9.90-8.1
ncurses-debuginfo.x86_64 0:5.7-2.20090207.fc11

CDebugDump::Lock(): waiting...done.
warning: Can't read pathname for load map: Input/output error.
Quitting: You can't do that without a process to debug.
CDebugDump::Lock(): waiting...done.
CDebugDump::Lock(): waiting...done.

The progress bar is still moving left-right'n'back, never ends.

  • closed the small window
  • "Save" on the same report
  • Now I got the report.

Gedit crash - warning about missing debuginfo with debuginfo installed

Opened '20090226T17:35:41' by hondra as https://fedorahosted.org/abrt/ticket/31

Reproducer:
{{{
service crash-catcher start
cc-applet &
yum install gedit
debuginfo-install gedit
gedit &
kill -SIGSEGV $(pidof gedit)

now click crash handler icon -> select gedit -> click forward:
"Unable to get report! Debuginfo missing?"

gedit-2.25.7-1.fc11.i586
gedit-debuginfo-2.25.7-1.fc11.i586
crash-catcher-0.0.1-7.fc11.i586

}}}
Reproducible: always

crash-catcher should create dir /var/cache/crash-catcher when is not present

Opened '20090226T12:36:02' by mnowak as https://fedorahosted.org/abrt/ticket/7

Install c-c

dhcp-lab-124 Download # /etc/init.d/crash-catcher restart
Stopping crash-catcher daemon: [FAILED]
Starting crash-catcher daemon: Plugin SQLite3 (0.0.1) succesfully loaded.
Plugin Logger (0.0.1) succesfully loaded.
Plugin Mailx (0.0.1) succesfully loaded.
Plugin CCpp (0.0.1) succesfully loaded.
Registred plugin CCpp(Language)
Registred plugin Mailx(Reporter)
Registred plugin SQLite3(Database)
[ OK ]
--------> OK

dhcp-lab-124 Download # rm -rf /var/cache/crash-catcher/

dhcp-lab-124 Download # /etc/init.d/crash-catcher restart
Stopping crash-catcher daemon: Got SIGINT/SIGTERM, cleaning up..
UnRegistred plugin CCpp(Language)
Plugin CCpp sucessfully unloaded.
Plugin Logger sucessfully unloaded.
UnRegistred plugin Mailx(Reporter)
Plugin Mailx sucessfully unloaded.
UnRegistred plugin SQLite3(Database)
Plugin SQLite3 sucessfully unloaded.
[ OK ]
Starting crash-catcher daemon: Plugin SQLite3 (0.0.1) succesfully loaded.
Plugin Logger (0.0.1) succesfully loaded.
Plugin Mailx (0.0.1) succesfully loaded.
Plugin CCpp (0.0.1) succesfully loaded.
Registred plugin CCpp(Language)
Registred plugin Mailx(Reporter)
Registred plugin SQLite3(Database)
Cannot create daemon: Add watch failed:/var/cache/crash-catcher
[ OK ]
`----------------------------------------------------------^^^^^^^^ ???

  1. c-c not running

dhcp-lab-124 Download # ps axu | grep crash
root 3805 0.0 0.0 87748 784 pts/1 S+ 13:33 0:00 grep --color=auto crash

--------> FAIL

  • create /var/cache/crash-catcher via c-c and
  • fail the init script when the service is not running at all

cc-applet not started

Opened '20090226T16:25:41' by jscotka as https://fedorahosted.org/abrt/ticket/26

everythung seems to be ok, but when I started cc-applet, nothing appears. I errase all cache of catchcatcher, and restart deamon, and stil same problem. in teminal hwhere I restart ccatcher shows, when I kill application ( xterm, xclock - both same problem):
{{{
CDebugDump::Lock(): waiting...
CDebugDump::Lock(): waiting...
CDebugDump::Lock(): waiting...
CDebugDump::Lock(): waiting...
CDebugDump::Lock(): waiting...
CDebugDump::Lock(): waiting...
CDebugDump::Lock(): waiting...
CDebugDump::Lock(): waiting...
...
}}}

  • Distro: F11 - Rawhide

  • HW - runned on virtualized HW (basic machine is Lenovo T61 X86_64 dualcore 2Gb ram) qemu-kvm - full virtualized, as virt machine.
    so HW are 2 virt procs x86-64, 512Mb of RAM,

  • Disc connected via virtio device /dev/vda

  • Bridged etherned.

  • uname -a

    {{{
    Linux dhcp-lab-194.englab.brq.redhat.com 2.6.29-0.148.rc6.fc11.x86_64 #1 SMP Tue Feb 24 10:36:50 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
    }}}

  • all packages updated

    and files of xclock crashed output
    {{{

    for foo in /tmp/cc/ccpp-1235660642-4943/*; do echo ==foo; cat $foo;echo; done

=== /tmp/cc/ccpp-1235660642-4943/architecture
x86_64
=== /tmp/cc/ccpp-1235660642-4943/cmdline
xclock
=== /tmp/cc/ccpp-1235660642-4943/executable
/usr/bin/xclock
=== /tmp/cc/ccpp-1235660642-4943/kernel
2.6.29-0.148.rc6.fc11.x86_64
=== /tmp/cc/ccpp-1235660642-4943/language
CCpp
=== /tmp/cc/ccpp-1235660642-4943/release
Fedora release 10.91 (Rawhide)

=== /tmp/cc/ccpp-1235660642-4943/time
1235660642
=== /tmp/cc/ccpp-1235660642-4943/uid
500

}}}

Autorefresh the list of crash reports

Opened '20090305T14:06:58' by mnowak as https://fedorahosted.org/abrt/ticket/36

  • have open the abrt-gui
  • crash next app
  • window with msg "Another crash detected, do you want to refresh the data?" pops up

Don't ask just refresh the list but stay on the selected item/report.

Good idea also might be to have the unread reports in bold and read in normal font and thus indicate the state of reports.

Description frame is always blank

Opened '20090305T15:01:49' by mnowak as https://fedorahosted.org/abrt/ticket/40

Frame "Description" is always blank on Rawhide.

  • Load the GUI after crash - frame not populated

D-BUS messages stack:

{{{
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=48 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
string ":1.89"
string ":1.89"
string ""
signal sender=:1.62 -> dest=(null destination) serial=55 path=/com/redhat/abrt; interface=com.redhat.abrt; member=Crash
string "procps-3.2.7-27.fc11"
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=49 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
string ":1.90"
string ""
string ":1.90"
}}}

  • Click on item - nothing (I'd expect the info there)

CCReporterDialog.py crash when comment field is clicked

Opened '20090401T13:10:34' by azelinka as https://fedorahosted.org/abrt/ticket/51

/usr/share/abrt/CCReporterDialog.py:95: GtkWarning: gtk_text_buffer_get_insert: assertion GTK_IS_TEXT_BUFFER (buffer)' failed result = self.window.run() /usr/share/abrt/CCReporterDialog.py:95: GtkWarning: gtk_text_buffer_get_iter_at_mark: assertionGTK_IS_TEXT_MARK (mark)' failed
result = self.window.run()
Segmentation fault (core dumped)

abrt-0.0.2-1.fc11.x86_64

"Do you want to file a report?" window is bad UI

Opened '20090226T18:18:27' by adamwill as https://fedorahosted.org/abrt/ticket/33

I don't think the UI design for handling a crash is very good. The user sees a flashing icon, and clicks, and sees a window which just asks:

"Do you want to file a report now?"

No context. The user thinks - file a report? About what? What is this window? Why is it here? What should I do?

I'm not sure the window is serving any useful purpose at all. If it is, it should be much more explicit about what it is and what exactly it's asking.

crash-catcher-5 dead but subsys locked

Opened '20090226T13:20:13' by psklenar as https://fedorahosted.org/abrt/ticket/15

[nonroot]# xclock
[nonroot]# kill -SIGSEGV <pid_xclock>

[root@localhost ~]# /etc/init.d/crash-catcher status
crash-catcher dead but subsys locked

console msg:

CDebugDump::Lock(): waiting...

many times

Freeing locks for locker 0x9: 2670/3087431456
Freeing locks for locker 0xa: 2670/3087431456
Freeing locks for locker 0xb: 2670/3087431456

rpm -q crash-catcher

Freeing locks for locker 0xf: 4705/3086870304
Freeing locks for locker 0x10: 4705/3086870304
Freeing locks for locker 0x11: 4705/3086870304
crash-catcher-0.0.1-5.fc10.i386
realease: F10

SQLite3::Create(): Could not create database.unable to open database file

Opened '20090226T12:52:41' by mnowak as https://fedorahosted.org/abrt/ticket/12

Blank c-c installation

dhcp-lab-124 Download # file /var/cache/crash-catcher/
/var/cache/crash-catcher/: directory

dhcp-lab-124 Download # ll /var/cache/crash-catcher/
total 0

start service
---> OK

cc-applet

dhcp-lab-124 Download # strace -p $(pgrep crash-catcher )
Process 4049 attached - interrupt to quit
restart_syscall(<... resuming interrupted call ...>

newman@dhcp-lab-124 ~ $ sleep 30&
[5] 4054
newman@dhcp-lab-124 ~ $ kill -SIGSEGV $!
newman@dhcp-lab-124 ~ $
[5]+ Segmentation fault (core dumped) sleep 30

[...]
rt_sigaction(SIGHUP, {SIG_DFL, [], SA_RESTORER, 0x3c69e33340}, NULL, 8) = 0
rt_sigaction(SIGINT, {0x40d0c0, [INT], SA_RESTORER|SA_RESTART, 0x3c69e33340}, NULL, 8) = 0
rt_sigaction(SIGTERM, {0x40d0c0, [TERM], SA_RESTORER|SA_RESTART, 0x3c69e33340}, NULL, 8) = 0
rt_sigaction(SIGQUIT, {SIG_DFL, [], SA_RESTORER, 0x3c69e33340}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {0x1, [], SA_RESTORER, 0x3c69e33340}, NULL, 8) = 0
open("/var/cache/crash-catcher/ccpp-1235652671-4054/package", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 5
write(5, "coreutils-7.0-7.fc11"..., 20) = 20
close(5) = 0
open("/var/cache/crash-catcher/ccpp-1235652671-4054/decsription", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 5
write(5, "A set of basic GNU tools commonly"..., 183) = 183
close(5) = 0
stat("/var/cache/crash-catcher/ccpp-1235652671-4054/application", 0x7fff41857830) = -1 ENOENT (No such file or directory)
stat("/var/cache/crash-catcher/ccpp-1235652671-4054/language", {st_mode=S_IFREG|0644, st_size=4, ...}) = 0
open("/var/cache/crash-catcher/ccpp-1235652671-4054/language", O_RDONLY) = 5
read(5, "CCpp"..., 8191) = 4
read(5, ""..., 8191) = 0
close(5) = 0
stat("/var/cache/crash-catcher/ccpp-1235652671-4054", {st_mode=S_IFDIR|0655, st_size=4096, ...}) = 0
open("/var/cache/crash-catcher/ccpp-1235652671-4054.lock", O_RDONLY) = 5
read(5, "4049"..., 8191) = 4
read(5, ""..., 8191) = 0
close(5) = 0
open("/var/cache/crash-catcher/ccpp-1235652671-4054/binary_data1", O_RDONLY) = 5
lseek(5, 0, SEEK_END) = 356352
lseek(5, 0, SEEK_CUR) = 356352
read(5, ""..., 356352) = 0
close(5) = 0
open("/var/cache/crash-catcher/ccpp-1235652671-4054/executable", O_RDONLY) = 5
read(5, "/bin/sleep"..., 8191) = 10
read(5, ""..., 8191) = 0
close(5) = 0
open("/var/cache/crash-catcher/ccpp-1235652671-4054/time", O_RDONLY) = 5
read(5, "1235652671"..., 8191) = 10
read(5, ""..., 8191) = 0
close(5) = 0
open("/var/cache/crash-catcher/ccpp-1235652671-4054/uid", O_RDONLY) = 5
read(5, "500"..., 8191) = 3
read(5, ""..., 8191) = 0
close(5) = 0
open("/var/cache/crash-catcher", O_RDWR) = -1 EISDIR (Is a directory)
open("/var/cache/crash-catcher", O_RDWR|O_CREAT, 0644) = -1 EISDIR (Is a directory)
futex(0x3c75c19b70, FUTEX_WAKE_PRIVATE, 2147483647) = 0
write(2, "SQLite3::Create(): Could not crea"..., 73SQLite3::Create(): Could not create database.unable to open database file) = 73
write(2, "\n"..., 1
) = 1
exit_group(0) = ?
Process 4049 detached
`--------------------------------------------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

SELinux is preventing mailx (sendmail_t) "read" to ./binary_data1 (var_t).

Opened '20090226T12:48:56' by koca as https://fedorahosted.org/abrt/ticket/10

hi,[[BR]]
while attempting to send the report following SELinux preventing appeared[[BR]]
'''Detailed Description'''[[BR]]
SELinux denied access requested by mailx. It is not expected that this access is required by mailx and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. [[BR]]
'''Allowing Access'''[[BR]]
Sometimes labeling problems can cause SELinux denials. You could try to restore the default system file context for ./binary_data1, restorecon -v './binary_data1'

CCMainWindow.py:153:on_analyze_complete_cb:AttributeError: MainWindow instance has no attribute 'timer'

Opened '20090316T16:57:12' by mnowak as https://fedorahosted.org/abrt/ticket/50

Some python-exception-helper saved for me this report on cc-gui (sic!) crash:

{{{
Component: cc-gui
Version: 0.0.1
Summary: TB11e879e5 CCMainWindow.py:153:on_analyze_complete_cb:AttributeError: MainWindow instance has no attribute 'timer'

Traceback (most recent call last):
File "/usr/share/abrt/CCMainWindow.py", line 153, in on_analyze_complete_cb
gobject.source_remove(self.timer)
AttributeError: MainWindow instance has no attribute 'timer'

Local variables in innermost frame:
report: dbus.Dictionary({dbus.String(u'Comment'): dbus.String(u''), dbus.String(u'Kernel'): dbus.String(u'2.6.29-0.215.rc7.fc11.x86_64'), dbus.String(u'Executable'): dbus.String(u'/usr/bin/rhythmbox'), dbus.String(u'UUID'): dbus.String(u'14489436461647512495'), dbus.String(u'Package'): dbus.String(u'rhythmbox-0.11.6-30.r6184.fc11'), dbus.String(u'MWID'): dbus.String(u'CCpp;500;/usr/bin/rhythmbox_59596800'), dbus.String(u'BinaryData2'): dbus.String(u''), dbus.String(u'BinaryData1'): dbus.String(u'/var/cache/abrt/ccpp-1237222127-31993/binary_data1'), dbus.String(u'CmdLine'): dbus.String(u'rhythmbox'), dbus.String(u'TextData2'): dbus.String(u''), dbus.String(u'Architecture'): dbus.String(u'x86_64'), dbus.String(u'TextData1'): dbus.String(u"[New Thread 31998]\nCore was generated by `rhythmbox'.\nProgram terminated with signal 11, Segmentation fault.\n#0 _rb_source_search_create_simple_query (search=0x1779a60, db=0x17d6050, search_text=0x0, search_prop=RHYTHMDB_PROP_ARTIST_FOLDED) at rb-source-search.c:114\n114\t\tif (search_text[0] == '\0')\n#0 _rb_source_search_create_simple_query (search=0x1779a60, db=0x17d6050, search_text=0x0, search_prop=RHYTHMDB_PROP_ARTIST_FOLDED) at rb-source-search.c:114\n#1 0x00000000004568de in impl_search (asource=, search=0x1779a60, cur_text=0x0, new_text=0x0) at rb-browser-source.c:668\n#2 0x00000000004311f5 in rb_source_state_sync (header=, set_text=, text=0x0, set_search=1, action=0x19c1b10, set_disclosure=, disclosed=0)\n at rb-source-header.c:751\n#3 0x000000000043278f in search_action_changed_cb (action=, current=0x19c1b10, header=0x1911040) at rb-source-header.c:774\n#4 0x0000000000a768ee in IA__g_closure_invoke (closure=0x1704f90, return_value=0x0, n_param_values=2, param_values=0x1916260, invocation_hint=0x7fff8ab99bb0) at gclosure.c:767\n#5 0x0000000000a8cf18 in signal_emit_unlocked_R (node=0x1704f30, detail=, instance=, emission_return=, instance_and_params=)\n at gsignal.c:3244\n#6 0x0000000000a8e2fe in IA__g_signal_emit_valist (instance=0x154ecb0, signal_id=, detail=0, var_args=0x7fff8ab99da0) at gsignal.c:2977\n#7 0x0000000000a8e893 in IA__g_signal_emit (instance=0x1779a60, signal_id=24993872, detail=0) at gsignal.c:3034\n#8 0x00000036fc188148 in gtk_radio_action_activate (action=) at gtkradioaction.c:361\n#9 0x0000000000a768ee in IA__g_closure_invoke (closure=0x16f65a0, return_value=0x0, n_param_values=1, param_values=0x7f516e0e0180, invocation_hint=0x7fff8ab99ff0) at gclosure.c:767\n#10 0x0000000000a8c715 in signal_emit_unlocked_R (node=0x173b0a0, detail=, instance=, emission_return=, instance_and_params=)\n at gsignal.c:3174\n#11 0x0000000000a8e2fe in IA__g_signal_emit_valist (instance=0x19c1b10, signal_id=, detail=0, var_args=0x7fff8ab9a1e0) at gsignal.c:2977\n#12 0x0000000000a8e893 in IA__g_signal_emit (instance=0x1779a60, signal_id=24993872, detail=0) at gsignal.c:3034\n#13 0x00000036fc06ec83 in _gtk_action_emit_activate (action=0x19c1b10) at gtkaction.c:727\n#14 0x00000036fc223d19 in button_clicked (widget=, button=0x1a4e6c0) at gtktoolbutton.c:705\n#15 0x0000000000a768ee in IA__g_closure_invoke (closure=0x1a93b40, return_value=0x0, n_param_values=1, param_values=0x7f516e0deb00, invocation_hint=0x7fff8ab9a430) at gclosure.c:767\n#16 0x0000000000a8cf18 in signal_emit_unlocked_R (node=0x16fc2c0, detail=, instance=, emission_return=, instance_and_params=)\n at gsignal.c:3244\n#17 0x0000000000a8e2fe in IA__g_signal_emit_valist (instance=0x1a4fea0, signal_id=, detail=0, var_args=0x7fff8ab9a620) at gsignal.c:2977\n#18 0x0000000000a8e893 in IA__g_signal_emit (instance=0x1779a60, signal_id=24993872, detail=0) at gsignal.c:3034\n#19 0x00000036fc21894d in gtk_toggle_button_released (button=0x1779a60) at gtktogglebutton.c:485\n#20 0x0000000000a768ee in IA__g_closure_invoke (closure=0x16fc0f0, return_value=0x0, n_param_values=1, param_values=0x7f516e0e0200, invocation_hint=0x7fff8ab9a850) at gclosure.c:767\n#21 0x0000000000a8c715 in signal_emit_unlocked_R (node=0x16fc1f0, detail=, instance=, emission_return=, instance_and_params=)\n at gsignal.c:3174\n#22 0x0000000000a8e2fe in IA__g_signal_emit_valist (instance=0x1a4fea0, signal_id=, detail=0, var_args=0x7fff8ab9aa40) at gsignal.c:2977\n#23 0x0000000000a8e893 in IA__g_signal_emit (instance=0x1779a60, signal_id=24993872, detail=0) at gsignal.c:3034\n#24 0x00000036fc0894d7 in gtk_button_button_release (widget=, event=) at gtkbutton.c:1594\n#25 0x00000036fc14b713 in _gtk_marshal_BOOLEAN__BOXED (closure=0x16eed40, return_value=0x7fff8ab9ad00, n_param_values=, param_values=0x7f516e0df750, invocation_hint=, \n marshal_data=0x36fc0894a0) at gtkmarshalers.c:84\n#26 0x0000000000a768ee in IA__g_closure_invoke (closure=0x16eed40, return_value=0x7fff8ab9ad00, n_param_values=2, param_values=0x7f516e0df750, invocation_hint=0x7fff8ab9acc0) at gclosure.c:767\n#27 0x0000000000a8cbd0 in signal_emit_unlocked_R (node=0x16eedb0, detail=, instance=, emission_return=, instance_and_params=)\n at gsignal.c:3282\n#28 0x0000000000a8e1be in IA__g_signal_emit_valist (instance=0x1a4fea0, signal_id=, detail=0, var_args=0x7fff8ab9aeb0) at gsignal.c:2987\n#29 0x0000000000a8e893 in IA__g_signal_emit (instance=0x1779a60, signal_id=24993872, detail=0) at gsignal.c:3034\n#30 0x00000036fc26b9bf in gtk_widget_event_internal (widget=0x1a4fea0, event=0x7f517170ab40) at gtkwidget.c:4761\n#31 0x00000036fc142875 in IA__gtk_propagate_event (widget=0x1a4fea0, event=0x7f517170ab40) at gtkmain.c:2396\n#32 0x00000036fc1439cb in IA__gtk_main_do_event (event=0x7f517170ab40) at gtkmain.c:1601\n#33 0x00000036fb85322c in gdk_event_dispatch (source=, callback=, user_data=) at gdkevents-x11.c:2364\n#34 0x00000000035ae11e in g_main_dispatch (context=) at gmain.c:1814\n#35 IA__g_main_context_dispatch (context=) at gmain.c:2367\n#36 0x00000000035b1878 in g_main_context_iterate (context=0x16c7f10, block=, dispatch=, self=) at gmain.c:2448\n#37 0x00000000035b1d15 in IA__g_main_loop_run (loop=0x179f6f0) at gmain.c:2656\n#38 0x00000036fc143f47 in IA__gtk_main () at gtkmain.c:1205\n#39 0x0000000000420fc8 in main (argc=, argv=) at main.c:336\n"), dbus.String(u'Release'): dbus.String(u'Fedora release 10.92 (Rawhide)\n')}, signature=dbus.Signature('ss'))
daemon: <DBusManager object at 0x16a8be0 (GObject at 0x14b0ee0)>
pBarWindow: <gtk.Window object at 0x16b9320 (GtkWindow at 0x1712830)>
self: <main.MainWindow instance at 0x16ad050>
}}}

abrt-applet output:
{{{
/usr/share/abrt/CCReporterDialog.py:95: GtkWarning: gtk_text_buffer_get_insert: assertion GTK_IS_TEXT_BUFFER (buffer)' failed result = self.window.run() /usr/share/abrt/CCReporterDialog.py:95: GtkWarning: gtk_text_buffer_get_iter_at_mark: assertionGTK_IS_TEXT_MARK (mark)' failed
result = self.window.run()
/usr/share/abrt/exception.py:252: DeprecationWarning: the md5 module is deprecated; use hashlib instead
import md5
}}}

I was just reviewing report from crashed Rhythmbox and this just crashed without an obviour reason. I also wander why is there version 0.0.1 (and name cc-gui) becasuse I have for sure abrt-0.0.2 and no such cc-* things installed...

abrt-gui crashes on attempt to edit the "How to reproduce"

Opened '20090305T14:41:22' by mnowak as https://fedorahosted.org/abrt/ticket/39

{{{
/usr/share/abrt/CCReporterDialog.py:95: GtkWarning: gtk_text_buffer_get_insert: assertion GTK_IS_TEXT_BUFFER (buffer)' failed result = self.window.run() /usr/share/abrt/CCReporterDialog.py:95: GtkWarning: gtk_text_buffer_get_iter_at_mark: assertionGTK_IS_TEXT_MARK (mark)' failed
result = self.window.run()
Segmentation fault (core dumped)
}}}

crash-catcher applet crash

Opened '20090226T15:57:12' by kvolny as https://fedorahosted.org/abrt/ticket/24

the console log

[kvolny@rawhide ~]$ cc-applet
/usr/share/crash-catcher/CCMainWindow.py:30: GtkWarning: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead
self.wTree = gtk.glade.XML(self.gladefile)
/usr/share/crash-catcher/CCReporterDialog.py:17: GtkWarning: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead
self.wTree = gtk.glade.XML(self.gladefile)
/usr/share/crash-catcher/CCMainWindow.py:30: GtkWarning: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead
self.wTree = gtk.glade.XML(self.gladefile)
Error while reading shared library symbols:
Cannot enable thread event reporting for Thread 0x7fecc63e87b0 (LWP 2725): generic error

[PATCH] Starting abrt daemon without D-Bus reload SIGSEGVs/aborts the daemon

Opened '20090315T14:43:41' by mnowak as https://fedorahosted.org/abrt/ticket/49

F-10, i386

Install abrt from Git, no restart, run ``abrt'':

{{{
root ~ # gdb abrt
GNU gdb Fedora (6.8-29.fc10)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...
(gdb) run
Starting program: /usr/sbin/abrt
[Thread debugging using libthread_db enabled]
[New Thread 0xb7fe2720 (LWP 26590)]
Detaching after fork from child process 26599.
Detaching after fork from child process 26600.
Detaching after fork from child process 26601.
Detaching after fork from child process 26602.
Detaching after fork from child process 26603.
Detaching after fork from child process 26604.
Plugin Mailx (0.0.1) succesfully loaded.
Plugin KerneloopsReporter (0.0.1) succesfully loaded.
Plugin Logger (0.0.1) succesfully loaded.
Plugin SQLite3 (0.0.1) succesfully loaded.
Plugin CCpp (0.0.1) succesfully loaded.
Plugin Kerneloops (0.0.1) succesfully loaded.
Registred plugin CCpp(Language)
Registred plugin Kerneloops(Application)
Registred plugin KerneloopsReporter(Reporter)
Registred plugin Mailx(Reporter)
Registred plugin SQLite3(Database)
terminate called after throwing an instance of 'DBus::Error'
what(): Connection ":1.864" is not allowed to own the service "com.redhat.abrt" due to security policies in the configuration file

Program received signal SIGABRT, Aborted.
0x0032e416 in __kernel_vsyscall ()
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-3.fc10.i386 compat-db45-4.5.20-5.fc10.i386 cyrus-sasl-lib-2.1.22-19.fc10.i386 dbus-c++-0.5.0-0.5.20090203git13281b3.fc10.i386 dbus-libs-1.2.4-2.fc10.i386 e2fsprogs-libs-1.41.4-4.fc10.i386 elfutils-libelf-0.140-1.fc10.i386 file-libs-4.26-4.fc10.i386 glib2-2.18.4-2.fc10.i386 glibc-2.9-3.i686 keyutils-libs-1.2-3.fc9.i386 krb5-libs-1.6.3-16.fc10.i386 libcap-2.10-2.fc10.i386 libcurl-7.19.4-2.fc10.i386 libgcc-4.3.2-7.i386 libidn-0.6.14-8.i386 libselinux-2.0.78-1.fc10.i386 libssh2-0.18-7.fc9.i386 libstdc++-4.3.2-7.i386 lua-5.1.4-1.fc10.i386 nspr-4.7.3-2.fc10.i386 nss-3.12.2.0-4.fc10.i386 openldap-2.4.12-1.fc10.i386 openssl-0.9.8g-12.fc10.i686 popt-1.13-4.fc10.i386 rpm-libs-4.6.0-2.fc10.i386 sqlite-3.5.9-4.fc10.i386 zlib-1.2.3-18.fc9.i386
(gdb) bt
Display all 31628 possibilities? (y or n)
(gdb) bt
Display all 31628 possibilities? (y or n)
(gdb) bt
Display all 31628 possibilities? (y or n)
(gdb) help bt
Print backtrace of all stack frames, or innermost COUNT frames.
With a negative argument, print outermost -COUNT frames.
Use of the 'full' qualifier also prints the values of the local variables.

(gdb) bt full
#0 0x0032e416 in __kernel_vsyscall ()

No symbol table info available.
#1 0x00a13460 in raise () from /lib/libc.so.6

No symbol table info available.
#2 0x00a14e28 in abort () from /lib/libc.so.6

No symbol table info available.
#3 0x0729dc48 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6

No symbol table info available.
#4 0x0729bb35 in ?? () from /usr/lib/libstdc++.so.6

No symbol table info available.
#5 0x0729bb72 in std::terminate () from /usr/lib/libstdc++.so.6

No symbol table info available.
#6 0x0729bcaa in __cxa_throw () from /usr/lib/libstdc++.so.6

No symbol table info available.
#7 0x00cec9e9 in DBus::Connection::request_name () from /usr/lib/libdbus-c++-1.so.0

No symbol table info available.
#8 0x0804d7c6 in CCrashWatcher (this=0x805ca20, pPath=@0xbffff790, connection=@0xbffff77c) at CrashWatcher.cpp:105

No locals.
#9 0x0805510b in main (argc=1, argv=0xbffff844) at Daemon.cpp:48

conn = <incomplete type>

}}}

a lot of messages "CDebugDump::Lock(): waiting..." displayed

Opened '20090226T14:45:35' by mmalik as https://fedorahosted.org/abrt/ticket/21

When I kill a program (kill -SIGSEGV ...) a lot messages "CDebugDump::Lock(): waiting..." is displayed in terminal where I restarted the crash catcher daemon (/etc/init.d/crash-catcher restart).

Fully updated Fedora 10 with:

crash-catcher-plugin-sqlite3-0.0.1-6.fc10.i386
crash-catcher-gui-0.0.1-6.fc10.i386
crash-catcher-plugin-logger-0.0.1-6.fc10.i386
crash-catcher-applet-0.0.1-6.fc10.i386
crash-catcher-0.0.1-6.fc10.i386
crash-catcher-addon-ccpp-0.0.1-6.fc10.i386
crash-catcher-plugin-mailx-0.0.1-6.fc10.i386

dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.

Opened '20090226T11:36:10' by mnowak as https://fedorahosted.org/abrt/ticket/3

Have scenario from Ticket #2. Open the CCMainWindow.py -> Forward -> (hang for few secs) -> BT

self.wTree = gtk.glade.XML(self.gladefile)
Traceback (most recent call last):
File "/usr/share/crash-catcher/CCMainWindow.py", line 129, in on_bNext_clicked
report = self.ccdaemon.getReport(dump.getUUID())
File "/usr/share/crash-catcher/CCDBusBackend.py", line 52, in getReport
return self.cc.CreateReport(UUID)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in call
**keywords)
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

can't delete crash report

Opened '20090226T13:11:21' by mhlavink as https://fedorahosted.org/abrt/ticket/14

Can't delete crash in list with crash reports, clicking "Delete" does nothing

warning: Can't read pathname for load map: Input/output error.
Quitting: You can't do that without a process to debug.
CMiddleWare::CreateReport() e1
CMiddleWare::CreateReport() e2
CMiddleWare::CreateReport() e3
ksh-20081104-1.fc11
CMiddleWare::Report() s
/var/cache/crash-catcher/ccpp-1235653240-2951/binary_data1: Permission denied
CMiddleWare::Report() e

Incorrect %requires on sub-packages?

Opened '20090224T17:50:36' by jlaska as https://fedorahosted.org/abrt/ticket/1

= Summary =

Attempting to install the packages built in koji at http://koji.fedoraproject.org/koji/taskinfo?taskID=1140338 results in ...

= Download packages =

Wget each of the rpm files from http://koji.fedoraproject.org/koji/taskinfo?taskID=1140338. For example
{{{

ls Desktop/crash-catcher-*.rpm

Desktop/crash-catcher-0.0.1-1.fc11.i586.rpm Desktop/crash-catcher-applet-0.0.1-1.fc11.i586.rpm Desktop/crash-catcher-plugin-mailx-0.0.1-1.fc11.i586.rpm
Desktop/crash-catcher-addon-ccpp-0.0.1-1.fc11.i586.rpm Desktop/crash-catcher-plugin-logger-0.0.1-1.fc11.i586.rpm Desktop/crash-catcher-plugin-sqlite3-0.0.1-1.fc11.i586.rpm

}}}

= Attempt installation =

{{{

yum localinstall Desktop/crash-catcher*.rpm

Loaded plugins: dellsysidplugin2, refresh-packagekit
Setting up Local Package Process
Examining Desktop/crash-catcher-0.0.1-1.fc11.i586.rpm: crash-catcher-0.0.1-1.fc11.i586
Marking Desktop/crash-catcher-0.0.1-1.fc11.i586.rpm to be installed
Examining Desktop/crash-catcher-addon-ccpp-0.0.1-1.fc11.i586.rpm: crash-catcher-addon-ccpp-0.0.1-1.fc11.i586
Marking Desktop/crash-catcher-addon-ccpp-0.0.1-1.fc11.i586.rpm to be installed
Examining Desktop/crash-catcher-applet-0.0.1-1.fc11.i586.rpm: crash-catcher-applet-0.0.1-1.fc11.i586
Marking Desktop/crash-catcher-applet-0.0.1-1.fc11.i586.rpm to be installed
Examining Desktop/crash-catcher-plugin-logger-0.0.1-1.fc11.i586.rpm: crash-catcher-plugin-logger-0.0.1-1.fc11.i586
Marking Desktop/crash-catcher-plugin-logger-0.0.1-1.fc11.i586.rpm to be installed
Examining Desktop/crash-catcher-plugin-mailx-0.0.1-1.fc11.i586.rpm: crash-catcher-plugin-mailx-0.0.1-1.fc11.i586
Marking Desktop/crash-catcher-plugin-mailx-0.0.1-1.fc11.i586.rpm to be installed
Examining Desktop/crash-catcher-plugin-sqlite3-0.0.1-1.fc11.i586.rpm: crash-catcher-plugin-sqlite3-0.0.1-1.fc11.i586
Marking Desktop/crash-catcher-plugin-sqlite3-0.0.1-1.fc11.i586.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package crash-catcher.i586 0:0.0.1-1.fc11 set to be updated
--> Processing Dependency: libdbus-c++-1.so.0 for package: crash-catcher
---> Package crash-catcher-addon-ccpp.i586 0:0.0.1-1.fc11 set to be updated
--> Processing Dependency: crashcatcher = 0.0.1-1.fc11 for package: crash-catcher-addon-ccpp
---> Package crash-catcher-applet.i586 0:0.0.1-1.fc11 set to be updated
--> Processing Dependency: crashcatcher = 0.0.1-1.fc11 for package: crash-catcher-applet
---> Package crash-catcher-plugin-logger.i586 0:0.0.1-1.fc11 set to be updated
--> Processing Dependency: crashcatcher = 0.0.1-1.fc11 for package: crash-catcher-plugin-logger
---> Package crash-catcher-plugin-mailx.i586 0:0.0.1-1.fc11 set to be updated
--> Processing Dependency: crashcatcher = 0.0.1-1.fc11 for package: crash-catcher-plugin-mailx
---> Package crash-catcher-plugin-sqlite3.i586 0:0.0.1-1.fc11 set to be updated
--> Processing Dependency: crashcatcher = 0.0.1-1.fc11 for package: crash-catcher-plugin-sqlite3
--> Running transaction check
---> Package crash-catcher-addon-ccpp.i586 0:0.0.1-1.fc11 set to be updated
--> Processing Dependency: crashcatcher = 0.0.1-1.fc11 for package: crash-catcher-addon-ccpp
---> Package crash-catcher-applet.i586 0:0.0.1-1.fc11 set to be updated
--> Processing Dependency: crashcatcher = 0.0.1-1.fc11 for package: crash-catcher-applet
---> Package crash-catcher-plugin-logger.i586 0:0.0.1-1.fc11 set to be updated
--> Processing Dependency: crashcatcher = 0.0.1-1.fc11 for package: crash-catcher-plugin-logger
---> Package crash-catcher-plugin-mailx.i586 0:0.0.1-1.fc11 set to be updated
--> Processing Dependency: crashcatcher = 0.0.1-1.fc11 for package: crash-catcher-plugin-mailx
---> Package crash-catcher-plugin-sqlite3.i586 0:0.0.1-1.fc11 set to be updated
--> Processing Dependency: crashcatcher = 0.0.1-1.fc11 for package: crash-catcher-plugin-sqlite3
---> Package dbus-c++.i586 0:0.5.0-0.7.20090203git13281b3.fc11 set to be updated
--> Finished Dependency Resolution
crash-catcher-plugin-mailx-0.0.1-1.fc11.i586 from Desktop/crash-catcher-plugin-mailx-0.0.1-1.fc11.i586.rpm has depsolving problems
--> Missing Dependency: crashcatcher = 0.0.1-1.fc11 is needed by package crash-catcher-plugin-mailx-0.0.1-1.fc11.i586 (Desktop/crash-catcher-plugin-mailx-0.0.1-1.fc11.i586.rpm)
crash-catcher-plugin-logger-0.0.1-1.fc11.i586 from Desktop/crash-catcher-plugin-logger-0.0.1-1.fc11.i586.rpm has depsolving problems
--> Missing Dependency: crashcatcher = 0.0.1-1.fc11 is needed by package crash-catcher-plugin-logger-0.0.1-1.fc11.i586 (Desktop/crash-catcher-plugin-logger-0.0.1-1.fc11.i586.rpm)
crash-catcher-addon-ccpp-0.0.1-1.fc11.i586 from Desktop/crash-catcher-addon-ccpp-0.0.1-1.fc11.i586.rpm has depsolving problems
--> Missing Dependency: crashcatcher = 0.0.1-1.fc11 is needed by package crash-catcher-addon-ccpp-0.0.1-1.fc11.i586 (Desktop/crash-catcher-addon-ccpp-0.0.1-1.fc11.i586.rpm)
crash-catcher-plugin-sqlite3-0.0.1-1.fc11.i586 from Desktop/crash-catcher-plugin-sqlite3-0.0.1-1.fc11.i586.rpm has depsolving problems
--> Missing Dependency: crashcatcher = 0.0.1-1.fc11 is needed by package crash-catcher-plugin-sqlite3-0.0.1-1.fc11.i586 (Desktop/crash-catcher-plugin-sqlite3-0.0.1-1.fc11.i586.rpm)
crash-catcher-applet-0.0.1-1.fc11.i586 from Desktop/crash-catcher-applet-0.0.1-1.fc11.i586.rpm has depsolving problems
--> Missing Dependency: crashcatcher = 0.0.1-1.fc11 is needed by package crash-catcher-applet-0.0.1-1.fc11.i586 (Desktop/crash-catcher-applet-0.0.1-1.fc11.i586.rpm)
Error: Missing Dependency: crashcatcher = 0.0.1-1.fc11 is needed by package crash-catcher-addon-ccpp-0.0.1-1.fc11.i586 (Desktop/crash-catcher-addon-ccpp-0.0.1-1.fc11.i586.rpm)
Error: Missing Dependency: crashcatcher = 0.0.1-1.fc11 is needed by package crash-catcher-plugin-sqlite3-0.0.1-1.fc11.i586 (Desktop/crash-catcher-plugin-sqlite3-0.0.1-1.fc11.i586.rpm)
Error: Missing Dependency: crashcatcher = 0.0.1-1.fc11 is needed by package crash-catcher-plugin-logger-0.0.1-1.fc11.i586 (Desktop/crash-catcher-plugin-logger-0.0.1-1.fc11.i586.rpm)
Error: Missing Dependency: crashcatcher = 0.0.1-1.fc11 is needed by package crash-catcher-applet-0.0.1-1.fc11.i586 (Desktop/crash-catcher-applet-0.0.1-1.fc11.i586.rpm)
Error: Missing Dependency: crashcatcher = 0.0.1-1.fc11 is needed by package crash-catcher-plugin-mailx-0.0.1-1.fc11.i586 (Desktop/crash-catcher-plugin-mailx-0.0.1-1.fc11.i586.rpm)
}}}

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.